I'm in the progress of updating some code to clang in the NDK (since
they are not longer supporting GCC), and getting some ODR errors which
seem to be caused by a bad link configuration.
The generated executables / shared libraries seem to link to both the
selected standard library, and
_VERSION_MINOR 9)
-set(CMake_VERSION_PATCH 20170726)
+set(CMake_VERSION_PATCH 20170727)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/
Hi!
I did click on "Upgrade CDash", but that did not solve the problem.
After some investigations, I realized that the table
cdash.dynamicanalysissummary was missing (so the migration script did
not create it or failed to do so for any other reason). Once I created
it, everything worked.
According to Brad King, toolchain files are not intended for what I'm
asking about. I recall someone mentioning some built-in modules in
CMake that are responsible for toolchain and platform setup, that can
be overridden somehow. This is different from toolchain files AFAIK. I
apologize for being
Hi Robert,
I usually do all my platform and compiler specific customization in a
toolchain file [1]. Such a toolchain file is more or less standard CMake
script which get executed before the root CMakeLists.txt from the
project is processed. When invoking cmake for the first time you simply
Here is a spin-off topic from this thread which I believe may
be of general interest.
Bill Hoffman contacted me off list about the possibility of testing
cmake with a build of a rapidly changing CMake corresponding to the
tip of your release branch or possibly one of your development
branches
On 2017-07-25 17:48-0700 Alan W. Irwin wrote:
More later on those git bisect results when that process is completed.
As per usual, git bisect (along with ccache to speed up the process by
a noticable amount especially in the last 5 steps or so) is awesome.
Here is what it found:
