June 2019 - Boost-users - lists.boost.org

Re: [Boost-users] [CMake] Specifying name of library file on CMake command line?
by Osman Zakir 17 Jun '19

17 Jun '19

From: Kyle Edwards <kyle.edwards(a)kitware.com> Sent: Monday, June 17, 2019 6:49 PM To: Osman Zakir; cmake(a)cmake.org Subject: Re: [CMake] Specifying name of library file on CMake command line? On Mon, 2019-06-17 at 13:47 +0000, Osman Zakir wrote: >> I want to know how to specify the name of a library I file I want to >> link against. How do I do this? I wanted to build a library with a >> static runtime and static libs; it requires linking against a Boost >> library which I did build with static runtime but when I tried to >> build it, I had linker errors because the dynamic version of the >> library was used instead of the static one. I want to somehow make >> it use the static one. So yeah, how do I do this? Is there a way? >Are you using the FindBoost module? >https://cmake.org/cmake/help/v3.14/module/FindBoost.html >Kyle Yes, I'm using that module. I didn't make any changes to it; it came with the third-party library I'm trying to build.

2 2

Boost.Units: unit type for dBm
by Carel Combrink 17 Jun '19

17 Jun '19

Hi, I have a system that uses dBm to indicate Signal Amplitude, how do I create a type using Boost.Units for this? At the moment I am not concerned about any type of conversions between power and this ratio. Any help will be appreciated. I am already using boost.unit successfully for other units and conversions with the help from the mailing list. I want to now define the correct strong type for this type for consistency. Regards, Carel

2 1

Building Boost.Python for a custom Python installation
by Evan Driscoll 14 Jun '19

14 Jun '19

I have a build of Python I made that was installed (--prefix) at ~/python-3.5.2-asan/. I want to build Boost.Python against it. I have Boost 1.70.0. I have tried a variety of permutations of passing various --with-python options and such to both bootstrap and b2 with no success. Perhaps the closest I've gotten is ./bootstrap.sh --prefix=$HOME/boost-1.70.0/ --with-python=$HOME/python-3.5.2-asan/bin/python3.5 python-debugging=on ./b2 --with-python python-debugging=on -d+2 -j8 cxxflags=-fsanitize=address cflags=-fsanitize=address but with those commands compilation fails because it is looking for include files in ...../include/python3.5/ instead of ..../include/python3.5dm While I'm at it, I had to add cflags and cxxflags explicitly instead of doing what some documentation [1] said to, because: ./b2 --with-python python-debugging=on -d+2 -j8 address-sanitizer=1 /home/evan/Downloads/boost_1_70_0/tools/build/src/build/feature.jam:327: in validate-feature from module feature error: unknown feature "<address-sanitizer>" [1] https://boostorg.github.io/build/manual/develop/index.html#_sanitizers Evan

1 0

[Process] Zombie Processes left behind
by Ryan Ruhge 05 Jun '19

05 Jun '19

Boost Team: We are trying to use boost process to have an always running process spawn child processes in a fire and forget manner (don't wait or block on the process that was just spawned). The issue we are running into is that the child processes become zombie processes when finished until the parent process completes. However in our system the parent process is never intended to complete, it is always running and listening. We have provided code snippets which give a simple example of the symptom we are experiencing. It's an infinite loop (imitating our always running process) that spawns processes that run and then become zombies instead of finishing (I included a sleep so it doesn't spawn processes too quickly). Please advise on whether there is something else we can do, if we are using child or spawn wrong, or if we are using boost process in a manner that it is not intended to be used. Thanks, Ryan Ruhge #include <boost/process.hpp> using namespace std; int main() { while (true) { boost::process::spawn("sleep 10"); sleep(5); } } #include <boost/process.hpp> using namespace std; int main() { while (true) { boost::process::child childProcess("sleep 10"); childProcess.detach(); sleep(5); } }

2 1