| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
941be1d356 cmNinjaTargetGenerator: Clarify variable names for preprocessing conditions
33a8e0bb09 cmNinjaTargetGenerator: Simplify scan rule depfile selection
bff1871c39 cmNinjaTargetGenerator: Generalize GetScanRule helper
9f60e8aa52 cmNinjaTargetGenerator: Remove redundant conditions for dyndep blocks
43fe7e0c97 cmNinjaTargetGenerator: Revise conditions to clarify dyndep code paths
1416012f2c cmNinjaTargetGenerator: Clarify scan rule code grouping
f2eec04728 cmNinjaTargetGenerator: Clarify scan rule helper functions
170cfc764d cmNinjaTargetGenerator: Drop unnecessary mutation
...
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !5478
|
| |
| |
| |
| |
| | |
What is important about code paths for Fortran's explicit preprocessing
is that the compilation step following it does not do preprocessing.
|
| |
| |
| |
| |
| | |
The depfile can always be the first output of the build statement
with a `.d` suffix added. This approach easily avoids conflicts.
|
| |
| |
| |
| |
| | |
Allow the caller to provide any number of commands, and to choose which
ones get a launcher.
|
| |
| |
| |
| |
| | |
The GetScanCommand and GetScanBuildStatement helpers are called only in
code paths for dyndep. Drop their checks for this condition.
|
| |
| |
| |
| |
| |
| | |
All the scan-related code paths are actually about dyndep rather than
explicit preprocessing. It just happens that the implementation for
Fortran requires explicit preprocessing.
|
| | |
|
| |
| |
| |
| |
| | |
Revise names to clarify that these helpers are for the dependency
scanning commands, which may happen to preprocess.
|
| |
| |
| |
| | |
GetPreprocessScanRule's caller always has `vars.Source` set to `$in`.
|
| | |
|
| | |
|
| | |
|
| | |
|
|/ |
|
|\
| |
| |
| |
| |
| |
| | |
1134064e22 clang-tidy: allow OBJC and OBJCXX
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !5467
|
| | |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
f6e7d5f3a0 Reduce the scope of temporary cmProp variables and other improvements
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !5471
|
| | | |
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
5f782119c8 cmake-gui: Restore workaround for crash in file dialog
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !5472
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
In commit ce9dbceb42 (QtDialog: remove Qt4-only code, 2020-06-02,
v3.19.0-rc1~712^2~1) we removed an event filter that was thought to be
necessary only as a workaround for a bug in Qt. However, that bug was
fixed in Qt 4.5, and the file dialog still crashes as of Qt 5.14 without
the filter. Restore the workaround pending further investigation.
Fixes: #21400
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
bffb17be3d Xcode: Inherit target library and framework search paths from project
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !5463
|
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Xcode has multiple levels of build settings with priority in descending
order:
1. Target
2. Project
3. Workspace
4. SDK defaults
`CMAKE_XCODE_ATTRIBUTE_*` path variables add these to project level, but
linked frameworks and libraries override this in target level. Add the
`$(inherited)` macro to keep both in the final list.
Fixes: #21387
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Defer adding this command until post-3.19 development so that it
has more time to mature before being included in a release.
Issue: #21385
|
| |/ /
|/| | |
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
52152409c3 Makefiles: Honor CMAKE_EXPORT_COMPILE_COMMANDS for ASM
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !5464
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Generate build command for assembly file in `compile_command.json`.
Issue: #20059
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
c7b50349de cmSourceFile::GetPropertyForUser: return cmProp
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !5462
|
| |/ / /
| | | |
| | | |
| | | | |
also fix GetSafeProperty() return type
|
| |_|/
|/| | |
|
|/ / |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
f808f27919 cmLocalGenerator::GetRuleLauncher: return cmProp
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !5456
|
| | | |
|
|\ \ \
| | |/
| |/|
| | |
| | |
| | |
| | | |
cb2d01c182 CMakePresets.json: Don't warn if no path argument is given
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !5455
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
If --preset is specified with no path argument, use the current
directory as the source directory, the preset's binaryDir as the
binary directory, and don't issue the standard warning for no path
specified.
Fixes: #21386
|
| | | |
|
| |\ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
c619be2784 ccmake: Don't list --preset in --help
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !5428
|
| |\ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
ef03124237 CMake GUI: Add --browse-manual argument
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !5417
|
| |\ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
5dc23300b1 Xcode: Fix regression that automatically links libraries in source list
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !5432
|
| |_|_|_|/
|/| | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
|\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
3e36d5e846 cmGeneratorTarget: Refactor custom command dependency evaluation
c404f64289 cmCustomCommandGenerator: Collect genex target references in commands
2a640d4199 cmCustomCommandGenerator: Add move operations
fab772c3e1 cmAddCustomCommandCommand: Drop outdated comment
84fecbf214 cmLocalNinjaGenerator: Remove leftover local debugging comment
9e5e2d704a Remove unnecessary arbitrary CollapseFullPath second arguments
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !5435
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Previously we only used cmCustomCommandGenerator to evaluate generator
expressions for dependencies. Use it for command lines too. It also
collects target references for us, with backtraces.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
These will become target-level dependencies.
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Some calls to CollapseFullPath that already have an absolute path were
updated by commit 22f38c0d6b (cmake: avoid getcwd in `CollapseFullPath`,
2020-01-14, v3.17.0-rc1~171^2) to pass an arbitrary second argument to
prevent unnecessary `getcwd` calls. Since then, the KWSys
implementation of CollapseFullPath has learned to avoid unnecessary
`getcwd` calls on its own, so we can drop the arbitrary second arguments
to our CollapseFullPath calls.
|
| | | | | | |
|