[Prev][Next][Index][Thread]
Re: Issues with GD
-
To: info-dylan@ai.mit.edu
-
Subject: Re: Issues with GD
-
From: Nolan Darilek <nolan@ethereal.dhis.org>
-
Date: Mon, 20 Mar 2000 21:30:02 -0500 (EST)
-
Organization: The University of Texas at Austin; Austin, Texas
-
References: <87vh2h8n4j.fsf@ethereal.dyndns.org> <m3g0tlfcal.fsf@soma.andreas.org>
-
Xref: traf.lcs.mit.edu comp.lang.dylan:11675
>>>>> "Andreas" == Andreas Bogk <andreas@andreas.org> writes:
>> I don't see how this can be done due to d2c's apparent need for
>> a .lid, but I could quite possibly be missing something which
>> isn't immediately apparent. :)
Andreas> I don't see a problem at all, can you elaborate?
Sure.
If I want to use automake for a project in C/C++, I might do:
bin_PROGRAMS = myapp
myapp_SOURCES = myapp.dylan myapp2.dylan myapp.lid
Yet, since the compilation process only needs to do:
d2c myapp.lid
And not:
d2c -c myapp.dylan
d2c -c myapp2.dylan
d2c -o myapp myapp.o myapp2.o
in traditional GNU-ish fassion, how would I use automake for the
project, while still supporting options such as 'make dist' to quickly
pack the sources and such into a tarball? Or, is there another way to
do this?