From: Mat Marcus (mat-lists_at_[hidden])
Date: 2008-06-26 20:24:48
On Thu, Jun 26, 2008 at 4:51 AM, Andrej van der Zee <mavdzee_at_[hidden]> wrote:
> Thanks for your reply. Sorry for my ignorance, I am
> fairly new to Windows and Cygwin ;)
> I noticed that if I use the NT-version of bjam (the
> one ending up in tools/jam/bin.ntx86 after compiling
> with build.bat), then the include paths are working
> correctly, even though they appear as Cygwin-paths in
> the output of "bjam -d2". Are they being translated to
> Windows-paths before sent to msvc?
> But uhhhh, what version of bjam (NT or Cygwin) should
> I use to compile my own projects? In my case, I use
> Cygwin because I want to be able to use Linux tools
> for development, but I want to create native Windows
> apps (i.e. I want my executables and libraries to be
> the same as if I would compile them in Visual Studio).
> Which one should I choose then,
> tools/jam/bin.ntx86/bjam compiled with build.bat (vc9)
> or tools/jam/bin.cygwinx86/bjam compiled with build.sh
We have been successful for a number of years in using the msvc-built
bjam from the cygwin shell. It is possible but more difficult to use
the cygwin-built bjam with msvc.
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk