On Mon, Aug 17, 2015 at 6:27 AM, David Halls <[email protected]> wrote: > > > There are no quick/easy workarounds for such issues other than: > > 1. Making sure that all components involved make use of the same Boost > library versions, or > > 2. Making sure that the components which require Boost statically link > against the Boost version which they prefer, or > > 3. Separating the different components which require Boost into separate > applications. > > In further detail: > > Option 1: It looks like you are making use of GNU Radio from Python, I do > believe that GNU Radio depends on Boost. You may be able to (re)compile GNU > Radio to make it use Boost 1.49 and where you even specifically link it to > the Boost libraries shipped with the MCR (these can be found in the > bin/glnxa64 directory). > > Option 2: If GNU Radio specifically requires a different Boost version you > may be able to recompile it and statically link it against this version. > > Option 3: Instead of compiling your MATLAB Code into a Shared Library, > compile it into a standalone application which you can launch from your > Python process. This separate standalone should be able to use its own > Boost libraries without problems then. There are Python libraries which can > read and write MAT-files so you can relatively efficiently pass in- and > outputs from and to that standalone application through MAT-files." >
This sounds like good advice. Option 2 sounds the most sane.
_______________________________________________ Discuss-gnuradio mailing list [email protected] https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
