aboutsummaryrefslogtreecommitdiff
path: root/kde-modules
AgeCommit message (Collapse)Author
2015-01-13Stop lying in the KDEInstallDirs documentation.Alex Merry
2015-01-11Do not unset cache variables in KDEInstallDirs.Alex Merry
Cache variables such as CMAKE_INSTALL_BINDIR may be used by other modules included from parallel parts of the tree, so we should not touch them. We still override them in the runtime environment, but this will not interfere with parallel subtrees of the project. As part of this, the order of precedence of variables specified on the command line is changed, so that KDE_INSTALL_* is considered first (although it is still considered "undefined" in the documentation). This means that if you only specify CMAKE_INSTALL_BINDIR, that will be used by both KDEInstallDirs and GNUInstallDirs, but if you specify both that and KDE_INSTALL_BINDIR, KDEInstallDirs will use KDE_INSTALL_BINDIR instead. This is probably not too useful, but seems more useful than any other arrangement. BUG: 342717 REVIEW: 121982
2015-01-07fix typo that lead to nearly empty KDE_INSTALL_TARGETS_DEFAULT_ARGS var on macChristoph Cullmann
2014-12-28Fix include directory change spotted by Hrvoje Senjan.v1.6.0-rc1v1.6.0Alex Merry
A previous commit inadvertantly changed the KF5 include prefix to kf5 (uppercase to lowercase).
2014-12-28Add deprecation warnings for old-style variables.Alex Merry
REVIEW: 121646
2014-12-28Make KDEInstallDirs provide KDE_INSTALL_* variables.Alex Merry
Creating variables whose names start with CMAKE_ is a bad idea for modules distributed outside CMake itself. Since the module is called KDEInstallDirs, having a KDE_INSTALL_ prefix for the variables is clear and intuitive. Both CMAKE_INSTALL_* variables and the older KDELibs4-compatible variables are provided, unless KDE_INSTALL_DIRS_NO_DEPRECATED is set to TRUE before the module is included. Even then, the CMAKE_INSTALL_* variables provided by the GNUInstallDirs module will still be set and understood (for compatibility with that module), unless KDE_INSTALL_DIRS_NO_CMAKE_VARIABLES is set to TRUE. REVIEW: 121646
2014-11-14Update the comments about the default lib MSVC hacksv1.5.0-rc1v1.5.0Alex Merry
Having done a lot of (unrelated) Windows development recently, I've come to understand the situation much better, so I'm recording that information here for the benefit of others.
2014-11-07Set CMAKE_INSTALL_SYSCONFDIR to /etc when CMAKE_INSTALL_PREFIX is /usrAlex Merry
When installing to /usr, we should use /etc for configuration. Using /usr/etc does not make sense. REVIEW: 120246
2014-11-03enable -D_USE_MATH_DEFINES on WindowsPatrick von Reth
2014-09-16allow qmldir to follow qt_sys_pathHarald Sitter
when running with the KDE_INSTALL_USE_QT_SYS_PATHS option allow QMLDIR in KDEInstallDirs to follow whatever is defined by qmake this change makes sure that qml plugins will end up in a default Qt path when using the super special magic flag.
2014-09-11Fix fallout from recent ECM patchesAlex Merry
KDE modules cannot assume the normal ECM modules are in the CMake module path, and CMAKE_INSTALL_IMPORTS_INSTALL_DIR / QTQUICKIMPORTSDIR was not set correctly. Also, ECMQueryQmake.cmake used a deprecated CMake command (exec_program).
2014-09-11Make code coverage possible in any KDE projectAleix Pol
Introduces a BUILD_COVERAGE option from a ECMCoverageOption file so that projects can easily enable code coverage in their applications. Furthermore, KDECompilerSettings does include that by default, so all proper KDE projects have the option by default. REVIEW: 120118
2014-09-11Add compiler sanitizers supportMathieu Tarral
REVIEW: 119968
2014-09-03Fix ECM to use qmake instead of hardcoding plugin install dirsRohan Garg
Packagers and other interested folks should pass -DKDE_INSTALL_USE_QT_SYS_PATHS=ON when building in order to install various files to the same dir as the Qt5 install dirs. CCMAIL: kde-packagers@kde.org REVIEW: 119901
2014-08-13KDECompilerSettings: Be more portable across libc's.Raphael Kubo da Costa
Defining _XOPEN_SOURCE to 500 is too restrictive: it corresponds to _POSIX_C_SOURCE 199506L, and hides several symbols that standard libraries like libc++ expect to find, leading to errors like this on FreeBSD: In file included from /tmp/attica/src/accountbalance.cpp:21: In file included from /tmp/attica/src/accountbalance.h:25: In file included from /usr/local/include/qt5/QtCore/QString:1: In file included from /usr/local/include/qt5/QtCore/qstring.h:50: In file included from /usr/include/c++/v1/string:437: In file included from /usr/include/c++/v1/string:437: /usr/include/c++/v1/cstdio:143:9: error: no member named 'snprintf' in the global namespace using ::snprintf; ~~^ This isn't a problem on Linux (actually, on systems using glibc) because defining _GNU_SOURCE enables a lot more features that are not made available on other libc implementations where it does not have any effect. Instead, stop defining _XOPEN_SOURCE at all and leave it up to the platform to show or hide as many symbols as necessary if no standards-related defines are set, and only set _GNU_SOURCE on systems where it is actually meaningful (ie. systems using glibc). REVIEW: 119696
2014-08-11also define _UNICODE on windowsPatrick von Reth
2014-07-19Check the libdir also on kFreeBSD and HurdPino Toscano
This way, on the Debian versions of these OSes, the library directory can be a multiarch path.
2014-07-18Define variable for AppStream upstream XML directoryMatthias Klumpp
REVIEW:118020
2014-07-07Define convenience variable for DATAROOTDIR/kxmlgui5.David Faure
See RR 119142 for more details.
2014-05-14Do not fail if vars like CMAKE_INSTALL_LIBDIR are defined as normal varsAurélien Gâteau
REVIEW: 118127
2014-05-13Use CMAKE_INSTALL_FOODIR style variables for KDEInstallDirsAlex Merry
This matches how CMake's GNUInstallDirs does things. REVIEW: 118057
2014-05-12Check that KDEInstallDirs defines the variables it claims toAlex Merry
2014-05-08bump Windows requirements to Windows Vista, as desided in ↵Patrick von Reth
http://techbase.kde.org/Projects/KDE_on_Windows/kf5/meetingnotes-2014-05-06
2014-05-08Make the KF5_LIBEXEC_INSTALL_DIR default depend on LIBEXEC_INSTALL_DIRAlex Merry
This way, overriding LIBEXEC_INSTALL_DIR will change where frameworks install libexec files in the expected way. REVIEW: 118048
2014-05-07Windows: Make sure plugin dlls get built inside ${CMAKE_BINARY_DIR}/binAlex Richardson
This is needed for e.g. kpluginfactorytest in kcoreaddons. Plugins are searched relative to the directory containing the running executable and before this commit the unit test was in ${CMAKE_BINARY_DIR}/bin and the plugin dll in ${CMAKE_BINARY_DIR}/lib, which meant that it could not be found. This was not a problem on Linux since there the unit test and the plugin .so ends up in ${CMAKE_CURRENT_BINARY_DIR}. Reviewed on #kde-windows
2014-05-04use the correct global variablesPatrick Spendrin
use CMAKE_[RUNTIME|ARCHIVE|LIBRARY]_OUTPUT_DIRECTORY. dlls and executables are built into the bin subdir and import & static libraries and plugins end up in the lib subdir of the build directory. REVIEW:117965
2014-05-04On Mac, define _DARWIN_C_SOURCE and QT_MAC_USE_COCOA unconditionallyAllen Winter
REVIEW: 117682
2014-05-02Set _FILE_OFFSET_BITS=64 again when necessaryAlex Merry
This essentially reverts db553c810cbc3a446f90d4c962110d6262853cde. It turns out that (for better or worse) quite a few places access files without going through KFile, so it is worth making sure they can deal with files larger than 2Gb on 32-bit systems. Reviewed by: Harald Sitter <sitter@kde.org> CCBUG: 165449
2014-05-02Also set KF5_LIBEXEC_INSTALL_DIR on WindowsAlex Richardson
REVIEW: 117935
2014-04-30more updates to commentsJonathan Riddell
REVIEW: 117907
2014-04-30make documentation match new values in codeJonathan Riddell
2014-04-27Do not use a "kf5" subdirectory for PLUGIN_INSTALL_DIRAlex Merry
This is where applications install plugins, so "kf5" is incorrect. Software should use application- or framework-specific directories (which may or may not be versioned).
2014-04-27Library executables are installed to lib/libexecAleix Pol
Also provide a subdirectory specific to kf5 that will put them in lib/libexec/kf5
2014-04-26Fix KF5_INSTALL_TARGETS_DEFAULT_ARGS on MacAlex Merry
2014-04-26Add a KNOTIFYRC_INSTALL_DIR variable to KDEInstallDirsAlex Merry
KNotifications will look here for .notifyrc files.
2014-04-26Improve installation directories naming for services and servicetypesAleix Pol
kde5/services is kservices5 kde5/servicetypes is kservicestypes5
2014-04-26Provide a KF5_DATA_INSTALL_DIR variableAlex Merry
This provides versioning in a way that is simple to update for KF6, and reduces our footprint in /usr/share.
2014-04-26Remove KF5 suffix from INCLUDE_INSTALL_DIR default valueAlex Merry
Only frameworks should be installing in include/KF5. They use KF5_INCLUDE_INSTALL_DIR, which has the KF5 suffix, while other code should install to just include (or a subdirectory of their choice).
2014-04-26Add KF5_INCLUDE_INSTALL_DIR variable to KDEInstallDirsAlex Merry
Currently, this is the same as INCLUDE_INSTALL_DIR, but INCLUDE_INSTALL_DIR will lose the "KF5" suffix once the frameworks are changed to use KF5_INCLUDE_INSTALL_DIR. Because INCLUDE_INSTALL_DIR is used in INSTALL_TARGETS_DEFAULT_ARGS, there is now also a KF5_INSTALL_TARGETS_DEFAULT_ARGS.
2014-04-15Add TODOs to KDEInstallDirs.cmakeAlex Merry
2014-04-11Add documentation generation using SphinxAlex Merry
This is deliberately modelled very closely on CMake's documentation system. It's a hefty patch, because it involved changing all the documentation to be in reStructuredText format. I also cleaned up the copyright/license statements at the same time. Note that the find modules contain the full license, due to the fact that ecm_use_find_module() copies them out of the ECM distribution.
2014-03-17Add historical info to comments in the compiler settings hacksAlex Merry
Hopefully these might be of some use in determining whether they are still needed.
2014-03-04Also pass -fno-exceptions when building with clangAlex Richardson
All of KF5 + kate + kde-workspace compile with clang and -fno-exceptions The only problem related to clang and -fno-exceptions I could find was http://llvm.org/bugs/show_bug.cgi?id=10910 and that is fixed since clang version 3.0 which was released in December 2011 REVIEW: 115395
2014-02-14build on Mac OS XHarald Fernengel
2014-02-14Improve docs for kde modulesAlex Merry
REVIEW: 115488
2014-02-12Install app desktop files to share/applications, not in a kde5 subdirAlex Merry
Given that binaries are all installed in PREFIX/bin, and have to avoid clashes, doing the same for desktop files is no great issue, and installing into a subdirectory of applications/ just complicates matters for client code that needs to refer to the desktop file (is it "kde5-foo[.desktop]", "kde5/foo[.desktop]" or just "foo[.desktop]"?). REVIEW: 115683
2014-02-05Remove commands that just set variables to their defaultsv0.0.10Alex Merry
REVIEW: 115477
2014-02-04Use the MSVC variable directly, instead of the compiler IDAlex Merry
This is cleaner and easier to read. REVIEW: 115378
2014-02-04Resolve some FIXMEs related to MSVC and IntelAlex Merry
In particular, MSVC (and Intel on Windows) have no equivalent of the -std flag to set the language standard, and Intel does not appear to produce the warnings that were disabled for MSVC. REVIEW: 115378
2014-02-04Fix MSVC libc linkage for debug buildsAlex Richardson
Previously we would end up with both /DEFAULTLIB:msvcrt and /DEFAULTLIB:msvcrtd on the command line. As a result of the the programs would link to both the debug and the release C library and always crash soon after startup. REVIEW: 115456
generated by cgit v1.2.1 (git 2.18.0) at 2025-05-03 22:29:13 +0000