Thomas Hertweck wrote:
Hi!
Per Jessen wrote:
our production environment is AMD64, so x86_64. Our test environment is still old i386, and will likely be for a while.
We have a similar situation in our company. Most of the time, we still build 32-bit executables for the various OS we have to support (all i386 and x86_64 RHEL-based, I have to admit). We also have a 64-bit build but that's hardly ever used in production for various reasons.
We did consider just running 32bit executables, but as the production environment is highly likely to remain on AMD64, we have pretty much decided to move to 64bit. I think we'll have to upgrade the test-systems any way, but until we do, we're running in 32+64 mode.
How do you guys go about building for an i386 target on your x86_64 workstations? In plain practical terms - I know how to build 32bit objects, but how do you organise source code, builds etc? A typical project would involve one or more binaries, some of our own libraries and some external ditto.
We have dedicated build hosts for the various platforms and OS. The source code and various other files are kept in an SVN repository (which is hosted by a special server). The master Makefile simply includes a <hostname>.mk file which contains all the host-dependent (i.e. system- and OS-dependent) settings. Very simple, but very effective.
Yep, I can see how that would work. Not sure if we will want to establish separate build-systems - our code is only used internally, we don't ship it anywhere.
Our experience shows that dedicated build hosts are simpler to handle and operate than, for instance, building 32-bit and 64-bit executables on the same machine running a 64-bit OS.
Thanks, I'll bear that in mind. /Per Jessen, Zürich --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-programming+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-programming+help@opensuse.org