Re: [CMake] global variable passing up via INTERNAL cache

2007-11-29 Thread Tal Blum
I only use one variable and I define 2 macros. The second macro is used to initialize the list before I call APPEND_INTERNAL_LIST(). Notice that I do not use a temp variable that is shared between calls and can cause problems. # A macro for passing lists between different directories # through an

Re: [CMake] global variable passing up via INTERNAL cache

2007-11-29 Thread James Bigler
Ha, ha. I just had this problem. This week in fact. The problem is that if you initialize the list it won't work. The following code worked for me. You have to have two variables. One for the building and one for the storing/using. MACRO(APPEND_VALUE VALUE) SET(temp_value ${MY_VALUE_

Re: [CMake] global variable passing up via INTERNAL cache variable

2007-11-28 Thread James Bigler
Erik Johansson wrote: 2007/11/27, James Bigler <[EMAIL PROTECTED]>: I got a hint that I could do this to set values that could be read by the CMakeLists.txt file above: You can also use get_directory_property. See for example how we use it in Licq [1] to get a the list of files from a subdire

Re: [CMake] global variable passing up via INTERNAL cache variable

2007-11-28 Thread Erik Johansson
2007/11/27, James Bigler <[EMAIL PROTECTED]>: > I got a hint that I could do this to set values that could be read by > the CMakeLists.txt file above: You can also use get_directory_property. See for example how we use it in Licq [1] to get a the list of files from a subdirectory (to implement co

Re: [CMake] global variable passing up via INTERNAL cache variable

2007-11-28 Thread James Bigler
On Nov 27, 2007, at 3:55 PM, Luigi CALORI wrote: I encoundered the same problems and in the end used the horrible hack to use a file where append, clear it in the main file. I think I saw a thread about this. Good to know in the future. I did figure out a solution without involving a file.