Hi Danushka, Ok, I still have the issues... Lots of messages like these:
1>Plugin.cpp 1>C:\Program Files (x86)\boost\boost_1_35_0\boost/program_options/errors.hpp(21) : warning C4275: non dll-interface class 'std::logic_error' used as base for dll-interface class 'boost::program_options::error' 1> C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\include\stdexcept(21) : see declaration of 'std::logic_error' 1> C:\Program Files (x86)\boost\boost_1_35_0\boost/program_options/errors.hpp(21) : see declaration of 'boost::program_options::error' 1>C:\Program Files (x86)\boost\boost_1_35_0\boost/program_options/errors.hpp(61) : warning C4251: 'boost::program_options::ambiguous_option::alternatives' : class 'std::vector<_Ty>' needs to have dll-interface to be used by clients of class 'boost::program_options::ambiguous_option' 1> with 1> [ 1> _Ty=std::string 1> ] 1>C:\Program Files (x86)\boost\boost_1_35_0\boost/program_options/options_description.hpp (120) : warning C4251: 'boost::program_options::option_description::m_value_semantic' : class 'boost::shared_ptr<T>' needs to have dll-interface to be used by clients of class 'boost::program_options::option_description' 1> with 1> [ 1> T=const boost::program_options::value_semantic 1> ] I only show a sample... There are hundreds of them. Your original patch disabled the warnings. I'm not completely comfortable disabling the warnings without really understanding the issues (I'm not sure I do) and checking all of the diagnostics to be sure they are not issues (which I'm not going to do). I think I understand the issues the compiler is warning against, but I don't have 100% confidence. What rationale did you use for disabling the warnings? For the benefit of the rest of dev... I'm going to take out the thing that triggers these warnings, so it has no affect at this time on M5. Thanks, -Steve > -----Original Message----- > From: Steve Huston [mailto:[email protected]] > I had a lot of problems with BOOST_ALL_DYN_LINK initially, so > I removed it. Now that more issues are resolved, I'll try > adding it back in. > > FWIW, I ran the examples and such and didn't see any of the > crashes that Shan did. > > -Steve > > -- > Steve Huston, Riverace Corporation > Check out my networked programming blog at > http://stevehuston.wordpress.com/ > > > > -----Original Message----- > > From: Danushka Menikkumbura [mailto:[email protected]] > > Sent: Friday, March 06, 2009 7:16 AM > > To: [email protected] > > Subject: Re: Experiences with qpid-1673 branch? > > > > > > > > > The other day you mentioned you may be able to point some test > > > resources at the qpid-1673 branch (which adds Windows DLLs to the > > > build). Have you had an opportunity to do that? > > > > > > Anyone else given this a try? I'd like to merge this to trunk > > > shortly... > > > > > Hi Steve, > > > > I am failing to build the DLL's. This is due to libraries > > trying to link > > with non-win32 boost libs. I managed to get them to link > with correct > > boost libs using the BOOST_ALL_DYN_LINK preprocessor > > definition and see > > this is missing in all the projects under 1673 branch. > > > > Danushka > > > > -- > > Danushka Menikkumbura > > Technical Lead, WSO2 Inc. > > > > blog : http://danushka-menikkumbura.blogspot.com/ > > > > http://wso2.com/ - "The Open Source SOA Company" > > > > > > > > > --------------------------------------------------------------------- > > Apache Qpid - AMQP Messaging Implementation > > Project: http://qpid.apache.org > > Use/Interact: mailto:[email protected] > > > --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
