John Torjo wrote:

I would like however for all binaries for a specific library to be built in the same dir. This way all I need to remember is the directory where the library binaries are, and include that in my 'Additional library directories'.

You can use the stage rule to accomplish this. For an example, have a look at boost/libs/filesystem/build.

I do bjam -sTOOLS=vc7.1 install all of the libraries end up in ONE directory At Friday 2004-05-21 01:27, you wrote:

Hi all,

Looking at how bjam makes its great subdirs - when creating binaries for a library, I see that each libs/dlls is put in its own sub-directory.

As I see, anyway, the binary name already indicates the compiler + release type + etc. And all the library linkinage is solved automatically (for instance, if I need boost_date_time-vc71-mt-gd-1_31.lib, it will automatically be added to my dependencies).

I would like however for all binaries for a specific library to be built in the same dir. This way all I need to remember is the directory where the library binaries are, and include that in my 'Additional library directories'.

I know that the current behavior (making subdirs) is much better for existing libraries, but I would like to create a new library, and build all binaries in the same dir.

Does bjam allow this? (note: I will have four binaries per compiler)

Best, John

-- John Torjo Freelancer -- john@torjo.com -- http://www.torjo.com/logview/ - viewing/filtering logs is just too easy!

_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

Victor A. Wagner Jr. http://rudbek.com The five most dangerous words in the English language: "There oughta be a law"