[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Discuss-gnuradio] Fwd: GNURadio/Module builds and std=C++11
From: |
Michael Dickens |
Subject: |
Re: [Discuss-gnuradio] Fwd: GNURadio/Module builds and std=C++11 |
Date: |
Tue, 20 Jun 2017 14:12:11 -0400 |
If the OOT requires C++11, then the setting you mention is the best way to go. If the OOT does not require C++11 or later, then not setting this variable is the way to go.
Clang will auto-detect pretty reliably, but that makes for sloppy programming. I'd guess GCC6 or 7 does the same by now. It's much safer to specify the C++ standard if such a setting is required, at least in my opinion.
So, your quick fix / workaround if probably actually the better way to go. - MLD
On Tue, Jun 20, 2017, at 02:06 PM, GhostOp14 wrote:
I ran into it earlier today with the gr-osmosdr module and libfreesrp that produced errors, but I had run into it in some of the modules I had developed that are up in pybombs (gr-clenabled, gr-lfast, and gr-grnet) when I first moved to Ubuntu from a straight debian install. As soon as I realized it was happening I fixed it in the makefiles with the "set (CMAKE_CXX_STANDARD 11)" workaround so others didn't run into it. I did it as a "quick fix" thinking others may have a better way on Ubuntu and maybe I was missing something. If I hadn't moved to Ubuntu I may never have realized it was an issue on some platforms, so I don't know if there's other OS versions it could be happening on with gcc versions prior to 6?
I think that's the long way of asking if there's a better way?