Hi all,
I'm trying to reduce the number of toplevel projects in my CMake generated
Visual Studio solution. The idea is to group some targets in solution paths.
The layout should look like this:
Solution
- Target 1
- Foo
+ Target 2
+ Target 3
- Target 4
...
Is there a way to achieve this
Hi Justin,
I'm very unsure if this is the correct solution, but it worked for me. I
haven't been able to find any good documentation stating how the CMakeCache
interacts with other parts of CMake.
My assumption is that since CMAKE_C{XX}_FLAGS is supposed to allow the user
to set optional
I'm trying to reduce the number of toplevel projects in my CMake
generated Visual Studio solution. The idea is to group some targets in
solution paths. The layout should look like this:
Solution
- Target 1
- Foo
+ Target 2
+ Target 3
- Target 4
...
Is there a way to
I am building a Windows DLL that has some of its global variables allocated
in a special shared memory segment.
In order to inform the linker (VS Express 2008) about the segment's
properties, I need to provide the following command-line parameter to the
linker:
/SECTION:.shared,RWS
Could
I am building a Windows DLL that has some of its global variables
allocated in a special shared memory segment.
In order to inform the linker (VS Express 2008) about the segment's
properties, I need to provide the following command-line parameter to the
linker:
/SECTION:.shared,RWS
Hi,
I'm having some trouble setting PYTHONPATH in order to test a python
extension module built with cmake.
Currently I do the following:
add_test(NAME py_test COMMAND ${PYTHON_EXECUTABLE}
${CMAKE_CURRENT_SOURCE_DIR}/test_runner.py)
if (CMAKE_CONFIGURATION_TYPES)
set (PY_DIR
On 12/14/2010 05:00 PM, Anders Wang Kristensen wrote:
Hi,
I'm having some trouble setting PYTHONPATH in order to test a python
extension module built with cmake.
Currently I do the following:
add_test(NAME py_test COMMAND ${PYTHON_EXECUTABLE}
On Tue, Dec 14, 2010 at 4:45 AM, Johan Björk p...@spotify.com wrote:
Hi Justin,
I'm very unsure if this is the correct solution, but it worked for me. I
haven't been able to find any good documentation stating how the CMakeCache
interacts with other parts of CMake.
My assumption is that
Greetings,
I keep stalling on line 100 of FindOOoSDK.cmake shipped with the current
version of koffice (of kde.org) (A copy is attached) I have all the
prerequisites installed in /opt/openoffice.org. I would be grateful if
someone more aufait with cmake modules could offer some advice on
On Tuesday 23 November 2010, Alexander Neundorf wrote:
On Tuesday 23 November 2010, Brad King wrote:
On 11/23/2010 03:31 PM, Alexander Neundorf wrote:
On Monday 22 November 2010, Brad King wrote:
On 11/22/2010 04:06 PM, Alexander Neundorf wrote:
On Monday 22 November 2010, Brad King
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 07fa3d311e56cd7158cb668318fcb58ca0e4218e (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 75844666ac03a95c6546cafb54bce8827e1b664a (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 b0dffc7e9ca010e42e5baac9623493423664abe8 (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 24b251ac555a7cb1d3fa8fb4cfc8d0bbb38aac3d (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 f1adcefdf419cee3c358c279984bca1dc69cddc6 (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 b3f2d19ba763401f7c940d9c9f289d5d74422fe1 (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 5bea0917ef53ccb3eb5cca40b3900668161cf5e7 (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 8e7f0488b47458775a162ed031b8635e043978ad (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 03c4623fb4605a347acc20a1914582e794dd474d (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 2c7d36ce6fd0cef9cbd45bb94795dc42526424f2 (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 9e7e106dcbf9112f80b6a4eed35b5927df61416d (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 2d1aa4ad06eedf6bc677c8ebf757f4978a839e02 (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 631504cbc0a6f85090711c4d3aca8582ca2de262 (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 d555dd3854f7b59f1c335a05f1920908ee3f1fcd (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 a9808eeba7a31ebe404f92c7a4add539155036cd (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 fc4026227e2abaef0de9a7843bf8f528b503cabb (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 9a2f329c4c07a3f3c2bb4c8a1addea36f83c0f67 (commit)
via
27 matches
Mail list logo
