kconfig.git/src/kconfig_compiler/CMakeLists.txt, branch v5.39.0-rc1

Allow to build KConfig without Qt5Gui

2017-08-04T16:54:42+00:00

Summary:
This is particularly useful for cross-compilation, where we only need the
kconfig_compiler on the host system.

Reviewers: #frameworks, apol, aacid

Reviewed By: aacid

Subscribers: aacid

Tags: #frameworks

Differential Revision: https://phabricator.kde.org/D6994

Mark kconfig-compiler as non-gui tool

2015-09-25T11:01:37+00:00

Makes sure that it doens't create an app bundle on Mac OS X

REVIEW: 125337

Upgrade Qt version requirement to 5.3

2015-08-01T12:41:18+00:00

Mark message() as WARNING

2015-06-24T21:21:59+00:00

As recommended by Alex Merry

CCMAIL: alex.merry@kde.org

Install kconfig_compiler into libexec

2015-06-23T19:44:32+00:00

This will make it end up in a platform-dependent prefix (i.e. /usr/lib64,
/usr/lib/arm-linux-gnueabihf, etc) rather than /usr/bin, making it possible
to have different kconfig_compiler versions installed, useful for
cross-compilation.

REVIEW: 124138

Make it possible to use kconfig_compiler from different sources

2015-06-21T00:14:54+00:00

This way we can specify the used tooling targets to be used, useful if we're
cross-compiling, since we get to use the tooling that runs in the local
platform.

REVIEW: 124104

Use KF5_INCLUDE_INSTALL_DIR and KF5_INSTALL_TARGETS_DEFAULT_ARGS

2014-04-26T11:09:00+00:00

This is instead of INCLUDE_INSTALL_DIR and INSTALL_TARGETS_DEFAULT_ARGS,
which will lose the "KF5" suffix from the include path.

Rename the kconfig_compiler_kf5 target to kconfig_compiler

2014-03-24T11:49:49+00:00

Just because the executable has the "_kf5" suffix, that does not mean
the target should have it.  This is ugly API, and will be unnecessary
porting effort for KF6.

REVIEW: 116995

Remove unhelpful comments

2014-03-24T11:22:36+00:00

These lines of code do not really require any justification.

REVIEW: 116962

rename kconfig_compiler to kconfig_compiler_kf5

2014-01-09T16:41:25+00:00