Difference between revisions of "Config office"
(migrate) |
(Categorize.) |
||
| Line 16: | Line 16: | ||
In many cases running 'configure' when you have [[LinuxIntelEnv.Set]] sourced creates rather subtle problems; configuring from a clean shell is to be recommended. | In many cases running 'configure' when you have [[LinuxIntelEnv.Set]] sourced creates rather subtle problems; configuring from a clean shell is to be recommended. | ||
| + | |||
| + | [[Category:source directory]] | ||
Revision as of 16:54, 3 January 2006
What it contains
This directory manages the configuration of the OO.o source tree. In a 'normal' project this would be expected to be in the toplevel source directory - however, due to a rather unfortunate initial repository setup, this is not possible.
Configure process
The configure script is generated from configure.in by 'autoconf' - when checking into a cws including this module it is best not to update the 'configure' script since this creates cws merge problems for releng.
When run the configure script does a load of system checks, and with the result generates 'set_soenv' from 'set_soenv.in' using the normal autotools substitution rules.
'set_soenv' is then run at the tail of configure, which does more checks, and finally builds LinuxIntelEnv.Set which contains the environment for this build. This freezes all the significant settings including PATH, LD_LIBRARY_PATH etc. The idea here is to allow this build to be repeated trivially, and to reduce unexpected environment related problems in subsequent builds.
The configure script also creates 'bootstrap' in the toplevel - a simple script that builds dmake - the tool which then is used to build the rest of the project.
Gotchas
In many cases running 'configure' when you have LinuxIntelEnv.Set sourced creates rather subtle problems; configuring from a clean shell is to be recommended.
