Jason,
You can set the CXXFLAGS env variable to "-std=c++11" and any CMake
builds you run (assuming the same shell) will check the CXXFLAGS var
first. This assumes that you don't overwrite the value of
CMAKE_CXX_FLAGS. I just tried it in a terminal with `export
CXXFLAGS="-std=c++11"`, then `cmake ..`, and finally `VERBOSE=1 make -j
1`. The verbose make command will show you if your flags are taking or not.
-Dave
On Tue, Jun 5, 2018 at 8:00 AM Jason Matusiak <[email protected]>
wrote:
> I am trying to install gnuradio onto a Centos 7 box and am having more and
> more issues with packages that use c++11 commands. For some of the
> packages, I add the line:
> CMAKE_CXX_FLAGS "-std=c++11"
> to the module's CMakeLists.txt file.
>
> The issue is that that requires a fetch, the mod, and then a rebuild.
> This worked OK with it was just gqrx I was doing it for, but now I need it
> for other modules it appears, and so I am trying to find a more elegant
> solution that covers everything that is built via a pybombs install
> gnuradio command (like gr-blocks, which I can't use this trick for).
>
> If I understand the problem correctly, Ubuntu uses new enough tools to
> realize that it needs to use the c++11 version (or newer I assume) to build
> since it is needed. It seems like even though Centos 7 has the c++11
> capability, it does not smartly trying to use it, and must be directed to
> for the installs to work.
>
> Is there something I can do at an upper level to make things happy on an
> install?
> _______________________________________________
> Discuss-gnuradio mailing list
> [email protected]
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>
_______________________________________________
Discuss-gnuradio mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
