summaryrefslogtreecommitdiffstats
path: root/Source/cmExtraEclipseCDT4Generator.cxx
Commit message (Collapse)AuthorAgeFilesLines
* Merge topic 'EclipseFixIndexerBySettingSourcePath'Brad King2012-11-061-5/+7
|\ | | | | | | | | 077de8b Eclipse: set source path once to fix Eclipse indexer (#13596)
| * Eclipse: set source path once to fix Eclipse indexer (#13596)Alex Neundorf2012-11-061-5/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Since CMake 2.8.7 no src-path entry was generated anymore, in response to http://www.cmake.org/Bug/view.php?id=12213 Before that a src-path entry was added for each linked resource. Now only one src-path entry is added, for the ${CMAKE_SOURCE_DIR}. According to http://www.cmake.org/Bug/view.php?id=13596 this makes the indexer behave better. Alex
* | Merge topic 'EclipseNoLinkedResources'David Cole2012-10-311-0/+13
|\ \ | | | | | | | | | | | | fbda958 Eclipse: add switch to disable linked resources (#13189)
| * | Eclipse: add switch to disable linked resources (#13189)Alex Neundorf2012-10-171-0/+13
| |/ | | | | | | | | | | | | | | Eclipse may get confused by these linked resources, because it sees the same source file multiple times then and doesn't recognize that it's the same file actually. Alex
* | GenEx: Create cmGeneratorTargets for imported targets.Stephen Kelly2012-10-221-0/+4
|/ | | | | | | | | | | | | We're going to need to link to them, and all the linking API is moving to cmGeneratorTarget. Skip imported targets when iterating over cmGeneratorTargets in places where we only want targets we build. The GetGeneratorTargets result now includes IMPORTED targets where it didn't before. The GetTargets result, which was what used to be called in these methods does not include IMPORTED targets. This doesn't relate to any known bugs, but in some future uses of GetGeneratorTargets it will be important, so starting the convention and being deliberate now is a good idea.
* Fix config-specific INCLUDE_DIRECTORIES in multi-config generatorsStephen Kelly2012-10-171-1/+2
| | | | | | | | Commit 08cb4fa4 (Process generator expressions in the INCLUDE_DIRECTORIES property, 2012-09-18) contained an incorrect assumption that CMAKE_BUILD_TYPE was set on the makefile for each generated configuration in multi-config generators. Fix that by making the GetIncludeDirectories API depend on the config.
* Move GetIncludeDirectories to cmGeneratorTarget.Stephen Kelly2012-09-191-3/+5
|
* Merge topic 'HandleMacFrameworkIncludeDirs_13465'David Cole2012-08-201-0/+10
|\ | | | | | | | | | | | | a3815e6 -fix line length 9110d0e Eclipse on OSX: improve handling of framework include dirs (#13367) d97b385 Eclipse on OSX: fix handling of framework include dirs (#13464)
| * -fix line lengthAlex Neundorf2012-08-161-3/+3
| | | | | | | | Alex
| * Eclipse on OSX: improve handling of framework include dirs (#13367)Alex Neundorf2012-08-161-0/+10
| | | | | | | | | | | | | | | | | | | | It seems that if cmake finds something like the following: /System/Library/Frameworks/GLUT.framework/Headers Eclipse doesn't like that and wants to have /System/Library/Frameworks instead Alex
* | Eclipse: fix #13358: don't create bad linked resourcesAlex Neundorf2012-08-161-86/+0
|/ | | | | | | | | | | | | | directory where the project file is located (${CMAKE_BINARY_DIR}), which can happen e.g. for EXECUTABLE_OUTPUT_PATH and related variables. Now, it seems this code never worked. If EXECUTABLE_OUTPUT_PATH was set to point into a subdir of CMAKE_BINARY_DIR, the code did nothing. If it pointed directly at CMAKE_BINARY_DIR or some other location, it created a linked resource. I tested this with Eclipse Europa (3.3) and Juno (4.2), and in this case both versions of Eclipse complained that this is a bad location for a linked resource. Alex
* Eclipse: fix #13358: don't create bad linked resourcesAlex Neundorf2012-07-281-0/+14
| | | | | | | Don't create linked resources which point to CMAKE_BINARY_DIR itself or one of its parent dirs. Eclipse complained about that. Alex
* Ninja: enable ninja support everywherePeter Kümmel2012-07-201-2/+0
|
* Merge topic 'ninja-cldeps'David Cole2012-06-191-2/+4
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | eb410e8 Ninja: disable cldeps for bcc32, it's too old, and ninja would also not build 5ead31d Ninja: try work around for bcc32 bug 1333b57 Ninja: build server fixes 9081e3a remove warning about unused parameter f430bea Ninja: maybe this fixes the bcc32 build f2c1288 Ninja: msvc6 for-scoping 44b9bbc Ninja: build with old msvc versions 57156a5 Ninja: build server fixes f1abdce Ninja: some bytes of the rc files couldn't be piped correctly 2de963d Ninja: don't remove space between command and parameters 50b6f33 Ninja: build cmcldeps with mingw c05653e Ninja: try to make GetProcessId visible ab245ff Ninja: but cl supports /nologo ... bf58e9a Ninja: no /nologo option in old rc.exe 2fb07fc Ninja: Eclipse and KDevelop fixes for ninja 518c065 Ninja: don't pollute build dir with preprocessed rc files ...
| * Ninja: Eclipse and KDevelop fixes for ninjaPeter Kuemmel2012-06-151-2/+4
| | | | | | | | Thx to Claus Klein
* | Eclipse: parallel build also for "Build project" #13287Alex Neundorf2012-06-131-2/+5
|/ | | | | | | Use ${CMAKE_ECLIPSE_MAKE_ARGUMENTS} also for the overall build command, not only for the per-target commands. Alex
* fix #13054: support OBJECT libraries in EclipseAlex Neundorf2012-03-301-0/+2
| | | | Alex
* Merge topic 'target-include-directories'David Cole2012-03-081-3/+7
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | d662dff Fix shadowed variable warning on dashboard results f66e735 Fix compiler warning reported on older Borland dashboard. d90eed4 Fix compiler error reported on older Borland dashboard. 8233636 Update the documentation regarding INCLUDE_DIRECTORIES. d899eb7 Call ExpandVariablesInString for each target's INCLUDE_DIRECTORIES c21db87 Make search paths ordered and unique 22021f0 Remove cmMakefile::GetIncludeDirectories 9106b56 Extract and use the INCLUDE_DIRECTORIES target properties. 840509b Keep the INCLUDE_DIRECTORIES target property up to date. a4d5f7b Add API to get the ordered includes for a target. 8adaee2 CMake: Eliminate cmMakefile::IncludeDirectories 7620932 Remove include flags memoization. 97a5faa Make it safe to call this method without creating duplicates. edd5303 Refactor GetIncludeFlags to take includes instead of fetching them
| * Extract and use the INCLUDE_DIRECTORIES target properties.Stephen Kelly2012-02-221-3/+7
| | | | | | | | | | | | | | | | | | Eliminate callers of cmMakefile::GetIncludeDirectories. All callers of GetIncludeDirectories should go through the local generator object. Only the local generator calls cmTarget::GetIncludeDirectories directly.
* | Factor cmInstallType out of cmTarget::TargetTypeBrad King2012-02-271-4/+0
|/ | | | | | The purpose of the TargetType enumeration was overloaded for install type because install rules were once recorded as targets. Factor the install types out into their own enumeration.
* Eclipse: use new variable CMAKE_ECLIPSE_GENERATE_SOURCE_PROJECTAlex Neundorf2011-11-191-1/+10
| | | | | | | | | | | | | Previously ECLIPSE_CDT4_GENERATE_SOURCE_PROJECT was used, but the new name CMAKE_ECLIPSE_GENERATE_SOURCE_PROJECT is more in line with the general naming conventions in cmake, and, more importantly IMO, in cmake-gui it now appears right next to the other eclipse-related variables, which all start with CMAKE_ECLIPSE_. A warning is printed if the old variable is TRUE and the new one isn't, so users should notice that they have to enable the new one. Alex
* Eclipse: create links to subprojects also in the source-project (#12579)Alex Neundorf2011-11-191-5/+15
| | | | Alex
* Merge topic 'FixTargetsInVirtualFoldersForEclipseIndigo'David Cole2011-11-081-1/+5
|\ | | | | | | | | | | d31b1ac Eclipse: quote the build dir (to make it work with spaces) 0576331 Eclipse: make targets work from any directory
| * Eclipse: quote the build dir (to make it work with spaces)Alex Neundorf2011-11-011-2/+2
| | | | | | | | | | | | | | | | When creating the targets for Eclipse, quote the directory in which make should change. Otherwise it will fail if the path contains with spaces. Alex
| * Eclipse: make targets work from any directoryAlex Neundorf2011-10-311-1/+5
| | | | | | | | | | | | | | | | | | Set the working directory for make targets which are associated to virtual folders, otherwise Eclipse simply runs make from the current working directory (where Eclipse has been started), and where probably not the correct makefile is located. Alex
* | Eclipse: warn if CMAKE_BINARY_DIR is subdir of CMAKE_SOURCE_DIRAlex Neundorf2011-11-011-0/+10
|/ | | | | | | | | Eclipse doesn't handle this case well. When doing out-of-source builds we create a linked resource which points to CMAKE_SOURCE_DIR, so the user can browse the source dir in Eclipse. This is not possible when the build dir is a subdir of the source dir. Alex
* Eclipse: fix #12417, don't create wrong src pathentriesAlex Neundorf2011-10-231-0/+13
| | | | | | | | | | | | Actually the Eclipse generator now does not create any CDT_SOURCE pathentries anymore, since I was not able to find out what they are good for, not even by asking on the cdt-dev mailing list. So, at least the warning from eclipse about bad pathentries are gone this way, and I didn't see anything which was not working anymore. Let's see whether we can find out what they are good for. Alex
* Eclipse: add Build and Clean targets to targetsAlex Neundorf2011-10-231-2/+31
| | | | | | | | With this commit the virtual folder for the targets now have "Build" and "Clean" targets associated to them, so you can build and clean per-target now in the project explorer. Alex
* Eclipse: move code for generating links to targets into separate functionAlex Neundorf2011-10-231-79/+83
| | | | Alex
* Eclipse: move code for generating links to projects into separate functionAlex Neundorf2011-10-231-27/+36
| | | | Alex
* Eclipse: add virtual folder for each targetAlex Neundorf2011-10-191-7/+96
| | | | | | | | For each target a virtual folder is created, which contains one virtual folder for each sourcegroup, which contain links to the actual source files (#12294, #12223) Alex
* Eclipse: don't create VirtualFolders if not supportedAlex Neundorf2011-10-151-21/+24
| | | | | | | | Eclipse versions before 3.6 (Helios) did not support VirtualFolders yet (#12479), so only create them if Eclipse is new enough. Alex
* Detect whether the current Eclipse version supports VirtualFoldersAlex Neundorf2011-10-151-0/+20
| | | | | | | | VirtualFolders are supported since 3.6 (Helios). Next patch will be to actually make use of the new flag SupportsVirtualFolders. Alex
* fix #12392: handle CMAKE_CXX_COMPILER_ARG1 for Eclipse projectsAlex Neundorf2011-10-011-2/+11
| | | | | | | CMAKE_CXX/C_COMPILER_ARG1 have to be used for finding the include dirs and builtin macros, so Eclipse can do code completion Alex
* Also put builtin include dirs into CodeBlocks project fileAlex Neundorf2011-08-011-4/+5
| | | | | | | | Refactor code from CMakeFindEclipseCDT4.cmake so it can be used alkso for CodeBlocks, and move it into new file CMakeExtraGeneratorDetermineCompilerMacrosAndIncludeDirs.cmake. Alex
* Remove useless line of codeAlex Neundorf2011-08-011-1/+0
| | | | Alex
* -fix VirtualFolders in Eclipse under WindowsAlex Neundorf2011-05-061-4/+11
| | | | | | | | Under Windows "locationURI" must be used for virtual folders, while "location" must be used only for linked folders. Under Linux it doesn't seem to matter. Alex
* Eclipse projects: created one linked resource for each subprojectAlex Neundorf2011-02-131-19/+52
| | | | | | | | Now a virtual folder "Subprojects" is created, and in this virtual folder is a linked resource for each project(). This can be considered a fix for #11657 Alex
* Add XML escaping for directory name in Eclipse projects (#11658)Alex Neundorf2011-02-121-2/+4
| | | | Alex
* Fix XML escaping for target names in Eclipse project files (#11658)Alex Neundorf2011-02-121-2/+3
| | | | Alex
* Fix XML escaping for the project() name in Eclipse projects (#11658)Alex Neundorf2011-02-121-3/+5
| | | | Alex
* Fix crash in Eclipse generator with empty project (#11616)Alex Neundorf2010-12-211-1/+1
| | | | | | | If there was no language at all enabled, CMAKE_BUILD_TYPE was empty, which was not expected, and made the generator crash. Alex
* Add cache var CMAKE_ECLIPSE_MAKE_ARGUMENTS when using the Eclipse generatorAlex Neundorf2010-12-121-8/+11
| | | | | | | | This variable can be set to command line arguments which will be passed to make when eclipse invokes make, e.g. you can enter "-j8" to get 8 parallel builds (#9930) Alex
* Don't disable colors in the CodeBlocks generator and minor cleanup.Alex Neundorf2010-11-111-10/+0
| | | | | | | Since now the only users of SetToolSupportsColor() are gone, this method is removed too. Alex
* Remove trailing whitespaceAlex Neundorf2010-11-111-33/+33
| | | | Alex
* -don't add the INCLUDE env.var twice to the Eclipse project fileAlex Neundorf2010-04-191-1/+0
| | | | Alex
* -fix bug for Eclipse projects where targets which are in a subdir which has ↵Alexander Neundorf2010-02-131-19/+19
| | | | | | | | | | | | | | the same name as the project (... and so the linked resource) could not be built http://public.kitware.com/Bug/view.php?id=9978 Now instead of one linked resource for each project() just one linked resource to the top level source directory is created. This should really avoid this type of name clashes. And to me it looks also much less confusing. Hopefully the name "[Source directory]" containing a space and square brackets doesn't lead to problems somewhere. Here it works. Alex
* fix line lengthsAlexander Neundorf2009-12-301-2/+3
| | | | Alex
* fix the way the PATH and other related env.vars are stored in the eclipse ↵Alexander Neundorf2009-12-231-21/+79
| | | | | | | | | | | | | | | | | | project file when using MSVC Before this commit, the value of PATH at cmake time was put into the eclipse project file. The problem with this is that this will be lost the first time cmake is rerun from an build inside eclipse which was started without the environment externally already set. This patch now: -adds the env.var to the cache if it is not already in the cache -reuses the variable from the cache if it is in the cache, but not in the env. -uses the variable from the cache if it contains the whole content of the current env.var (e.g. if it is the full PATH plus the MSVC dirs) Also store INTEL_LICENSE_FILE in the project file if an Intel compiler is used. Alex
* disable cmake's verbose output in the Eclipse and KDevelop generatorsAlexander Neundorf2009-12-231-5/+4
| | | | | | | | | | | | The Eclipse and KDevelop generators set the VERBOSE environment variable to TRUE in the project files, because they must be able to "see" the full command lines and errors, otherwise they can't parse the errors. But the VERBOSE env.var. also enables cmakes own verbose output, which can be quite long. This commit introduces an environment variable CMAKE_NO_VERBOSE, which when set disables cmake's verbose output also when VERBOSE is set. This env.var is now set by both the Eclipse and the KDevelop generators. Alex
generated by cgit v0.12 at 2025-01-07 17:44:18 (GMT)