Re: [Boost-build] My troubles when compiling without link=static. (with msvc-8.0)

From: Guido Ziliotti (guido.ziliotti_at_[hidden])
Date: 2008-06-17 09:19:16

Thanks a lot Jurko, you are right. 
Your suggestion solves the problem for filesystem and that is my 
main interest.

Program options still does not work but I expected that, many of the warnings
I get when compiling the library seams to boil down to 
"forget about surviving name mangling here". Well that's my own
optimistic and naive translation of warning C4251 and C4275.
I might be wrong but theese warnings seems to state the differnce
between staic and dynamic (shared) linking inthis context.

As to minmax_timer I think it's helpless and it does not work period.

So far so good but then I recalled somtehing buried deep down in my 
boost memory if we copy filesystrem example elsewhere and
raplece Jamfile.v2 with Jamroot 
--Jamroot content--
path-constant BOOST_INSTALLED_LIB : C:/Boost/lib ; 
path-constant BOOST_INSTALLED_INC : C:/Boost/include/boost-1_35 ; project 
 : requirements <include>$(BOOST_INSTALLED_INC)
 <linkflags>/LIBPATH:$(BOOST_INSTALLED_LIB) 
 ;
 
exe file_size : file_size.cpp ;
exe simple_ls : simple_ls.cpp ;    
--en of Jamroot content---

then 
bjam file-size link=static -a

bjam file_size link=shared -a
bjam file_size define=BOOST_ALL_DYN_LINK -a

all work and (-a is there to be shure we are rebuilding)

line1 => file_size.exe is 96KB 
line2 => file_size.exe is 96KB (still!)
line3 => file_size.exe is 48KB (finally i.e. the same as modifing boost/Jamroot file).

So here evrything works fine since we are building aginst the installed version of boost.

Notice there is a config.hpp in include/filesystem which is missing in BOOST_ROOT corresponding
folder and we are not using the original bjam project file.

The gap between this 2 ways should be much more stressed. I would like to have 
other options too and the chance to switch between them on th bjam cmdline.

Sometimes it might be much more helpful to exploit the project Jamfile directly.
I'd be glad to go that way at least.

Any opinion is welcome.

On Tue Jun 17 12:39 AM  , Jurko Gospodneti <jurko.gospodnetic_at_[hidden]> sent:undefinedundefinedundefinedundefinedundefinedHi Guido.

> My building platform : using msvc : 8.0 ;
> 
> I have attached som attempt in compiling some boost examples. 
> Notice I have set C:\Boost\lib in my LIB environment variable (set 
> LIB=%LIB%;c:\Boost\lib )
> 
> Onestly I am a bit pessimistic. Still I hope I am missing something 
> obvious.

I have just tried this and it seems the build for those examples is 
buggy. Fails on both MSVC 7.1 and 9.0.

It seems that for some reason the main Boost Jamroot file says that 
all Boost libraries should be built without automatic linking (specified 
by adding BOOST_ALL_NO_LIB=1 to the main boost library 
requirements). If you remove that line then your examples compile & link 
correctly, assuming you have built the needed libraries and have them on 
your library search path.

Volodya: Is there something Boost Build could do to help with this? 
File-system library target already has a dependency listed on the system 
library and its examples have a dependency on the file-system library. 
Why would that not be enough to make its examples explicitly link to the 
system library? I am asking you because I'm kinda swamped in real-life 
work at the moment and your name is listed in the file-system examples 
build file.

Best regards,
Jurko Gospodneti

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

-------
Sent from Orgoo.com - Your communications cockpit!