Warning linking boost lib in WDK build (“LNK4217: locally defined symbol _ imported in function _”)?

You are explicitly including ..\boost_1_40_0\stage\lib\libboost_program_options-vc100-mt. Lib in the link.

You are explicitly including ..\boost_1_40_0\stage\lib\libboost_program_options-vc100-mt. Lib in the link. You should let the boost auto_link stuff configure do the correct #pragma comment(lib, ...) stuff ensure you bring in the right library and set the linker search path correctly.

The most likely thing is that the boost library and your code are linking against different runtime libraries.

Your answer helped me past this first build issue - thanks - but now the linker complains about not being able to find libboost_program_options-vc90-mt-s-1_40. Lib, whereas I have only -vc100- files - strange, since I built boost from the exact same (Visual C 9.0) terminal window right before trying to build my app. Any ideas?

Is bootstrap/bjam configuring itself to use a different VC? Any way to determine this and/or control it? – Yang Oct 17 '09 at 21:26 That explains why the runtime libraries are different and why you saw the error.

Yes, the boost build system will examine your registry and see which compilers you have installed. If you want to build boost with msvc 9, invoke bjam with "toolset=msvc-9.0". The resultant libraries should have vc90 in their names.

You can also check the boost-build documentation. If you want this to be reproducible without a command line option you can add something like: "using msvc : 9.0 ;" to user-config.jam. – janm Oct 19 '09 at 23:25.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.