I develop software for a target, whose build tools are hosted on
MS-Windows NT 4.0.
During my development process, I also develop various auxiliary scripts
and makefiles, and I prefer to run them on a Linux system.
As a result, the process of building the software ping-pongs between the
two environments. Each environment needs its own makefile, and each of
those makefiles needs to be executed to make part of the targets needed
for the next stage for the other platform.
(The actual situation is a bit simpler than depicted above, in that it
suffices to build first on Linux, and then on MS-Windows NT, because at
present no Linux target depends upon a file built in the MS-Windows NT
environment.)
Does anyone have experience, tips, methodology about how to set up the
software build process, so that a single 'make' (or 'nmake') suffices to
trigger the entire build?
(One possible solution is to have a daemon in one platform periodically
check for the existence of a file created by the other platform, but I'd
like to use a less smelly solution.)
(VMWare? I need no stinking VMWare, I use two computers, which share
files by fast Ethernet and SAMBA; and enjoy the view of two large CRT
displays.)
--- Omer
Joel Spolsky (http://www.joelonsoftware.com/articles/fog0000000045.html)
would have said that it is a turd-drop process.
WARNING TO SPAMMERS: see at http://www.zak.co.il/spamwarning.html
=================================================================
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]
