Re: [Cppcms-users] feedback after testing cppcms svn trunk compiled with msvc2005

[Artyom <art...@ya...>]

> Then this means that cppcms must be compiled  with the same version of
> boost as the application.
> Doesn't this imply usage  of an external
> boost (the one that is shared with the application)? And you  just said
> that using an external boost is not going to be supported anymore.

No this means that CppCMS should not be compiled against Boost. Period.

I'm quite surprised it worked for you at all because it shouldn't.

Also I compile in some boost code so (iostreams) so you may get something
very wrong as internal code may use different version.

I think I'll remove this "EXTERNAL_BOOST" at all.


> I'm
> thinking of using the external boost feature only to compile  cppcms
> and the application with the same version of boost (not the  opposite
> that you are trying to avoid).

CppCMS 1.x.x is going to handle stable ABI.

So if you once compiled and application against version
1.0.0 then you can easily ugrade the dll for example to
1.8.3 and it should work out of the box same as for
Qt4 or GTK2

Boost does not support this, more then that it breaks
ABI every 3 month...

> Using an internal version of boost  is
> what really opens the door for an application to use a  different
> version of boost then the one cppcms uses.

Yes exactly.

> By the way which is  the
> minimum version of boost which can be used to compile  cppcms?
>

I use internally 1.39 and slowly use it less and less in 
favor of booster - boost like library with some adopted/taken/redesigned
boost API for ABI stability.

Artyom