---
Help/manual/cmake-variables.7.rst |1 +
Help/variable/WINCE.rst |5 +
2 files changed, 6 insertions(+)
create mode 100644 Help/variable/WINCE.rst
diff --git a/Help/manual/cmake-variables.7.rst
b/Help/manual/cmake-variables.7.rst
index 149e4ac..b00c16e 100644
---
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=15150
==
Reported By:Martin Oberhuber
Assigned To:
On 09/11/2014 05:07 AM, Pascal Bach wrote:
Help/manual/cmake-variables.7.rst |1 +
Help/variable/WINCE.rst |5 +
Applied, thanks:
Help: Document the WINCE variable
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=4b4555de
-Brad
--
Powered by www.kitware.com
On 09/10/2014 03:42 PM, Nils Gladitz wrote:
extract everything into its own class cmConditionEvaluator and have it
keep everything that was being passed around as members instead.
Good work. I think the net change is now in good shape. To make
it easier to review now and bisect in the
On 11.09.2014 15:04, Brad King wrote:
Good work. I think the net change is now in good shape. To make it
easier to review now and bisect in the future, please rewrite the
topic to start with refactoring cmIfCommand to split out the
cmConditionEvaluator, and then add the rest of the changes.
On 09/11/2014 09:20 AM, Nils Gladitz wrote:
Is there a trick to recreate the history in that order or
would I have to start from scratch?
First rewrite the branch to squash your updates back into
the first commit, leaving all my CMP0054 warning commits
later in the topic. Then start a new
On 11.09.2014 15:28, Brad King wrote:
First rewrite the branch to squash your updates back into
the first commit, leaving all my CMP0054 warning commits
later in the topic. Then start a new branch from the
squashed commit containing only your part of the changes.
Note the sha1 of this commit,
On 09/11/2014 11:35 AM, Nils Gladitz wrote:
Thanks for the walk through.
I am a bit stuck on removing the CMP0054 changes from
cmConditionEvaluator.cxx part given that file is new and didn't exist
without the changes.
The file should exist, just remove the CMP0054 parts from it
and amend
On 09/05/2014 03:53 PM, Brad King wrote:
I think CMAKE_GENERATOR_PLATFORM may be a suitable name. Ideally
this setting should be added as a general-purpose replacement for
putting ARM or Win64 in the generator name. The changes for
that are more sweeping than I'd like to ask of you just for
On 11.09.2014 17:39, Brad King wrote:
On 09/11/2014 11:35 AM, Nils Gladitz wrote:
Thanks for the walk through.
I am a bit stuck on removing the CMP0054 changes from
cmConditionEvaluator.cxx part given that file is new and didn't exist
without the changes.
The file should exist, just remove
We are pleased to announce that CMake 3.0.2 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.0.2 since 3.0.1:
On 09/11/2014 11:52 AM, Nils Gladitz wrote:
cmConditionEvaluator.cxx doesn't exist without the CMP0054 changes
because I created it after I did most of the CMP0054 changes.
Since most of the changes are replacements rather than plain additions
*removing* those changes would mean having to
On 11.09.2014 18:53, Brad King wrote:
On 09/11/2014 11:52 AM, Nils Gladitz wrote:
cmConditionEvaluator.cxx doesn't exist without the CMP0054 changes
because I created it after I did most of the CMP0054 changes.
Since most of the changes are replacements rather than plain additions
*removing*
On 09/11/2014 12:57 PM, Nils Gladitz wrote:
Then keep editing the files and amending the commit to leave
behind only the refactoring pieces.
That is the part I was stuck at.
At this point cmConditionEvaluator.cxx exists in the source tree.
What is the problem?
-Brad
--
Powered by
On 11.09.2014 18:59, Brad King wrote:
At this point cmConditionEvaluator.cxx exists in the source tree.
What is the problem?
I can not create a CMP0054 free version of cmConditionEvaluator.cxx by
simply removing content from the file (or the patch).
I would have to add back lines to
On 09/11/2014 01:07 PM, Nils Gladitz wrote:
I would have to add back lines to cmConditionEvaluator.cxx which where
removed while they were still in cmIfCommand.cxx.
Look at the diff in commit 5922fc2c and you will see all those lines as
removed from cmIfCommand. You can put them all in
I think I've got it rewritten properly but I didn't know what half the
git commands I ran did most of the time so I am not entirely secure with
the result.
Would have probably not figured this out without your help.
Thanks again!
Nils
--
Powered by www.kitware.com
Please keep messages
Hi Ravi.
In what sense is the name incorrect? There is no correct/incorrect way to
name object files in relation to the source file name; it can be arbitrary,
as long as it's correctly passed on to the linker. I believe CMake chooses
to append .obj to the whole file name if there is more than one
Hi,
Thanks Petr for your reply. By incorrect I meant instead of the conventional
main.obj, we get main.cpp.obj.
I understood what you are saying. We have found a solution for this in our
cmake code.
We have explicitly set the /Fo compiler flag for main.cpp. With that it creates
main.obj for
Hi,
Date: Thu, 11 Sep 2014 07:49:23 +
From: Ravi Raman ravi.ra...@xoriant.com
Hi,
Thanks Petr for your reply. By incorrect I meant instead of the conventional
main.obj, we get main.cpp.obj.
I understood what you are saying. We have found a solution for this in our
cmake code.
I was wondering about this as well. Ravi, what is your motivation for
having object file names of a particular format? I don't think I've ever
had to care what object files in our builds are called.
Petr
On Thu, Sep 11, 2014 at 10:01 AM, Andreas Mohr a...@lisas.de wrote:
Hi,
Date: Thu, 11
Actually, in our project, the names of the object files matter because these
object files go as an input to a object file comparison tool that compares
object file names. So, there are 2 sets of object files, one coming from cmake
build and one from Visual Studio build.
The set coming from
On Thu, Sep 11, 2014 at 08:25:27AM +, Ravi Raman wrote:
Actually, in our project, the names of the object files matter because
these object files go as an input to a object file comparison tool that
compares object file names. So, there are 2 sets of object files, one
coming
I think (Ravi, correct me if I'm wrong) that they're transitioning to
CMake from a previously purely Visual Studio build system, and they're
writing some tools to validate that the builds are ending up the same.
So it's not really a problem for anybody -- I think he was just
looking for an
Yes. That's correct David. I was actually looking for an explanation why the
object file name is coming with the suffix .cpp.obj instead of the conventional
.obj.
It was kind of a problem for me because the object file comparison tool uses
the object file name as the reference for object file
Hi all,
Ninja does not clean out non-empty directories.
Given this CMakeLists.txt:
==
cmake_minimum_required(VERSION 2.8)
add_custom_command(
OUTPUT dir
COMMAND ${CMAKE_COMMAND} -E make_directory dir
COMMAND ${CMAKE_COMMAND} -E touch dir/file
)
add_custom_target(
dir-target DEPENDS
For a project that uses include(CPack) and produces
CPack_Example-0.1.1-Linux.sh when cpack is run and produces
CPack_Example-0.1.1-Linux.exe when cpack -G NSIS is run, am I remiss
for thinking that
cpack -G NSIS -P NEW_NAME -R 3.1.4
should produce NEW_NAME-3.1.4-Linux.exe?
As always, thanks.
Hi,
How can I create two linker steps with different flags for the same target
at the same build?
Example:
target: X
link: linker.exe libs_for_a linker_flags_for_a -o A/X.bin
link: linker.exe libs_for_b linker_flags_for_b -o B/X.bin
Thanks
--
Powered by www.kitware.com
Please keep
Hi, I am working at team developing RPM pacage generator.
Now I am solving a problem how can i get dependencies using cmake.
Basically we need to get paths to libs like they are cached in
CmakeCache.txt, is it somehow possible before calling cmake and then
parsing the file ?
--
Powered by
On Thu, Sep 11, 2014 at 9:51 AM, Vojtech Mašek shooter...@gmail.com wrote:
Hi, I am working at team developing RPM pacage generator.
Now I am solving a problem how can i get dependencies using cmake.
Basically we need to get paths to libs like they are cached in
CmakeCache.txt, is it somehow
Are you trying to generate two different libraries from the same target?
On Thu, Sep 11, 2014 at 10:45 AM, fungos fun...@gmail.com wrote:
Hi,
How can I create two linker steps with different flags for the same target
at the same build?
Example:
target: X
link: linker.exe libs_for_a
On 9/11/2014 7:04 AM, Ravi Raman wrote:
Yes. That's correct David. I was actually looking for an explanation
why the object file name is coming with the suffix .cpp.obj instead
of the conventional .obj. It was kind of a problem for me because the
object file comparison tool uses the object file
Hi Greg,
You might want to check out our current fork of CMake on
http://cmakems.codeplex.com. I've just added support for multiplatform support
for Windows Phone and Windows Store app in a similar way that it is done for
iOS.
You can try the build on
We are pleased to announce that CMake 3.0.2 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.0.2 since 3.0.1:
Yes, we can say that.. in reality I need two outputs for a single target,
but these outputs are generated almost exactly with just 2 different linker
flags removed.
On Thu, Sep 11, 2014 at 11:31 AM, Robert Maynard robert.mayn...@kitware.com
wrote:
Are you trying to generate two different
Generally the easiest way is to have two targets that share the same
source files but have different linker flags.
On Thu, Sep 11, 2014 at 12:53 PM, fungos fun...@gmail.com wrote:
Yes, we can say that.. in reality I need two outputs for a single target,
but these outputs are generated almost
Ok, but will this _recompile_ the sources for each target? We must use the
same generated object files for the two outputs, the only difference must
be the linker flags.
On Thu, Sep 11, 2014 at 1:20 PM, Robert Maynard robert.mayn...@kitware.com
wrote:
Generally the easiest way is to have two
Sounds like what you want is an object library,
http://www.cmake.org/Wiki/CMake/Tutorials/Object_Library:
set(FOO_SOURCES
Foo1.cxx
Bar2.cxx
FooBar3.cxx
)
add_library(FooObjLib OBJECT ${FOO_SOURCES})
add_executable(A $TARGET_OBJECTS:FooObjLib)
set_target_properties(A PROPERTIES LINK_FLAGS
I have a strange, and very frustrating, problem. I have a pretty large piece of
software that I build nightly as part of regression testing of my own software.
All of the software uses CMake and I use a ctest script, via ctest -S [script
file], for my nightly regression testing . As I stated,
Hi Gary,
Do you see either of these two warning messages show up:
warning: -jN forced in submake: disabling jobserver mode.
or
warning: jobserver unavailable: using -j1. Add `+' to parent make rule.
These warnings often accompany the forced serialization of a parallel make
build, although
Excuses; I found the target property setting in the respective
`myLibTargets-none.cmake` file:
```
set_target_properties(myLib PROPERTIES
IMPORTED_LINK_INTERFACE_LIBRARIES_NONE /usr/lib/liblapack.so
IMPORTED_LOCATION_NONE
${_IMPORT_PREFIX}/lib/x86_64-linux-gnu/libmylib.so.1.0
Thanks for the reply Chuck.
Unfortunately there is no such message. I’m not even sure the GNU make
jobserver is the problem. It’s just that the symptom is the same as if that
were happening.
Am I comparing apples to apples when I go into the build directory created via
ctest and invoking
Cool, this did the trick. It was needed a post-build step to rename the
target but it works.
Thank you
On Thu, Sep 11, 2014 at 2:19 PM, Chuck Atkins chuck.atk...@kitware.com
wrote:
Sounds like what you want is an object library,
http://www.cmake.org/Wiki/CMake/Tutorials/Object_Library:
Hi all,
One of my projects contains two libraries libA and libB, where libB
depends on libA, and both are exporting their configuration through
the usual `INSTALL(EXPORT ...)` mechanisms.
I'm getting errors of the type
```
CMake Error: install(EXPORT SEACASNemesis-exports ...) includes
target
Set the OUTPUT_NAME or OUTPUT_NAME_CONFIG property on the target to
change what the name of the generated library will be. This will
eliminate the need for a post-build step.
On Thu, Sep 11, 2014 at 4:16 PM, fungos fun...@gmail.com wrote:
Cool, this did the trick. It was needed a post-build step
On Thursday, September 11, 2014 23:51:21 Nico Schlömer wrote:
Hi all,
One of my projects contains two libraries libA and libB, where libB
depends on libA, and both are exporting their configuration through
the usual `INSTALL(EXPORT ...)` mechanisms.
I'm getting errors of the type
```
On 9/11/2014 4:09 PM, Hennigan, Gary L wrote:
Thanks for the reply Chuck.
Do you have an external projects in this build?
-Bill
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to
Is there a significant amount of output from make? What does make do if
it's running low on RAM?
ctest may be holding onto too much memory trying to process the
output if it's very large...
Just a thought -- worth a look, though.
D
--
Powered by www.kitware.com
Please keep messages
Or are these customizing CPack command line options mostly meant to be
used with a CPACK_PROJECT_CONFIG_FILE?
On Thu, Sep 11, 2014 at 9:07 AM, Iosif Neitzke
iosif.neitzke+cm...@gmail.com wrote:
For a project that uses include(CPack) and produces
CPack_Example-0.1.1-Linux.sh when cpack is run
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, hooks has been updated
via 6f2466c503b192c2065bcdc2135137ec5c74ceef (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 a3fa29228138e26839fcbf8948db5d714fa483b9 (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 de3cfe7da8659b0e5689bdc5b653f8425d1e2bf0 (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 0f63c7d223d5d134bb13953af261857b7288e91f (commit)
via
20140911)
+set(CMake_VERSION_PATCH 20140912)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/post-receive
--
CMake
54 matches
Mail list logo
