summaryrefslogtreecommitdiffstats
path: root/Source/cmMakefileTargetGenerator.cxx
Commit message (Collapse)AuthorAgeFilesLines
* Add CMAKE_GNUtoMS option to convert GNU .dll.a to MS .libBrad King2011-12-051-0/+10
| | | | | | | | | | | | | | | | Teach the Windows-GNU.cmake platform file to look for Visual Studio tools matching the target ABI. Add an extra step to the link command for shared libraries and executables that export symbols and on which a new GNUtoMS property is set (initialized by the CMAKE_GNUtoMS option). Tell the GNU linker to output a module definition (.def) file listing exported symbols in addition to the GNU-format import library (.dll.a). Pass the .def file to the MS "lib" tool to construct a MS-format DLL import library (.lib). Teach the install(TARGETS) command to install the MS import library next to the GNU one. Teach the install(EXPORT) and export() command to set the IMPORTED_IMPLIB property pointing at the import library to use the import library matching the tools in the importing project.
* Factor makefile generator link rule lookup into helper functionBrad King2011-12-051-0/+7
| | | | | This provides a place in the makefile generators to adjust the link rules for both libraries and executables.
* Fortran: Add support for free- and fixed-form flagsBrad King2011-08-311-0/+35
| | | | | | | Define a "Fortran_FORMAT" target and source file property. Initialize the target property from a "CMAKE_Fortran_FORMAT" variable. Interpret values "FIXED" and "FREE" to indicate the source file format. Append corresponding flags to the compiler command line.
* Make std::map usage more portable in language=>flags/defines mapsBrad King2011-05-171-14/+22
| | | | | | | | | | | | | | Older versions of GCC, the HP compiler, and the SGI MIPSpro compiler do not like the use of make_pair in this case and the conversions it requires: a value of type "const char *" cannot be used to initialize an entity of type "char [1]" /usr/include/g++-3/stl_pair.h:68: assignment of read-only location Instead use a map lookup pattern already used throughout the rest of our source tree.
* make compile command output optionalManuel Klimek2011-04-251-1/+2
|
* implement cxx command outputManuel Klimek2011-04-251-2/+19
|
* cache flags and definesManuel Klimek2011-04-251-45/+52
|
* refactor flags and definesManuel Klimek2011-04-251-55/+65
|
* Optionally pass include directories with response filesBrad King2011-03-171-2/+35
| | | | | | Create platform option CMAKE_<lang>_USE_RESPONSE_FILE_FOR_INCLUDES to enable use of response files for passing the list of include directories to compiler command lines.
* Factor old-style -D flags out from -I flag generationBrad King2011-03-151-0/+5
| | | | | | Move the GetDefineFlags call from cmLocalGenerator::GetIncludeFlags to all call sites so that the method exclusively constructs a string of include search path flags.
* Merge topic 'link-depend-def-file'Brad King2010-12-161-0/+6
|\ | | | | | | | | 3e27997 Make link rule depend on ".def" file (#11014)
| * Make link rule depend on ".def" file (#11014)Brad King2010-12-151-0/+6
| | | | | | | | | | | | | | When the link command line references a ".def" file the rule should depend on it. Inspired-By: Eric Huhtala
* | Merge topic 'cray-compiler'Brad King2010-12-161-7/+6
|\ \ | |/ |/| | | | | ab9ebb0 Fix Fortran .mod timestamps with Cray compiler
| * Fix Fortran .mod timestamps with Cray compilerBrad King2010-12-061-7/+6
| | | | | | | | | | | | | | | | | | | | | | | | Commit 34e1ac24 (Create Fortran info variables for .mod behavior, 2010-11-12) incorrectly taught GetFortranModuleDirectory to return a relative path. We really want to use "." as the module directory only as a workaround for compilers that do not do so by default. Therefore we need this default only when generating the compiler command line and not when scanning dependencies. Revert the previous change to GetFortranModuleDirectory and apply the change only at one of its call sites.
* | Make Fortran $obj.provides.build targets not .PHONYBrad King2010-12-061-1/+1
|/ | | | | | | Commit 60cd72d0 (Cleaned up generation of symbolic rules, 2006-02-15) incorrectly made these Makefile targets .PHONY even though the build rule touches an actual file. Correct it so that the copy_f90_mod and touch steps do not happen on every "make".
* Create Fortran info variables for .mod behaviorBrad King2010-11-121-0/+13
| | | | | | Define CMAKE_Fortran_MODDIR_DEFAULT and CMAKE_Fortran_MODOUT_FLAG variables to help some Fortran compilers generate .mod files in the current working directory.
* Define LINK_DEPENDS target property (#11406)Brad King2010-11-051-0/+7
| | | | | Custom Makefile link rules may need to depend on linker scripts. Define this property to allow user-specified link-time dependencies.
* Consolidate duplicate link rule make dependency codeBrad King2010-11-051-0/+31
| | | | | Factor code previously duplicated for library and executable rules into a common method.
* Merge branch 'tru64-make-includes'Brad King2010-06-151-3/+6
|\
| * Tru64: Use full-path include directives in Makefiles (#10569)Brad King2010-06-141-3/+6
| | | | | | | | | | | | | | | | Tru64's make(1) resolves relative paths in "include" directives with respect to the includer. This is inconsistent with all other known make tools. Note that this make tool treats the path literally so we cannot use our standard FULL path code which escapes spaces. Instead qualify the paths with $(CMAKE_BINARY_DIR) to avoid the problem.
* | Merge branch 'mingw-response-files'Brad King2010-06-151-2/+13
|\ \ | |/ |/|
| * Use platform variable for response file flagBrad King2010-03-111-1/+12
| | | | | | | | | | | | | | | | Create platform variable "CMAKE_<LANG>_RESPONSE_FILE_LINK_FLAG" to specify an alternative to "@" for referencing response files. It applies specifically to response files with linker options. See issue #10401.
| * Use forward slashes for objects in response filesBrad King2010-03-111-1/+1
| | | | | | | | | | | | | | | | | | | | Response files are parsed by tools, not by shells. We teach cmLocalGenerator::Convert() a new "RESPONSE" output format and use it for objects listed in response files. It does not do special slash or MSYS root translation like the "SHELL" format does. This is necessary for GNU tools on Windows to understand response file content. See issue #10401.
* | -fix GetFrameworkFlags() for Mac, which was broken with my last commitAlex Neundorf2010-05-031-2/+1
| | | | | | | | Alex
* | -improve crosscompiling from Linux to iphone (#10526)Alex Neundorf2010-05-011-6/+8
|/ | | | | | Patch by Karol Krizka Alex
* Fix line-too-long style violationsBrad King2009-10-231-1/+2
| | | | | The commit "Define per-target OSX_ARCHITECTURES property" introduced some long lines. This wraps them into multiple shorter lines.
* Define per-target OSX_ARCHITECTURES propertyBrad King2009-10-211-0/+4
| | | | | | | | | | | The CMAKE_OSX_ARCHITECTURES variable works only as a global setting. This commit defines target properties OSX_ARCHITECTURES OSX_ARCHITECTURES_<CONFIG> to specify OS X architectures on a per-target and per-configuration basis. See issue #8725.
* remove unused variables, reported by icpcAlexander Neundorf2009-10-031-3/+0
| | | | Alex
* Create INTERPROCEDURAL_OPTIMIZATION build featureBrad King2009-10-021-0/+5
| | | | | | | | This commit creates target and directory properties to enable the Intel interprocedural optimization support on Linux. Enabling it adds the compiler option '-ipo' and uses 'xiar' to create archives. See issue #9615.
* Introduce "build feature" lookup frameworkBrad King2009-10-021-0/+12
| | | | | | | This creates cmTarget::GetFeature and cmMakefile::GetFeature methods to query "build feature" properties. These methods handle local-to-global scope and per-configuration property lookup. Specific build features will be defined later.
* Centralize language flag addition for MakefilesBrad King2009-10-021-4/+11
| | | | | | We create cmMakefileTargetGenerator::AddFeatureFlags to consolidate addition of language flags. Currently it just adds the flags from generic per-language flag variables (AddLanguageFlags).
* Fix module definition file reference for VS6 NMakeBrad King2009-09-301-4/+4
| | | | | | When building through NMake with VS 6, the module definition file must be passed without spaces in the path. This is because 'cl -link' does not escape the spaces when passing the value on to the linker.
* Fix use of module .def files for MS toolsBrad King2009-09-291-0/+28
| | | | | | | We recognize .def source files and map them to the /DEF:<file> option in the MSVC tools. Previously this worked only for shared libraries. This commit cleans up the implementation and makes it work for executables too. See issue #9613.
* Convert CMake to OSI-approved BSD LicenseBrad King2009-09-281-14/+9
| | | | | | | 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.
* Do not call CollapseFullPath for PDB file namesBrad King2009-09-171-1/+1
| | | | | | | | | | | | | | | | Some vendor tools convert PDB file names given on the command line to lower-case before creating the file. When CMake places a mixed-case PDB file name into the build system, the file does not exist the first time and it is written with mixed case. After the first build though the native tool has created a lower-case version of the file. If CMake does CollapseFullPath again, the file exists so the actual-case lookup gets the lower-case name. This causes the build files to change so the project rebuilds. The solution is to avoid calling CollapseFullPath for files generated by the build. In the case of PDB files we already construct them from paths that have been collapsed, so we can just skip the call altogether. See issue #9350.
* ENH: Pass config to cmTarget::GetDirectory()Brad King2009-07-031-1/+1
| | | | | | | This teaches the makefile generators to always pass the configuration name to the cmTarget::GetDirectory method. Later this will allow per-configuration target output directories, and it cleans up use of the current API.
* ENH: Create cmMakefileTargetGenerator::ConfigNameBrad King2009-07-031-2/+2
| | | | | | This member stores the build configuration for which Makefiles are being generated. It saves repeated lookup of the equivalent member from cmLocalUnixMakefileGenerator3, making code shorter and more readable.
* ENH: Cleanup make progress rule generation codeBrad King2009-06-251-39/+0
| | | | | | | | This cleans up the Makefile generator's progress rule code. Instead of keeping every cmMakefileTargetGenerator instance alive to generate progress, we keep only the information necessary in a single table. This approach keeps most of the code in cmGlobalUnixMakefileGenerator3, thus simplifying its public interface.
* ENH: Allow projects to disable per-rule echo linesBrad King2009-03-161-14/+20
| | | | | | | | | This creates global property RULE_MESSAGES which can be set to disbale per-rule progress and action reporting. On Windows, these reports may cause a noticable delay due to the cost of starting extra processes. This feature will allow scripted builds to avoid the cost since they do not need detailed information anyway. This replaces the RULE_PROGRESS property created earlier as it is more complete. See issue #8726.
* ENH: Allow projects to disable per-rule progressBrad King2009-03-161-9/+22
| | | | | | | | This creates global property RULE_PROGRESS which can be set to disbale per-rule progress reporting. On Windows, progress reports may cause a noticable delay due to the cost of starting an extra process. This feature will allow scripted builds to avoid the cost since they do not need detailed progress anyway. See issue #8726.
* ENH: Factor out makefile progress rule commandsBrad King2009-03-161-24/+18
| | | | This factors duplicate progress rule code into a common method.
* BUG: Pass shared library export symbol in DEFINESBrad King2009-02-271-2/+1
| | | | | | | The <target>_EXPORTS macro defined for object files when built in a shared library <target> should be put in the <DEFINES> make rule replacement and not <FLAGS>. Also, it should honor the platform variable CMAKE_<LANG>_DEFINE_FLAG. See issue #8107.
* ENH: Define RULE_LAUNCH_* propertiesBrad King2009-02-101-0/+2
| | | | | | | This defines global, directory, and target properties RULE_LAUNCH_COMPILE, RULE_LAUNCH_LINK, and RULE_LAUNCH_CUSTOM. Their values specify 'launcher' command lines which are prefixed to compile, link, and custom build rules by Makefile generators.
* ENH: Give target in which custom commands buildBrad King2009-02-101-1/+1
| | | | | | This gives the cmTarget instance for which custom command rules are being generated to cmLocalUnixMakefileGenerator3::AppendCustomCommands. It will be useful in the future.
* BUG: Fix preprocess and assembly rule expansionBrad King2009-02-021-12/+12
| | | | | | The recent change to avoid expanding rule variables in informational and 'cd' commands broke the logical order in generation of preprocess and assembly rules. This corrects the order.
* BUG: Do not expand rule variables in info rulesBrad King2009-02-021-33/+36
| | | | | | | Previously the makefile generator would expand rule variables even on its progress and echo commands for object compilation rules (but not for link rules). This fixes the implementation to only expand rule variables on user-specified rules.
* ENH: Refactor custom command rule hashingBrad King2009-02-021-6/+5
| | | | | | | | | | This simplifies computation of custom command rule hashes to hash content exactly chosen as the custom commands are generated. Unfortunately this will change the hashes of existing build trees from earlier CMake versions, but this is not a big deal. The change is necessary so that in the future we can make optional adjustments to custom command lines at generate time without changing the hashes every time the option is changed.
* BUG: Fix color check for dependency scanningBrad King2008-10-151-2/+5
| | | | | Generation of color rules for dependency scanning messages did not account for disabling color at generation time. See issue #7814.
* ENH: Support object lists longer than 128K on MSVCBrad King2008-10-151-8/+29
| | | | | | We use response files to list object files for the MSVC linker. The linker complains if any response file is greater than 128K, so we split the object file lists into multiple response files.
* ENH: Factor out listing of objects on command lineBrad King2008-10-151-0/+38
| | | | | | Previously generation of object file lists for linker and cleaning command lines was duplicated for library and executable target generators. This combines the implementations.
generated by cgit v0.12 at 2024-11-08 21:17:19 (GMT)