From: Stefan S. <ssc...@gm...> - 2005-01-27 15:49:31
|
On Thu, 27 Jan 2005 14:10:07 +0100, Valient Gough <vg...@po...> wrote: > > How about having 'make install' install the source files from the > example directory? thats a good idea, but we should not not build them as everyone who reads the source wants to do that himself I think, and they are not just for running. ls /usr/share/doc/fuse-2.2_pre5/example/ Makefile.am.gz Makefile.in.gz hello.c.gz Makefile.gz fusexmp.c.gz null.c.gz there I have it currently in gentoo. > > This is a patch I've been adding to fuse before I build rpm files, so > that 'make install' installs the source files from examples into > /usr/share/doc/packages/fuse/examples (when --prefix=/usr). > why the additional "packages"? > RCS file: /cvsroot/fuse/fuse/example/Makefile.am,v > retrieving revision 1.6 > diff -u -3 -p -r1.6 Makefile.am > --- Makefile.am 3 Jun 2004 13:21:08 -0000 1.6 > +++ Makefile.am 27 Jan 2005 12:59:57 -0000 > @@ -1,6 +1,10 @@ > ## Process this file with automake to produce Makefile.in > > -noinst_PROGRAMS = fusexmp null hello > +docdir = $(datadir)/doc/packages/$(PACKAGE) > +exampledir = $(docdir)/examples > + > +example_PROGRAMS = fusexmp null hello > +example_DATA = fusexmp.c hello.c Makefile.am null.c > > fusexmp_SOURCES = fusexmp.c > null_SOURCES = null.c > > ------------------------------------------------------- > This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting > Tool for open source databases. Create drag-&-drop reports. Save time > by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. > Download a FREE copy at http://www.intelliview.com/go/osdn_nl > _______________________________________________ > fuse-devel mailing list > fus...@li... > https://lists.sourceforge.net/lists/listinfo/fuse-devel > |