Hi, Daniel, I've tried this, but it doesn't work, it returns same error as
before. And there are 2 lines in CMakeCache.txt:
//No help, variable specified on the command line.
A:BOOL=ON
Best Regards,
ashi
On Tue, Apr 2, 2013 at 7:44 PM, Daniel Pfeifer dan...@pfeifer-mail.dewrote:
Yeah, my current approach is exactly creating different toolchain files.
Best Regards,
ashi
On Wed, Apr 3, 2013 at 8:19 PM, Yngve Inntjore Levinsen
yngve.levin...@gmail.com wrote:
On 03. april 2013 13:13, Johannes Zarl wrote:
Hi,
On Tuesday, 2. April 2013, 06:42:47, Ashi wrote:
I
Hi,
On Tuesday, 2. April 2013, 06:42:47, Ashi wrote:
I think I find something to explain this: the config.cmake(the
CMAKE_TOOLCHAIN_FILE) is reloaded several times. on first-load, the A is
set, but on second-load and later-load, the A is not set. I think I can get
around this problem when A
On 03. april 2013 13:13, Johannes Zarl wrote:
Hi,
On Tuesday, 2. April 2013, 06:42:47, Ashi wrote:
I think I find something to explain this: the config.cmake(the
CMAKE_TOOLCHAIN_FILE) is reloaded several times. on first-load, the A is
set, but on second-load and later-load, the A is not set.
Hi all, I've a problem in using else() in CMAKE_TOOLCHAIN_FILE, all files
are:
#==CMakeLists.txt==
message(TEST)
#==config.cmake==
if(A)
message(A)
elseif(B)
message(B)
elseif(C)
message(C)
else()
message(FATAL_ERROR NONE)
endif()
and I run the cmake:
$ cmake
I think I find something to explain this: the config.cmake(the
CMAKE_TOOLCHAIN_FILE) is reloaded several times. on first-load, the A is
set, but on second-load and later-load, the A is not set. I think I can get
around this problem when A is kept set. However, I don't know how can I
keep the value
