Re: [CMake] Weird behaviour of functions with list arguments

2011-01-19 Thread Johannes Zarl
On 01/18/2011 at 20:51, Alexander Neundorf a.neundorf-w...@gmx.net wrote: On Saturday 11 December 2010, Johannes Zarl wrote: So ARGV0 is not the same as the first argument of ARGV. Why? Is it that the ARGV and ARGN lists get flattened, but the ARGVx are assigned before that? How can I

Re: [CMake] Weird behaviour of functions with list arguments

2011-01-18 Thread Alexander Neundorf
On Saturday 11 December 2010, Johannes Zarl wrote: Hello, I noticed that when defining a function, one can access lists as arguments using named arguments or ARGV0..ARGVn, but not using ARGV and ARGN. To elaborate, assuming the function list_as_args defined as follows:

[CMake] Weird behaviour of functions with list arguments

2010-12-11 Thread Johannes Zarl
Hello, I noticed that when defining a function, one can access lists as arguments using named arguments or ARGV0..ARGVn, but not using ARGV and ARGN. To elaborate, assuming the function list_as_args defined as follows: function(list_as_arg) message(STATUS ${ARGC} arguments, ARGV: ${ARGV})