I'm trying to use the EPEL package boost169-devel on CentOS 8. I'm trying to build my C++ source code with the boost library version 1.69 from this package.
I see that that package has header & .so files in non-standard locations, /usr/include/boost169 instead of /usr/include for headers and /usr/lib64/boost169/ instead of /usr/lib64 for .so.
I know I can hack my build files to make it work -- munge my gcc's -I to have /usr/include/boost169 in front and add a -L /usr/lib64/boost169 in the beginning. But my build files are also used to build on other distros, so I'm looking for a cleaner way that does not involve introducing a lot more complexity to my build system. E.g. for gcc-toolset-9, which also installs things in non-standard locations, one can use scl enable gcc-toolset-9 bash to have the paths setup properly without caring about the implementation details. Is there a prescribed way or cleaner way for dealing with the non-standard location of boost169-devel than manually munging -I and -L?