t a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index cf21839..1a0e0d3 100644
--- a/Source/CMakeVersion.cmake
+++ b/Source/CMakeVersion.cmake
@@ -1,5 +1,5 @@
# CMake version number components.
set(CMake_VERSION_MAJOR 3)
set(CMake_VERSION_MINOR 15)
-set(CMake_VERSION_PATCH 20190719)
+set(CMake_VER
On Fri, Jul 19, 2019 at 2:52 PM Geoffroy J
wrote:
> Hello
>
> i have tried today to build a library using CMake Green Hills MULTI
> generator.
>
> It seemed to work quite well, but i end up not being able to configure the
> "-cpu" option for gbuild, which i need to set to "cortexa7".
>
> I've
Also, I would not suggest using the Java language support as reference as
it is not a first class supported language. As you said, it defines custom
functions and macros to do everything.
I would suggest you look at the C# support as it is a first class language
(meaning: you can add it to your
On Fri, 2019-07-19 at 21:30 +0100, hex wrote:
> dear community,
> I want to make a module for a language that is not supported by
> CMake.
> are there any restrictions in using add_executable for any language
> other than C / C++,
> must the build be constructed very similar to C language?
> I
dear community,
I want to make a module for a language that is not supported by CMake.
are there any restrictions in using *add_executable* for any language
other than C / C++,
must the build be constructed very similar to C language?
I was looking into Java module for reference and noted
Hello
i have tried today to build a library using CMake Green Hills MULTI
generator.
It seemed to work quite well, but i end up not being able to configure the
"-cpu" option for gbuild, which i need to set to "cortexa7".
I've went through the CMake code, i think something similar to
variable
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".
The branch, master has been updated
via 16bb46eaf3261a2991e35e22116fd8a51d031b15 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".
The branch, release has been updated
via fc2a7c8b3fc95b90ff69b7bb4a16b216b8ac3671 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".
The branch, master has been updated
via 573f1fc19b39f0aaea6c17c1c11c1f5bbde227d3 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".
The branch, master has been updated
via ca7ec2e188a6f66546a0f5dc9e76a6f24c22bfa6 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".
The branch, release has been updated
via 8d2299975393bb341d7afe8bdd200b8dbe3010e3 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".
The branch, master has been updated
via 1bdb5a3b5113a075393a0760888604684c43c64b (commit)
via
Yes, this was the problem. I was running cmake .. -LA to check the cache
variables /before/ setting the toolchain. You can even see that the
CMAKE_TOOLCHAIN_FILE is not set.
It is working now, thank you.
On 17/07/2019 18:12, Robert Maynard wrote:
Is this with a clean build directory? The
13 matches
Mail list logo
