Bodo Moeller wrote:
>
> An issue that still is open as of yet is what to do with the exported
> header files. Currently, /usr/local/ssl/include/foo.h will
> #include "bar.h"
> which it should't --
> #include <bar.h>
> is better because it cannot conflict with application files.
> However, I'd prefer moving everything to <openssl/bar.h>
> so that it cannot conflict even with other libraries.
> To compile applications that don't know about the new names,
> one would have to add -I/usr/local/ssl/include/openssl to
> their CFLAGS; new applications could use only -I/usr/local/ssl/include,
> and the header files could alternatively be installed in (or linked
> to) /usr/local/include/openssl.
>
> Comments, ideas, vetoes ....?
I'd like to see <openssl/foo.h>, and encourage packagers to install
foo.h in /usr/include/openssl/
Currently I feed the .h files through
sed -e 's/\(#include *\)"\([^"]*\)"/\1<openssl\/\2>/'
--
Niels Poppe - org.net bv <[EMAIL PROTECTED]>
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
