4 Apr
2012
4 Apr
'12
3:48 a.m.
On 04/03/2012 04:38 PM, Darrell Anderson wrote:
That is what my on-the-fly patching does in my master
build script: fixes the admin and cmake directory in each module. I don't know whether
there is a shortcut to fixing the mess.
There is a common admin and cmake directory in the source tree, but I don't know how
that is related to the individual admin and cmake directories in each module. Are those
common admin and cmake directories replicated nightly to the individual modules ?
Darrell
Short answer - I don't know, but my understanding is 'yes' -- those are
replicated/updated when you update the git tree. That's the whole purpose behind
the submodule init stuff. Having standardization behind the build mechanics of
every module/app in the TDE project. The /admin and /cmake files would be the
proper place to do all this if the path info can be set there. I know that is
the proper place for the cmake 'tde_setup_paths( )' magic to take place and I
suspect the same can be done for all the autoconf files through acinclude.m4.in
files (or something similar).
Those are the dimly lit misty places where the likes of the 'White Wizard' and
the creature called 'sameleian' lurk and control the keys to the rest of the
kingdom. I think with a small amount of magic, those two could probably unlock
the secret to getting the doc files in the right place without having to mount a
frontal attack on the individual modules themselves :)
Looking at the cmake files for tdelibs/tdebase/etc.. the doc paths are not set
in the top-level CMakeLists.txt file along with the other paths that are
specified. I suspect that is the answer...
--
David C. Rankin, J.D.,P.E.