Instead of using the LOCATION property, you might consider doing
something along these lines, using the LOCATION_Release, LOCATION_Debug,
etc. properties. I do something similar to this on windows/MSVC to toss
extra files around that have an executable's full path:
foreach(_configname ${CMAKE_
Response Below
Inline...
On Fri, Feb 5, 2010 at 12:05 AM, Alan W. Irwin
wrote:
> On 2010-02-04 22:44-0600 Tim St. Clair wrote:
>>
>> On Thu, Feb 4, 2010 at 6:14 PM, Alan W. Irwin
>> wrote:
>>>
>>> Why not simply use install(FILES ... PERMISSIONS RENAME ... )?
>>>
>>> You would have to use
On 2010-02-04 22:44-0600 Tim St. Clair wrote:
On Thu, Feb 4, 2010 at 6:14 PM, Alan W. Irwin wrote:
Why not simply use install(FILES ... PERMISSIONS RENAME ... )?
You would have to use the target property LOCATION to find the
(cross-platform) filename associated with the target, and you w
Inline.. Re: Alan
On Thu, Feb 4, 2010 at 6:14 PM, Alan W. Irwin wrote:
> On 2010-02-04 23:38+0100 Eric Noulard wrote:
>
>> 2010/2/4 Tim St. Clair :
>>>
>>> Is there a clean way to copy the install target e.g.
>>>
>>> install (TARGETS foo DESTINATION bin)
>>>
>>> ~ install(TARGETS foo DESTINATIO
On 2010-02-04 23:38+0100 Eric Noulard wrote:
2010/2/4 Tim St. Clair :
Is there a clean way to copy the install target e.g.
install (TARGETS foo DESTINATION bin)
~ install(TARGETS foo DESTINATION loc2 RENAME foo_bar) <-doesn't exist.
I basically need to install the same target to *multiple* l
2010/2/4 Tim St. Clair :
> Is there a clean way to copy the install target e.g.
>
> install (TARGETS foo DESTINATION bin)
>
> ~ install(TARGETS foo DESTINATION loc2 RENAME foo_bar) <-doesn't exist.
>
> I basically need to install the same target to *multiple* locations
> with different names.
I th
Is there a clean way to copy the install target e.g.
install (TARGETS foo DESTINATION bin)
~ install(TARGETS foo DESTINATION loc2 RENAME foo_bar) <-doesn't exist.
I basically need to install the same target to *multiple* locations
with different names.
--
Cheers,
Timothy St. Clair
