|Message: Re: Build scripts bugs (9.2.0.p01)||Not Logged In (login)|
Click on the Forum title, e.g. on the "Forums by Category" page, to read a sequence of postings to the Forum and its threads all in one page. If you are only interested in one thread or the thread following a specific posting, click the thread or the posting, which takes you to a smaller page, which contains only the part you are interested in and may be easier to navigate.
Messages are "chained" if there are only replies at the first level, i.e. 1/1.html, 1/1/1.html etc. In case of "chained" messages the message number is replaced by the icon and there is no indentation.
Inline: Display the subject line only or also the text of the posting(s); for the choice "All" the "Outline" choices are switched off.
|1||0||1||no text / full text of posting|
|2||1||All||text for level 1 only / text for All postings|
Outline: Choose the depth of the posting thread, successive toggle controls provide increasing detail.
|1||2||1||2 levels / 1 level (original posting)|
|2||3||2||3 levels / 2 levels|
|3||3||All||3 levels / all levels (all postings)|
Thanks for the feedback!
On Mon, 17 Aug 2009 09:24:52 GMT, Olivier LAHAYE wrote: > 1) If you select build with Qt and choose /usr/lib64/qt4 as QTDIR, the > moc program is /usr/bin/moc (a 3.3 version) instead of $QTDIR/bin/moc > (/usr/lib64/qt4/bin/moc)
This is already fixed in CVS, where an extra check is done to confirm that the detected
> 2) There is no way to select a paralell build (make -j12). I need to > edit the /config/...../config.sh file
I've been putting together a Configure-generated top level Makefile that should resolve this (giving you a potential Configure/make/make install solution). It is still a work in progress though...
> 3) 64bit is not handeled correctly. libdir name is hardcoded to lib > instead of lib64 on 64bits systems. This prevents to install geant4 as a > system wide application (typicaly from a rpm package).
Do you mean
> 4) Configure script fails to recreate a config from a config.sh file. In > fact, many variables are missed, resulting in a bad config. ./Configure > -der -f config.sh -E If you do a diff between this config.sh and > .config/bin/Linux-g++/config.sh you'kll see that many variable are using > default values instead of values from config.sh
Right, that's probably due to some incorrect logic in the handling of default values. I'll take a look.
> 5) install.sh and move.sh have missleading names. install.sh should be > renamed build.sh move.sh should be renamed install.sh
Agreed, we'll see about changing these, or using the top-level Makefile solution.
> 6) if copy all includes in one directory is selected, then the make > include in not triggered by default.
> 7) No way to set XERCESCROOT from Configure script.
I'm not sure what you mean here - running interactively, Configure will automatically check for Xerces-c, and then query the user for XERCESCROOT if it doesn't find it. One can force the value via the variables
which you can set in your input config.sh, or at the command line with
> 8) No way to install geant4 as a system wide app like: /usr/bin (for > binaries) /usr/lib64/geant4 (for libraries) /usr/include/geant4 (for > includes) /usr/share/geant4/config (for config) /usr/share/geant4/data > (for data) Instead (enventhough I said that I want to build only for one > architecture), I'm force to have my libs and binaries in a sub directory > named Linux-g++ which is more than ugly when you install a system wide > application.
I'll take a look at fixing this!
> Please concider using autotools or cmake as build system as the current > one is buggy and difficult to maintain (IMHO).
The collaboration is working on a replacement build system using standard cross-platform tools - we're aware of the issues with the current system... - and it's a work in progress at this point!