On 02/11/2015 04:19 AM, opensgu...@web.de wrote:
> Is there any chance the feature to support genex in DESTINATION the
> install() command will be added?
I've implemented it for install(TARGETS):
http://www.cmake.org/Bug/view.php?id=14317#c37959
That is the important one AFAICT. For other inst
Brad King ...> writes:
>
> Steve,
>
> On 07/26/2013 04:43 AM, Mantis Bug Tracker wrote:
> > http://www.cmake.org/Bug/view.php?id=14317
>
> What do you think about adding generator expressions to install
> DESTINATION options. In particular the $ genex
> would be useful in this case.
>
> Th
Brad King writes:
>
> Steve,
>
> On 07/26/2013 04:43 AM, Mantis Bug Tracker wrote:
> > http://www.cmake.org/Bug/view.php?id=14317
>
> What do you think about adding generator expressions to install
> DESTINATION options. In particular the $ genex
> would be useful in this case.
>
> Thanks,
>
Brad King wrote:
> On 07/31/2013 11:05 AM, Stephen Kelly wrote:
>> Config sensitive dirs are likely more common for libraries
>> than includes, so actually I think it would be fine to make that an error
>> and always do full evaluation.
>
> To clarify, the no-config rule is for INCLUDES DESTINATI
On 07/31/2013 11:05 AM, Stephen Kelly wrote:
> Config sensitive dirs are likely more common for libraries
> than includes, so actually I think it would be fine to make that an error
> and always do full evaluation.
To clarify, the no-config rule is for INCLUDES DESTINATION only, but full
with-co
Brad King wrote:
>> So, I think for the case of INCLUDES DESTINATION, we can either decide
>> and fix it now, or revert the change adding it for 2.8.12.
>
> Let's try to decide now and revert as a last resort.
>
> So the only reason we need partial evaluation is to leave
> configuration-dependent
On 07/31/2013 09:25 AM, Stephen Kelly wrote:
> As INCLUDES DESTINATION is already in master, that would be a behavior
> change, and probably need a policy.
Technically that will be true for the real DESTINATION values too
but I doubt anyone has installed to a path with "$<" in it. Since
INCLUDES
Brad King wrote:
>> The bug report is about adding genex support to those destinations.
>
> Yes, it's also the one that started this thread. Do we agree that
> full generate-time evaluation is appropriate for these? If so then
> the implementation will require BUILD_TYPE conditional blocks in
>
Brad King wrote:
>> I've pushed a INCLUDES-DESTINATION-partial-eval topic to my clone with
>> some ideas for it. Please let me know what you think.
>
> Are you proposing this for inclusion in 2.8.12?
Yes.
> IMO it can wait along with the rest.
As INCLUDES DESTINATION is already in master, that
On 07/31/2013 07:53 AM, Stephen Kelly wrote:
> I think two things are being confused here. One is the DESTINATION for
> things that are installed by the current command. Eg:
>
> install(TARGETS foo
>RUNTIME DESTINATION bin
>LIBRARY DESTINATION lib
>ARCHIVE DESTINATION lib
> )
> in
Brad King wrote:
> On 07/30/2013 09:46 AM, Stephen Kelly wrote:
>> That is, parameters to install(TARGETS) are evaluated at export time, and
>> otherwise the contents of the property are reproduced verbatim.
>
> Yes, I think this makes sense. The install rules run as part of
> the current projec
On 07/30/2013 09:46 AM, Stephen Kelly wrote:
> That is, parameters to install(TARGETS) are evaluated at export time, and
> otherwise the contents of the property are reproduced verbatim.
Yes, I think this makes sense. The install rules run as part of
the current project's build just like custom
Brad King wrote:
> On 07/29/2013 06:57 PM, Stephen Kelly wrote:
>> Yes, $ should work both before and after export.
>
> So the question is how to know whether to evaluate it during
> export or write it literally in the file. In this case we want
> to expand it during export because we want $ to
On 07/29/2013 06:57 PM, Stephen Kelly wrote:
> Yes, $ should work both before and after export.
So the question is how to know whether to evaluate it during
export or write it literally in the file. In this case we want
to expand it during export because we want $ to
refer to the build configurat
Brad King wrote:
> Steve,
>
> On 07/26/2013 04:43 AM, Mantis Bug Tracker wrote:
>> http://www.cmake.org/Bug/view.php?id=14317
>
> What do you think about adding generator expressions to install
> DESTINATION options. In particular the $ genex
> would be useful in this case.
Yes, $ should work
Steve,
On 07/26/2013 04:43 AM, Mantis Bug Tracker wrote:
> http://www.cmake.org/Bug/view.php?id=14317
What do you think about adding generator expressions to install
DESTINATION options. In particular the $ genex
would be useful in this case.
Thanks,
-Brad
--
Powered by www.kitware.com
Visit
The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=14317
==
Reported By:Fabian Saccilotto
Assigned To:
17 matches
Mail list logo
