[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kmobiletools
Subject:    Re: [kmobiletools] KDE/kdepim/kmobiletools/tests/testlibkmobiletools
From:       David Faure <dfaure () kdab ! net>
Date:       2007-06-21 15:06:32
Message-ID: 200706211706.33283.dfaure () kdab ! net
[Download RAW message or body]

On Thursday 21 June 2007, Allen Winter wrote:
> On Thursday 21 June 2007 10:22:21 am Marco Gulino wrote:
> > SVN commit 678491 by gulino:
> > 
> > SILENT: Got the right one this time..
> > 
> > 
> >  M  +1 -2      CMakeLists.txt  
> > 
> > 
> > --- trunk/KDE/kdepim/kmobiletools/tests/testlibkmobiletools/CMakeLists.txt #678490:678491
> > @@ -1,11 +1,10 @@
> >  include_directories(
> >     ${CMAKE_CURRENT_SOURCE_DIR}
> > -   ${CMAKE_CURRENT_SOURCE_DIR}/../../kmobiletools/libkmobiletools
> > +   ${CMAKE_CURRENT_SOURCE_DIR}/../../kmobiletools
> 
> ^ick.
> how about  ${CMAKE_SOURCE_DIR}/kmobiletools
> ?

Using relative paths (with CMAKE_CURRENT_SOURCE_DIR) allows 
1) to move the whole thing without having to adjust all CMakeLists.txt files
 (e.g. if kdepim/kmobiletools became kdepim/tools/kmobiletools, like we did in kdebase)
2) to configure only one subdir with cmake instead of the whole module, possibly
 (like I do in extragear and playground).

So in general I do recommend to use relative paths instead of absolute paths.

-- 
David Faure, faure@kde.org, dfaure@klaralvdalens-datakonsult.se
KDE/KOffice developer, Qt consultancy projects
Klarälvdalens Datakonsult AB, Platform-independent software solutions
_______________________________________________
kmobiletools mailing list
kmobiletools@kde.org
https://mail.kde.org/mailman/listinfo/kmobiletools

[prev in list] [next in list] [prev in thread] [next in thread]