- 02 Nov, 2015 1 commit
-
-
Thiago Macieira authored
The Qt Project recommendation is that there should always be a "qmake" binary and it should never be renamed. If it's necessary to handle multiple Qt versions, the Qt Project recommends using qtchooser. Unfortunately, some distros do not follow the recommendation, so we would need to check qmake-qt4, qmake-qt5, etc. So, instead, let's try pkg-config. Signed-off-by:
Thiago Macieira <thiago.macieira@intel.com> Reported-by:
Alexey Brodkin <abrodkin@synopsys.com> Acked-by:
Michal Marek <mmarek@suse.com>
-
- 20 Oct, 2015 1 commit
-
-
Michal Sojka authored
Fixes: 31847b67 ("kconfig: allow use of relations other than (in)equality") Signed-off-by:
Michal Sojka <sojkam1@fel.cvut.cz> Reviewed-by:
Jan Beulich <jbeulich@suse.com> Signed-off-by:
Michal Marek <mmarek@suse.cz>
-
- 14 Oct, 2015 38 commits
-
-
Gabriel de Perthuis authored
merge_config.sh can usefully be applied to a single file. It implicitly merges with the default configuration. Signed-off-by:
Gabriel de Perthuis <g2p.code@gmail.com> Signed-off-by:
-
Gabriel de Perthuis authored
All make targets support $KCONFIG_CONFIG because they run scripts/kconf. Make sure merge_config.sh accesses the correct file in all cases. Previously this script broke in two different code paths, one for targets like kvmconfig (which use merge_config.sh -m then call a target that respects KCONFIG_CONFIG) and one for direct use of the script without -m, which called make rules that edit KCONFIG_CONFIG but verified a different file. Signed-off-by:
-
Thiago Macieira authored
The buildsystem will now only search for Qt 4 and Qt 5. Support for Qt 2 and 3 was dropped in the previous commits (Qt 3 was EOL'ed in 2010 or so...). For Qt 5, to be future-proof with the future direction notice appearing in the 5.5 release, C++11 support is automatically enabled. Signed-off-by:
-
Boris Barbulovski authored
Signed-off-by:
Boris Barbulovski <bbarbulovski@gmail.com> Signed-off-by:
-
Boris Barbulovski authored
Signed-off-by:
-
Boris Barbulovski authored
Signed-off-by:
-
Boris Barbulovski authored
Signed-off-by:
-
Boris Barbulovski authored
Signed-off-by:
-
Boris Barbulovski authored
Signed-off-by:
-
Boris Barbulovski authored
Signed-off-by:
-
Boris Barbulovski authored
Signed-off-by:
-
Boris Barbulovski authored
Signed-off-by:
-
Boris Barbulovski authored
Signed-off-by:
-
Boris Barbulovski authored
ConfigItem executes parent->takeChild(0) while ConfigList executes parent->takeTopLevelItem(0) Signed-off-by:
-
Boris Barbulovski authored
Signed-off-by:
-
Boris Barbulovski authored
Signed-off-by:
-
Boris Barbulovski authored
Signed-off-by:
-
Boris Barbulovski authored
Signed-off-by:
-
Boris Barbulovski authored
Signed-off-by:
-
Boris Barbulovski authored
Signed-off-by:
-
Boris Barbulovski authored
Signed-off-by:
-
Boris Barbulovski authored
Signed-off-by:
-
Boris Barbulovski authored
Signed-off-by:
-
Boris Barbulovski authored
Signed-off-by:
-
Boris Barbulovski authored
Signed-off-by:
-
Boris Barbulovski authored
Signed-off-by:
-
Boris Barbulovski authored
Signed-off-by:
-
Boris Barbulovski authored
Signed-off-by:
-
Boris Barbulovski authored
Signed-off-by:
-
Boris Barbulovski authored
Signed-off-by:
-
Boris Barbulovski authored
Signed-off-by:
-
Boris Barbulovski authored
Signed-off-by:
-
Boris Barbulovski authored
Signed-off-by:
-
Boris Barbulovski authored
Signed-off-by:
-
Boris Barbulovski authored
Signed-off-by:
-
Boris Barbulovski authored
Signed-off-by:
-
Boris Barbulovski authored
Signed-off-by:
-
Boris Barbulovski authored
Signed-off-by:
-
