From kde-core-devel  Thu Apr 20 12:20:11 2006
From: David Faure <faure () kde ! org>
Date: Thu, 20 Apr 2006 12:20:11 +0000
To: kde-core-devel
Subject: Re: Proposal: New module "kdecore"
Message-Id: <20060420122011.GE8646 () ktown ! kde ! org>
X-MARC-Message: https://marc.info/?l=kde-core-devel&m=114553561628611

> It's a bit offtopic, but would this actually be possible? I.e. adding 
> build-system files to the KDE/ level without enforcing the checkout of all 
> modules and while retaining the current way of building?

If we want to do that, then we have to stop using CMAKE_SOURCE_DIR everywhere
to mean "the top of this module", and use relative paths only...

(If we have CMakeLists.txt in KDE/ then CMAKE_SOURCE_DIR will be that dir,
and e.g. CMAKE_SOURCE_DIR/kio won't be kdelibs/kio as it is now)


But I think we should do that anyway, using relative paths. I regret that
am2cmake used absolute paths everywhere, since it makes it harder to move around
or rename things.

--
David Faure
faure@kde.org