[Pkg-octave-devel] Re: [sundials-users] include file directory layout

Andrey Romanenko andrey at enginum.com
Fri Jun 16 00:54:29 UTC 2006


Hi!

On Wednesday 14 June 2006 23:49, Radu Serban wrote:
> 1. Keep the directory layout for the exported header files as it is right
> now.
>
> That is, the main solver and nvector header files in the top directory
> <sundials_install_path>/include, all other solver specific header files in
> <sundials_install_path>/include/<solver>, and all shared header files in
> <sundials_install_path>/include/sundials

Please, please, reconsider. We build SUNDIALS as a Debian package to be a 
system wide library. Therefore, sundials_install_path is /usr in this case.
It really looks strange to have /usr/include/cvode or /usr/include/ida (that 
is, parts of SUNDIALS) next to /usr/include/asm or /usr/include/sys.
May I suggest that the top directory for header file be 
<install_path>/include/sundials? In this case, it is still possible to have
subdirectories for each solver (/usr/include/sundials/cvode),
but it is better to keep the core and shared headers in /usr/include/sundials, 
that is, without creating a special subdirectory for them. Alternatively,  
put all headers in the same directory (/usr/include/sundials), as John 
suggested. 

Such header structure helps not only in system wide setups, but also in 
situations where SUNDIALS makes part of a bigger software package:
suppose we have

./include/sundials
./include/package1
./include/package2
./include/package3.

Ok, just my 2 cents.

Andrey
p.s. The fresh 2.2.0 Debian package installs SUNDIALS headers and header 
subdirectories right into /usr/include. Guess we have to fix this  in Debian.
Rafael, what do you think?




More information about the Pkg-octave-devel mailing list