Hi all,
yes, I know, there has been a thread some days ago, but I just
registered and don't know how to reply to a mail that I don't have.
Anyway, there seems to be a bug in boost 1.34.1 with VC 2005 when using
directory_iterator.
I used the filesystem before and everything worked fine.
Now (since I use the iterator), I get
1>HD2.obj : error LNK2019: Verweis auf nicht aufgelöstes externes Symbol
""unsigned int boost::filesystem::detail::not_found_error"
(?not_found_error@detail@filesystem@boost@@3IA)" in Funktion ""private:
unsigned int __thiscall
boost::filesystem::basic_directory_iterator,struct
boost::filesystem::path_traits> >::m_init(class
boost::filesystem::basic_path,struct
boost::filesystem::path_traits> const &)"
(?m_init@?$basic_directory_iterator@V?$basic_path@V?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@Upath_traits@filesystem@boost@@@filesystem@boost@@@filesystem@boost@@AAEIABV?$basic_path@V?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@Upath_traits@filesystem@boost@@@23@@Z)".
I looked into the filesystem dll with depends and found the function
there with ordinal 48 (0x30) (in both the debug and the release Version
for multithreading). Also in the lib, I found it.
Rather strange.
The signatures of the linker and the ones found in the DLL also match.
I used the installer from Boost-Consulting.
In the thread some time ago, a responder claimed, he could compile
successfully. Maybe he used a self-compiled boost version?
I am going to test that, but maybe somebody has an answer right now?
Best regards,
Rainer Thaden