Re: [dev] To OOo Builders ...
Kay Ramme - Sun Germany - Hamburg wrote: - There are various files in solenv/inc, some of them having more or less speaking names, while others are just differing by a prepanded underscore (e.g. _tg_app.mk vs. tg_app.mk ). What is the meaning of the underscore prefix? Is there an overview somewhere where I can find some explanations regarding the makefile system? _tg_app.mk is generated from tg_app.mk via some tool (whose name I forgot; mkunroll?), copying the input ninefold, replacing $(TNR) in the input with 1--9. Arguably, only _tg_app.mk should be checked in, and tg_app.mk built afresh during each build. This has already lead to errors in the past, where the two files went out of sync... -Stephan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] To OOo Builders ...
hi! Stephan Bergmann wrote: Kay Ramme - Sun Germany - Hamburg wrote: - There are various files in solenv/inc, some of them having more or less speaking names, while others are just differing by a prepanded underscore (e.g. _tg_app.mk vs. tg_app.mk ). What is the meaning of the underscore prefix? Is there an overview somewhere where I can find some explanations regarding the makefile system? _tg_app.mk is generated from tg_app.mk via some tool (whose name I forgot; mkunroll?), copying the input ninefold, replacing $(TNR) in the input with 1--9. Arguably, only _tg_app.mk should be checked in, and tg_app.mk built afresh during each build. This has already lead to errors in the past, where the two files went out of sync... i would prefer generation the other way ;) also the unroll tooling (mkunroll) currently orginates from module tools which makes bootstrapping a bit harder... any voluteers to rewrite in e.g. perl or C (please no java or python...)? [...] tschau... ause - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] To OOo Builders ...
Just created another patch to make deliver.pl less verbose ... http://udk.openoffice.org/issues/show_bug.cgi?id=79798 Kay Ramme - Sun Germany - Hamburg wrote: Hi builders, - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] To OOo Builders ...
Looked more into this ... and wrote some little patches to avoid dmake: Executing shell macro ..., please see http://udk.openoffice.org/issues/show_bug.cgi?id=79760 Some dmake questions in general: - Computed Names: Is there something similar to computed names as in GNU make? The only way I got macros indirectly expanded (e.g. $($(MYMACRO)) in a recipe was by calling some kind of function (e.g. $(strip $($(MYMACRO))) ), but likely I just missed that in the docs. - call Function: Is there something similar to the call function of GNU make? That would come quite handy when trying to simplify the makefiles somewhat ... - eval Function: Same question for the GNU make eval function, which I like to use once a while ... Some questions regarding our makefiles in particular: - It is unclear to me, what the error handling strategy is. On the one hand dmake (as most other makes) aborts execution if any command returns a non zero value and has not been explicitly marked to be ignored, on the other hand I see commands (e.g. @cat $(MISC)$/$(TARGET).$(@:b)_1.cmd ) whichs purpose seems solely to be to help diagnose errors. My expectation would be, that all output while building would just be for showing the progress, and to stop in case of an error, or at least to collect all errors and to report them at the end ... - There are various files in solenv/inc, some of them having more or less speaking names, while others are just differing by a prepanded underscore (e.g. _tg_app.mk vs. tg_app.mk ). What is the meaning of the underscore prefix? Is there an overview somewhere where I can find some explanations regarding the makefile system? Thanks for any help Kay Kay Ramme - Sun Germany - Hamburg wrote: Hi builders, while building OOo on multiple machines because of some map file issues ;-), I was wondering, if I am the only one being annoyed by the excessive verbosity of the build system ... actually slowing down build performance unnecessarily. If others have the same feeling, I am going to submit some patches to get the verbosity under control again ... Thanks for your opinions Kay - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] To OOo Builders ...
Hi Stephan, Stephan Bergmann wrote: Undecided. For example, echoing of compiler command lines could be helpful when a CWS owner tries to track down why a tinderbox built broke, to see whether it is an issue of the tinderbox build environment or an issue of the CWS... It actually should be easy, to echo the command line, which lead to an error in case of an error ... -Stephan Kay - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] To OOo Builders ...
Actually I think, the output should per default look like: compiling module/source/bla.cxx compiling module/source/foo.cxx linking module/unxlngi6.pro/lib/libgr.so Looks good. I'd like to see an option to do build this way at least. But sometimes both methods are good. I upload full build logs along my builds and they were used a lot of times in the past... -- Pavel Janík - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] To OOo Builders ...
Pavel Janík wrote: Actually I think, the output should per default look like: compiling module/source/bla.cxx compiling module/source/foo.cxx linking module/unxlngi6.pro/lib/libgr.so Looks good. I'd like to see an option to do build this way at least. But sometimes both methods are good. Well disabling the recipe has to be done in the makefiles, i.e. place an '@' sign at the beginning. To get back the full, verbose output pass '-vr' to dmake. (Use `build -- -vr`) I upload full build logs along my builds and they were used a lot of times in the past... Indeed, if everything works smoothly the long logfile is anoying, but if something fails it's nice to have it already. Volker -- = http://wiki.services.openoffice.org/wiki/Debug_Build_Problems = PGP/GPG key (ID: 0x9F8A785D) available from wwwkeys.de.pgp.net key-fingerprint 550D F17E B082 A3E9 F913 9E53 3D35 C9BA 9F8A 785D signature.asc Description: OpenPGP digital signature
[dev] To OOo Builders ...
Hi builders, while building OOo on multiple machines because of some map file issues ;-), I was wondering, if I am the only one being annoyed by the excessive verbosity of the build system ... actually slowing down build performance unnecessarily. If others have the same feeling, I am going to submit some patches to get the verbosity under control again ... Thanks for your opinions Kay - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] To OOo Builders ...
On Thu, 2007-06-28 at 15:28 +0200, Kay Ramme - Sun Germany - Hamburg wrote: Hi builders, while building OOo on multiple machines because of some map file issues ;-), I was wondering, if I am the only one being annoyed by the excessive verbosity of the build system ... actually slowing down build performance unnecessarily. If others have the same feeling, I am going to submit some patches to get the verbosity under control again ... FWIW, I build with build build-flags -- other-dmake-flags -s where the -s suppresses a goodly part of the output. C. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] To OOo Builders ...
Kay Ramme - Sun Germany - Hamburg wrote: Hi builders, while building OOo on multiple machines because of some map file issues ;-), I was wondering, if I am the only one being annoyed by the excessive verbosity of the build system ... actually slowing down build performance unnecessarily. If others have the same feeling, I am going to submit some patches to get the verbosity under control again ... Thanks for your opinions Undecided. For example, echoing of compiler command lines could be helpful when a CWS owner tries to track down why a tinderbox built broke, to see whether it is an issue of the tinderbox build environment or an issue of the CWS... -Stephan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
