Hi all,
I have been busy with upgrading my Intel ifort compiler from 14 to 16.
After I generated my Makefiles using CMake and compile my application I
get the following warning
ifort: command line remark #10148: option 'i_dynamic' not supported
Looking through the CMake mailing list archive
Hi,
For some reason, compiler flags passed to cmake, appear twice at build time.
I have a message line at the bottom of the cmakelist file, and it reports
the compilers flag as expected.
cmake \
-G "Eclipse CDT4 - Unix Makefiles" \
-D MPI=ON \
-D CMAKE_Fortran_FLAGS="-132
Solved problem from another post with similar space escaping.
set(PARAMS
"$(if $(verbose), --verbose)"
"$(if $(xml-output), --xml-output)"
"$(if $(run), --run=$(run))"
"$(if $(suite), --suite=$(suite))"
)
string(REPLACE " " ";" PARAMS ${PARAMS})
I would like to create a custom target to run UnitTest++ based unit tests that
has builtin default parameters.
For example:
make unit_test verbose=1 xml-output=1 run=test_name suite=suite_name
The actual parameters passed to the unit_test are:
unit_test --verbose --xml-output
I would like to create a custom target to run UnitTest++ based unit tests that
has builtin default parameters.
For example:
make unit_test verbose=1 xml-output=1 run=test_name suite=suite_name
The actual parameters passed to the unit_test are:
unit_test --verbose --xml-output
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 8429068d7c37d06e53b871811760419ab3e36455 (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, next has been updated
via 19fec70c0830e7c31b2b552ed6f560762950fbf0 (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 33f636264a5d830f67316dc6184f4056b3a3629f (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 17c151965d4c8f7d5a75e82341403fa43c7ca42f (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 58ec4932e348814d70d70f7e60ad0c2fcb2240f7 (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 31282e7854dfa4f28ebe26839599104b4f0b7008 (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 32f13fbe09fc8a5814bb3137abf2158cf1e24807 (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 0b0e28d30b1b3b91150ce88a3cb94c8bf39fa7ce (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 f104fe45fc9179e96065f576b0cc3529b29cd624 (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, next has been updated
via 1b1ec57d5aef2e96192b7bc5f16d1e5a215784a1 (commit)
via
On 02/24/2017 10:29 AM, Gregor Jasny via cmake-developers wrote:
> I just noticed that the Xcode generator creates one xcode project per
> project() call:
>
> Is that intentional?
Yes. The idea is that one can load the project for a subdirectory only.
It works well in VS and is at least
Hello,
I just noticed that the Xcode generator creates one xcode project per
project() call:
> $ find _build_xcode -name "*.xcodeproj" |grep -v CMakeFiles |grep -v Tests
> _build_xcode/CMake.xcodeproj
> _build_xcode/Source/CursesDialog/form/CMAKE_FORM.xcodeproj
>
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, next has been updated
via 6db54841a2c989474985a959a46caf688a0bab4f (commit)
via
Hi Soumaia,
It looks like your issues are not related to CMake but to the FAST project
it'self. I see you're already in contact with the user community on their
mailing lists,
https://lists.gforge.inria.fr/pipermail/nossi-tddft-users/2017-February/06.html.
Please continue to work through the
On 08/08/2016 02:04 PM, Brad King wrote:
> Ninja: Use full path for all source files
> https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=955c2a63
Unfortunately using an absolute path triggers a ninja limitation and
breaks rebuilds in some cases. See the issue [1] and MR to revert
the change
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, next has been updated
via 813afd66c2017ab3ef7385beb5d476ea16e0d0d0 (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, next has been updated
via 0da16ecd007f3a444aefa6f70fe075ed09dbb795 (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, next has been updated
via 3cc17beb1eb141920e16afe1a0739765db33ec88 (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, next has been updated
via 434c1123eb011a242e60279691df906e4a5244a7 (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, next has been updated
via fa678294b653cb39dda9e631e24aead5a308cb78 (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, next has been updated
via 617e34c8d5fed40eb5d1d99a4d1717c091c3ad2d (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 5eb4d9d80bbdbf316a1ccb2b062dcc9f34f95c3a (commit)
via
_VERSION_MINOR 8)
-set(CMake_VERSION_PATCH 20170224)
+set(CMake_VERSION_PATCH 20170225)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/
28 matches
Mail list logo
