Re: [Boost-build] building boost in cygwin using msvc

From: Jurko Gospodnetić (jurko.gospodnetic_at_[hidden])
Date: 2008-06-27 07:48:14

   Hi Ilya.

>>>> In msvc.jam replace
>>>>
>>>> suffix = " >nul \"&&\" " ;
>>>>
>>>> with
>>>>
>>>> suffix = " \">nul\" && " ;
>>>
>>>   Should this be changed on the trunk?
>>>
>>>   What are the quotes around >nul for anyway?
>>>
>>>   I'm not a shell expert but I've tried playing around with this from 
>>> the cygwin bash shell but could not find a command in which those 
>>> quotes were needed?
>>
>>   After some more testing it seems that >nul needs to be quoted so cmd 
>> would process it and not bash.
>>
>>   I also believe that && needs to be changed to \"&\" so it would be 
>> processed by cmd.exe and not bash.
> 
> No, this is from Windows help:
> 
> \quote
> & [...] command1 & command2
> Use to separate multiple commands on one command line. Cmd.exe runs the 
> first command, and then the second command.
> 
> && [...] command1 && command2
> Use to run the command following && only if the command preceding the 
> symbol is successful. Cmd.exe runs the first command, and then runs the 
> second command only if the first command completed successfully.
> \end
> 
> Using & will cause ignoring of vsvars??.bat errors.

   Ok, thanks for the info. I did not know that.

   Could you please test whether:

                 setup-prefix = "cmd.exe /S /C call " ;
                 setup-suffix = " \">nul\" \"&&\" " ;

   works for you, as opposed to:

                 setup-prefix = "cmd.exe /S /C call " ;
                 setup-suffix = " \">nul\" && " ;

   As I see is these quotes around && are needed or otherwise && gets 
interpreted by the bash shell.

   Best regards,
     Jurko Gospodnetić