2011/4/12 Nicolas Desprès nicolas.desp...@gmail.com:
2011/4/11 Brad King brad.k...@kitware.com:
On 04/11/2011 05:16 AM, Nicolas Desprès wrote:
I have continued my work on the Ninja generator this weekend and I
Great! Thanks for working on this.
Here my roadmap:
1/ Configure and build an
Hi Oliver,
On Sunday 17 April 2011, Oliver Buchtala wrote:
Hi Alex,
Am 17.04.2011 20:46, schrieb Alexander Neundorf:
Hi,
On Sunday 17 April 2011, Oliver Buchtala wrote:
Hi,
I like to get involved offering work on the Eclipse CDT generator.
Currently, the generated project
On Mon, Apr 18, 2011 at 11:22 PM, Michael Hertling mhertl...@online.dewrote:
On 04/19/2011 02:17 AM, Oliver Buchtala wrote:
Am 18.04.2011 06:58, schrieb Michael Hertling:
On 04/16/2011 12:05 AM, Oliver Buchtala wrote:
Am 15.04.2011 23:48, schrieb Michael Hertling:
On 04/15/2011 11:22 PM,
Hi Mike
Thanks for this very helpful answer.
I am nevertheless still facing few problems. My project contains:
- a shared library
- an executable using the shared lib
- a plugin lib (loaded using dylib)
I have modified my exec target to be
ADD_EXECUTABLE(main MACOSX_BUNDLE main.cpp
Use the SHARED library type for your shared library and MODULE for your
plugin.
Have you downloaded the Qt example from the Wiki? It shows what you need to do.
The terse summary of how some of us do it is this:
Write a configurable *.cmake.in file that gets configured at cmake time. An
Kitware is offering a free lunchtime seminar on May 4th at 12pm in the
Hamner Conference Center at the North Carolina Biotechnology Center. This 90
minute seminar will cover cutting-edge topics in open-source scientific
software solutions and provide case studies for their successful integration
On Tuesday 19 April 2011, Dan Schmidt wrote:
Hi everybody,
I was wondering if anyone has run into the following problem. With version
2.8.2 of cmake, the project generated for C::B included the tree of the src
files starting at the base of the project. However, I've upgraded to cmake
2.8.4,
On Tue, Apr 12, 2011 at 2:24 PM, Bill Hoffman bill.hoff...@kitware.comwrote:
On 4/12/2011 4:13 PM, David Cole wrote:
Does somebody have reproducible steps to get to the point where
CMAKE_SIZEOF_VOID_P disappears??
I've never seen that...
How many times do you have to re-configure before
I'm a real cmake novice, and I find the cmake documentation hard to follow,
because it assumes that you know what you're doing (and I obviously don't) and
doesn't provide examples. I simply want to add to CMakeLists.txt an instruction
to copy the executable created to another directory. I
Hi Gib,
Try the following:
GET_TARGET_PROPERTY(FUBAR_EXE fubar LOCATION)
ADD_CUSTOM_COMMAND(TARGET fubar POST_BUILD COMMAND ${CMAKE_COMMAND} -E
copy ${FUBAR_EXE} somepath)
Cheers,
Fraser.
On 20/04/2011 03:31, Gib Bogle wrote:
I'm a real cmake novice, and I find the cmake documentation
It worked! Brilliant! Thanks very much. I have a lot to learn ...
Gib
Quoting Fraser Hutchison fraser.hutchi...@googlemail.com:
Hi Gib,
Try the following:
GET_TARGET_PROPERTY(FUBAR_EXE fubar LOCATION)
ADD_CUSTOM_COMMAND(TARGET fubar POST_BUILD COMMAND ${CMAKE_COMMAND}
-E copy
On 04/20/2011 05:47 AM, Gib Bogle wrote:
It worked! Brilliant! Thanks very much. I have a lot to learn ...
Gib
Quoting Fraser Hutchison fraser.hutchi...@googlemail.com:
Hi Gib,
Try the following:
GET_TARGET_PROPERTY(FUBAR_EXE fubar LOCATION)
ADD_CUSTOM_COMMAND(TARGET fubar
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 cc214c68ddcf7b51a827a64517b877f55d75cba4 (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 bf238d6f0ef39b474e68b84e3964deaf3653aa72 (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 4d2d9d44e614a2f6e651d04a4387561e2943eab7 (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 2b445349508730d4f79478b0e22ea1b48e7bffc0 (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 19a4b8856d01b019956ad42bf9eb25703dc345ee (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 b019f5f58c0e14039facaf8ce391ca2354984024 (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 2f50ec5f5cb13d05df0fe7e4fd9e7faf631b20b6 (commit)
from
19 matches
Mail list logo
