The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=13157
==
Reported By:Matt Darland
Assigned To:
The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=13158
==
Reported By:Andrey Kamaev
Assigned To:
I love cmake, but I am still a bit of a novice, so perhaps there is a
better way to approach this problem. I am building a library using
cmake. On Windows I need to be able to build two versions: one that
links statically to the CRT (/MT) and one that links dynamically to
the CRT (/MD). I would
Hi Petr,
Thanks for your advices which goes on the line I already explored.
Indeed I have played a bit with similar constructions (either using
functions or macros) and yes it works (simply I thought I had missed
some features in CMake)
One point which forced me to manually add some tricks
Hi,
I would like to have your opinion before to start to implement it.
I would like to add the following options to the cmake command line interface:
--help-option opt [file] = Print help for a given option and exit.
--help-option-list [file] = List available options and exit.
--help-options
Hi,
I have noticed that most cmake based projects document their options
in their README file whereas the documentation is already included in
cmake when you call the option() and set() commands. I hope this
feature will help to remove this duplication and people will just
write in their
On Fri, Apr 20, 2012 at 10:58 AM, Rolf Eike Beer e...@sf-mail.de wrote:
Hi,
I have noticed that most cmake based projects document their options
in their README file whereas the documentation is already included in
cmake when you call the option() and set() commands. I hope this
feature will
Le 20 avril 2012 10:44, Nicolas Desprès nicolas.desp...@gmail.com a écrit :
Hi,
I would like to have your opinion before to start to implement it.
I would like to add the following options to the cmake command line interface:
--help-option opt [file] = Print help for a given option and
Hi
[I am on windows]
If I use cmake-gui to build my project, it starts asking me for the
build directory. Which is OK!
(my project is named B, it stands in test/B, where there is a
test/B/CMakeLists.txt and I want to build into test/B/build)
Now, if I use command interface CMake as
On 04/19/2012 07:00 PM, Eric Noulard wrote:
Compiler, Visual Studio something?
You run cpack from the command line or from within IDE/Makefile etc
No compilers used for this project (it's python) and I run from command
line.
Anyway it might be a good idea also in general so I tried to
2012/4/20 Andrea Crotti andrea.crott...@gmail.com:
On 04/19/2012 07:00 PM, Eric Noulard wrote:
Compiler, Visual Studio something?
You run cpack from the command line or from within IDE/Makefile etc
No compilers used for this project (it's python) and I run from command
line.
Anyway
I never used --build myself, but my guess is you can't generate and
build the project in a single step. I'd try the following (on a blank
setup):
cd test/B/build
cmake ..
cmake --build .
When running cmake from the command line to generate a buildsystem,
the source directory (where
2012/4/20 Eric Noulard eric.noul...@gmail.com:
Le 20 avril 2012 10:44, Nicolas Desprès nicolas.desp...@gmail.com a écrit :
Hi,
I would like to have your opinion before to start to implement it.
I would like to add the following options to the cmake command line
interface:
--help-option
2012/4/20 Christian Arnault arna...@lal.in2p3.fr:
Hi
[I am on windows]
If I use cmake-gui to build my project, it starts asking me for the build
directory. Which is OK!
(my project is named B, it stands in test/B, where there is a
test/B/CMakeLists.txt and I want to build into
Le 20 avril 2012 13:40, Nicolas Desprès nicolas.desp...@gmail.com a écrit :
2012/4/20 Eric Noulard eric.noul...@gmail.com:
Le 20 avril 2012 10:44, Nicolas Desprès nicolas.desp...@gmail.com a écrit :
Hi,
I would like to have your opinion before to start to implement it.
I would like to add
2012/4/20 Eric Noulard eric.noul...@gmail.com:
Le 20 avril 2012 13:40, Nicolas Desprès nicolas.desp...@gmail.com a écrit :
2012/4/20 Eric Noulard eric.noul...@gmail.com:
Le 20 avril 2012 10:44, Nicolas Desprès nicolas.desp...@gmail.com a écrit
:
Hi,
I would like to have your opinion before
Thanks to all who gave me hints and recipes to use CMake. And this
works. Great!
Christian
Le 20/04/2012 13:41, Petr Kmoch a écrit :
I never used --build myself, but my guess is you can't generate and
build the project in a single step. I'd try the following (on a blank
setup):
cd
2012/4/20 Nicolas Desprès nicolas.desp...@gmail.com:
2012/4/20 Eric Noulard eric.noul...@gmail.com:
Le 20 avril 2012 13:40, Nicolas Desprès nicolas.desp...@gmail.com a écrit :
2012/4/20 Eric Noulard eric.noul...@gmail.com:
Le 20 avril 2012 10:44, Nicolas Desprès nicolas.desp...@gmail.com a
Hi
I'm looking for query features in CMake.
In a very complex and large project with 100's of packages, developped
by many persons, each responsible of a subset, but forming a complex
graph of interrelated stuff, it important to be able to query the
configuration (at least for debugging
Hi,
I have a situation where I need to package up a build for
installation where there are two available license choices
(1) Non-commercial/evaluation
(2) Commercial
For the NSIS packaging, is there a way to show different licensing
text depending on some radio button choice?
Also, is
2012/4/20 David Cole david.c...@kitware.com:
2012/4/20 Nicolas Desprès nicolas.desp...@gmail.com:
2012/4/20 Eric Noulard eric.noul...@gmail.com:
Le 20 avril 2012 13:40, Nicolas Desprès nicolas.desp...@gmail.com a écrit
:
2012/4/20 Eric Noulard eric.noul...@gmail.com:
Le 20 avril 2012 10:44,
I'm trying to write a CMake patch script for a package that needs a
TARGET_LINK_LIBRARIES command replaced.
In the original it covers multiple lines, e.g.
TARGET_LINK_LIBRARIES(targetname1
boguslib1
boguslib2
boguslib3
)
I tried this to replace it:
string(REGEX REPLACE
On Fr., 20. Apr. 2012 11:23:08 CEST, Nicolas Desprès
nicolas.desp...@gmail.com wrote:
On Fri, Apr 20, 2012 at 10:58 AM, Rolf Eike Beer e...@sf-mail.de wrote:
Hi,
I have noticed that most cmake based projects document their options
in their README file whereas the documentation is
2012/4/20 Nicolas Desprès nicolas.desp...@gmail.com:
2012/4/20 David Cole david.c...@kitware.com:
2012/4/20 Nicolas Desprès nicolas.desp...@gmail.com:
2012/4/20 Eric Noulard eric.noul...@gmail.com:
Le 20 avril 2012 13:40, Nicolas Desprès nicolas.desp...@gmail.com a
écrit :
2012/4/20 Eric
FYI -- CMake 2.8.8 was released the evening of April 18, and we have
scheduled this webinar about the new stuff that's in it. But. we have
had to adjust the time slightly. It will now occur on Tuesday, April 24,
2012 at *2:15 pm Eastern* time.
Register for it here if you're interested:
Hi Dan,
I don't think it's possible to set compiler flags on a
per-configuration, per-target basis without splitting your project.
There was a very similar discussion recently [1],[2] which indicated a
couple of options. However the first option can't be used on a
per-configuration basis,
I downloaded and installed the latest version of CMake 2.8.8. I found
problems with the FindBLAS, FindLAPACK modules.
First thing I noticed was the ACML library search does not work for
versions 5.0. ACML no longer distributes acml_mv (multivector library)
with ACML for versions 5.0.
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
discards 7610e3cf0ef3b6abf1374bf0f56bad74e5091244 (commit)
This update discarded existing
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 1e1ba4dd6189c8c4db295a838aea551e7e593eb3 (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 b3f920f6928c6bfeb7937ce33bc51d37182b531b (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 0c7029c6420d6387b74a85bb8e62194e80b4e879 (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 7546abdfb11d14ffc55c5ba5f2a12203a2f78816 (commit)
via
32 matches
Mail list logo
