The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=15498
==
Reported By:chenliang xu
Assigned To:
On Mon, Apr 6, 2015 at 8:47 PM, Daniel Dilts dilts...@gmail.com wrote:
I have a custom executable that does some codegen to produce an
enumeration and a couple of tables. I need this to be run against each
source file before actual compilation. It needs include directories and
macro
I have a custom executable that does some codegen to produce an enumeration
and a couple of tables. I need this to be run against each source file
before actual compilation. It needs include directories and macro
definitions from the build system.
Is there a way to do this with a CMake build
Hi Folks,
This is actually a ctest question. It would be nice to be able to run a
series of test suites, serial (1-core), parallel (4-core) and long (8-core)
with a single execution of ctest using –j # of cores across multiple nodes of
a cluster. As a prototype, consider 2 nodes, 24-cores
You can specify the PROCESSORS (
http://www.cmake.org/cmake/help/v3.0/prop_test/PROCESSORS.html ) property
on a test that will tell ctest how man processors from the pool a test
should take. Note that this still requires that you specify the affinity
for the MPI processes.
On Mon, Apr 6, 2015 at
On Mon, Apr 06, 2015 at 19:08:37 +0200, Stephen Kelly wrote:
AFAICT, CMake does still know the command line in your output-target-flags-
once-in-ninja branch.
You just need to compute two outputs - once for writing the Ninja file
(containing variables), and again for writing the content
Currently the only compilers that support compiler features are:
Apple Clang versions 4.4 though 6.1.
GNU compiler versions 4.4 through 5.0 on UNIX and Apple.
Microsoft Visual Studio versions 2010 through 2015.
Oracle SolarisStudio version 12.4.
If you are interested in adding support for the
This is a somewhat artificial example, but is being used by a client as an objection for migrating to CMake.In the attached example, there are two source files: file1.F90 and file2.F90. Both define the module ‘foo_mod’, but only one is listed in CMakeLists.txt for any given configuration. (The
With the GNU compilers I am able to enable C++11 for a specific target
using:
set_target_properties( my_target PROPERTIES CXX_STANDARD 11 )
set_target_properties( my_target PROPERTIES CXX_STANDARD_REQUIRED ON )
When I build, this adds the flag -std=gnu++11, which is great.
If I compile with
I have a script that builds some package sort of files based on other
sources...
Basically a simplified version...
I would think since the output file of add_custom_command was referenced in
a INSTALL that those targets should get build before INSTALL... but using
MinGW Makefiles, 'make install'
20150406)
+set(CMake_VERSION_PATCH 20150407)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/post-receive
--
CMake
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 9ddbacdb74c7f3daf824decee9a1d900ddb44744 (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 b9c1eb4dcc801ea0a8f3f33aec58c5f9ab04026e (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 f762ceb26eb08ade9ea795cfee46b43850beb9bb (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 dfbde6fa991e60853a9f7ad165c4b8c8416a9ba4 (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 89ee57f6c79858bf350a5afce2ef588348dacb1c (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 d0e8149a661cd8580b3dbc7879b142c38d12592b (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 4bf326d69cf167d8deb892339d96dc44eddb416f (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 71a89464921583f66548ca91bddb132d2f55e024 (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 9b7213dc47d2477cb4ceb5032a9078412b5474bd (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 7ab2d0f90ecb24878ebeef37bbe845d0b88a066c (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 6ec818dad66ff35f2cfeb44c5527b01cf5d8f8fc (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 0e6b00ee494f341be104fa2a00543fc4acd43c6f (commit)
via
On 04/05/2015 11:07 PM, Matt McCormick wrote:
In each place that you ExpandListArgument to get the emulator
command and arguments and write them out before an executable
name, you need to be sure to make the proper call to escape
each argument. In each case the code just below your hunk
does
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 b698a9b255e5012a50a3b9a76342f3ccbb19fffd (commit)
via
On Sat, Apr 04, 2015 at 14:32:51 +0200, Stephen Kelly wrote:
On 04/02/2015 10:29 AM, Anton Makeev wrote:
Just to make sure, you mentioned that this file should be deprecated with
this new metadata.json,
is that correct?
I'm not sure I mentioned that, just that it's an externally defined
Ben Boeckel wrote:
On Sat, Apr 04, 2015 at 14:32:51 +0200, Stephen Kelly wrote:
However, there are other users
of the compile-commands.json, so it will remain and the feature for
generation of it will not be deprecated.
Or, to be more clear - it doesn't need to be deprecated as a result of
27 matches
Mail list logo
