discuss-gnuradio
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Discuss-gnuradio] External modules include path / namespace


From: Johnathan Corgan
Subject: Re: [Discuss-gnuradio] External modules include path / namespace
Date: Sun, 2 Jun 2013 10:30:20 -0400

On Jun 2, 2013, at 9:58, "Martin Braun (CEL)" <address@hidden> wrote:

> On Sun, Jun 02, 2013 at 12:18:49AM +0200, Sylvain Munaut wrote:
>> include: $prefix/include/module_name/
>> namespace: gr::module_name::
>> python: $prefix/lib/site-package/module_name/
>>
>> Since the module are placed in the gr:: namespace, wouldn't it make
>> sense to have :
>>
>> include: $prefix/include/gnuradio/module_name/
>> namespace: gr::module_name::
>> python: $prefix/lib/site-package/gnuradio/module_name/
>>
>> This would also make external modules that much closer to internal
>> ones and further reduce the difference between in-tree / out-of-tree
>
> Just pointing out that oot-modules have always been a bit different,
> e.g. import MODULE vs. from gnuradio import MODULE. Also, I don't mind
> having a dedicated folder for core gnuradio stuff.
> I agree making the folder structures for in- and out-tree modules more
> similar is good, though. So, just some thoughts here, perhaps we'll talk
> about this this week.

The main reason OOT modules are 'import foo' and not 'from gnuradio
import foo' is that OOT modules typically install into
$PREFIX=/usr/local, and if GNU Radio is installed into $PREFIX=/usr,
the import would not work.

Johnathan



reply via email to

[Prev in Thread] Current Thread [Next in Thread]