_VERSION_MINOR 8)
-set(CMake_VERSION_PATCH 20170426)
+set(CMake_VERSION_PATCH 20170427)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/
I reckon it might be better to ignore the Fortran 90 module API for now.
Adding a function for that would mean that the linked target has to be
visible everywhere where the MPI package is being used with Fortran. Not
to mention that all projects using the F90 module API then would need to
have
On 04/26/2017 04:11 PM, Christoph Grüninger wrote:
> thanks for helping me out with the patch. Your wording of the message is
> better than my proposal.
> Please find attached an improved patch.
Thanks. This is a good start. Please see CONTRIBUTING.rst
and open a merge request on
On 01/18/2017 03:14 PM, Ben Boeckel wrote:
> Installing the target can install the objects.
[snip]
On 01/18/2017 02:47 PM, Chris Bieneman wrote:
> If this allowed TARGET_OBJECTS to be used in the install(FILES ...)
> command, then we could create an object library and a custom install
> rule for
Hi Brad,
thanks for helping me out with the patch. Your wording of the message is
better than my proposal.
Please find attached an improved patch.
Bye
Christoph
--
[..] Mathematicians are like theologians: we regard
existence as the prime attribute of what we study.
But unlike theologians, we
On 04/26/2017 04:14 AM, Alan W. Irwin wrote:
> On 2017-04-25 08:54-0400 Brad King wrote:
>> + else()
>> +# assume empty prefix because we expect the module to be dynamically
>> loaded
>> +set_target_properties (${SWIG_MODULE_${name}_REAL_NAME} PROPERTIES
>> PREFIX "")
>
> Yes, exactly.
On 04/25/2017 03:55 PM, Christoph Grüninger wrote:
> please find attached a first attempt to implement OPTIONAL for
> find_package. It is supposed to suppress all warnings and indicate the
> negative result by a single line of output. Unfortunately, I still get a
> warning and I could figure out
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 41b84b2220ef147d76f5b1291601c069397f854b (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 341486fd09e386529cfc93e0433dab9548357bcd (commit)
via
Is there any way to ask ctest run the set of tests impacted by a
commit/change ?
Or may be asking ctest to run only the tests that were built no later than
say 3 min. ago.
The use case is simple.
I do some modification in my code call the build tool (ninja in my case)
and I want ctest
to only run
On 2017-04-25 08:54-0400 Brad King wrote:
On 04/25/2017 04:08 AM, Alan W. Irwin wrote:
set PREFIX to "" for all languages not specifically covered by the if
and elseif blocks.
Do you mean
```
diff --git a/Modules/UseSWIG.cmake b/Modules/UseSWIG.cmake
index 277f4ca28a..bfe1a6f754 100644
---
Hi,
I'm new to cmake and we started using it to build proprietary embedded
projects with a proprietary toolchain. We love the new build system's
performance and its simplicity! Compared with what we were used to
have, it is just superior in every aspect we met, really great!
We hopefully based
12 matches
Mail list logo
