The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=14499
==
Reported By:mar-na
Assigned To:
On 10/21/2013 10:41 AM, Daniele E. Domenichelli wrote:
Does it seem ok now? Can I merge to next?
Yes, please.
Thanks,
-Brad
--
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
On 21.10.2013 16:19, Bill Hoffman wrote:
On 10/19/2013 7:09 AM, Peter Kümmel wrote:
CMake now uses Ninja's database feature for dependency
tracking.
An empty build now takes about a third less (e.g. Clang
160ms-100ms)
Therefore ninja master is needed, please update your build
server.
This
On 10/21/2013 2:39 PM, Nils Gladitz wrote:
I haven't see that fail on my local test runs.
Is it sporadic or does it fail for you consistently?
Never mind on this one. Looks like it fails for me without your changes.
-Bill
--
Powered by www.kitware.com
Visit other Kitware open-source
Do Windows Store and Desktop apps have different toolsets? If yes it should be
enough IMO.
On 21.10.2013, at 14:26, Paul Annetts wrote:
To differentiate between Windows Store and Windows desktop apps.
Paul.
From: Patrick Gansterer
Sent: 21/10/2013 09:12
To: Paul Annetts
Cc: 'Brad
Attached is the latest version of the Perforce support patch for CTest.
I've added a test (CTest.UpdateP4) that launches a Perforce server
listening on a custom port and performs the same operations as other VCS
tools. Some release notes:
- Unix is expected. Windows could work (it's a matter
Hello,
I have seen that CMake 2.8.13 has been removed from the Mantis Roadmap. Instead
there is a new 3.0 version
Can you tell us more about it?
Does that mean that we are to expect great new stuff ?
I guess it will break backward compatibility since you change major, what is
going to be
Jed Brown wrote:
Stephen Kelly steve...@gmail.com writes:
Jed Brown wrote:
I just upgraded from cmake-2.8.11.2 to 2.8.12 and now get errors when a
comma ',' appears in a linker flag. Test case below. Note that this is
but one of many reasons for a comma to appear in linker flags.
I've
On Wednesday, 16. October 2013, 19:45:32, Alexander Neundorf wrote:
On Tuesday 15 October 2013, Johannes Zarl wrote:
I'd like to make some code in my build system dependent on the existance
of a target. Basically I'd like to write something like this:
if(TARGET optional_lib)
On Thursday, 17. October 2013, 07:12:51, Clark WANG wrote:
When I'm using CMake more and more I find it's not a real serious
language. It's so tricky.
I can see why you are frustrated. I don't think it's all bad though. Hopefully
CMake3 will be used for some language cleanups at the expense of
Hi,
according to the documentation, list(SORT list) sorts the list
in-place alphabetically. Without changing the host system: Does the
order depend on any additional input (like settings of environment
variables)?
For instance the sort tool (on POSIX systems) shows significant
dependencies with
cmake 2.8.12
MacOSX 10.8.5
gcc i686-apple-darwin11-llvm-gcc-4.2
OpenCV 2.4.3
Hi. I am new to cmake. Now I am trying to build a system that requires
OpenCV.
Source codes are separated into several modules, so cmake can make my life
easier.
running
cmake .
in the project directory seems ok,
list(SORT) does an std::sort() of std::strings.
I think CMake does not perform any character set conversions so the
available strings retain the encoding as used in the input file and
std::string ordering is based on byte-wise comparison.
Nils
On 10/21/2013 12:58 PM, Ingolf Steinbach wrote:
I would like for there to be support for debuginfo builds as well. This is
essential in my use case, where I am debugging a huge program on a remote
system with limited memory and a relatively slow network link.
Having a separate symbol pacakge is the preferred way to debug remotely
since
Hi all,
I'm using CMake to try compile a set of C bindings to the FLTK GUI library
and would like to set the C/C++ compiler variables in the build script but
haven't been successful. I realize that setting environment variables is
the recommended method but I've tried to explain why I need it
Is there a predefined variable for the TARGET.dir subdirectory of
${CMAKE_CURRENT_BINARY_DIR}${CMAKE_FILES_DIRECTORY} ?
I'm rolling my own - easy enough -but wanted to double check I'm not missing an
easier way to do it?
Gerard Weatherby
Appllication Architect
Virtual Cell, Center for Cell
On Monday 21 October 2013, Weatherby,Gerard wrote:
Is there a predefined variable for the TARGET.dir subdirectory of
${CMAKE_CURRENT_BINARY_DIR}${CMAKE_FILES_DIRECTORY} ? I'm rolling my own -
easy enough -but wanted to double check I'm not missing an easier way to
do it?
No, there is not, and
On 2013-10-21 04:12, Gregoire Aujay wrote:
I have seen that CMake 2.8.13 has been removed from the Mantis Roadmap. Instead
there is a new 3.0 version
Can you tell us more about it?
See
http://permalink.gmane.org/gmane.comp.programming.tools.cmake.devel/8207.
--
Matthew
--
Powered by
I'm trying to convert a large(ish) project to cmake. Everything works fine in
Linux, but I'm having problems on Windows.
Specifically, we have both C and Fortran sources mixed together in a single
directory. Cmake is producing an vcxproj file and none of the Fortran code gets
compiled.
I've
hi,all
I was working on windows7 and use cmake-2.8.12, swig:
C:/swigwin-2.0.10/swig.exe, Python:C:/Python27/python.exe.
I meet an error when i compile Bolt source code.
the steps as below:
1. Start a Powershell.exe and then enter my work directory.
2. Download Bolt source code by git clone
Hi Brian,
as I understand it, it is an explicit limitation of Visual Studio that a VS
project can only contain
a single programming language. The solution to this would to split the sources
into separate lists and
build libraries from them.
An alternative might be to use the Nmake approach -
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 9fb65d7090ca314cd8bfd88e52fefa6905938a6d (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 595060f3837a7da28810c644177b63d6319631b6 (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 8fa1ceb136dfa6c4d969fe78f4ebb46ae0abe6d0 (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 6d1444feacb1c2d621b776ac61412f92ff0a1c34 (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 d06610888dd357a7085be0bfff86f5d5d291771d (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 739215f342a68c9c91ab64db664159808318b27e (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 bf02e750796c6b42b0e9d39ba322cd5191489a0e (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 334d6e332fde0b7e8336918ebc6d7b8d0f46d54d (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 24146bfcd7e07a5bf88df300bbf6acc63cc680f1 (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 51e5088fd8a56be26d11cac5c2466f27acec69fa (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 a00f5dc9af0db7055210a566026de7643682649f (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 400e9b26e55ff96dd5b86d9127ca077e1d444862 (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 ed9516ebb09a6f7bab0e7f32e5f153d54fcba760 (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 1c469b1b9577f62c420fcf8182f66bda8fd776b3 (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 06db1883b8631f8b5ce86ab75249ca146dcfde07 (commit)
via
36 matches
Mail list logo
