This is a meta-port for boost libraries, depends on all of them.
Boost provides free peer-reviewed portable C++ source libraries.
The emphasis is on libraries that work well with the C++ Standard
Library. Boost libraries are intended to be widely useful, and usable
across a broad spectrum of applications. The Boost license encourages
both commercial and non-commercial use.
The goal is to establish "existing practice" and provide reference
implementations so that Boost libraries are suitable for eventual
standardization. Ten Boost libraries are already included in the C++
Standards Committee's Library Technical Report (TR1) and will be in
the new C++0x Standard now being finalized. C++0x will also include
several more Boost libraries in addition to those from TR1. More Boost
libraries are proposed for TR2.
===> The following configuration options are available for boost-all-1.92.0:
DOCS=on: Build and/or install documentation
JAM=on: Boost.Jam - Build tool from the boost.org
LIBRARIES=on: Free portable C++ libraries
MPI=off: Boost.MPI + Python bindings
PYTHON=off: Boost.Python - interfacing Python and C++
===> Use 'make config' to modify these settings
devel/boost*: update to 1.92.0 release (+)
Include corresponding update for boost_build to 5.5.2
Introduce new library, Cobalt, which forces C++20 standart (option OFF by
default)
Release notes: https://www.boost.org/releases/1.92.0/
all: drop support for FreeBSD 13, mips and risc64sf
Reviewed by: many (*)
Differential Revision: https://reviews.freebsd.org/D55624
Differential Revision: https://reviews.freebsd.org/D55642 (merged in from bofh)
many (*)
acm arrowd brooks cmt dch decke dinoex eduardo fluffy fuz gahr garga
jbeich joerg jrm kai kenrap martymac matthew mfechner michaelo mizhka
nobutaka pkubaj se tagattie thj
Anton Saietskii
GenericRikka
Gert Doering
Jan Bramkamp
Oleh Hushchenkov
Oleksandr Kryvulia
Ralf van der Enden
Yamagi
desktop kde python tcltk office
devel/boost: update to 1.89.0 release (+)
Major change:
Boost::system component which converted to header-only since 1.70.0,
stops providing an empty stub library libboost_system.so for compatibe reasons
and goes as pure header-only since 1.89.0.
All consumers must be adjusted.
Release notes: https://www.boost.org/releases/1.89.0/
devel/boost: improve port (+)
1. Convert ZSTD support to option, default on.
2. Support for additional image formats in the Generic Image Library (adds raw,
PNG, TIFF, and JPEG formats). Added as an option, default off.
3. Resolve the problem preventing our *at() functions (like statat() and
openat()) from being detected, it'a Linux-only feature.
4. do-test target provided -- it is of limited utility, because it takes
multiple days and reports a lot of seemingly false problems.
5. Only extract the docs subdirectory, when building boost-docs -- saves some
diskspace during builds. Likewise, when building jam (b2) don't extract other
code.
6. Plist sort, .CURDIR usage optimization.
7. Backport a proper fix for broken function program_location_impl in Boost.DLL
PR: 286403, 287204 (based on), 287514 (fix previous version)
devel/boost: update to 1.88.0 release (+)
This release include two new libraries, Hash2, and MQTT5
Allow to use Boost.iostream with ZSTD compression [requested in 1]
Release Notes: https://www.boost.org/releases/1.88.0/
PR: 286403 [1]
all: drop support for expired FreeBSD 14.0
Simplify expressions for FreeBSD 13.X
Reviewed by: many
Differential Revision: https://reviews.freebsd.org/D46601
devel/boost-{all,libs}: Adjust range of OSVERSION to use LLVM from ports
The reason to use LLVM from ports is that there is bug in Clang/LLVM
of base system that causes assertion failure while building
devel/boost-libs. The bug is already fixed with main, stable/14 and
stable/13 branches of src repository. So we need to use LLVM from
ports only with following ranges of OSVERSION.
1. 1500000 <= OSVERSION < 1500017
2. 1400000 <= OSVERSION < 1400509
3. 1300000 <= OSVERSION < 1303502
And commit 3b8c51bd37b0 adjusts the range as above.
But there is a pitfall about it. The assertion failure happens only if
(Only the first 15 lines of the commit message are shown above )
devel/boost-all: Use clang from base for OSVERSION >= 1500017
In https://cgit.freebsd.org/src/commit/?id=bcd401b5a39c I committed a
fix for clang's assertion failures when building recent boost libraries.
I also bumped __FreeBSD_version to 1500017 so this can be detected from
devel/boost-all/compiled.mk.
The fix was also merged to stable/14, with __FreeBSD_version 1400509,
and stable/13, with __FreeBSD_version 1303502.
Adjust the ranges to use the default llvm port to [1500000..1500017>,
[1400000..1400509>, and [1300000..1303502>.
PR: 277850
Approved by: fluffy (maintainer)
MFH: 2024Q1
devel/boost-all: Adjust range to use llvm from ports
When boost was updated to 1.81.0, the problem was reported as PR
269067 that build of devel/boost-libs fails because of assertion
failure of Clang in base system. According to the comment submitted to
upstream issue tracker (*), the source of the problem is very long
standing bug of LLVM/Clang. So the bug itself is included in all of
supported branch of src repository. But the problem only happens with
main because assertion is only enabled with it. To work it around
compiled.mk was modified so llvm from ports is used instead of that of
base system when __FreeBSD_version is 1400000 or later. This is what
was done with commit 3efdfab9b59f.
And recently stable/14 branch is created in src repository. After it
is created __FreeBSD_version of the branch is bumped from 1400096 to
1400097. And the value of main is bumped from 1400096 to 1500000. So
adjust range to use llvm from ports as following.
Case 1: 1400000 <= OSVERSION < 1400097 (main before stable/14 is branched)
Case 2: OSVERSION >= 1500000 (main after stable/14 is branched)
Reference: https://github.com/llvm/llvm-project/issues/39319#issuecomment-1444452238
(*)
PR: 273335
Approved by: sunpoet (office@, maintainer)
MFH: 2023Q3
Remove WWW entries moved into port Makefiles
Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.
This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.
Approved by: portmgr (tcberner)
Add WWW entries to port Makefiles
It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.
Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.
There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.
(Only the first 15 lines of the commit message are shown above )
devel: remove 'Created by' lines
A big Thank You to the original contributors of these ports:
* "Waitman Gobble" <uzimac@da3m0n8t3r.com>
* <jkoshy@FreeBSD.org>
* Aaron Dalton <aaron@FreeBSD.org>
* Aaron Dalton <aaron@daltons.ca>
* Aaron H. K. Diep <ahkdiep@gmail.com>
* Aaron Hurt <ahurt@anbcs.com>
* Abel Chow <abel_chow@yahoo.com>
* Adam McLaurin
* Adam Saponara <as@php.net>
* Adam Weinberger <adamw@FreeBSD.org>
* Ade Lovett <ade@FreeBSD.org>
(Only the first 15 lines of the commit message are shown above )
Followup on r483807.
jbeich commented on some ports in D17724 but I forgot to add them to the list.
Submitted by: rene
Reviewed by: bapt, jbeich
Differential Revision: https://reviews.freebsd.org/D17724
devel/boost-all: drop obsolete CONFLICTS
devel/boost|devel/boost-libs|2009-07-28|Boost ports were split and sliced
devel/boost-python|devel/boost-python-libs|2009-07-28|Boost ports were split and
sliced
devel/boost-python-libs got forgotten in the python flavorization, fix
this oversight.
Reviewed by: antoine
Sponsored by: Absolight
Differential Revision: https://reviews.freebsd.org/D14368
devel/boost-all: remove CPE information
- Since CPE should not be applied to meta ports, I am reverting the commit with
CPE info
PR: 197711
Approved by: bapt
- Fix build when using WITH_CCACHE_BUILD.
ccache's documentation says to set CCACHE_SLOPPINESS=time_macros and
CFLAGS+= -fpch-preprocess (it's a magic check in ccache for the string),
but doing these does not actually fix the build when files are cached.
Disabling PCH for ccache still results in an 18 second build, down from 143,
on a 12 core machine.
- While here, strip libraries with STRIP_CMD (not bumping rev as this is
not significant enough to warrant a rebuild).
Update to boost 1.55.0
switch back to normal library naming
Add a compat symlink for .so.5
Use compiler.mk to detect compiler
Use a modern compiler (doesn't work with base gcc)
- Allow WITH_CCACHE_BUILD to work with boost.
This speeds up building from 35 minutes to 5 minutes.
If you are building boost with ccache by changing CC="ccache cc",
change to using WITH_CCACHE_BUILD=yes in make.conf. This will
automatically handle installing and using ccache for port building,
while avoiding build breakages.
Reported by: Samu Nuutamo
Discussed with: bapt (who marked it unsafe)
PKGORIGIN being defined earlier, CATAGORIES needs to be defined prior any *.mk
include meaning common.mk has to be included earlier [1]
While here switch to new options helpers
Reported by: erwin
Respect the locally set CXXFLAGS (and CFLAGS) -- except for optimization
level (-O*), which Boost sets to -O3 automatically.
Approved by: maintainer (bapt)
When BOOST_TOOLSET is "gcc", the actual compiler can be anything from g++ to
g++48.
Make sure, the ${CXX} specified is used by the port, rather than the default
g++.
Tested with: g++48
Approved by: bapt
- update to 1.52.0
- pass maintainership to office@
- detect if compiler is gcc or clang and correctly set the toolset for bjam
- enable long-double support
- some cleanup
Approved by: maintainer timeout (3 weeks with no reply)
- Update boost to 1.39
- Split boost port to separate components, with boost-all metaport
PR: ports/137054
Submitted by: Alexander Churanov <churanov.port.maintainer@gmail.com>
(maintainer)
