Review Request 124104: Make it possible to use kconfig_compiler from different sources

[Sebastian Kügler]

-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/124104/#review81550
-----------------------------------------------------------


>From a cross-compile POV, this makes sense. I can't comment on the CMake foo, however.

- Sebastian Kügler


On June 18, 2015, 1:19 a.m., Aleix Pol Gonzalez wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://git.reviewboard.kde.org/r/124104/
> -----------------------------------------------------------
> 
> (Updated June 18, 2015, 1:19 a.m.)
> 
> 
> Review request for Build System, KDE Frameworks, Matthew Dawson, and Harald Sitter.
> 
> 
> Repository: kconfig
> 
> 
> Description
> -------
> 
> Separates the tooling that is supposed to be used at run-time so that we can specify which to use explicitly.
> 
> Ideally this would be done automagically, for now we'll have to specify -DKF5ConfigCompiler_DIR=...
> 
> Additionally, we should make kconfig_compiler co-installable by putting it in libexec, but I'd prefer to do that in a future patch. This same process should also happen on other frameworks.
> 
> 
> Diffs
> -----
> 
>   CMakeLists.txt f510e3e 
>   KF5ConfigConfig.cmake.in b4e5f56 
>   src/kconfig_compiler/CMakeLists.txt ec4a733 
> 
> Diff: https://git.reviewboard.kde.org/r/124104/diff/
> 
> 
> Testing
> -------
> 
> Works as expected on my debian chroot environment.
> 
> 
> Thanks,
> 
> Aleix Pol Gonzalez
> 
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-frameworks-devel/attachments/20150618/6367fad8/attachment.html>