2

I am seeking some ideas for how to build and install software with some parameters. These including target OS, target platform CPU details, debugging variant, etc. Some parts of the install are shared, such as documentation and many platform independent files, others are not, such as 64 and 32 bit libraries when these are separated and not together in a multi-arch library.

On big networked platforms one often has multiple computers sharing some large server space, so there is actually cause to have even Windows and Unix binaries on the same disk.

My product has already fixed an install philosophy of $INSTALL_ROOT/genericname/version/ so that multiple versions can coexist.

The question is: how to manage the layout of all the other stuff?

2
  • 1
    You may want to see how GNU programs are built. They have solved this for their needs a while back.
    – user1249
    Commented Dec 26, 2011 at 10:32
  • Considering the many many many many issues of sharing Windows and UNIX binaries I've not seen it done in practice.
    – Karlson
    Commented Jan 6, 2012 at 13:55

3 Answers 3

1

Given that when a package is installed in a system - there is only 1 system at hand. i.e. OS, CPU/Arch, 32/64 bits variables are fixed for that system target.

In this context, usually i would NOT make separate folder like

$INSTALL_ROOT/package//<64-32bit>/versions/

Rather, i would define it as part of the naming. Look at it for example the RPM file naming convention:

name-version-release.architecture.rpm

It does include the distribution version number as like like fc8 or fc11 etc.

Debian follows a similar naming convention but probably the packages have some internal directory layout. (Sorry donno details here!)

3
  • 1
    Depends on the platform. Mac OS X supports universal binaries with several targets inside a single deployment.
    – user1249
    Commented Dec 26, 2011 at 10:27
  • Unfortunately the "given" is incorrect. Almost all desktops run Intel x86_64 CPUs and both Linux and OSX support both 32 and 64 bit code. In addition as mentioned on enterprise networks there are many computers with different archs sharing a file server so we need to install multiple archs in a single file system.
    – Yttrill
    Commented Dec 26, 2011 at 15:16
  • @Yttrill ok, I didn't assume that requirement. As a general rule, whatever needs multiple instance may have a directory of it's own; everything else should go in a file naming convention. Commented Dec 26, 2011 at 15:56
1

At one time, I worked for an SAN manufacturer in the build group. We had to support about 40 different operating systems.

The distributions were organized by major OS families at the root level of the distribution media (CD and DVD), such as HPUX, Z/OS and Windows, with versions branching off those. So for example, the Windows branch would have Server and Workstation off that folder, and each would have a set of x86, x64, ia64 and Alpha folders, each with their own installs.

0

Use a build tool which allows different source and target directories. For each platform have a separate target directory into which the platform specific files are generated.

Builds may run faster if you use a common build directory for non-platform specific files.

1
  • Yes, but the question really asks "what is a platform"? I already use such a build tool. Is it enough to have completely separate targets for every variation? Eg debugging or non-debugging libraries? If so how do you name the target directories .. that's the real question.
    – Yttrill
    Commented Dec 26, 2011 at 15:18

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.