OK; good arguments. Hard-coding into OOT module == bad. Agreed.
Maybe something more along the lines of: When GR is installed, create a
"${prefix}/etc/gnuradio/install.cfg" file that contains what GR CMake found, in
a file that's easily loadable by CMake. Then in the gr-modtool OOT module
CMake look for this file and if found load it to get the correct values. This
way, the gr-modtool installs will all be consistent on the local OS globally
(for any user doing an OOT module) but OOT modules will not contain hard-wired
settings.
That seems better to me. Thoughts on this version? - MLD
On May 27, 2014, at 10:25 AM, Tom Rondeau <t...@trondeau.com> wrote:
> I'm with Sylvain that hard-coding that information in gr-modtool is a bad
> idea for the same reasons. If someone develops it on OS X and then wants to
> distribute that project to other people working on other systems, we need to
> re-find everything there, too. The two aren't and can't be that coupled
> together.
_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
