Re: Is there a strategy for multiplatform builds and distributions?
From: Arjen Markus (arjen.markus_at_wldelft.nl)
Date: 01/28/04
- Next message: Jugoslav Dujic: "Re: Is there a strategy for multiplatform builds and distributions?"
- Previous message: Arjen Markus: "Re: Fortran and C++ portability (was Re: Help from fellow Fortran Users)"
- In reply to: Daniel Grimwood: "Re: Is there a strategy for multiplatform builds and distributions?"
- Next in thread: Jugoslav Dujic: "Re: Is there a strategy for multiplatform builds and distributions?"
- Reply: Jugoslav Dujic: "Re: Is there a strategy for multiplatform builds and distributions?"
- Reply: Daniel Grimwood: "Re: Is there a strategy for multiplatform builds and distributions?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Wed, 28 Jan 2004 10:06:35 +0100
Daniel Grimwood wrote:
>
>
> > The build processes work, but they are a nuisance to set up.
> > So, my question is:
>
> > Does anyone know of general/practical guidelines
> > to deal with these issues?
>
> Hi Arjen,
>
> I'm not 100% sure of what you're asking, but here goes.... We have a
> configure script that works out some string associated with the system,
> such as "INTEL-ifc-on-LINUX", "LAHEY-lf95-on-WINDOWS" etc. It then
> substitutes this name into the makefile as both the name of a file that
> contains compiler flags etc specific to that system, and as the name of a
> top level directory in the build tree into which goes all the compiled
> files. Thus we get directories created named INTEL-ifc-on-LINUX/modules,
> INTEL-ifc-on-LINUX/objects, INTEL-ifc-on-LINUX/dependencies, etc. To swap
> between platforms, I just rerun the configure script on the new platform
> and don't do a "make clean" or anything like that. If the compiler wants
> to leave the .mod file in the current directory, we just manually move it
> with a script. Is that what you're talking about?
>
Okay, so you have automated the process of getting all the files in
place.
It is a bit difficult to clearly formulate the question, as it is partly
a matter of different platforms/compilers/build tools and partly a
matter of user perception/culture/attitude ... I realise now.
If I may summarise the answers sofar:
- Make as uniform a file system as possible (include for anything used
at compile-time, lib for anything used at link-time)
- Hide the platform issues inside the build tools (makefiles and
auxiliary scripts)
One issue that I should have raised in my original question is:
How to deal with MS Developer Studio? It has its merits, but it
is far less flexible than any "make" utility.
Well, I thank you all for taking the trouble to answer a troublesome
question. You have given me some thoughts on how to deal with the
problem ... now to fit it in with the daily work ;)
Regards,
Arjen
- Next message: Jugoslav Dujic: "Re: Is there a strategy for multiplatform builds and distributions?"
- Previous message: Arjen Markus: "Re: Fortran and C++ portability (was Re: Help from fellow Fortran Users)"
- In reply to: Daniel Grimwood: "Re: Is there a strategy for multiplatform builds and distributions?"
- Next in thread: Jugoslav Dujic: "Re: Is there a strategy for multiplatform builds and distributions?"
- Reply: Jugoslav Dujic: "Re: Is there a strategy for multiplatform builds and distributions?"
- Reply: Daniel Grimwood: "Re: Is there a strategy for multiplatform builds and distributions?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|