aboutsummaryrefslogtreecommitdiff
path: root/kde-modules
AgeCommit message (Collapse)Author
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
2014-01-29Improve the compiler version checksAlex Merry
- Only warn if the compiler is not recent enough (it may still work...) - Bump up the GCC version to 4.5 (on Linux, at least) to match Qt - Add checks for Windows (both MSVC and MinGW) - Add check for Clang REVIEW: 115372
2014-01-29Check the C_COMPILER_ID when settings C_FLAGS, not CXX_COMPILER_IDAlex Merry
Not that anyone is likely to use different compilers for C and C++... REVIEW: 115379
2014-01-29KDE_SOURCE_FILES_ENABLE_EXCEPTIONS: Handle case where COMPILE_FLAGS is not setAurélien Gâteau
When COMPILE_FLAGS is not set, get_source_file_property(flags ${source_file} COMPILEFLAGS) set flags to "NOTFOUND". Leading to interesting build failures in kde-runtime when we then set flags to "NOTFOUND -fexceptions", see http://build.kde.org/job/kde-runtime_frameworks_qt5/58/ REVIEW: 115376
2014-01-29Move and comment -fno-common settingAlex Merry
REVIEW: 115363
2014-01-29Remove the allocator and visibility checkAlex Merry
I am reasonably sure the allocator check is out of date, given our minimum GCC version, and it was not used for anything interesting anyway. The visibility check will not be performed in practice, as this file will almost always be included before any check for Qt. REVIEW: 115360
2014-01-28Add a note about why we use C89 instead of C99Alex Merry
2014-01-28Do not explicitly link against libcAlex Merry
This is entirely unnecessary with any sane toolchain, and should be in the linker flags (rather than the compiler flags) for any system where it is required. REVIEW: 115362
2014-01-28Better documentation for system API definesAlex Merry
2014-01-27Organise KDECompilerSettings.cmake more logicallyAlex Merry
Very little should have changed in practice (apart from the Intel compiler stuff being properly separated between things for WIN32 and things for other platforms, and not defining _BSD_SOURCE).
2014-01-27Replace the KDE_ENABLE_EXCEPTIONS variable with a pair of functionsAlex Merry
kde_enable_exceptions() essentially does what set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} ${KDE_ENABLE_EXCEPTIONS}") used to do. kde_target_enable_exceptions does it on a per-target basis.
2014-01-27Add system API feature macros to CMAKE_REQUIRED_DEFINESAlex Merry
Various defines we set affect the API offered by the system; subsequent CMake configure checks should happen in a matching environment. REVIEW: 115294
2014-01-23Only set QT_STRICT_ITERATORS when not compiling with MSVCAlex Richardson
On MSVC linker errors will happen when this flag is set (with Qt < 5.3) REVIEW: 115234
2014-01-20Use add_definitions directly, instead of via _KDE4_PLATFORM_DEFINITIONSAlex Merry
Setting the variable just leads to set() calls overwriting each other accidentally (as appeared to have happened in the WIN32 block). REVIEW: 114908
2014-01-20Remove KDE4 magic from _SET_FANCY in KDEInstallDirs.cmakeAlex Merry
This appears to be a hangover from the KDE4 days, which would adjust certain paths to match the ones for kdelibs if you installed an application to the same prefix as kdelibs. This was probably to make KStandardDirs work properly in unusual setups. REVIEW: 114904
2014-01-14substitute QT_USE_FAST_CONCATENATION with QT_USE_QSTRINGBUILDERMichal Humpula
REVIEW: 115012
2014-01-07Do not set CMP0022Alex Merry
We do not want to suppress any warnings about LINK_INTERFACE_LIBRARIES vs INTERFACE_LINK_LIBRARIES; everything should be using the latter, since we depend on CMake 2.8.12 everywhere. REVIEW: 114903
2014-01-07Improve comments in KDECompilerSettings.cmakeAlex Merry
2014-01-07Remove commented-out manifest tool code from KDECompilerSettingsAlex Merry
This originally found the manifest tool from kdewin, which was then used by kde4_add_executable to embed a standard manifest file in applications, apparently allowing applications to have administrator privileges when run by an administrator. Given we do not have kde4_add_executable any more, this is useless (and certainly does not belong in this file). kdewin should provide any relevant manifest macros itself, in a KDEWinMacros.cmake file or some such, and these should be used on an as-needed basis for executables that require it.
2014-01-07Improve comments in RPATH section of KDECMakeSettingsAlex Merry
The old comments were somewhat out-of-date.
generated by cgit v1.2.1 (git 2.18.0) at 2025-06-05 00:17:14 +0000