Re: What *target* use for non-source files want to add to package like DATA?

[cs]

Roger

My data directory in my source tree has a Makefile.am that
/just/ has something similar to your suggestion:

my_datadir        = $(pkgdatadir)/blah
dist_my_data_DATA = datafile1 datafile2 datafile3
EXTRA_DIST        = $(dist_my_data_DATA)

When I compile from top of source tree, it crashes at this
data directory with the message,

"No rule to make target `all'."

I guess this little snippet is not a COMPLETE Makefile.am???

Chris


 -------- Original Message --------
   Subject: Re: What *target* use for non-source files want to add to
package like DATA?
   From: Roger Leigh <address@hidden>
   Date: Tue, April 29, 2003 8:20 am
   To: <address@hidden>

   <address@hidden> writes:

   > I have been reading Automake docs and found
   > target for extra non-compiled junk like this one:
   >
   > EXTRA_mypgrogram_SOURCES

   That's not for "non-compiled junk", it's for conditionally compiled
   sources that may or may not need to be built.

   > I'm not sure if this is the one to use for stuff like
   > DATA that isn't compiled but you still want to
   > drag it around with your program.
   >
   > Which is best for non-source code stuff like data files?

   EXTRA_DIST, to distribute, but not install anywhere.  If it's
   e.g. HTML docs, I do this:

   htmldatadir = $(pkgdatadir)/doc/html
   htmldata_DATA = index.html ...
   EXTRA_DIST = $(htmldata_DATA) ...

   For installed program data files, I'd do something very similar:

   xmldatadir = $(pkgdatadir)/xml
   xmldata_DATA = foo.xml bar.xml ...
   EXTRA_DIST = $(xmldata_DATA)

   etc.


   --
   Roger Leigh

                   Printing on GNU/Linux?
                   http://gimp-print.sourceforge.net/ GPG Public Key:
                   0x25BFB848 available on public keyservers