At 05:13 PM 8/27/2006, Alan W. Irwin wrote:
>On 2006-08-27 16:30-0400 William A. Hoffman wrote:
>
>>At 12:00 PM 8/27/2006, Steve Johns wrote:
>>>Michael Bell wrote:
>ADD_CUSTOM_TARGET(makeExecutable ALL)
>FOREACH(file ${SCRIPTS})
> CONFIGURE_FILE(${CMAKE_CURRENT_SOURCE_DIR}/${file}
>>>
On 8/27/06, Alan W. Irwin <[EMAIL PROTECTED]> wrote:
On 2006-08-27 16:30-0400 William A. Hoffman wrote:
> At 12:00 PM 8/27/2006, Steve Johns wrote:
>> Michael Bell wrote:
ADD_CUSTOM_TARGET(makeExecutable ALL)
FOREACH(file ${SCRIPTS})
CONFIGURE_FILE(${CMAKE_CURRENT_SOURCE_DIR}/${
On 2006-08-27 16:30-0400 William A. Hoffman wrote:
At 12:00 PM 8/27/2006, Steve Johns wrote:
Michael Bell wrote:
ADD_CUSTOM_TARGET(makeExecutable ALL)
FOREACH(file ${SCRIPTS})
CONFIGURE_FILE(${CMAKE_CURRENT_SOURCE_DIR}/${file}
${EXECUTABLE_OUTPUT_PATH}/../${file}
@ONLY)
ADD_CUS
At 12:00 PM 8/27/2006, Steve Johns wrote:
>Michael Bell wrote:
>>>ADD_CUSTOM_TARGET(makeExecutable ALL)
>>>FOREACH(file ${SCRIPTS})
>>> CONFIGURE_FILE(${CMAKE_CURRENT_SOURCE_DIR}/${file}
>>> ${EXECUTABLE_OUTPUT_PATH}/../${file}
>>> @ONLY)
>>> ADD_CUSTOM_COMMAND(
>>> TARGET mak
Michael Bell wrote:
ADD_CUSTOM_TARGET(makeExecutable ALL)
FOREACH(file ${SCRIPTS})
CONFIGURE_FILE(${CMAKE_CURRENT_SOURCE_DIR}/${file}
${EXECUTABLE_OUTPUT_PATH}/../${file}
@ONLY)
ADD_CUSTOM_COMMAND(
TARGET makeExecutable
POST_BUILD
COMMAND chmod
ARGS
Brad King wrote:
> A completely different approach would be to make sure that
> myscript.pl.in has execute permission in the source tree.
...and a much simpler way is to not actually make them executable at all
but instead use FIND_PACKAGE(Perl) to get the perl executable and then
run the script b
Michael Bell wrote:
> I have one more issue to deal with. I have been relying on
> CONFIGURE_FILE to set some variables as my scripts get copied. How can
> I integrate that into this framework? cmake -E copy does not seem to
> set the variables.
You can instead run "cmake -P somescript.cmake" to c
Brad,
I have one more issue to deal with. I have been relying on
CONFIGURE_FILE to set some variables as my scripts get copied. How can
I integrate that into this framework? cmake -E copy does not seem to
set the variables.
thanks,
michael
On 8/24/06, Brad King <[EMAIL PROTECTED]> wrote:
Micha
Michael Bell wrote:
> Ok, it certainly makes sense that running cmake globally would
> simplify things, which is a good thing. It does seem to cause a
> problem for me that maybe you can help me work around:
>
> Say I have a several subdirectories, each with C++ code and perl
> wrappers to that co
Brad,
Ok, it certainly makes sense that running cmake globally would
simplify things, which is a good thing. It does seem to cause a
problem for me that maybe you can help me work around:
Say I have a several subdirectories, each with C++ code and perl
wrappers to that code. If I change the code
Michael Bell wrote:
> All,
>
> I am running cmake 2.4.3 on solaris.
>
> In many of my subdirectories, I have commands to copy files to a
> release directory and make some of them executable:
> ADD_CUSTOM_TARGET(makeExecutable ALL)
> FOREACH(file ${SCRIPTS})
>CONFIGURE_FILE(${CMAKE_CURRENT_SOU
All,
I am running cmake 2.4.3 on solaris.
In many of my subdirectories, I have commands to copy files to a
release directory and make some of them executable:
ADD_CUSTOM_TARGET(makeExecutable ALL)
FOREACH(file ${SCRIPTS})
CONFIGURE_FILE(${CMAKE_CURRENT_SOURCE_DIR}/${file}
${EXECUTABLE_
12 matches
Mail list logo
