On Thu, Jun 15, 2000 at 04:15:47PM -0500, Pete Willemsen wrote:
> Hello.
>
> I'm struggling with figuring out a way to maintain my directory
> structure for my header files. I have the following structure
>
> file1.c ... fileN.c PackageName/ Makefile.am configure.in ...
> |
> file1.h ... fileN.h
>
> I can build my code into a library and install the library correctly and
> place the header files into the include directory with a Makefile.am
> that resembles
>
> lib_LIBRARIES = libtest.a
> libtest_a_SOURCES = \
> file1.c \
> ... \
> fileN.c
> include_HEADERS = PackageName/file1.h \
> ... \
> PackageName/fileN.h
>
> However, this does not maintain the directory PackageName in the
> installed include directory. For instance, if a person were to use this
> library and needed to include a header file in their code, the line
> would look like this:
>
> #include <PackageName/filei.h>
I do the following in some of my packages:
pkginclude_HEADERS = \
file1.h \
... \
fileN.h
However, both my sources and headers are in the same directory.
I'm not sure how "pkginclude" deals with your directory structure, but
adding a Makefile.am to your PackageName directory in your package
distribution that contains something like the above should work.
HTH,
-Ossama
--
Ossama Othman <[EMAIL PROTECTED]>
Distributed Object Computing Laboratory, Univ. of California at Irvine
1024D/F7A394A8 - 84ED AA0B 1203 99E4 1068 70E6 5EB7 5E71 F7A3 94A8
