Matt wrote:
Rene Rivera wrote:
If not is there any other way to specify that you don't want the boost version appended to the end of the filename?
Use the "--layout=system" option when building/installing.
Thanks Rene, that worked a treat.
Welcome.
I couldn't find much documentation about this feature, is there any plans to expose it? It seems like a common thing to want to do. Can I help?
Well it's a feature used by packagers so it's there to stay. Docs, yes you can help if you want to write up a short explanation of what it does we can incorporate that into the getting started docs.
Also, I found some weirdness when building libraries. Specifically, the Test library built libs for the dynamic versions altough the dll's themselves were not built. I understand that the test library doesn't have a dynamically linked version (according to the faq: http://tinyurl.com/77cjd) so why are the (dynamic) .libs being generated?
Not sure why, I'd have to investigate.
I also found that a couple of the libraries were producing seemingly duplicate libs. By that I mean that two versions of a lib were being created, one _with_ the boost version number appended and one without - the filesizes were the same and, according to the naming convenion (http://tinyurl.com/aycpa), I believe the ones without the version number should not exist. I was using the 'stage' option with the vc-7_1 toolkit and noticed this on at least the serialization and wave libraries.
Again I'd have to investigate... Are you sure that you aren't seeing left overs from previous compiles on this one?
Are these two issues known?
No.
I may have been using an old version of bjam though if that helps...
As long as it's 3.1.10 it should be OK. But using the newest version is always better as that's what we test with. -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - Grafik/jabber.org