On Mon, Sep 26, 2011 at 11:48 AM, Ben Hilburn wrote:
> Restarting the discussion for a small point:
>
> > 1) It separates publicly installed headers vs private headers in the lib
> > directory.
>
> I think this, honestly, is the best argument for having the separate
> directory. In terms of proj
On Mon, Sep 26, 2011 at 3:39 AM, Martin Braun wrote:
> On Wed, Sep 21, 2011 at 10:04:23AM -0400, Tom Rondeau wrote:
> > On Sat, Sep 17, 2011 at 3:14 PM, Martin Braun
> wrote:
> >
> > I'd like to point out a disadvantage to get a discussion going:
> > While you're developing, this might b
On Wed, Sep 21, 2011 at 10:04:23AM -0400, Tom Rondeau wrote:
> On Sat, Sep 17, 2011 at 3:14 PM, Martin Braun wrote:
>
> I'd like to point out a disadvantage to get a discussion going:
> While you're developing, this might be an inconvenience because the
> files are physically separate
On Sat, Sep 17, 2011 at 3:14 PM, Martin Braun wrote:
> I'd like to point out a disadvantage to get a discussion going:
> While you're developing, this might be an inconvenience because the
> files are physically separated. Most IDEs/editors have many features
> such as tagging, switching from hea
I'd like to point out a disadvantage to get a discussion going:
While you're developing, this might be an inconvenience because the
files are physically separated. Most IDEs/editors have many features
such as tagging, switching from headers to sources and vice versa, 'go
to file at cursor' commands
This is the currently recommended directory structure:
http://gnuradio.org/redmine/projects/gnuradio/wiki/Development2#Top-level-Directory-Structure
I think there has been some wavering around an "include" directory. I
personally like the idea of an include directory because:
1) It separates publ
