| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
- Use a response file when enabled by
CMAKE_<LANG>_USE_RESPONSE_FILE_FOR_OBJECTS
- Enable for C and CXX with cl (MSVC)
- Enable for Fortran with ifort (Intel Fortran)
|
|
|
|
| |
a dependency of the link rule.
|
| |
|
|
|
|
| |
build directory. Converted Info.plist files to be generated directly instead of configured with make variables. The MACOSX_BUNDLE_* variables are now properties (and vars for compatibility).
|
|
|
|
| |
not link.
|
|
|
|
| |
rules are available. Enable use of archive construction rules on MSYS.
|
|
|
|
| |
CMAKE_<LANG>_ARCHIVE_APPEND, and CMAKE_<LANG>_ARCHIVE_FINISH to support creation of static archive libraries out of a large number of objects. See bug #6284.
|
|
|
|
|
|
|
|
| |
- Imported frameworks have the FRAMEWORK property set
- Added cmTarget::IsFrameworkOnApple method to simplify checks
- Also remove separate IMPORTED_ENABLE_EXPORTS property and just use ENABLE_EXPORTS since, like FRAMEWORK, it just represents the target type.
- Document FRAMEWORK keyword in INSTALL command.
- Updated IMPORTED_LOCATION property documentation for Frameworks
|
|
|
|
| |
cmMakefileLibraryTargetGenerator to cmMakefileTargetGenerator and use for cmMakefileExecutableTargetGenerator too. This addresses bug #6192.
|
|
|
|
| |
IMPLICIT_DEPENDS feature of custom commands when building in custom targets. Convert multiple-output pair checks to be per-target instead of global.
|
|
|
|
| |
incremental links work, incremental links are still broken for vs 2005 and greater because of the manifest stuff
|
|
|
|
| |
and install now. More work needed on the packaging step. See Tests/Framework for example use.
|
|
|
|
| |
support just added to the Xcode generator. BUG: Remove spurious warning and eliminate empty Libraries subdir inside built framework.
|
| |
|
|
|
|
| |
targets
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
CMake-SourceFile2-bp and CMake-SourceFile2-b-mp1 to trunk. This
commit is surrounded by tags CMake-SourceFile2-b-mp1-pre and
CMake-SourceFile2-b-mp1-post on the trunk.
The changes re-implement cmSourceFile and the use of it to allow
instances to be created much earlier. The use of cmSourceFileLocation
allows locating a source file referenced by a user to be much simpler
and more robust. The two SetName methods are no longer needed so some
duplicate code has been removed. The strange "SourceName" stuff is
gone. Code that created cmSourceFile instances on the stack and then
sent them to cmMakefile::AddSource has been simplified and converted
to getting cmSourceFile instances from cmMakefile. The CPluginAPI has
preserved the old API through a compatibility interface.
Source lists are gone. Targets now get real instances of cmSourceFile
right away instead of storing a list of strings until the final pass.
TraceVSDependencies has been re-written to avoid the use of
SourceName. It is now called TraceDependencies since it is not just
for VS. It is now implemented with a helper object which makes the
code simpler.
|
| |
|
| |
|
|
|
|
| |
files directly. The target-level rule must add dependencies on the file-level custom commands to drive them. This bug was introduced by the "fix" to bug 4377. This also restores the documented behavior that PRE_BUILD rules are treated as PRE_LINK rules on non-VS generators. Also fixed custom command dependencies on the rule file build.make so that custom commands re-run when the commands themselves change.
|
|
|
|
| |
targets. The module import libraries should never be used but some windows compilers always create them for .dll files since there is no distinction from shared libraries on that platform. The executable import libraries may be used to create modules that when loaded bind to symbols from the executables. This is an enhancement related to bug#4210 though not requested by it explicitly.
|
|
|
|
| |
library. This simplifies tracking down problems with trying to create import libraries for MODULEs.
|
|
|
|
| |
creation of rules to drive creation of extra outputs generated as side effects of another rule. Reimplemented generation of custom command multiple output rules to use it. Reimplemented soname symlink output dependencies to use it. Now if a symlink is deleted the library will be recreated with the symlink.
|
|
|
|
| |
clean rule for the import library. This is an incremental fix for bug #4210.
|
|
|
|
| |
directory containing the import library. This is an incremental step for bug#4210.
|
|
|
|
| |
are nearly the same. This is another step for bug#2240.
|
|
|
|
| |
Makefile and VS generators to instead ask each target for its output path. This significantly reduces total code size and centralizes previously duplicate code. It is also a step towards bug#2240.
|
|
|
|
| |
the output to the build shell. The calls have now been converted to call Convert() with SHELL.
|
|
|
|
| |
finishes addressing bug#4341.
|
|
|
|
| |
real file name used for the target. This addresses bug#3277.
|
|
|
|
| |
cmGlobalUnixMakefileGenerator3 to give access to all methods. Fixed broken custom targets with no commands for Borland makefiles when CMAKE_SKIP_RULE_DEPENDENCY is set.
|
|
|
|
| |
Default is 0.0, but the VERSION target property may change the value. Windows now has first-class support for dll and exe versioning. This addresses bug#1219.
|
|
|
|
| |
shell escapes because the script is not interpreted by a make tool.
|
|
|
|
| |
to have .. in the path. This makes the makefile generator consistent with the already working Xcode implementation of this feature. Also added a test for @executable_path/.. style settings for this property.
|
|
|
|
| |
strings work. Fix ZERO_CHECK target always out of date for debugging. Fix Makefile driving of custom commands in a custom target. Fix dependencies on custom targets not in ALL in VS generators.
|
|
|
|
| |
.dll files.
|
| |
|
|
|
|
| |
library name so that static and shared libraries of the same name can coexist in a single build directory.
|
|
|
|
| |
supposed to be a no-op anyway.
|
| |
|
|
|
|
| |
command in order to support longer link lines. This is needed only on platforms without response file support and that may have weak shells.
|
| |
|
|
|
|
| |
should be generated whether or not an object file in the target needs them. This useful and makes Makefile builds more consistent with VS IDE builds.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
is set then messages produced by makefiles will be in color if the native tool supports it. This addresses bug#3060.
|
| |
|
|
|
|
| |
module link commands
|
|
|
|
| |
of files to be removed without making the command line too long
|