This sounds like a pkg-config package. In fact, several projects moved from such custom scripts to pkg-config. Anyway, the main problem here is to make the build system (b2) output those flags in a parseable manner. If that was implemented, it could be used to make pkg-config packages, CMake config modules, etc. Another problem is that different boost libraries will require different build flags to use them, so you'll actually need e.g. boost-thread-config, boost-filesystem-config (or boost-thread.pc and boost-filesystem.pc if pkg-config is used). пн, 6 сент. 2021 г., 14:03 Sreeraj K via Boost <boost@lists.boost.org>:
*[I initialially raised this question in https://github.com/boostorg/boost/issues/548 <https://github.com/boostorg/boost/issues/548>, but @mclaw recommended this mailing list.]*
Similar to many other packages (eg: curl, krb5, pcre, xml2, xslt etc..), can we also ship boost-config that would provide the installation options ?
We can probably start with something like this ?
$ /usr/bin/boost-config --help Usage: boost-config [ options ]
Options: --cflags print compiler options --ldflags print linker options --prefix print the boost prefix --version print the boost version --help print this usage summary
$ /usr/bin/boost-config --version 1.66.0 $ /usr/bin/boost-config --cflags -I/usr/include $ /usr/bin/boost-config --ldflags -L/usr/lib64 -Wl,-R/usr/lib64
Thanks.
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost