| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
| |
These generator expressions can only be used in link options properties.
These expressions return the arguments respectively for device and host link
step, otherwise return an empty string.
|
|\
| |
| |
| |
| |
| |
| | |
461efa7b51 Genex: Add $<LINK_LANGUAGE:...> and $<LINK_LANG_AND_ID:...>
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !4244
|
| |
| |
| |
| |
| |
| | |
This MR may help to solve issues #19757 and #18008
Fixes: #19965
|
|/
|
|
|
| |
Explain ``tgt`` at beginning of section.
Then refer to ``tgt`` without redundant reexplanations.
|
| |
|
|
|
|
|
|
| |
`if()` uses the internal `IsOn` call whild `$<BOOL:>` uses `IsOff`. For
historical reasons, these are not inverses of each other, so drop
mention of `if()` from the documentation of `$<BOOL:>`.
|
|\
| |
| |
| | |
Merge-request: !3939
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Fix the `COMPILE_LANGUAGE/CXX_COMPILER_ID` variant of the example to
have the same meaning as the `COMPILE_LANG_AND_ID` variant. The
inconsistency was introduced by commit 808b818063 (Genex: CompileLang
and CompileLangAndId now match against a list of ids, 2019-05-30,
v3.15.0-rc1~11^2~1).
Fixes: #19862
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Add entries in Modules and Modules/Platform to support
Objective-C++ compiler determination and identification.
Add Modules to check Objective-C++ compiler flags, source
compilations, program checks, etc...
Use OBJCXX as the designator of the language, eg:
project(foo OBJCXX)
Add various tests for Objective-C++ language features. Add
tests to preserve C++ handling of .M and .mm files when
Objective-C++ is not a configured language.
Co-authored-by: Cristian Adam <cristian.adam@gmail.com>
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add entries in Modules and Modules/Platform to support
Objective-C compiler determination and identification.
Add Modules to check Objective-C compiler flags, source
compilations, program checks, etc...
Use OBJC as the designator of the language, eg:
project(foo OBJC)
Add various tests for Objective-C language features. Add
tests to preserve C++ handling of .m and .mm files when
OBJC is not a configured language.
Co-Authored-By: Cristian Adam <cristian.adam@gmail.com>
|
|
|
|
|
|
| |
This allows for expressions such as:
$<COMPILE_LANG_AND_ID, CXX, GNU, Clang>
|
| |
|
|
|
|
|
| |
This allows for expressions like:
$<$<CXX_COMPILER_ID:Clang,GNU>:-DMY_PRIVATE_DEFINE>
|
| |
|
| |
|
|
|
|
|
| |
This capability complement MR !3190 and !3207
and is also needed to solve issue #18771.
|
|\
| |
| |
| |
| |
| |
| | |
ce078dda79 Relax the usage of TARGET_OBJECTS generator expression
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !3178
|
| |
| |
| |
| |
| | |
The geneator expression can now be used with static, shared, and
module libraries and executables.
|
| | |
|
| |
| |
| |
| |
| | |
These capabilities complement MR !3190
and is also needed to solve issue #18771.
|
| | |
|
| |
| |
| |
| |
| | |
The generator expression $<REMOVE_DUPLICATES:list> is string-valued, not
boolean-valued.
|
| |
| |
| |
| | |
This new capability is required to solve efficiently issue #18771
|
| | |
|
|/ |
|
|\
| |
| |
| |
| |
| |
| |
| | |
b53766b205 CUDA: Support compiler id and version generator expressions
b544e34af6 All VersionNode use the same capitalization pattern
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !3085
|
| |
| |
| |
| |
| | |
Introduce the CUDA_COMPILER_ID and CUDA_COMPILER_VERSION generator
expressions.
|
|/
|
|
|
|
|
| |
Extend the genex added by commit ca6ba3fee5 (Genex: Add a SHELL_PATH
expression, 2015-09-24, v3.4.0-rc1~37^2) to accept a `;`-list of paths,
convert them all, and generate a list separated by the native shell
`PATH``` separator.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Adds `Fortran_COMPILER_ID` and `Fortran_COMPILER_VERSION` generator
expression support to match equivalent `C_COMPILER_ID`,
`CXX_COMPILER_ID`, `C_COMPILER_VERSION`, and `CXX_COMPILER_VERSION`
support.
This is very helpful in the case where the C/C++ compiler suite is a
different type of compiler from the platform Fortran compiler and
projects use generator expressions to assign compiler flags and
definitions. (e.g. `GNU` C/C++ and `SunPro` Fortran on Linux)
|
| |
|
|
|
|
| |
This resolves #18550.
|
|
|
|
| |
This resolves #18549.
|
| |
|
| |
|
|
|
|
| |
And point out that STREQUAL is case sensitive.
|
|
|
|
|
| |
Makes things yet clearer and simpler.
Also correct remnant of "informational expression".
|
| |
|
| |
|
|
|
|
|
| |
* Consolidate examples
* Sort, and insert subsection headers
|
|
|
|
|
| |
Main classification by return type,
subclassification by dependences
|
|
|
|
|
| |
Rename Logical -> Boolean Generator Expressions.
It's the return type that helps us to sort the expression zoo.
|
|
|
|
|
|
|
|
|
| |
Before, the closely related signatures
$<condition:true_value>
$<IF:condition,true_value,false_value>
were explained in two different sections. The former section
was badly explained, with '0' and '1' in place of the formal
parameter 'condition'.
|
|
|
|
|
|
|
| |
That generator expressions enable conditional things
has not been said before.
Amended for nicer source format.
|
|
|
|
|
|
|
| |
No need to save a few characters on formal parameters.
Use this occasion to correct $<PLATFORM_ID:comp>:
the parameter is a platform_id, not a compiler_id.
|
|
|
|
|
|
| |
Expand "..." and "?", which could be mistaken as metacharacters
(and in the explanations of AND and OR actually were meant as
metacharacters).
|
|
|
|
|
|
| |
When using $<TARGET_PROPERTY:prop>, the value of prop comes from
the consuming target rather than the current target. Add a note to
clarify this.
|
| |
|
|
|
|
| |
in cmake-generator-expressions
|
| |
|