I'm working on a bash script to automate the build process. The script calls, depending on the parameters the Microsoft VC6 compiler and/or the GreenHills compiler and/or the Cygwin GCC for one or more project/makefiles. If I invoke the script like: c:/bat/sbuild ...... things work pretty well. However if I invoke it as cd /cygdrive/d/CCase/anv009_SPRINT_8/SPRINT_VOB/SPRINT;c:/bat/sbuild ..... it does not work as expected. The ..... symbolizes the parameters which are in both cases the same and are not relevant for the problem (I think)
In the first scenario, the prompt does not reappear till the script is completed (this may be several minutes). In the second scenario, the prompt returns much earlier but I also get compilation errors. If I check the Windows taskmanager, then the Microsoft compiler is still consuming close to 100% of the processor, but it will end in due time. Why does in the 2nd scenario the Microsoft compiler runs in the background (at least that is my idea what is happening) while the 1st scenario behaves as I expect/want? Nico Valster -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/