Re: [Boost-bugs] [Boost C++ Libraries] #3103: Allow using libraries without separately compiling them

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #3103: Allow using libraries without separately compiling them
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2009-06-08 16:24:19

#3103: Allow using libraries without separately compiling them
-------------------------------+--------------------------------------------
  Reporter:  eckhardt          |       Owner:                
      Type:  Feature Requests  |      Status:  new           
 Milestone:  To Be Determined  |   Component:  Building Boost
   Version:                    |    Severity:  Problem       
Resolution:                    |    Keywords:                
-------------------------------+--------------------------------------------

Comment(by Jonathan Wakely <jwakely.boost_at_[hidden]>):

 "it's up to the user to make sure that it's exactly done once"

 This seems like a supremely bad idea to me, and so does asking users to
 {{{#include "something.cpp"}}}

 What is the advantage of asking users to {{{#include}}} a file and then
 compile it, rather than just compiling it?

 Wouldn't it achieve the same goals, without being needlessly
 unconventional, to make it easier for users to compile the sources into
 their app directly?

 e.g. provide a makefile fragment with the commands necessary to turn
 src/libs/thread/src/thread.cpp into thread.o which could be linked
 directly into the application.  Or make bjam print suitable commands
 (without running them) so that users can copy the commands into their own
 build system.

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