The sdk is a collection of source files and libs. We include those libs and source when we statically compile our dll, and then we add the compiled dll to the application's plugin directory to add it to the app. -----Original Message----- From: boost-users-bounces@lists.boost.org [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Igor R Sent: Tuesday, September 20, 2011 4:23 PM To: boost-users@lists.boost.org Subject: Re: [Boost-users] Multiple versions of boost at once/IPC Alternative
I am working on an application where we have a plugin written to an application, and then a second app that communicates with the plugin using boost::ipc. For this we are using boost 1.46.
The 2012 release of the application we are plugging into has released their SDK and included boost 1.35 as part of the SDK (so they can hook into boost python.)
Is there any way for us to continue using boost 1.46 for our plugin even though it is compiling in an sdk which includes boost 1.35?
What do you mean by saying that your plugin "is compiling in an sdk"? Is this SDK a collection of source files, static libs, DLLs?