On Thu, Oct 8, 2009 at 12:53 PM, Jochen Küpper <
kuepper.joc...@googlemail.com> wrote:
> On 08.10.2009, at 21:46, Darren Weber wrote:
>
> On Thu, Oct 8, 2009 at 12:16 PM, Ryan Schmidt
>> wrote:
>> On Oct 8, 2009, at 13:37, Darren Weber wrote:
>>
>> In cursory exploration of /opt/local/include/,
On Oct 8, 2009, at 14:46, Darren Weber wrote:
Firstly, it's a convenience. When using ctags or any IDE system to
analyze a set of header files (for programming autocompletion), it
is convenient to have the headers in a package specific path within
the general ${prefix}/include path. This
On 08.10.2009, at 21:46, Darren Weber wrote:
On Thu, Oct 8, 2009 at 12:16 PM, Ryan Schmidt
wrote:
On Oct 8, 2009, at 13:37, Darren Weber wrote:
In cursory exploration of /opt/local/include/, it appears that many,
if not all, of the hdf5 header files are located at the root of /opt/
local/
On Thu, Oct 8, 2009 at 12:16 PM, Ryan Schmidt wrote:
> On Oct 8, 2009, at 13:37, Darren Weber wrote:
>
> In cursory exploration of /opt/local/include/, it appears that many, if
>> not all, of the hdf5 header files are located at the root of
>> /opt/local/include/. Is that a mistake? Should the
On Oct 8, 2009, at 13:37, Darren Weber wrote:
In cursory exploration of /opt/local/include/, it appears that many,
if not all, of the hdf5 header files are located at the root of /opt/
local/include/. Is that a mistake? Should the hdf5 include files
get stored into something like /opt/loca
In cursory exploration of /opt/local/include/, it appears that many, if not
all, of the hdf5 header files are located at the root of
/opt/local/include/. Is that a mistake? Should the hdf5 include files get
stored into something like /opt/local/include/hdf5/?
Take care,
Darren
__
