for Bro-2.4.1 I am currently creating a package for the Gentoo
Distribution. Gentoo is a distro which compiles packages natively on the
user's computer; for that our package manager hooks into the build system.
I've created a package for the actor-framework and the its libs can be
found in /usr/lib/libcaf_{io,core}.so.0.14.4; its headers can be found
in /usr/include/caf.
Attached you can find a build.log and from there you can see that during
the configure phase, Libcaf is properly found. You can also see which
options cmake is run with.
However, while compiling broker, the file
caf/detail/abstract_uniform_type_info.hpp cannot be found. Is there some
magic involved regarding the passing on of include files to the actual
compile of broker?
Disabling broker, the whole compile works smoothly.
I've created a package for the actor-framework and the its libs can be
found in /usr/lib/libcaf_{io,core}.so.0.14.4; its headers can be found
in /usr/include/caf.
That sounds right. Would you mind sharing the CAF ebuild with us?
However, while compiling broker, the file
caf/detail/abstract_uniform_type_info.hpp cannot be found. Is there
some magic involved regarding the passing on of include files to the
actual compile of broker?
The reason why this fails is because
caf/detail/abstract_uniform_type_info.hpp has been removed with the 0.14
releases. The current Broker release 0.4 does not support CAF 0.14.
Broker 0.4 requires CAF 0.13.2. However, the master branch of Broker
supports 0.14.
We're currently in the process of porting Broker to 0.15, which Bro 2.5
will depend on. Sorry about the inconvenience.
The CAF ebuild looks good to me. The deprecation warnings arise because
of the combination of Broker 0.4 with CAF >= 0.14. If you want a stable
release, you would have to use the following combination:
Bro 2.4.1 + Broker 0.4 + CAF 0.13.2
And as mentioned in an earlier email, for the next release Bro 2.5, it
would be Broker 0.5 and CAF 0.15.
I don't have a gentoo installation handy so that I could further debug
the issue with the symlinked .sh file. Would you mind giving us a bit
more insight in to that error?