Tiny Core Extensions > TCE 3.x

boost

(1/3) > >>

Jason W:
Thanks to robc for:


--- Code: ---Title:          boost-dev.tcz
Description:    Peer-reviewed portable C++ source libraries Development Files (TESTING)
Version:        1.43.0
Author:         Various (http://www.boost.org/users/people.html)
Original-site:  http://www.boost.org/
Copying-policy: Boost Software License v1.0 (http://www.boost.org/LICENSE_1_0.txt)
Size: 10.7M
Extension_by:   robc
Comments:


----------------------------------------------

Please see the man page for additional
information.

Also see http://www.boost.org/
for more information.

----------------------------------------------

Change-log:     2009/08/05 Original
2009/10/28 Updated to v1.40.0
2010/01/22 Updated to v1.41.0
2010/06/04 Updated to v1.43.0
Current: 2010/06/04 Updated to v1.43.0


--- End code ---


--- Code: ---Title:          boost.tcz
Description:    Peer-reviewed portable C++ source libraries (TESTING)
Version:        1.43.0
Author:         Various (http://www.boost.org/users/people.html)
Original-site:  http://www.boost.org/
Copying-policy: Boost Software License v1.0 (http://www.boost.org/LICENSE_1_0.txt)
Size: 2.7M
Extension_by:   robc
Comments:


----------------------------------------------

Please see the man page for additional
information.

Also see http://www.boost.org/
for more information.

----------------------------------------------

Change-log:     2009/08/05 Original
2009/10/28 Updated to v1.40.0
2010/01/22 Updated to v1.41.0
2010/06/04 Updated to v1.43.0
Current: 2010/06/04 Updated to v1.43.0


--- End code ---

curaga:
Please enable static libs (preferably without the dynamic ones) on the next update.

Boost declares an ABI break on every update, forcing all depending extensions to a rebuild. Unwanted behavior, IMO.
Linking boost and only it statically removes this.

Arslan S.:
no need to static link, i suggest putting version numbers to boost and not deleting old ones except their dev packages (*.so symlinks must be deleted from lib extensions)

for example
boost-1.41 (without lib*.so)
boost-1.42 (without lib*.so)
boost-1.43 (with lib*.so)
boost-dev --> which is actually boost-1.43-dev

thus all new extensions will be linked to latest boost while old ones won't be broken with each boost update

similar approach can be applied to other such extensions like icu

extension maintainers can easily handle this case

Jason W:
I think it would be good to enable and allow static linking in this case.  If I was building against boost, I would static link to avoid the potential version pitfalls.

But either way we should give a version number to the boost package.  If the -dev package is not version numbered, it would be good to state in the info file that it one would need to update it upon each update of the main boost extension.

curaga:
Jason, do you have the 1.41 version still somewhere?

Navigation

[0] Message Index

[#] Next page