No, it isn't main problem itself. I faced this while trying to build dynamic library on MinGW instead of static and solved it.
tabish121 wrote: > > At the moment we have no desire to enter into "DLL Hell". > > Are you actually experiencing a problem or just don't like the static > library? > > > > On Wed, 2007-04-18 at 07:33 -0700, Motl wrote: >> Hi, >> >> 72 of 173 object files, included in libactivemq-cpp.a have unresolved >> symbols. >> It works as long as static linking is used and there are no dependencies >> to >> symbols from that files. >> On Unix systems (i.e. when using autotools as a build system) all 173 >> .cpp >> files are compiled, while when building under MSVC only 52 .cpp files are >> used (the latter files have all symbols resolved). >> >> Why don't switch to dynamic linking to avoid that problems? >> >> Thanks > > -- View this message in context: http://www.nabble.com/linking-against-activemq-cpp-tf3601214s2354.html#a10060324 Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
