Hi.
1. You can report this issue on the CMake gitlab (
https://gitlab.kitware.com/cmake/cmake/issues ). You will want to
attach the result of dumping all defines from the compiler ( xlc++ -dD
-E - < /dev/null or xlc++ -dM -E ). Currently it looks like we are
using '__IBMCPP__' to detect xlc++,
The official CMake binaries do the same thing as you and build with a
static libstdc++ and libgcc.
As far as dependencies we use static builds of those too, with most
being the version provided inside CMake, and an external openssl.
You can find the more information on the exact flags we are
See https://cmake.org/pipermail/cmake/2011-March/043320.html for a
discussion on overloading functions and the dangers that can occur.
On Wed, Apr 4, 2018 at 11:38 AM, Zaak Beekman wrote:
> I have been moving towards modern CMake where
>
We are pleased to announce that CMake 3.11.1 is now available for download.
Please use the latest release from our download page:
https://cmake.org/download/
Thanks for your support!
-
Changes in 3.11.1 since 3.11.0:
Are you trying to construct a BUILD_COMMAND line that looks like
CXXFLAGS=-g -02 -w && ./configure?
If so, you should be able to do that with the CMake -E env command option
like this ( Starting in CMake 3.1 ):
set(cxx_flags "-g -O2 -w")
set(command_to_run ${CMAKE_COMMAND} -E environment)
In general your options are to look at the command line or use
cmake-server mode to query the code model. The full set of include
directories is not known while configuring due to generator
expressions expanding after the configure step.
On Mon, Mar 26, 2018 at 9:45 PM, Saad Khattak
I am proud to announce that CMake 3.11.0 is now available for download at:
https://cmake.org/download/
Documentation is available at:
https://cmake.org/cmake/help/v3.11
Release notes appear below and are also published at
https://cmake.org/cmake/help/v3.11/release/3.11.html
Some of the more
uld be very happy to learn otherwise!)
>
> On Wed, Mar 28, 2018 at 2:14 PM, Robert Maynard <robert.mayn...@kitware.com>
> wrote:
>>
>> I am proud to announce that CMake 3.11.0 is now available for download at:
>> https://cmake.org/download/
>>
>> Documen
> if I (accidentally, or through ignorance) write code that would only work in
> CMake 3.x but not in 2.8.12, will the build fail or should I make sure to
> install 2.8.12 and test using that? if I ended up using an entirely new
> command that did not exist at the time of 2.8.12, but does
We are pleased to announce that CMake 3.10.3 is now available for download.
Please use the latest release from our download page:
https://cmake.org/download/
Thanks for your support!
-
Changes in 3.10.3 since 3.10.2:
CMake type is based on the OS platform, so you will be good with just
having the 64bit version of CMake. Both versions support generating 32
and 64 bit projects.
On Wed, Mar 14, 2018 at 6:12 PM, Tettey Nartey via CMake
wrote:
> I am not entirely sure if I am reaching the right
I am proud to announce the fourth CMake 3.11 release candidate.
https://cmake.org/download/
Documentation is available at:
https://cmake.org/cmake/help/v3.11
Release notes appear below and are also published at
https://cmake.org/cmake/help/v3.11/release/3.11.html
Some of the more
My initial thought is that the differences between -mmd and -md would
be pretty minimal. The original discussion on this change (
https://cmake.org/Bug/view.php?id=14914 ) has people agreeing with
that as this information is generated when the compiler builds each
file.
Have you used something
Thanks for spotting this and this will need to be handled for 3.13. I
have opened an issue to track the progress of the fix:
https://gitlab.kitware.com/cmake/cmake/issues/18466
On Wed, Oct 17, 2018 at 9:37 AM Hendrik Sattler wrote:
>
> Zitat von Robert Maynard :
> > * The "Bundle
No, if you need the executable to be launched by mpiexec you will need
to use some combination od custom_commands instead of try_run
On Tue, Oct 30, 2018 at 12:37 PM Hector E Barrios Molano
wrote:
>
> Hi CMake Users,
>
> Is there a way to use ${MPIEXEC_EXECUTABLE} during execution of a program
>
ies/Release: Add qthelp docs to binary archives
Help: Clarify command-line encoding of target_link_libraries items
curl: Update script to get curl 7.61.1
curl: Backport to work with CMake 3.1 again
curl: Update build within CMake to account for 7.61 changes
curl: add missi
installation
Marc Chevrier (1):
UseSWIG: fix regression for PHP language
Robert Maynard (2):
CUDA: Filter out host link flags during device linking
CUDA: Filter out non-static libraries during device linking
Vladimir Penev (1):
server: Fix assertion failure on directory paths
I am not seeing any generator expression
On Thu, Oct 25, 2018 at 2:25 PM Hendrik Greving
wrote:
>
> Hi @ll, does the generator expression above add a per-config subdir for
> multi-config generators?
> Thanks in advance
> --
>
> Powered by www.kitware.com
>
> Please keep messages on-topic and
The TARGET_FILE generator expression will give you the per-config
location for multi-config generators.
On Mon, Oct 29, 2018 at 11:15 AM Hendrik Greving
wrote:
>
> Subject: $
> Thanks
>
> On Mon, Oct 29, 2018 at 7:56 AM Robert Maynard
> wrote:
>>
>> I am not s
e PREFIX and SUFFIX (see above)
> don't appear to be set. Is it possible to retrieve the default library name
> on a given platform?
>
> On Mon, Nov 5, 2018 at 9:57 AM Robert Maynard
> wrote:
>>
>> That is correct behavior. OUTPUT_NAME is a customization poi
; of the test command. I can't use file(GENERATE to derive the target name and
> put the add_test part into a .cmake script because add_test is not scriptable.
> Thanks.
>
> On Mon, Nov 5, 2018 at 10:21 AM Robert Maynard
> wrote:
>>
>> Yes, you can do that. I d
At configure time you query OUTPUT_NAME target property
(https://cmake.org/cmake/help/v3.11/prop_tgt/OUTPUT_NAME.html) and if
not set you use NAME (
https://cmake.org/cmake/help/v3.11/prop_tgt/NAME.html )
On Mon, Nov 5, 2018 at 11:48 AM Hendrik Greving
wrote:
>
> Hi, is there a way to get the
> Same for RUNTIME_OUTPUT_NAME, LIBRARY_OUTPUT_NAME, PREFIX and SUFFIX
>
> On Mon, Nov 5, 2018 at 9:26 AM Robert Maynard
> wrote:
>>
>> At configure time you query OUTPUT_NAME target property
>> (https://cmake.org/cmake/help/v3.11/prop_tgt/OUTPUT_NAME.html) and if
>> n
King (12):
FindMPI: Pass -pthread to CUDA compiler through -Xcompiler
set_directory_properties: Restore in script mode
Flang: Fix command-line used to preprocess sources
CSharp: Fix regression in VS project type selection for custom target
curl: Update script to
With generator expressions making the reading of LOCATION non-viable
during configuration time ( since the actual location is now evaluated
at generate time ), the general solution is that you need to move your
LOCATION reading logic also to generate time. In general this means
using something
I believe that IMPORTED_LOCATION is safe to use.
On Wed, Nov 7, 2018 at 3:27 PM Hendrik Greving
wrote:
>
> So IMPORTED_LOCATION is obsolete as well? (since reading LOCATION is obsolete)
>
> On Wed, Nov 7, 2018 at 11:39 AM Robert Maynard
> wrote:
>>
>> With g
I am not seeing any cmake errors/warnings when I do so :)
On Wed, Nov 7, 2018 at 5:15 PM Hendrik Greving
wrote:
>
> Ok! Except (see above) I do not think one can actually read
> IMPORTED_LOCATION, can I?
> Thanks! - again!
>
> On Wed, Nov 7, 2018 at 2:07 PM Robert
ake) file that shared among things that use it for build
> targets and external projects for imported targets. Is there a way to find
> out whether a target is imported or a build target?
>
>
> On Wed, Nov 7, 2018 at 2:19 PM Robert Maynard
> wrote:
>>
>> I am not see
v 7, 2018 at 12:36 PM Robert Maynard
> wrote:
>>
>> I believe that IMPORTED_LOCATION is safe to use.
>> On Wed, Nov 7, 2018 at 3:27 PM Hendrik Greving
>> wrote:
>> >
>> > So IMPORTED_LOCATION is obsolete as well? (since reading LOCATION is
>&
about LINK_INTERFACE_MULTIPLICITYtoo.
> But I'm not in the situation of a "cyclic dependency" so I 'm not sure if it
> solve my problem.
> In my case (with B A and ImpLib) what would be the syntax?
>
> Il giorno mar 6 nov 2018 alle ore 06:30 Robert Maynard
> ha scritt
The target_link_libraries has a property called
LINK_INTERFACE_MULTIPLICITY that should help you out.
https://cmake.org/cmake/help/v3.13/command/target_link_libraries.html#cyclic-dependencies-of-static-libraries
On Tue, Nov 6, 2018 at 8:24 AM scrgiorgio wrote:
>
> Thanks for the help,
>
>
We are pleased to announce that CMake 3.12.3 is now available for download.
Please use the latest release from our download page:
https://cmake.org/download/
Thanks for your support!
-
Changes in 3.12.3 since 3.12.2:
I am proud to announce the first CMake 3.13 release candidate.
https://cmake.org/download/
Documentation is available at:
https://cmake.org/cmake/help/v3.13
Release notes appear below and are also published at
https://cmake.org/cmake/help/v3.13/release/3.13.html
Some of the more
Documentation changes can be done through the CMake project hosted on
gitlab. You would want to modify the file:
https://gitlab.kitware.com/cmake/cmake/blob/master/Help/variable/CMAKE_OSX_DEPLOYMENT_TARGET.rst
On Mon, Oct 1, 2018 at 11:13 AM James Turner via CMake
wrote:
>
>
> On 1 Oct 2018,
In news CUDA 10 release notes include the statement:
- Starting with CUDA 10.0, nvcc supports all versions of Visual Studio 2017
(past and upcoming updates)
So the problems of matching VS versions and CUDA versions should be behind
us.
On Sat, Aug 18, 2018 at 11:56 AM Brian Davis wrote:
>
>
Hi Jaffar,
CMake is still using Qt for the GUI, but we have moved from Qt4 to Qt5. If
you are able to tell me the explicit version of the GUI that last worked
for you that will help track down what is causing this regression.
On Fri, Sep 21, 2018 at 3:30 PM Jaffar Sidek
wrote:
>
I am happy to announce that CMake 3.13.0 is now available for download at:
https://cmake.org/download/
Documentation is available at:
https://cmake.org/cmake/help/v3.13
Release notes appear below and are also published at
https://cmake.org/cmake/help/v3.13/release/3.13.html
Some of the
You have defined 4 && 5 as public sources so that means that consumers
of mylib_core and mylib_core will build them. If you want the sources
to be part of mylib_core the sources should be private, if you want
the sources to be part of mylib_thing use interface. In general don't
use PUBLIC with
Just a heads up, CMake 3.15 is introducing policy 91 which removes the
runtime library from the default set of flags, and instead has targets
establish what runtime they want.
For more information see:
https://cmake.org/cmake/help/v3.15/prop_tgt/MSVC_RUNTIME_LIBRARY.html
On Tue, Jun 18, 2019 at
"export(PACKAGE)" command now does nothing unless enabled via
"CMAKE_EXPORT_PACKAGE_REGISTRY". See policy "CMP0090".
* The "Xcode" generator now requires at least Xcode 5.
* An explicit deprecation diagnostic was added for policy "CMP0066"
It look that starting with CMake 3.6 modification of system headers
will cause CMake to recompile projects. What version of CMake and your
compiler are you using?
On Mon, Jun 17, 2019 at 9:40 AM jl forums wrote:
>
> Hi,
> I want to create a full tag file and for this require to know the compiler
/usr/include/c++/8/istream /usr/include/c++/8/ios \
> /usr/include/c++/8/bits/basic_ios.h \
> /usr/include/c++/8/bits/basic_ios.tcc /usr/include/c++/8/ostream \
> /usr/include/c++/8/bits/ostream.tcc /usr/include/c++/8/bits/istream.tcc \
> /usr/include/x86_64-linux-gnu/c++/8/bits
I am proud to announce the third CMake 3.15 release candidate.
https://cmake.org/download/
Documentation is available at:
https://cmake.org/cmake/help/v3.15
Release notes appear below and are also published at
https://cmake.org/cmake/help/v3.15/release/3.15.html
Some of the more
jl forums wrote:
>
> ok, thanks
> by the way what about my ctags rule? how can i get the include path of an
> app? so that i can pass it to ctags and have my tags produced?
> thanks and regards
> jlm
>
> Le mer. 3 juil. 2019 à 16:52, Robert Maynard a
> écrit
instead.
* The "ADDITIONAL_MAKE_CLEAN_FILES" directory property is now
deprecated. Use the "ADDITIONAL_CLEAN_FILES" directory property
instead.
* The variable "CMAKE_AUTOMOC_RELAXED_MODE" is considered
deprecated. Support still exists but will be removed in future
versions.
In general I go with the source property approach, since you can pass
it a collection of files to be marked as CUDA.
If you are aware of when all sources have been added to a target you
can easily mark them all as cuda with:
get_target_property(source_files SOURCES)
Are you asking for a minimum CUDA SDK version or a restriction based
on the hardware of the machine?
We have no pre-built logic to enforce a minimum hardware component, as
we want to support building CUDA on a machine without a GPU.
As far as minimum CUDA SDK is concerned if you are doing it
You can use that method so you get the IDE features of VS2019 but the
VS2017 compiler.
On Fri, Aug 16, 2019 at 2:19 PM Michael Jackson
wrote:
>
> Why can't I do -T v141?
>
> --
> Mike Jackson
>
> On 8/16/19, 2:09 PM, "Kyle Edwards" wrote:
>
> On Fri, 2019-08-16 at 13:54 -0400, Michael
We are pleased to announce that CMake 3.15.2 is now available for download.
Please use the latest release from our download page:
https://cmake.org/download/
Thanks for your support!
-
Changes in 3.15.2 since 3.15.1:
I am happy to announce that CMake 3.15.0 is now available for download at:
https://cmake.org/download/
Documentation is available at:
https://cmake.org/cmake/help/v3.15
Release notes appear below and are also published at
https://cmake.org/cmake/help/v3.15/release/3.15.html
Some of the
We are pleased to announce that CMake 3.14.6 is now available for download.
Please use the latest release from our download page:
https://cmake.org/download/
Thanks for your support!
-
Changes in 3.14.6 since 3.14.5:
Is this with a clean build directory? The toolchain file is ignored
once CMake has run and has done compiler detection.
On Wed, Jul 17, 2019 at 11:29 AM hex wrote:
>
> I specified my toolchain like so:
>
> 1cmake -DCMAKE_TOOLCHAIN_FILE=myToolchain.cmake ..
>
> and created a toolchain file in
as by product.
On Wed, Jul 3, 2019 at 10:51 AM Robert Maynard
wrote:
>
> I completely forgot that the Makefiles based generators in CMake have
> a separate heuristic for determining system headers.
>
> If you use the Ninja generator I see the expected behavior:
> ~/W/t/nbuild $ sudo touch
Subsequent calls to project() from sub-directories is supported. For
calls to project from sub-directories it does everything but set
CMAKE_PROJECT_NAME.
On Wed, Jul 24, 2019 at 7:29 AM Jason Beach wrote:
>
> I've been reorganizing / updating our software cmake build. It currently uses
> a
ckages` to include to my
> `*-config.cmake`??
>
> On Thu, Jul 25, 2019 at 5:49 PM Robert Maynard
> wrote:
>>
>> target_link_libraries() when given an explicit path+filename as PUBLIC
>> ( not PRIVATE ) will be part of the transitive dependencies. An
>> exp
target_link_libraries() when given an explicit path+filename as PUBLIC
( not PRIVATE ) will be part of the transitive dependencies. An
explicit path+filename is not a target to CMake, nor will CMake
compute that it maps to an existing target ( be it imported or a
'normal' target ).
> This makes
es
Marc Chevrier (1):
FindPython: ensure interpreter is founded when cross-compiling
Marek Antoniak (1):
Fix allocation in CROSSCOMPILING_EMULATOR evaluation
Robert Maynard (2):
FindMPI: Updated to use INTERFACE_LINK_OPTIONS
FindMPI: make sure computed link flags are not de-duplicated
Saleem Abdulr
the initial
variadic specification, and not the updated specification.
On Thu, Jan 10, 2013 at 10:49 AM, Rolf Eike Beer e...@sf-mail.de wrote:
git://anongit.kde.org/scratch/**dakon/cmake-cxx11http://anongit.kde.org/scratch/dakon/cmake-cxx11
--
Robert Maynard
--
Powered by www.kitware.com
/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
--
Robert Maynard
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages
at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
--
Robert Maynard
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
We expect to have to make a RC2, which will include the genex fix.
On Fri, Mar 15, 2013 at 12:31 PM, Matthew Woehlke
matthew.woeh...@kitware.com wrote:
On 2013-03-15 11:57, Robert Maynard wrote:
I am happy to announce that CMake 2.8.11 has entered the release candidate
stage.
I guess
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
--
Robert Maynard
--
Powered by www.kitware.com
Visit other Kitware open-source projects
if the file
does not exist.
I hope to have a branch by the end of this week that will update the Ninja
generator with this fix.
--
Robert Maynard
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages
://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
--
Robert Maynard
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please
The CMake 2.8.11 release candidate continues. This is the last RC
unless a critical, must-fix issue is found. You can find the source
and binaries here:
http://www.cmake.org/files/v2.8/?C=M;O=D
Some of the notable changes in this release are:
- Introduced Target Usage Requirements
- Targets can
The CMake 2.8.11 release candidate continues. This is the last RC
unless a critical, must-fix issue is found. You can find the source
and binaries here:
http://www.cmake.org/files/v2.8/?C=M;O=D
Some of the notable changes in this release are:
- Introduced Target Usage Requirements
- Targets can
On behalf of myself, Ken, Bill, Brad, David, Alex, Eike, Steve, Eric,
Zach, Ben and the rest of the CMake team from all around the world, we
are pleased to announce that CMake 2.8.11 is now available for
download at:
http://www.cmake.org/files/v2.8/?C=M;O=D
It is also available from the usual
I can restart the meeting if people think it was useful.
On Tue, May 21, 2013 at 4:57 PM, Rolf Eike Beer e...@sf-mail.de wrote:
Eric Noulard wrote:
Sorry for the left over and my repeated absence on IRC for the CMake
meeting.
Since Dave left Kitware there has not been any such meeting.
I will restart the meetings next week!
On Tue, May 21, 2013 at 5:20 PM, Rolf Eike Beer e...@sf-mail.de wrote:
Robert Maynard wrote:
On Tue, May 21, 2013 at 4:57 PM, Rolf Eike Beer e...@sf-mail.de wrote:
Eric Noulard wrote:
Sorry for the left over and my repeated absence on IRC for the CMake
Did you verify that you have ssh access to g...@cmake.org?
On Fri, May 24, 2013 at 3:49 PM, Matthew Woehlke
matthew.woeh...@kitware.com wrote:
On 2013-05-21 15:54, Brad King wrote:
On 05/08/2013 05:09 PM, Matthew Woehlke wrote:
After chatting with Marcus how to resolve ParaView link errors
Due to memorial day I am unable to attend the weekly IRC developer
meeting. Lets restart the meetings next week.
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
That will be the goal.
Sent from my iPhone
On May 27, 2013, at 3:39 PM, Alexander Neundorf neund...@kde.org wrote:
On Monday 27 May 2013, Robert Maynard wrote:
Due to memorial day I am unable to attend the weekly IRC developer
meeting. Lets restart the meetings next week.
Every Monday
Some problems were reported with the 2.8.11 release. Thanks to the
swift work of Brad King, Stephen Kelly, Rolf Eike Beer and Modestas
Vainius, those problems have been fixed. We've prepared a 2.8.11.1 bug
fix release to address those issues.
The change log page for this bug-fix only release is
I will be holding a developer chat in the cmake irc channel starting
at 2pm est, or 18:00 gmt.
Server: freenode
Channel: #cmake
For those without an irc client installed: http://webchat.freenode.net/
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
I will be holding a developer chat in the cmake irc channel starting
at 2pm est, or 18:00 gmt.
Server: freenode
Channel: #cmake
For those without an irc client installed: http://webchat.freenode.net/
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
Will do.
On Mon, Jun 17, 2013 at 6:39 PM, Stephen Kelly steve...@gmail.com wrote:
Robert Maynard wrote:
@@ -666,7 +666,7 @@ public:
*/
const std::vectorstd::string GetOutputFiles() const
{ return this-OutputFiles; }
- void AddCMakeOutputFile(const char* file)
+ void AddCMakeOutputFile
I see no reason in using the register keyword. Currently compilers
ignore the register keyword, and basically it should be considered
noise when reading.
On Fri, Jun 28, 2013 at 11:37 AM, Sean McBride s...@rogue-research.com wrote:
Hi all,
Recently in clang trunk, they added a new warning
I will be holding a developer chat in the cmake irc channel starting
at 2pm est, or 18:00 gmt.
Server: freenode
Channel: #cmake
For those without an irc client: http://webchat.freenode.net/
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
(5):
cmCryptoHash: Increase alignment of HashFile buffer
cmcurl: Backport curl bug 1192 fix (#14250)
VS12: Add Visual Studio 12 generator (#14251)
VS12: Generate flag tables from MSBuild v120 tool files
FindBoost: Add -vc120 mangling for VS 12
Robert Maynard (1
Yeap, I was the one that introduced this error. I have just pushed a
new topic to next, that in testing on my windows machine fixed the
problem.
On Mon, Jul 22, 2013 at 9:27 AM, Brad King brad.k...@kitware.com wrote:
On 07/21/2013 11:59 AM, David Cole wrote:
Tests “ObjectLibrary” and
I will be holding a developer chat in the cmake irc channel starting
at 2pm est, or 18:00 gmt.
Server: freenode
Channel: #cmake
For those without an irc client: http://webchat.freenode.net/
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
I am happy to announce that CMake 2.8.12 has entered the release
candidate stage.
You can find the source and binaries here:
http://www.cmake.org/files/v2.8/?C=M;O=D
Some of the notable changes in this release are:
- Introduced target_compile_options command
- Specify compile options to use
Thanks,
I will add these to the blog post.
On Tue, Aug 20, 2013 at 4:46 PM, Stephen Kelly steve...@gmail.com wrote:
Robert Maynard wrote:
Some of the notable changes in this release are:
Some other things that I think are release-notes-worthy:
- New PUBLIC PRIVATE and INTERFACE options
The CMake 2.8.12 release candidate stream continues!
You can find the source and binaries here:
http://www.cmake.org/files/v2.8/?C=M;O=D
Some of the notable changes in this release are:
- Introduced target_compile_options command
- Specify compile options to use when compiling a given target.
The CMake 2.8.12 release candidate stream continues!
This is the last RC unless a critical, must-fix issue is found.
You can find the source and binaries here:
http://www.cmake.org/files/v2.8/?C=M;O=D
Some of the notable changes in this release are:
- Introduced target_compile_options command
Curious what the CMake 2.8.12 release brings? Join us Wednesday
October 16 at 1:30 EDT for the CMake 2.8.12 release webinar!
I will highlight the newest features and give a sneak peek into what's
in the pipeline for the next release.
To join us for this free, 15-minute event, please register
On behalf of myself, Ken, Bill, Brad, David, Alex, Eike, Steve, Eric, Zach,
Ben and the rest of the CMake team from all around the world,
we are pleased to announce that CMake 2.8.12 is now available for download at:
http://www.cmake.org/files/v2.8/?C=M;O=D
It is also available from the usual
Stephen,
As far as 'concepts' documentation is concerned, why don't we work together
to write a CMake blog article that rolls together the documentation
and an example?
Would that give the KDE people a good enough source for how to use the feature?
On Thu, Oct 10, 2013 at 12:02 PM, Stephen Kelly
...@gmail.com wrote:
Robert Maynard wrote:
If you ping me once the CMAKE_LANG_COMPILER_TARGET topic is in
master I will move the FindCuda module over to use it.
There is no guarantee that CMAKE_LANG_COMPILER_TARGET will get into master
before the release. That's why I recommended not merging
I am understanding properly that the last paragraph properly, this will fix
the problem that setting GIT_TAG to a named branch doesn't keep the branch
up to date with the remotes version of the branch?
Overall I really like this change to ExternalProject, and I see it being
more in line with how
If you are at Denver this week for IEEE Supercomputing
(http://www.supercomp.org), please stop by our booth (#4207) and say
hello. There will be CMake and software process experts available to
discuss best
practices and new developments in CMake/CTest/CPack and CDash. We'd
like to hear about what
The cmake repositories should be back online and behaving normally.
On Sun, Jan 5, 2014 at 3:07 PM, Eran Ifrah eran.if...@gmail.com wrote:
Thanks, I will try again tomorrow
On Sun, Jan 5, 2014 at 9:34 PM, Nils Gladitz nilsglad...@gmail.comwrote:
On 05.01.2014 19:26, Eran Ifrah wrote:
You could call CMAKE_USER_MAKE_RULES_OVERRIDE before the first project
call. Than have that override file set the CXX_INIT flags based on the
compiler/OS/current flags.
On Tue, Jan 14, 2014 at 4:14 PM, Jean-Christophe Fillion-Robin
jchris.filli...@kitware.com wrote:
Hi Folks,
For both Slicer
Some problems were reported with the 2.8.12 release. Thanks to the work of
Brad King, Robert Maynard, Rolf Eike Beer, Ruslan Baratov, and Ted Kremenek
those problems have been fixed. We've prepared a 2.8.12.2 bug fix release to
address those issues.
Some of the notable changes in this patch
I am proud to announce that CMake 3.0 has entered the release candidate stage.
Sources and binaries are available at:
http://www.cmake.org/files/v3.0/?C=M;O=D
Documentation is available at:
http://www.cmake.org/cmake/help/v3.0
Release notes appear below and are also published at
I am proud to announce the CMake 3.0 third release candidate.
Sources and binaries are available at:
http://www.cmake.org/files/v3.0/?C=M;O=D
Documentation is available at:
http://www.cmake.org/cmake/help/v3.0
Release notes appear below and are also published at
The one in VTK is a version from the findtbb project.
On Thu, Apr 3, 2014 at 9:33 AM, Brad King brad.k...@kitware.com wrote:
On 04/03/2014 03:45 AM, Julien Schueller wrote:
I'd like to maintain a module for intel tbb computing library:
https://gist.github.com/jschueller/9949814
Could someone
Dax projects has a different FindTBB, that is based off the FindTBB
that the OGRE3D project wrote.
I quickly scanned it, and it looks to me that it has better msvc support.
Here is that FindTBB:
https://github.com/Kitware/DaxToolkit/blob/master/CMake/FindTBB.cmake
On Thu, Apr 3, 2014 at 9:38 AM,
error string (#14882)
Nils Gladitz (1):
Policies: omit warnings about unset policies when they are
actually set to NEW
Robert Maynard (1):
Qt4Macros: Make QT4_CREATE_MOC_COMMAND a function
Sean McBride (1):
create_test_sourcelist: Initialize variable at declaration
Stephen Kelly
I am proud to announce the CMake 3.0 fifth release candidate.
Sources and binaries are available at:
http://www.cmake.org/files/v3.0/?C=M;O=D
Documentation is available at:
http://www.cmake.org/cmake/help/v3.0
Release notes appear below and are also published at
301 - 400 of 763 matches
Mail list logo