[Signals2] Error on building project RELEASE
Hi,
I'm writing a library that use the following:
#include
On Monday 27 April 2009, Daniele Barzotti wrote:
I retrieved Signals2 from svn on 15/04/09.
When I build it like STATIC DEBUG lib all works fine, but when I switch to STATIC RELEASE I got two errors...
ATDispatcher.cpp C:\Programmi\Microsoft Visual Studio 9.0\VC\include\xutility(419) : error C2664: 'boost::signals2::detail::stack_allocator
::stack_all ocator(boost::signals2::detail::stack_storage *)' : cannot convert parameter 1 from 'boost::signals2::detail::stack_allocator ' to 'boost::signals2::detail::stack_storage *'
It seems msvc 9 in release mode with iterator checking turned on needs to be able to copy construct allocators from allocators with different template types. See for example: http://www.mail-archive.com/qpid-dev@incubator.apache.org/msg13891.html Would you try applying changeset 52627 from svn trunk and see if that fixes it? : https://svn.boost.org/trac/boost/changeset/52627/trunk
Frank Mori Hess ha scritto:
It seems msvc 9 in release mode with iterator checking turned on needs to be able to copy construct allocators from allocators with different template types. See for example:
http://www.mail-archive.com/qpid-dev@incubator.apache.org/msg13891.html
Would you try applying changeset 52627 from svn trunk and see if that fixes it? :
YEP, This change seems to work!!! Thanks a lot Frank! Cheers, Daniele
Frank Mori Hess ha scritto:
On Monday 27 April 2009, Daniele Barzotti wrote:
I retrieved Signals2 from svn on 15/04/09.
When I build it like STATIC DEBUG lib all works fine, but when I switch to STATIC RELEASE I got two errors...
It seems msvc 9 in release mode with iterator checking turned on needs to be able to copy construct allocators from allocators with different template types. See for example:
http://www.mail-archive.com/qpid-dev@incubator.apache.org/msg13891.html
Would you try applying changeset 52627 from svn trunk and see if that fixes it? :
Today I switched to boost 1_39 and while I'm very happy to see that Signals2 is been included, I've noted that this change is not... Maybe is this only a workaround for this msvc issue? Thanks, Daniele.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday 04 May 2009, Daniele Barzotti wrote:
Today I switched to boost 1_39 and while I'm very happy to see that Signals2 is been included, I've noted that this change is not...
Maybe is this only a workaround for this msvc issue?
The fix for the msvc 9 "release mode with SECURE_SCL" compile bug will be included in the next release, it just came up a bit late for the 1.39 release. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkn+8YgACgkQ5vihyNWuA4WenACghmZMtxYJniyNBeyuBpROz8bh rAoAnjUUjQ5uJFnI9FdXbnT6S/bpT8PR =DiOF -----END PGP SIGNATURE-----
participants (3)
-
Daniele Barzotti
-
Frank Mori Hess
-
Frank Mori Hess