Ruslan Baratov via CMake wrote:
It may be helpful in situations when you build package with examples. In
case when you want examples to work both as a part of a project
(add_subdirectory) or stand-alone (find_package).
I expect external_project may lead to more readability for this case,
On 05-May-15 20:01, Stephen Kelly wrote:
CHEVRIER, Marc wrote:
Hi,
Currently it is not possible to create an alias target for an imported
target (I.e. add_library with ALIAS keyword). But I don’t understand what
is the technical constraint or semantic reason behind this limitation. If
anybody
My need is the following:
I have two imported targets, let say, IMPORTED::TARGET and
IMPORTED::STATIC::TARGET
And I have a project which can be customised, through an option, by selecting
which imported target will be used (shared or static).
So I tried, at first place:
if
CHEVRIER, Marc wrote:
Hi,
Currently it is not possible to create an alias target for an imported
target (I.e. add_library with ALIAS keyword). But I don’t understand what
is the technical constraint or semantic reason behind this limitation. If
anybody can explain this limitation, it
Hi,
Currently it is not possible to create an alias target for an imported target
(I.e. add_library with ALIAS keyword). But I don’t understand what is the
technical constraint or semantic reason behind this limitation.
If anybody can explain this limitation, it will be nice.
--
Powered by
