From: David B. <Dav...@mo...> - 2004-07-07 11:36:34
|
Dapr=E8s Paul Kienzle <pki...@us...> (le 07/07/2004): > Yeah, I was thinking about what would be required this morning > and deciding that it wasn't going to be so easy as I thought. Any > idea how Octave does it? After all, Makefile doesn't exist before > configure is run. Having a 'dist.sh' script in each subdirectory > that needs it is another way independent of make of doing this, > though since we always have 'Makefile' around in octave-forge > this isn't so compelling. The "dist" target in octMakefile within octave is nearly 40 lines long. It looks like it does much of the work itself rather than handing things off to the subdirectories. I don't think this is an option in octave-forg= e. The only problem is the need of the variables defined in Makeconf for something that needs to be built for the dist target. This hopefully shouldn't come up that often. The fix I have if pretty generic. The tests for the args of TEXINFO etc are perhaps the only place things might cause a problem (if you have the tools installed that this). These tests were more my paranoia than anything, so the effect disabling of=20 these for the dist target in main/comm and main/fixed is probably not an issue. Regards David --=20 David Bateman Dav...@mo... Motorola CRM +33 1 69 35 48 04 (Ph)=20 Parc Les Algorithmes, Commune de St Aubin +33 1 69 35 77 01 (Fax)=20 91193 Gif-Sur-Yvette FRANCE The information contained in this communication has been classified as:=20 [x] General Business Information=20 [ ] Motorola Internal Use Only=20 [ ] Motorola Confidential Proprietary |