Re: [dev] Bad PRJNAMEs

2006-12-14 Thread Nikolai Pretzell
Stephan Bergmann schrieb: Attached are two quick and dirty scripts that worked for me (within Hamburg build environment on a Linux box) to find all the places where PRJNAME is probably set wrongly (see below). Feel free to fix those you feel responsible for. ./autodoc/source/parser/tokens

Re: [dev] Bad PRJNAMEs

2006-11-14 Thread Juergen Schmidt
Frank Schönheit - Sun Microsystems Germany wrote: Hi Stephan, Attached are two quick and dirty scripts that worked for me (within Hamburg build environment on a Linux box) to find all the places where PRJNAME is probably set wrongly (see below). Feel free to fix those you feel responsible fo

Re: [dev] Bad PRJNAMEs

2006-11-13 Thread Stephan Bergmann
Frank Schönheit - Sun Microsystems Germany wrote: Hi Stephan, Attached are two quick and dirty scripts that worked for me (within Hamburg build environment on a Linux box) to find all the places where PRJNAME is probably set wrongly (see below). Feel free to fix those you feel responsible fo

Re: [dev] Bad PRJNAMEs

2006-11-13 Thread Frank Schönheit - Sun Microsystems Germa ny
Hi Stephan, > Attached are two quick and dirty scripts that worked for me (within > Hamburg build environment on a Linux box) to find all the places where > PRJNAME is probably set wrongly (see below). Feel free to fix those you > feel responsible for. In case nobody already volunteered to fi

[dev] Bad PRJNAMEs

2006-10-26 Thread Stephan Bergmann
Hi all, Each makefile.mk needs to set PRJNAME to the name of the (CVS) module it is contained in. That is for example used by the MODULES_WITH_WARNINGS lists, listing those modules (i.e., PRJNAMEs) which are still to be compiled without warnings=errors. There are occasionally cases where a