summaryrefslogtreecommitdiffstats
path: root/Source/cmExtraEclipseCDT4Generator.cxx
Commit message (Collapse)AuthorAgeFilesLines
* 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
* improve system/compiler specific settings of EclipseAlexander Neundorf2009-11-221-69/+41
| | | | | | | | | -use CMAKE_EXECUTABLE_FORMAT and CMAKE_SYSTEM_NAME to decide which binary parsers to load (ELF/Mach O/PE) -use CMAKE_(C|CXX)_COMPILER_ID to load the respective compiler error parser -remove EclipseToolchainType, which was a mixture between compiler and operating system Alex
* make testing the CodeBlocks and Eclipse generators easier by not requiring ↵Alexander Neundorf2009-10-201-2/+7
| | | | | | | | | | | | | the CMAKE_EDIT_COMMAND variable Both generators use the CMAKE_EDIT_COMMAND variable to determine whether they should add the edit_cache target, i.e. they don't add it if it's ccmake, since this does not work inside the output log view of Eclipse/Codeblocks. But instead of requiring the variable to be set they now check it for 0 and handle this appropriately. This should help Dave getting some testing for them :-) Alex
* Convert CMake to OSI-approved BSD LicenseBrad King2009-09-281-19/+13
| | | | | | | This converts the CMake license to a pure 3-clause OSI-approved BSD License. We drop the previous license clause requiring modified versions to be plainly marked. We also update the CMake copyright to cover the full development time range.
* Major improvement of the generated targets in Eclipse.Alexander Neundorf2009-09-161-13/+63
| | | | | | | | | | | | | | | Before this change all targets were displayed in the top level directory of the project. Now the targets are displayed in the correct directory. The targets "clean" and "all" are now created in every subdirectory. Also now the targets for just compiling one file, preprocessing one file, assembling one file are are created for Eclipse. Additionally all targets get a prefix now in eclipse, so that they are sorted in a way which makes sense (global targets first, then executable and libraries, then object files, then preprocessed, then assembly). Also this prefix gives the user a hint what the target is, i.e. whether it's a library or an executable or something else. Alex
* Put compiler defined macros into eclipse project filesAlexander Neundorf2009-09-161-0/+69
| | | | | | | | | Now gcc is queried also for the builtin definitions, and they are then added to the .cproject file. This should make the preprocessor highlighting in eclipse work better (#9272) Patch mostly from Miguel. Alex
* sync target generation with the CodeBlocks generatorAlexander Neundorf2009-09-101-79/+51
| | | | | | | | | | | Basically the code is now a copy of the one from the CodeBlocks generator, maybe this could move into a common helper function somewhere: -only insert GLOBAL targets from the toplevel directory -don't insert the edit_cache target if it calls ccmake, since this doesn't work in the output tab of Eclipse -add the /fast targets Alex
* ENH: don't enforce VERBOSE Makefiles, but set the env. var VERBOSE to 1 inAlexander Neundorf2009-03-131-1/+1
| | | | | | | when make is executed from within Eclipse. This way when building from the command line one can build also in non-verbose mode. Alex
* ENH: when using the Eclipse project generator, run gcc so that it tells usAlexander Neundorf2009-03-131-12/+48
| | | | | | | | | | its system include directories. These are catched in CMakeSystemSpecificInformation.cmake (only with the Eclipse generator) and then written by the Eclipse generator in the Eclipse project file. This way Eclipse can find the standard headers (#7585) Not sure CMakeSystemSpecificInformation.cmake is the best place to do this. Alex
* COMP: Fix const set find for Borland 5.5Brad King2009-01-141-2/+4
| | | | | | The Borland 5.5 compiler's STL set does not define correct signatures for its find() members, leading to build errors. This works around the problem.
* ENH: patch from Miguel,Alexander Neundorf2009-01-111-34/+54
| | | | | | | | | | | | | | | | | | | | | As it is today the generator creates linked resources to LIBRARY_OUTPUT_PATH and EXECUTABLE_OUTPUT_PATH if they are not a subdirectory of the binary dir, so that the IDE can detect the Binaries (this was addressed previously as a result of a bug report). Reduces code redundancy by encapsulating common behaviour for LIBRARY_OUTPUT_PATH and EXECUTABLE_OUTPUT_PATH in AppendLinkedResource. Addresses the two new variable names for these locations, CMAKE_LIBRARY_OUTPUT_DIRECTORY and CMAKE_RUNTIME_OUTPUT_DIRECTORY respectively. Finally, it is addressing a bug in the current code for relative paths in these variables. If it is a relative path to the binary dir, the IsSubdirectory call returns false and so it creates the linked resource. The created linked resource produces an error in the Eclipse IDE because the IDE expects it to be a full path. The patch now addresses this by concatenating the binary dir if it is a relative path.
* STYLE: remove debug outputAlexander Neundorf2009-01-101-1/+0
| | | | Alex
* BUG: fix #8073: also show targets created using add_custom_targets()Alexander Neundorf2009-01-101-34/+62
| | | | | | | -additionally also create the target/fast targets for Eclipse -skip preinstall and install/local, they should be only rarely used Alex
* BUG: remove the call to EnableInstallTarget(), don't know why it was there.Alexander Neundorf2009-01-101-1/+0
| | | | | | | This caused that always an install target was created which installed nothing, even if there was no install rule in the project. Alex
* BUG: fix #8105: don't hardcode "gcc" and "make" but use CMAKE_C_COMPILER andAlexander Neundorf2009-01-091-4/+19
| | | | | | CMAKE_MAKE_PROGRAM instead Alex
* BUG: apply patch from #8205, also fixes #8212: escape characters for XMLAlexander Neundorf2009-01-081-1/+15
| | | | | | when writing the eclipse project files Alex
* BUG: don't crash in the generator is EXECUTABLE_OUTPUT_PATH orAlexander Neundorf2008-08-061-3/+3
| | | | | | LIBRARY_OUTPUT_PATH are empty Alex
* ENH: add edit_cache target for Eclipse (if it's not ccmake, because thisAlexander Neundorf2008-04-031-0/+12
| | | | | | doesn't work inside the log view) Alex
* STYLE: patch part 3 from Miguel: follow naming style for variablesAlexander Neundorf2008-02-191-16/+16
| | | | Alex
* ENH: patch from Miguel part 2: if ECLIPSE_CDT4_GENERATE_SOURCE_PROJECT isAlexander Neundorf2008-02-191-65/+91
| | | | | | | | | | true, then the generator additionally generates eclipse project files in the source dir, since this is the only way to get cvs/svn working with eclipse This is off by default and the user has to enable it explicitely. If cmake can't write there it still continues. Alex
* ENH: patch part 1 from Miguel: use the cmake project name for the eclipseAlexander Neundorf2008-02-191-15/+34
| | | | | | project name Alex
generated by cgit v0.12 at 2024-11-01 12:24:13 (GMT)