>On Jan 21, 2008 7:40 AM, Brandon Van Every <[EMAIL PROTECTED]> wrote:
>This fails because add_library only understands target level
>dependencies. add_custom_command only generates file level
I think there is an inconsistence in the way ADD_CUSTOM_COMMAND run and how
dependencies are managed, b
Hi Brandon thanks for your help
problem with ADD_CUSTOM_TARGET is that runs allways even when it generate
files are up to date.
Quoted From Cmake docs:
Adds a target with the given name that executes the given commands. The
target has no output file and is ALWAYS CONSIDERED OUT OF DATE even if th
On Jan 21, 2008 8:39 AM, Brandon Van Every <[EMAIL PROTECTED]> wrote:
>
> then ADD_DEPENDENCIES(mylib DEPENDS blah).
Er, add_dependencies(mylib blah).
Cheers,
Brandon Van Every
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listin
On Jan 21, 2008 7:40 AM, Brandon Van Every <[EMAIL PROTECTED]> wrote:
> On Jan 21, 2008 6:16 AM, pepone. onrez <[EMAIL PROTECTED]> wrote:
> >
> > SET ( COPY_FILE cp -v )
>
> Better: ${CMAKE_COMMAND} -E copy
> Type cmake -E for details of OS portable commands.
>
> Your example build fails on Cygwin
On Jan 21, 2008 6:16 AM, pepone. onrez <[EMAIL PROTECTED]> wrote:
>
> SET ( COPY_FILE cp -v )
Better: ${CMAKE_COMMAND} -E copy
Type cmake -E for details of OS portable commands.
Your example build fails on Cygwin with the same problem.
Cheers,
Brandon Van Every
_
I Attach a incorrect file in the last mail, get the file attached to this
mail for view the correct example.
Thanks
cmake-customcommand-test.tar.gz
Description: GNU Zip compressed data
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman
I create and small test that's reproduce the problem described in this
thread
Download the cmake-customcommand-test.tar.gz attached to this mail
How to run the test.
uncompress it with "tar zxvf cmake-customcommand-test.tar.gz"
go to the build subdir "cd cmake-customcommand-test/build"
type "cma
I Create a small test to try replicate the problem and all works Fine at
first view and ADD_CUSTOM_COMMAND is called as expected.
I now thinking that can be a problem in how i concatenate values in OUTPUT
of the command, i go to change my script for clean and further inspect this
issue.
BTW i ca
I test various debug messages before my first post here and variable values
seems alright. Now ill try to reproduce the problem in a self contained
example and post here the results.
Thanks for all
On Jan 19, 2008 7:15 PM, Brandon Van Every <[EMAIL PROTECTED]> wrote:
> I'm going to take a wild g
I'm going to take a wild guess that one of your variables is emitting
extra quotes or open parentheses or something, such that the 2nd
ADD_CUSTOM_COMMAND gratuitously disappears. Suggest you message() all
your variables to see what they are, and also write a small test case
that simulates the beha
Hi Brandon
[EMAIL PROTECTED] ~/proyects/ydra-ipluginservice/build $ grep Moving * -R
[EMAIL PROTECTED] ~/proyects/ydra-ipluginservice/build $
I grep -R in the build dir and don't see the keword Moving that i put in
the Comment of the second ADD_CUSTOM_COMAND in any of CMake generated
files.
On Jan 19, 2008 11:50 AM, pepone. onrez <[EMAIL PROTECTED]> wrote:
>
> Case 2 - i don`t see that Cmake generated any rule for the second commands.
Did you grep all the files in the generated CMake tree? Perhaps they
were output to a different file.
Cheers,
Brandon Van Every
I know is not a good practice but this library only has generated code, and
the generated headers are need for build other applications made by third
parties. This is why i prefer to put in sources.
I atach here the relevant code for both cases and generated rules.
Case 1 - works as expected
Case
I solve the problem by adding the move step in the same ADD_CUSTOM_COMAND
Here is the new code. Any ideas for
#BEGIN
MACRO ( GENERATE_SLICE2CPP_RULES GENERATED_CPP_LIST GENERATED_HEADER_LIST )
FOREACH( SLICE_SOURCE_BASENAME ${ARGN} )
APPEND( GEN_SLICE_RULES_SLICE_DEPENDS
"${SLICE_SO
14 matches
Mail list logo