I have a situation where I want my CMakeLists.txt in a different place than my
source.
e.g.:
/some/path/project/CMakeLists.txt
/other/path/source/src/a.c
/other/path/source/include/a.h
Is there an easy way to say "process this CMakeLists.txt as if it were in
/other/path/source" (at least as
Hi,
This is a feature/problem on Windows, the library used for dynamic linking
is not the runtime module as Linux or OSX but the .lib, a collection of
symbols.
I suggest you could still use find_library() to locate the .lib file for
linking, then use find_file() to collect the runtime file then
Hi folks,
my cmake code reads version tags from the underlying git repository,
derives a new version with the help of the existing tags and then sets
that new version to the project() call. However, the cmake generate step
is not triggered when the version tags in the repository change, so
Hi Brad,
GCC : 6.1 and 7.2 on your side, and 6.3.0 on our side. That should be ok.
Did you build GCC on AIX by yourself or did you take it on some repository,
like BullFreeware?
Did you use cmake built on AIX for building a project with it? cmake tests are
98% OK here though that does not work
Hi All,
So from a previous threads, we were discussing pkgconfig and cmake
interoperability. One issue with using pkgconfig currently, is that the results
are completely flat. This is due to using the CLI to retrieve pkgconfig, which
gives the user all the flags from every transitive package.
t a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index 8662efc..96228d8 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 12)
-set(CMake_VERSION_PATCH 20180612)
+set(CMake_VER
On 06/12/2018 09:36 AM, REIX, Tony wrote:
> I never saw any package built on AIX using pthread or ppc64/pthread
> We have to understand why cmake is different.
We use C++11 std::thread. It requires GCC's -pthread flag on AIX,
and that flag changes the standard library that is used.
-Brad
--
Hi Brad,
You said:
> I think that should solve any problems with running CMake in environments
> different than it was built.
Yes. Tests may be OK though cmake does not work with complex package to build.
> The LIBPATH is
>
>
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 71f58d6bf7e02cd44c5d49d7b127ca6d99abdbeb (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 1f3221f365f269f3356de0ad0112cf68e4831fe6 (commit)
via
On 06/12/2018 03:38 AM, REIX, Tony wrote:
> Did you use cmake built on AIX for building a project with it?
> cmake tests are 98% OK here though that does not work with mariaDB.
The test suite passes and that is mostly made up of project-like tests.
It's also built using an existing CMake/CTest on
11 matches
Mail list logo