Re: [Boost-bugs] [Boost C++ Libraries] #8414: flyweights causes weird library initialization error

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #8414: flyweights causes weird library initialization error
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2013-04-08 14:14:03

#8414: flyweights causes weird library initialization error
-----------------------------------------------------------+----------------
  Reporter:  charles quarra <charlls_quarra@…>             |       Owner:  joaquin    
      Type:  Bugs                                          |      Status:  closed     
 Milestone:  To Be Determined                              |   Component:  flyweight  
   Version:  Boost 1.53.0                                  |    Severity:  Showstopper
Resolution:  invalid                                       |    Keywords:             
-----------------------------------------------------------+----------------

Comment (by charles quarra <charlls_quarra@…>):

 Hi joaquin,

 i don't understand what makes you believe the plugin is being link at
 build time; main.cpp is the executable doing the module, and it is being
 built with the simple command: g++ main.cpp -o xmain -ldl  as you see,
 nothing besides the libdl for dlopen and dlclose are being linked.

 the command line 'g++ -I/path/to/boost/includes -fPIC -shared -rdynamic
 test_plugin.cpp -o libpluginTest.so -L/path/to/boost/libs -lrt' it is the
 one building and linking the plugin. Since it is a single translation
 unit, the linking can be done at once. The -o libxxxx.so is not required
 but it is a cosmetic choice to avoid having to link a library called a.out

 i hope this helps

-- 
Ticket URL: <https://svn.boost.org/trac/boost/ticket/8414#comment:2>
Boost C++ Libraries <http://www.boost.org/>
Boost provides free peer-reviewed portable C++ source libraries.