Language:
switch to room list switch to menu My folders
Go to page: First ... 35 36 37 38 [39]
[#] Tue May 07 2019 14:01:33 EDT from fleeb @ Uncensored

[Reply] [ReplyQuoted] [Headers] [Print]


Another cool trick I'm about to try involves recompiling glibc for the linux kernel you want to support, with the compiler you want to use.

This gets into an area of weird when you need to support a 10 year old kernel on the current compiler.

If this works, I would be able to cross-compile our product on a modern linux for old linuxes. Which means I can finally keep up-to-date on Jenkins, since the current Jenkins distributables require a java run time so modern, it doesn't work on 10 year old machines.

[#] Thu Jun 06 2019 12:08:54 EDT from fleeb @ Uncensored

[Reply] [ReplyQuoted] [Headers] [Print]


CMake tantalizingly fails to work very well when you need to cross-compile.

I have a collection of files that I cannot know until after building all the executables. So, I need a post-build, pre-install/pre-packaging step that allows me to specify this collection of files so I can get them into the debian/RPM files.

CMake, though, isn't built to accomodate something like this... which, honestly, is kind of a basic requirement for a fair number of use cases. So, yeah.
Bravo, CMake. You fucking suck, yet you're the most popular system out there for this kind of thing.

*sigh*

[#] Fri Jun 21 2019 14:11:50 EDT from LoanShark @ Uncensored

[Reply] [ReplyQuoted] [Headers] [Print]


Anything's better than automake.

[#] Fri Jun 21 2019 14:50:35 EDT from IGnatius T Foobar @ Uncensored

[Reply] [ReplyQuoted] [Headers] [Print]

GNU Autotools is Considered Harmful. I know this won't work for everyone, but the mainstream target systems do not differ as wildly as they did 20 years ago. I've started rolling my own (and playfully calling it "conf-IG-ure") and it seems to work better.

Cross compiling isn't on the table, though.

[#] Mon Jun 24 2019 10:37:48 EDT from fleeb @ Uncensored

[Reply] [ReplyQuoted] [Headers] [Print]


I think CMake wants you to build tons of little packages that depend on each other. Which is, frankly, silly.

I have something that sorta-kinda seems to do the job after building this monster .cmake file, but the last quirk is to somehow modify any of these files I'm generating to create/set an environment variable to the base installation.

It looks like the way to do this is to call 'configure_file()', which causes the input file to be run through something that converts the variables therein to expanded values, generating a new file at the destination.

My concern, though, is that I have no idea when 'configure_file()' gets called.
If called during cpack (when building the debian or rpm package), great... this will work. But if called during the build, when I suspect it gets called, this isn't going to work for me, since I'm pre-generating the file(s) it intends to generate.

So... I'm eyeing this source code... and wondering...

Go to page: First ... 35 36 37 38 [39]