On 3/17/2012 8:26 PM, Peter Collingbourne wrote:
Most likely some object files were not rebuilt as a result of header
file changes. This will happen if the compiler does not support
emitting dependency files, such as cl.exe. I think there are a couple
of ways we could consider supporting
Hi Peter(s),
I've merged the ninja-generator topic to 'master' up through
the rebuild_cache fix. Just prior to merging I rewrote the
topic history to add a Ninja: prefix to all the commit
messages. This makes commits like add .def file support
clearly specific to Ninja as against adding .def
Hi Folks,
I've just pushed a new 'object-library' topic and merged to 'next'
for testing. David Cole and I have been working on it for a couple
of weeks. The following documentation added to the add_library
command explains:
2012/3/19 Brad King brad.k...@kitware.com:
Hi Folks,
I've just pushed a new 'object-library' topic and merged to 'next'
for testing. David Cole and I have been working on it for a couple
of weeks. The following documentation added to the add_library
command explains:
2012/3/19 Brad King brad.k...@kitware.com:
On 3/19/2012 1:56 PM, Eric Noulard wrote:
That's a great feature.
Thanks.
Is there a feature that could guarantee the order of appearance of
those objects / object library on the link line generated for
add_executable ?
Currently no order is
On 3/19/2012 2:25 PM, Eric Noulard wrote:
2012/3/19 Brad Kingbrad.k...@kitware.com:
Can you enumerate use cases when the order of objects matters? Unlike
static libraries *all* objects will be included. If there are duplicate
symbols it is an error. If there are not duplicate symbols then
On Monday 19 March 2012, Brad King wrote:
On 3/18/2012 4:41 PM, Alexander Neundorf wrote:
This is now in the ImprovedCOMPONENTSSupportInFindPackage2 branch on
stage.
It adds an OPTIONAL_COMPONENTS option to find_package().
It adds an option HANDLE_COMPONENTS to FPHSA(), so FPHSA()
On Monday 19 March 2012, Brad King wrote:
Hi Folks,
I've just pushed a new 'object-library' topic and merged to 'next'
for testing. David Cole and I have been working on it for a couple
of weeks. The following documentation added to the add_library
command explains:
Hello,
I have the following in my Cmakelists.txt file:
set_target_properties( MyApp PROPERTIES STATIC_LIBRARY_FLAGS
${SOME_LIB_FILENAME})
If the SOME_LIB_FILENAME path includes white space such as
c:/Projects/Foo 4/Src/somelib.lib
the generated visual studio 2008 file includes the following
Hello,
In our project, if we use NMake then targets package and
package_source are both supported. If we use the Visual Studio IDE
then only the PACKAGE target appears, not a PACKAGE_SOURCE. Is there
some way to get a PACKAGE_SOURCE project to appear in the solution?
Here's our CMakeLists.txt:
Hi there,
I am currently working on transitioning over a project (that has multiple
subprojects inside of it) over to Cmake.
There is one thing that I am not sure about - basically, to include the
subprojects from the top level CMakeLists.txt file, I just utilize the
add_subdirectory command,
Please notice the linebreak after Foo, this causes the linker to fail,
saying it can not find C:/Projects/Foo.
I guess this is a cmake bug, but I need to find a workaround for this one.
I am using cmake 2.8.2 on Windows 7.
I have the exact same whitespace issue with a custom command. I am using
2012/3/19 Ajay Panyala a...@csc.lsu.edu:
Please notice the linebreak after Foo, this causes the linker to fail,
saying it can not find C:/Projects/Foo.
I guess this is a cmake bug, but I need to find a workaround for this one. I
am using cmake 2.8.2 on Windows 7.
I have the exact same
Did you try playing around with:
file(TO_CMAKE_PATH path result)
file(TO_NATIVE_PATH path result)
I did try file(TO_NATIVE_PATH path result) at the time, but it was not
useful in my case.
The result is still a unix style path (maybe because I am using Cygwin)
Thanks
Ajay
On Mon, Mar 19, 2012
2012/3/19 Ajay Panyala a...@csc.lsu.edu:
Did you try playing around with:
file(TO_CMAKE_PATH path result)
file(TO_NATIVE_PATH path result)
I did try file(TO_NATIVE_PATH path result) at the time, but it was not
useful in my case.
The result is still a unix style path (maybe because I am
Did you use cygwin CMake or win32 CMake?
I think using win32 CMake with cygwin does not play well, one should
use cygwin CMake.
I do use the Cygwin CMake.
Thanks
Ajay
On Mon, Mar 19, 2012 at 11:28 AM, Eric Noulard eric.noul...@gmail.comwrote:
2012/3/19 Ajay Panyala a...@csc.lsu.edu:
Did you
I can also confirm that the problem also appears in custom targets where
the path is in the name of the output.
--
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:
Hi there,
I've been struggling getting a custom cdash script to work. I want to submit to
some subproject and also some additional files (exp: the compiled binary). If I
understand correctly I need to write a custom script.
Now I played around a bit and got this working. However, what I don't
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 73a126367cdbcc4ef8664afa18c2008ef80346ef (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 572994bd9f8ea77c3101f0b019b693c37b0d502e (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 6fe93f3f74f5b25968de2b17e8c54087cefb603e (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 24dfb445d2609f8b74a6d250ae1b7e58cf882818 (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 72fd7358d2dc1af465d963d681e4814a1b0f7dea (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 9727a6ddc82367df2f40946915d991f26d1839d4 (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 36a85b4cd5dd725e4c5f73ea3350f1a78de63bda (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 1df15c68d53865f5c0803522ff8ba01bc78177f8 (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 0e339f70542089b68a4ae35df53e05c195ac259f (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 f2b44c64fc1842ef355f80337d1260bd7594da55 (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 4e6fd4bf483e3e6ea260f95eb2fb7bc109f82cc3 (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 e0cebaaf7fe4828f6a0e26495f0e572c67e47704 (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 f7533740e9096d4944c378868685047e73d3afc0 (commit)
from
31 matches
Mail list logo
