search

bakercp / ofxIO

A collection of I/O core utils including a directory watcher, file filters and ordering, compression and more.
Other
83 stars 30 forks source link

link error,compiled issue #11

Closed liquidzym closed 10 years ago

liquidzym commented 10 years ago

with vs2013,any ideas? btw,i'm also using the latest poco develop branch,do you think that's the issue? cheers

1>DirectoryUtils.obj : error LNK2019: unresolved external symbol "public: thiscall Poco::RecursiveDirectoryIterator::RecursiveDirectoryIterator(class std::basic_string<char,struct std::char_traits,class std::allocator > const &,unsigned short)" (??0?$RecursiveDirectoryIterator@VChildrenFirstTraverse@Poco@@@Poco@@QAE@ABV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@G@Z)，referenced in function catch$?list@DirectoryUtils@IO@ofx@@SAXABV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@AAV?$vector@V?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@V?$allocator@V?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@@2@@5@_NPAVAbstractPathFilter@23@@Z$0

1>DirectoryUtils.obj : error LNK2019: unresolved external symbol "public: thiscall Poco::RecursiveDirectoryIterator::RecursiveDirectoryIterator(class std::basic_string<char,struct std::char_traits,class std::allocator > const &,unsigned short)" (??0?$RecursiveDirectoryIterator@VSiblingsFirstTraverse@Poco@@@Poco@@QAE@ABV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@G@Z)，referenced in function catch$?list@DirectoryUtils@IO@ofx@@SAXABV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@AAV?$vector@V?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@V?$allocator@V?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@@2@@5@_NPAVAbstractPathFilter@23@@Z$0

bakercp commented 10 years ago

Hey there -- if you're using the latest Poco development branch then you probably need to get rid of this directory:

https://github.com/bakercp/ofxIO/tree/master/libs

All of those classes are now in the latest Poco dev branch and probably conflict because I didn't change their namespace on my local copies.

bakercp commented 10 years ago

Hey @liquidzym I just pushed a possible fix to develop -- basically I put all of my Poco copies in the ofx namespace, so they shouldn't (theoretically) conflict with the same classes in Poco 1.5+.

That said, I only tested it on OSX/Linux/VS2012 ... so not sure about 2013.

liquidzym commented 10 years ago

@bakercp,great,thxs for the help,now its fully working with vs2013&Poco dev.

bakercp commented 10 years ago

Great. I'll merge develop into master. Thanks for the report.