- 08 Oct, 2013 9 commits
-
-
This function avoids creating the targets when the required dependencies were not found. Also fix some wrong dependency and some typo. ${FREETYPE_INCLUDE_DIR_ft2build} ${FREETYPE_INCLUDE_DIR_freetype2} are now required for gtkmm component -
On some older system they are not required
-
Some libraries (e.g. gio) are not necessary, and often not available with older GTK2 versions, therefore GTK_LIBRARIES should not contain GTK2_XXX-NOT_FOUND for these libraries.
-
As discussed on the mailing list, freetype includes used in GTK2 headers libraries do not require to link the library explicitly (even though it is already linked by GTK2 libraries. Also remove _GTK2_ADD_TARGET_LIBRARIES no longer used and use ${FREETYPE_INCLUDE_DIR_ft2build} ${FREETYPE_INCLUDE_DIR_freetype2} variables instead of ${FREETYPE_INCLUDE_DIRS} -
-
-
-
-
-
- 07 Oct, 2013 10 commits
-
-
-
This saves from using string(REGEXP) to create targets
-
Add a method _GTK2_ADD_TARGET_INCLUDE_DIRS to handle it.
-
Methods: * _GTK2_ADJUST_LIB_VARS * _GTK2_ADD_TARGET_DEPENDS_INTERNAL * _GTK2_ADD_TARGET_DEPENDS are strongly inspired by FindQt4.cmake
-
This is the topmost include file for GObject header files
-
-
Also add a debug message to report if the library was found or not
-
-
-
-
- 09 Aug, 2013 3 commits
-
-
b33c9844 Revert "Add compiler target compile options."
-
Stephen Kelly authored
This reverts commit 2d9ec1da.
-
Kitware Robot authored
-
- 08 Aug, 2013 18 commits
-
-
b93982fb Merge branch 'dev/fix-variable-watch-crash' into cmake-syntax c50f7ede cmListFileLexer: Modify flex output to avoid Borland warning bf732646 Warn about unquoted arguments that look like long brackets 58e52416 Warn about arguments not separated by whitespace e75b69f5 cmListFileCache: Convert CMake language parser to class e945949d Add RunCMake.Syntax test cases for command invocation styles 0546484e cmListFileArgument: Generalize 'Quoted' bool to 'Delimeter' enum 28685ade cmListFileLexer: Split normal and legacy unquoted arguments 1eafa3ed cmListFileLexer: Fix line number after backslash in string f3155cd6 Add RunCMake.Syntax test to cover argument parsing
-
6aa0c214 variable_watch: Add test for watching a variable multiple times b86e37c8 variable_watch: Check newValue for NULL f9bb20fe variable_watch: Don't share memory for callbacks 05dad99f variable_watch: Fix a typo in the error message 00ce12a3 variable_watch: Prevent making extra entries in the watch map 34b397e8 variable_watch: Allow specifying the data to match in RemoveWatch e43e207c variable_watch: Match client_data when finding duplicates 0d6acb1d variable_watch: Add a deleter for the client data fc7c3b4d variable_watch: Store client data as pointers
-
-
cd345aa7 Skip CTestLimitDashJ test on Borland
-
-
-
ae6a5ea5 Include cmMakefile.h before cm*Lexer.h to get stdint.h first
-
8120e13f cmake-gui: Fix build rules for Qt5 on Windows
-
Brad King authored
Resolve conflict in Source/cmVariableWatchCommand.cxx by integrating the changes from both sides.
-
-
On read access, newValue can be NULL since there is no new value, so use the empty string instead.
-
The command itself is owned by the cmMakefile class, but the cmVariableWatch which holds a pointer to the cmVariableWatchCommand via the client_data for the callback outlives the cmMakefile class in the Qt GUI. This means that when the cmMakefile is destroyed, the variable watch is still in effect, but with a stale pointer. To fix this, each callback is now a separate entity completely and doesn't rely on the command which spawned it at all. An example CMakeLists.txt which demonstrates the issue (only displayed in cmake-gui, so no tests can be written for it): set(var 0) variable_watch(var) -
There was no space between "callback" and the quoted command name.
-
When removing a watch on a variable, using the operator [] on the internal map will create an empty watch if the variable doesn't have any existing watches. Rather than creating this empty structure in the map, return if there isn't a watch on the variable already.
-
Now that watches are dependent on their client_data when adding, it also makes sense to allow matching the data for removal.
-
If a callback has the same data as another call, we don't want to delete the old callback. This is because if the client_data is the same, it might get deleted causing the new client_data to be bogus. Now, AddWatch will return true if it will use the watch, false otherwise. Callers should check the return value to know whether client_data was adopted by the watch or not.
-
The client data is arbitrary and the callback may be called an unspecified number of times, so the cmVariableWatch must be the one to delete the client data in the end (if it is needed at all).
-
The STL containers create extra copies which makes keeping track of the owner of the client data much messier.
-
