Re: [Boost-build] Visual Studio always calls bjam even on built projects

Subject: Re: [Boost-build] Visual Studio always calls bjam even on built projects
From: Anatoly Shirokov (shirokov_a_at_[hidden])
Date: 2009-11-26 16:11:07

Hi!

It seems to me it is not good idea to use makefile based solution. There 
is a lot of restrictions:
- solution know nothing about project structure
- solution know nothing about project dependencies
- solution know nothing about macro definitions
- solution know nothing about search path for include and library files
- to add/remove a file you have to do it twice for solution and for jamfile

I cannot work with such solution. It is real hell. I think that there is 
only one right way, this is native solution generation from jamroot (or 
something like this) file. May be you will be interested the following 
projects which can generate native solutions:
- hammer 
(http://sourceforge.net/project/showfiles.php?group_id=261476&package_id=324118) 

- CMake
Unfortunately bjam cannot do it. Thus we switched on CMake and use it 
for both development tasks (Visual Studio Generator) and for release 
production (NMake Makefiles Generator). Developers have 100% native 
generated solution with all sources and dependencies and have comftable 
enviropment for browsing and debugging code. On build machine we use 
generated makefile for NMake to prepare night builds and releases.

BR,
Anatoly Shirokov.

Christian Auby:
> When I start debugging VS says "This project is out of date" even if I
> just built everything. Doesn't matter if I say yes or no, debug still
> works as the exe was built previously.
>
> Makefile project with build command:
> "bjam toolset=msvc --without-python -j2"
>
> Christian
> _______________________________________________
> Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build
>
>
>