Linux build in Windows 4816

In a message on 18 Sep 2005 13:50:17 -0700, wrote :

Probably. But why? If the top-level of the build automation is some MS-Windows program(s), IT should be calling the cygwin bash script to do the Linux build part (and you might need several of these scripts, depending on the work flow of the build process), not the other way around. I think part of the reason you are getting the answers to your questions that you are getting is that we (the Linux people reading your questions) don't really follow what you are doing, or even why. One of the things you have to realize, as another poster has already stated, in the UNIX-Linux world the idea of distributing a task over more then one machine is common and a trivial thing, including automated tasks. The idea that the commands in a script might be run on a different machine than the one the script is running on is a common thing under Linux. It is trivial to spread a *single command pipeline* over three or more machines. For example (a somewhat far fetched one):

bar% ssh foo.domain.com tar cjvf - codebasebunzip2gzipssh baz.domain.com tar xzvf - -Cscratch

Here the directory tree under codebase (on foo.domain.com) is tar'ed up and compressed with bzip2 (tar's -j option) and piped to bunzip2 (on bar), then re-compressed with gzip (also on bar, which had better have lots of compute horsepower!), then piped to baz where it is uncompressed with gunzip (tar's -z option) and untared underscratch on baz. *Three* machines are working hard doing all of this. And this is only *one* command line. Maybe you need to provide more detail, such as what tools you want to use to 'automate' the build process and exactly what you plan on 'building' -- eg Linux RPMs-deb packages? Binary tarballs? A CD-DVD for Linux-MS-Windows? Something else?