Well, there is boost-libs to, which are compiled by default in dists like gentoo (and distributed in other I guess). Takes a really long time to compile them.
I'll look at your m4-macro and the one at http://autoconf-archive.cryp.to Yeah, running gcc with -ansi or -std=c99 (combinded with -pedantic for masochists ;)) is nice... Yeah, the gcc4 is a great catch up but still lacks features like Inline Procedual Optimization (IPO, sometimes called IPA). FWIW: My commits are now sent to the commit-list... //Markus Rob Savoye wrote: > Markus Gothe wrote: >> Exactly my thoughts! I think configure should #define HAVE_BOOST_LIB or >> something like that... I'll see if there is m4-macros for this already >> or write some kind of routine. > > I just wrote a configure macro for boost. My simple question is do you > prefer BOOST_CFLAGS value to match. Since I gather Boost is a collection > of related headers, I can keep adding code to look for the modules we > need. My current test just find the right directory to set the include > path. > >>>> For the boost part I discovered that the needed functions in boost can >>>> easily be extracted by using CC -E. The whole smart prt code (including >>>> shared pointers) is only ~26kb totally, so I don't see a reason not to > > Since Boost is just header files, why would we even need to extract > anything ? I'll admit I know little about Boost other than it's highly > recommended. > > - rob - > > > > _______________________________________________ > Gnash-dev mailing list > [email protected] > http://lists.gnu.org/mailman/listinfo/gnash-dev
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Gnash-dev mailing list [email protected] http://lists.gnu.org/mailman/listinfo/gnash-dev
