Peter Ekberg wrote:
Hello!
I have the following needs:
1. Extract some data from a list of files using script foo.
2. Process the data further using a second script bar.
3. Concatenate the processed data.
4. Run a third script foobar on the concatenation to
produce a .c file.
5. Distribute
How about using a bootstrap script (or something that gets put
into config.status) that touches your .c file?
H
Hello,
On Wed, Jan 04, 2006 at 01:15:23PM +0100, Peter Ekberg wrote:
.INTERMEDIATE: $(FOOBARS) splunk.foobar
[...]
Is there a portable solution to my needs?
a distributed file cannot depend on a non-distributed one.
So you have to replace the rule
.foobar.c:
./foobar $ $@
by
I expect that Automake conditionals with traditional make rules for
the intermediate targets wrapped up in a conditional will do the
trick. If you use Automake's maintainer-mode feature, then you can
use
if MAINTAINER_MODE
foo.c : foo.bar
dosomething
endif
There is also a
Hi,
On Wed, Jan 04, 2006 at 10:18:46AM -0800, Bruce Korb wrote:
Remove the generation of the .c files from your make files.
Put that logic in bootstrap and remove it from Makefile.am.
It makes life easier. If you distribute bootstrap, any
customer can run the script, if they so choose. :)
Hello,
On Wed, Jan 04, 2006 at 06:27:28PM +, Harlan Stenn wrote:
How about using a bootstrap script (or something that gets put
into config.status) that touches your .c file?
it would have to touch all the intermidiate files first, and then
the *.c file... Urghhh...
Have a nice day,
Stepan Kasal wrote:
That principle could rather be achieved by omitting the *.c file
from the distribution, supposing that every customer can install
the tools which are required to generate it.
Not every customer wants to install developer tools. In general,
people who install a project
