Hi,
i have a project in the path D:\folder1\folder2\prj1, all sources and
CMakeLists.txt are in this folder 'prj1'.
CMake generates for the Codeblocks project file in which the source files are
located in a virtual folders with the path not corresponding to the root folder
of the project
CMake + Ninja is definitely the best move you can make for giving your
developers the minimum possible build time on Windows.
NMake is basically useless, its underlying code hasn't been updated in
years, and it does absolutely nothing to try to take advantage of
multiple cores.
Fastest Windows
On 06/01/2015 05:10 AM, Nagy-Egri MĂĄtĂŠ Ferenc wrote:
Obtaining a list of files with identical compiler switches might be tricky.
[snip]
Deferred generation of the makefile is not nice, but might be the only way.
Yes. However, I'd prefer not to introduce major refactoring to the
Makefile
The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=15599
==
Reported By:trsystran
Assigned To:
Thanks Brad for the detailed description. From what I’ve read about the 3 level
makefile system, it should be pretty straightforward to implement batch-mode
support.
Actual compilation takes place only in the last level, and throughout
generation, this is the point where all the compilation
Hello all,
I'm struggling with the CMake Config-based package description when
using two depending packages where the upstream package has optional
link libraries.
Suppose you have libA that optionally uses zip functionality (say by
some option USE_ZLIB in libA's CMakeLists.txt). This means
Hello,
in the ExternalProject_add function, I would like to access to DOWNLOAD_DIR to
download a patch (for ARPACK).
So, I define my patch command like this:
==
PATCH_COMMAND cd DOWNLOAD_DIR
wget /myurl/mypatch.tar.gz
cd SOURCE_DIR
tar
At my company, we didn’t bother trying to use NMake.
We used the Visual Studio solution generator and the proper compilation flags
and msbuild flags to build in parallel. This proved to speedup our builds quite
a lot and was very easy to integrate.
The other solution you mentioned is “ninja” and
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 d8ada560d08b0e4591701e31e295c38f639042a6 (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 1d2ae2b307af884fde8124136a57d961d88dbdf7 (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 05845ac10ff4ce50449e94f38c97d6e57f433b64 (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 fb0cbafbcb0637050489ac52dc3fa6dc450c7fac (commit)
via
On 05/30/2015 09:27 AM, Tamar Kranenburg wrote:
Attached is my second attempt to add support for PostgreSQL 9.3 and 9.4
on Debian/Ubuntu.
Thanks. Although we currently have a freeze in place in preparation
for 3.3, this can be considered an environmental regression due to
the availability of
Sorry David, my bad.
CMake combined with GNU Make does indeed handle dependencies for Fortran, so it
can’t be impossible - but maybe it is hard enough that noone bothered
implementing it for ninja.
Paul
I have no experience with Fortran, and from what I understand,
parallel builds of
On 06/01/2015 11:55 AM, Paul Anton Letnes wrote:
CMake combined with GNU Make does indeed handle dependencies
for Fortran, so it can't be impossible - but maybe it is hard
enough that noone bothered implementing it for ninja.
Design for that was discussed in a thread on cmake-developers here:
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 4bfcad0d9156e20761fcb8ef630eee4885d34371 (commit)
via
On 05/30/2015 09:50 AM, Sylvain Joubert wrote:
The recent development to support different LIBRARY_DIR for Boost have
made the new cache entries appear in the default cache.
For reference, this was here:
FindBoost: Search for debug and release libraries separately
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 2b3579cacf628d83a3c715087b81c4fe22785fe7 (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 15074cd72e26b94d69f8bb4cf450e1bf2d45dc35 (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 ce8abdf145ae5d8dd4ec232fa4b25fd21c5f3f4c (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 419cba0e392565b3d24c0be7a4d7a27416df0075 (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 60d6f66fb2bdd8bded288a6f28549c2aa80a59c8 (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 836c4e9314f5afbde132ae34ed5cbfd5e422f905 (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 8247186281ec8c7adf78429d4c8a29ae22eb517e (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 f663e9d0a07ca5a86f04873060049ac6859eba1a (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 40bad5149054c7e9efdc9fdd645e5ce024225b4f (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 1992aaa96ef3e98e46b5ac548202d5502c401e82 (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 02c4aa1f97f5436e3f2f2ba07c492a24bad04c4f (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 aaa9af32fa233cb1497c65e912ea3d27c3dcf430 (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 ef586dcdca725f32b803692730554430bb708290 (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 2693c45e6237acba2514626ae794386f0a63525e (commit)
via
Hi,
Does CMake custom_command rebuild the output file if the dependency files
change? Seems like it should but I can't get it to work.
The CMake command is written like this:
add_custom_command(
OUTPUT ${ OUTPUT_FILE}
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 8b8baf5f95790866277ede63b8107cbf58974034 (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 b3de2a8e6451c9138948c23a974740823ade8263 (commit)
from
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 316232d5f5957182ab9baed2c05d91f1e6c59a4a (commit)
via
Are these absolute paths?
Yes. All absolute file paths.
Where is the output file referenced? It needs to be in a target somewhere.
Forgot to mention, we also do this after:
set_source_files_properties(${OUTPUT_FILE} PROPERTIES GENERATED 1)
list(APPEND SOURCE_FILES ${OUTPUT_FILE})
[...]
On 06/01/2015 02:03 PM, Robert Goulet wrote:
Forgot to mention, we also do this after:
set_source_files_properties(${OUTPUT_FILE} PROPERTIES GENERATED 1)
That shouldn't be necessary. add_custom_command does that for you.
list(APPEND SOURCE_FILES ${OUTPUT_FILE})
[...]
On 06/01/2015 01:19 PM, Robert Goulet wrote:
Does CMake custom_command rebuild the output file if the
dependency files change?
Yes, it should. This is well tested.
DEPENDS ${INPUT_FILES}
Are these absolute paths?
OUTPUT ${OUTPUT_FILE}
Where is the output file referenced? It needs to be
Removing the line
set_source_files_properties(${OUTPUT_FILE} PROPERTIES GENERATED 1)
...fixed it.
Indeed the documentation says Each output file will be marked with the
GENERATED source file property automatically. However it does not mention that
setting that property ourselves prevents the
Hi Brad,
Thanks for splitting the files, much cleaner. Just ran the tests on Mac,
Windows and Linux and I confirm that it still works.
Regards,
Tamar
On 1 jun. 2015, at 17:04, Brad King brad.k...@kitware.com wrote:
On 05/30/2015 09:27 AM, Tamar Kranenburg wrote:
Attached is my second
On 06/01/2015 03:41 PM, Tamar Kranenburg wrote:
Thanks for splitting the files, much cleaner.
No problem. It makes it easier to review when the changes
are isolated with their own explanation. It also helps with
git bisect to find problems in the future.
Just ran the tests on Mac, Windows
On 05/31/2015 12:43 PM, Dan Kegel wrote:
Did you try the workaround suggested in the first link you gave, i.e.
set( RatherLongLibraryName_GUID_CMAKE generated GUID CACHE INTERNAL
remove this and Visual Studio will mess up incremental builds)
On Sun, May 31, 2015 at 9:04 AM,
I appreciate the feedback on this issue.
Deterministically generating a GUID sounds like a real solution.
++David-Bjornbak;
-Original Message-
From: Brad King [mailto:brad.k...@kitware.com]
Sent: Monday, June 01, 2015 12:09 PM
To: BJORNBAK,DAVID (K-Sonoma,ex1)
Cc: Dan Kegel; cmake;
We are pleased to announce that CMake 3.2.3 is now available for download.
Please use the latest release from our download page:
http://www.cmake.org/download/
Thanks for your support!
-
Changes in 3.2.3 since 3.2.2:
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 annotated tag, v3.2.3 has been created
at 0a569d18496d4d384971d0c42be4300949896dc2 (tag)
tagging
We are pleased to announce that CMake 3.2.3 is now available for download.
Please use the latest release from our download page:
http://www.cmake.org/download/
Thanks for your support!
-
Changes in 3.2.3 since 3.2.2:
The boost I want is not in a normal location, but:
Boost's include dir is first in my CPATH.
Boost's lib dir is first in my LD_LIBRARY_PATH.
Why doesn't cmake 3.2.2 find it?
I'm not being picky about the version.
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake
Using a callback I now feed the error information back.
Here's the latest change:
https://github.com/ulrichard/CMake/commit/adf1cf5184d5a13702a03a090c501f1a6d0e39f4
The following line is still commented out:
this-Makefile-StoreMatches(re);
Is it important enough to add another callback?
What
I try add to my project *.xaml files, but xaml files adds to solutionincorrect.
For example, i have App.xaml, App.xaml.cpp and App.xaml.h. In solution these
files must be gropped and App.xaml must be have XAML Page or XAML
Application Definition item type. But these files is not grupped, and
Hi,
I noticed that sometimes when a target is reloaded, that the virtual folders
and targets for the complete visual studio solution get expanded.
For a small project this isn't a problem, but in a large project (~ 100
targets) this is a really big problem to close all targets every time.
Did
Hi,
I noticed that sometimes when a target is reloaded, that the virtual folders
and targets for the complete visual studio solution get expanded.
For a small project this isn't a problem, but in a large project (~ 100
targets) this is a really big problem to close all targets every time.
Did
Greetings,
I'm currently attempting a patch for
http://www.cmake.org/Bug/view.php?id=15578 and trying to do it how Brad
suggests. So far, I've propagated a string down into the comparision
functor. This string comes from
cmGlobalVisiaulStudioGenerator::GetStartupProjectName(). However,
0 Mon 19:44:33 yost DaveBook ~/p/c++/cmake/target-for-generate/build
261 Z% make help
The following are some of the valid targets for this Makefile:
... all (the default if no target is provided)
... clean
... depend
... edit_cache
... rebuild_cache
... foo
... genBar
... bar
... foo.o
... foo.i
On 2015-06-01, at 2:28 PM, Dave Yost d...@yost.com wrote:
The boost I want is not in a normal location, but:
Boost's include dir is first in my CPATH.
Boost's lib dir is first in my LD_LIBRARY_PATH.
Why doesn't cmake 3.2.2 find it?
I'm not being picky about the version.
In other
20150601)
+set(CMake_VERSION_PATCH 20150602)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/post-receive
--
CMake
Also, from what I can make of
CMake.app/Contents/share/cmake-3.2/Modules/FindBoost.cmake
findBoost looks in
/sw/local/
which is a path from the old, old Fink package system for OS X. findBoost
should also look in
/usr/local (Homebrew and long unix tradition)
/opt/local (MacPorts)
56 matches
Mail list logo
