-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dear all, I wanted to support Martin in his endeavor to move to ANT for our build process(es) and started working on a build.xml file in the P5 directory (within my new peterstadler-antify branch). Second reason, I want to become more familiar with the build process itself… It looks like a straightforward thing to do, the only things I'd like to change are: * create a directory "build" where all the built files go (rather than polluting the P5 directory * create a directory "release" where the zipped archives go Both directories then can easily be discarded when cleaning the working copy before commiting ;) Does that make sense? Is anyone already working on this by chance? Best Peter -----BEGIN PGP SIGNATURE----- iQEcBAEBAgAGBQJV5hLZAAoJEJclm6G69Xq24gIH/34ez/QmIDAKbQ2sw3/PEzRK ERJyVdOWNCqv4m5lES6PDjVicVgpzjiOhR7l4sc57h/oPM6t1rxFKcftc6NBFkYl x//JmHNuCPM1BWV2wVN2jrGh+k6uXlov8rJoKMPFdzpFqdl9Yh+nebVuptDSOLxC GOSUjcJsXNgHYgXNNYFTodceRLUi/JDxL7zkFHMEvUtGSpQOEq7maeTnFpHPyfGG ASHOW35DGJXTzHFm8D72D7Ep3l35Vugm6nyGWURfSmQSfF7myaGDKGWjBsB/o9Kn TKrB+u1qC4Y2NwPeiUisGFk2L+ZCNtqEGBXlSvBa9uvUuaW5yk2w1adiVv/w/ZA= =Ja1L -----END PGP SIGNATURE-----
Yes, Peter, those changes make sense to me. (And they make sense even in the absence of switching to `ant`.) My first concern, though, is that other processes elsewhere in TEI land rely on some of the by-products of building to be in the P5/ dir. (I'm thinking of p5subset.xml and p5.xml, in particular. Don't know what else might rely on those.)
I wanted to support Martin in his endeavor to move to ANT for our build process(es) and started working on a build.xml file in the P5 directory (within my new peterstadler-antify branch). Second reason, I want to become more familiar with the build process itself…
It looks like a straightforward thing to do, the only things I'd like to change are: * create a directory "build" where all the built files go (rather than polluting the P5 directory * create a directory "release" where the zipped archives go Both directories then can easily be discarded when cleaning the working copy before commiting ;)
Does that make sense? Is anyone already working on this by chance?
Hi Peter, Great work. I think the current Makefile does create a release directory: mkdir -p release/tei-p5-source/share/xml/tei/odd and similar. We can (initially at least) do all the LaTeX stuff with <exec>, but that will be platform-specific for the moment. I have to make the oxygen-tei ant task run on Windows for the Oxygen guys, so I'm going to have to learn how to do branching based on OS soon. Cheers, Martin On 15-09-01 02:04 PM, Peter Stadler wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Dear all,
I wanted to support Martin in his endeavor to move to ANT for our build process(es) and started working on a build.xml file in the P5 directory (within my new peterstadler-antify branch). Second reason, I want to become more familiar with the build process itself…
It looks like a straightforward thing to do, the only things I'd like to change are: * create a directory "build" where all the built files go (rather than polluting the P5 directory * create a directory "release" where the zipped archives go Both directories then can easily be discarded when cleaning the working copy before commiting ;)
Does that make sense? Is anyone already working on this by chance?
Best Peter -----BEGIN PGP SIGNATURE-----
iQEcBAEBAgAGBQJV5hLZAAoJEJclm6G69Xq24gIH/34ez/QmIDAKbQ2sw3/PEzRK ERJyVdOWNCqv4m5lES6PDjVicVgpzjiOhR7l4sc57h/oPM6t1rxFKcftc6NBFkYl x//JmHNuCPM1BWV2wVN2jrGh+k6uXlov8rJoKMPFdzpFqdl9Yh+nebVuptDSOLxC GOSUjcJsXNgHYgXNNYFTodceRLUi/JDxL7zkFHMEvUtGSpQOEq7maeTnFpHPyfGG ASHOW35DGJXTzHFm8D72D7Ep3l35Vugm6nyGWURfSmQSfF7myaGDKGWjBsB/o9Kn TKrB+u1qC4Y2NwPeiUisGFk2L+ZCNtqEGBXlSvBa9uvUuaW5yk2w1adiVv/w/ZA= =Ja1L -----END PGP SIGNATURE-----
participants (3)
-
Martin Holmes -
Peter Stadler -
Syd Bauman