Boost.Filesystem with MSVC8 & STLPort linker errors

Hi,
I have an application using Boost.Filesystem, Boost.Thread and others, that
I am building on Windows XP using MSVC8, STLPort and Boost 1.39.0. I have
built Boost using Boost Jam 3.1.17 and STLPort. Using the MSVC native STL I
get no errors and everything runs well, but with the STL version, I have
four linker errors; all from Boost.Filesystem.
Has anyone come across this problem before and found a solution, or give me
a clue what might be wrong?
Many thanks
-- Craig
1>fsdatasource.obj : error LNK2019: unresolved external symbol "class
boost::filesystem::file_status __cdecl
boost::filesystem::detail::status_api(class
stlpd_std::basic_string

Craig Henderson wrote:
Hi,
I have an application using Boost.Filesystem, Boost.Thread and others, that I am building on Windows XP using MSVC8, STLPort and Boost 1.39.0. I have built Boost using Boost Jam 3.1.17 and STLPort.
How exactly? What commands did you type, and what configuration files are you using? Did you use stdlib=stlport ?
Using the MSVC native STL I get no errors and everything runs well, but with the STL version, I have four linker errors; all from Boost.Filesystem.
Has anyone come across this problem before and found a solution, or give me a clue what might be wrong?
Many thanks -- Craig
1>fsdatasource.obj : error LNK2019: unresolved external symbol "class boost::filesystem::file_status __cdecl boost::filesystem::detail::status_api(class stlpd_std::basic_string
const &,class boost::system::error_code &)" (?status_api@detail@filesystem@boost@@YA?AVfile_status@23@ABV?$basic_string@ DV?$char_traits@D@stlpd_std@@V?$allocator@D@2@@stlpd_std@@AAVerror_code@syst em@3@@Z) referenced in function
The general procedure for debugging unresolved symbols can be found at: http://vladimir_prus.blogspot.com/2009/06/linking-101.html My guess in this case is that Boost was not actually built with STLPort, which you can probably check by looking at the symbol table of the library with whatever tool is suitable (dumbpin?) - Volodya
participants (2)
-
Craig Henderson
-
Vladimir Prus