Re: [Somelib] Makefile update - linux build now broken

[John P. <jo...@ma...>]

Fixed the build by defining BOOST_NO_TEMPLATE_PARTIAL_SPECIALIZATION for
linux builds.  This has to be added for all compilers that do not support
this functionality and should be documented in the FAQ for supporting of
new platforms.  I'm going to move from just platform builds to
platform_compiler builds since you can compile with different compilers on
different systems.  Oh, Microsoft C++ has command line tools that can be
configured with ./configure and used in the makefiles.  I'll install
VC++ in the future and work on making the Makefiles platform
independent (all info needed to compile is gathered with ./configure).

-Quinticent

John Palmieri wrote:

> I update the buldsystem to use recursive makes since I was trying to
> compile on a BSD and it didn't like some of the newer make symbols I was
> using. I also updated the install script in the main Makefile to install
> to <prefix>/include/SOMELib and <prefix>/lib/SOMELib.
>
> I couldn't test out the new build system since the current build is
> broken.  I get errors with some of the template functions in the boost
> headers:
>
> in file included from BasicDynLib.h:24,
>                  from BasicDynLib.cpp:22:
> ../boost_includes/boost_smart_ptr.hpp:353: parse error before `::'
> ../boost_includes/boost_smart_ptr.hpp:357: parse error before `::'
> ../boost_includes/boost_smart_ptr.hpp:358: redefinition of `template
> <class T> void swap(...)'
> ../boost_includes/boost_smart_ptr.hpp:354: `template <class T> void
> swap(...)' previously declared here
> ../boost_includes/boost_smart_ptr.hpp:358: redefinition of `void
> swap(...)'
> ../boost_includes/boost_smart_ptr.hpp:354: `void swap(...)' previously
> defined here
> ../boost_includes/boost_smart_ptr.hpp:367: parse error before `::'
> ../boost_includes/boost_smart_ptr.hpp:376: parse error before `::'
>
> As for getting ithe build working on HP I say we first concentrate on
> documentation for Windows and Linux and get out the beta.  We can then
> go and identify the platform dependent portions of SOMELib and write up
> specifications for adding new platforms to the build. ie.  What source
> files do I have to change for dynamic loading features? How do I add the
> new platform to configure.in for automatic configuration of my
> build? How do I edit the Makefiles? What documentaiton do I have to
> write up so that others will know how to use the lib on my platform?
> etc.
>
> -Quinticent
>
> _______________________________________________
> somelib-devel mailing list
> som...@li...
> http://lists.sourceforge.net/mailman/listinfo/somelib-devel