xeusC++ implementation of the Jupyter kernel protocol
5.0.0_1develΣ=0 5.0.0_1Version of this port present on the latest quarterly branch.upstream: 6.0.2A newer version was found upstream by portscout, first on 2026-06-20.
xeus is a library meant to facilitate the implementation of kernels for Jupyter.
It takes the burden of implementing the Jupyter Kernel protocol so developers
can focus on implementing the interpreter part of the kernel.
An example of kernel built with xeus is xeus-cling, a kernel for the C++
programming language based on the cling C++ interpreter.
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/xeus: Unbreak on systems incompatible with the system where the package
was built
-march=native caused SEGVs on incompatible systems
The cmake option that turned it off was renamed. I also added the NATIVE option
that now drives the -march flag.
MFH: 2020Q2
devel/xeus: don't optimize for the host CPU
It causes a build error on powerpc64:
g++9: error: unrecognized command line option '-march=native'; did you mean
'-mcpu=native'?
And may cause runtime issues even when it builds.
PR: 242582
Approved by: yuri (maintainer)
Update security/cryptopp to 8.2.0
Remove THREADS option - upstream recommends building with threads and the
build system now adds the appropriate flags automatically
Bump PORTREVISION on consumers due to shared lib version increase
PR: 241132
Submitted by: Farid Hajji <farid@hajji.name>
Remove the -mtune=generic/-march=native fiddling on all archs, not just
GCC-based ones.
This will unbreak the build on aarch64.
Approved by: portmgr (tier-2 blanket)
Bump PORTREVISION for ports depending on the canonical version of GCC
as defined in Mk/bsd.default-versions.mk which has moved from GCC 8.3
to GCC 9.1 under most circumstances now after revision 507371.
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, everything INDEX-11 shows with a dependency on lang/gcc9 now.
PR: 238330
For GCC-based systems, edit top-level CMakeLists.txt to eliminate
either of the following two problems:
g++8: error: unrecognized command line option '-march=native'
g++8: error: unrecognized argument in option '-mtune=generic'
Approved by: portmgr (tier-2 blanket)
net/openpgm: Do not add -I to non-existing directory in openpgm-5.2.pc
foo/lib/pgm-5.2/include does not exist, so applications using strict
compiler flags will fail to build due to this.
Here this breaks devel/xeus build after r491260 [1]:
CMake Error in CMakeLists.txt:
Imported target "cppzmq" includes non-existent path
"/usr/local/lib/pgm-5.2/include"
in its INTERFACE_INCLUDE_DIRECTORIES. Possible reasons include:
* The path was deleted, renamed, or moved to another location.
(Only the first 15 lines of the commit message are shown above )
Mark BROKEN: fails to configure
CMake Error in CMakeLists.txt:
Imported target "cppzmq" includes non-existent path
"/usr/local/lib/pgm-5.2/include"
Reported by: pkg-fallout
Change cmake default behaviour to outsource.
Ports that build out of source now simply can use "USES=cmake"
instead of "USES=cmake:outsource". Ports that fail to build
out of source now need to specify "USES=cmake:insource".
I tried to only set insource where explictely needed.
PR: 232038
Exp-run by: antoine
Bump PORTREVISION for ports depending on the canonical version of GCC
defined via Mk/bsd.default-versions.mk which has moved from GCC 7.4 t
GCC 8.2 under most circumstances.
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, as a double check, everything INDEX-11 showed depending on lang/gcc7.
PR: 231590
Update security/cryptopp to 7.0.0
We now install a pkgconfig file which will allow ports to check whether
cryptopp was built with assembly instructions enabled or not. There are
a few functions that will be undefined if built without assembly and
-DCRYPTOPP_DISABLE_ASM needs to be passed to the compiler in that case
to avoid build failures. This is not new, but the pkgconf file should
make it easier to determine if the flag is needed or not.
Fix several ports due to API changes and to use the new pkgconf file
to determine cryptopp location and build flags. Special cases below.
deskutils/cdcat
- Use cryptopp shared library instead of static, detect with pkgconf
(Only the first 15 lines of the commit message are shown above )