Ville Voutilainen wrote:
> On Fri, Jan 16, 2009 at 8:07 PM, Ville Voutilainen
> <ville.voutilainen@...> wrote:
>> On Fri, Jan 16, 2009 at 7:45 PM, Mark Evenson <evenson@...> wrote:
>>> Or alternatively (which I think is a little better), we create a new target
>>> in the 'build.xml' which writes the state of all the necessary variables to
>>> files that the Lisp-hosted build can parse rather easily.
>> That's fine too, although I see little difference between having a master
>> file that both ant and lisp read, and having ant dump the data to a separate
>> file from build.xml. We already include a bunch of properties into the
>> ant build.
> Reality check, please. There is a difference. If we require dumping the file
> list for lisp-build from the ant-build, we practically require lisp-build users
> to use the ant build, to get the dump. That's not what we're aiming for
> (allowing people to use either ant or the lisp build, neither depending
> on the other). Therefore we should probably try the route of loading the
> file list/lists from a file as properties for the ant build, and loading the
> same data in the lisp build.
We would distribute the dumped list(s) with the source as a separate
Ant should never be required for the Lisp hosted build.
"A screaming comes across the sky. It has happened before, but there is
nothing to compare to it now."