problem solved!

[Alexander Neundorf]

On Friday 15 February 2013, Treeve Jelbert wrote:
> It all finally compiles.
> 
> IN the the end the only changes that I made were
> 
> diff --git a/CMakeLists.txt b/CMakeLists.txt
> index 0011ac3..7992acd 100644
> --- a/CMakeLists.txt
> +++ b/CMakeLists.txt
> @@ -78,8 +78,8 @@ set(kcoreaddons_LIBRARIES kcoreaddons)
> 
>   set(kwindowsystem_LIBRARIES kwindowsystem)
> 
> -set(kconfig_INCLUDE_DIRS   ${kconfig_BINARY_DIR}/src/core
> -                           ${kconfig_SOURCE_DIR}/src/core )
> +set(kconfig_INCLUDE_DIRS  ${CMAKE_SOURCE_DIR}/tier2/kconfig/src/core
> +                          ${CMAKE_BINARY_DIR}/tier2/kconfig/src/core)
>   set(kconfig_LIBRARIES kconfigcore kconfiggui)
> 
>   # tier1/ already builds standalone, so it should not get any include
> dirs from here.

Ah, right.
Interesting effect.
When I added those line, I wondered whether I should put them together with 
the similar set of variables for kcoreaddons, or after the 
add_subdirectory(tier2/).

I decided to put them together with the other variables, which means before 
the add_subdirectory(tier2).

Now, for me this worked, but more accidentially.
project(kconfig)
sets the variables kconfig_SOURCE_DIR and kconfig_BINARY_DIR, and puts them in 
the cache.
So for me they were already in the cache, so they were already defined before 
the tier2/ directory (because I didn't do a fresh rebuild).

So there are two ways to make it work.
Either move the call after the directory tier2/, or change it as you do above.
Both are ok, go ahead and commit as you feel suitable.

> My problems were cause by having specified KDE_SKIP_BUILD_SETTINGS=1 on
> the cmake line


Ah, right, that's exactly what this switch is for.
You probably don't want to set this from the outside for any project.
This should be only set by projects which do 
find_package(KF5 COMPONENTS CMake)
but which don't want to have all those cmake options set (which leaves them 
with the KDE-style RPATH settings)

Alex