make dist and data package

2009-02-10 Thread Michel Briand
Hello all, I'm working on a project that release code/library but also a large amount of data. I wonder if it's possible to create 2 packages with make dist. One for the software, one for the data directory ? Cheers, Michel -- .''`. : :' : We are debian.org. Lower your prices, surrender your

automake and dist data

2009-02-10 Thread dagecko
Hello, I hope someone here will be able to help me. I'm developping a middle-scale library that uses autoconf and automake. This library comes along with some demo and test programs. Those demo and test programs now require some input files in order to run. Those input files also have to be di

Re: automake and dist data

2009-02-10 Thread Matěj Týč
What I do (not sure whether it is correct) is that I define a variable in configure.ac: AC_ARG_WITH([datadir], [AS_HELP_STRING([--with-datadir=path-to-your-foo-datafiles], [Normally you don't have to use this, but it is handy when you want to use foo withou

Re: 3 of 506 tests failed

2009-02-10 Thread Ralf Wildenhues
Hello Dennis, Thanks for the bug report. * Dennis Clarke wrote on Mon, Feb 09, 2009 at 01:10:01AM CET: > > $ gmake check > Making check in lib > gmake[1]: Entering directory > `/export/medusa/dclarke/build/automake/i386/automake-1.10.2-build-i386/lib' [...] > FAIL: check10.test [...] > FAIL: pr9

Expressing non-source dependency for a VPATH build

2009-02-10 Thread Rhys Ulerich
Hi all, I've got an autotooled project which I can successfully configure/build using something like ../project/configure && make. Is there some way to express a non-source dependency so that it gets "picked up" in a VPATH build? Maybe symlinked? Specifically, I've got a log4cxx.properties file

Re: Expressing non-source dependency for a VPATH build

2009-02-10 Thread Ralf Wildenhues
Hello Rhys, * Rhys Ulerich wrote on Wed, Feb 11, 2009 at 03:59:36AM CET: > > I've got an autotooled project which I can successfully > configure/build using something like ../project/configure && make. Is > there some way to express a non-source dependency so that it gets > "picked up" in a VPAT