On 05/12/2013 07:32 PM, Robert Dailey wrote:
I'm currently working on adding a CONFIG keyword to the
add_custom_command() command.
The need for a CONFIG keyword was largely removed by support for
generator expressions in custom commands.
There is discussion and and old patch here:
On 05/11/2013 11:09 PM, Wojciech Knapik wrote:
I recently ran into the issue of GLOBs being unsafe for source lists and
wrote a very simple piece of code to fix the problem. A generalized
version of that code is available here:
I am familiar with bug 9974 and I've been following it for quite some
time :) I thought there was enough interest in the feature (especially
from myself) to work on it. However, I do like the idea of generator
expressions being supported in OUTPUT, this is a more ideal situation
and would only
On 05/13/2013 10:10 AM, Robert Dailey wrote:
I am familiar with bug 9974 and I've been following it for quite some
time :) I thought there was enough interest in the feature (especially
from myself) to work on it. However, I do like the idea of generator
expressions being supported in OUTPUT,
Does anyone know if/how Xcode can handle versioning of dylibs that include
symbolic links?
When creating versioned shared libraries with Makefiles, I get the symbolic
links. But, I don't get that when building with Xcode.
I realize CMake generated Xcode projects don't support this, but I'm
Actually now that I think about this a littler closer, changing the
generator expressions may not work for a specific case I'm blocked on.
I store my third party library binaries in a debug and release
directories. I have a custom target that I define to copy the
appropriate debug or release DLLs
On 05/13/2013 02:07 PM, Robert Dailey wrote:
Actually now that I think about this a littler closer, changing the
generator expressions may not work for a specific case I'm blocked on.
I store my third party library binaries in a debug and release
directories. I have a custom target that I
Interesting, I must have overlooked your comment on that issue. Will
this also work for add_custom_command using the OUTPUT/DEPENDS/COMMAND
arguments? I don't copy using a post build event, I create a custom
target instead and attach the custom commands to it. I do it this way
so that if the
On Monday, May 13, 2013 02:30:32 PM Brad King wrote:
On 05/13/2013 02:07 PM, Robert Dailey wrote:
Actually now that I think about this a littler closer, changing the
generator expressions may not work for a specific case I'm blocked on.
I store my third party library binaries in a debug
On 05/13/2013 02:48 PM, Robert Dailey wrote:
Interesting, I must have overlooked your comment on that issue. Will
this also work for add_custom_command using the OUTPUT/DEPENDS/COMMAND
arguments? I don't copy using a post build event, I create a custom
target instead and attach the custom
On Monday, May 13, 2013 12:55:39 PM Clinton Stimpson wrote:
On Monday, May 13, 2013 02:30:32 PM Brad King wrote:
On 05/13/2013 02:07 PM, Robert Dailey wrote:
Actually now that I think about this a littler closer, changing the
generator expressions may not work for a specific case I'm
On 05/13/2013 02:55 PM, Clinton Stimpson wrote:
To avoid the copy step, would it be useful to make generator expressions work
in target properties?
The copy in my example in the issue is for an external dependency.
set_target_properties(mylib PROPERTIES
LIBRARY_OUTPUT_DIRECTORY
On Monday, May 13, 2013 03:03:27 PM Brad King wrote:
On 05/13/2013 02:55 PM, Clinton Stimpson wrote:
To avoid the copy step, would it be useful to make generator expressions
work in target properties?
The copy in my example in the issue is for an external dependency.
I think your idea coupled with OUTPUT and DEPENDS generator
expressions would be the perfect combination and solve this problem
beautifully.
The 2 main problems with POST_BUILD are:
1) if multiple targets depend on z, then z is copied multiple times.
2) Other dependencies (other than z) may cause
Hello,
There is an old known problem with the NCurses library: missing links
against ncursesw, and additionally ncursest with ncurseswt [1].
There is a bug report [2] marked as a backlog, with references to this
mailing list [3].
I have built my Linux system with the wide-character NCurses
On Mon, May 13, 2013 at 09:49:03AM -0400, Brad King wrote:
On 05/11/2013 11:09 PM, Wojciech Knapik wrote:
I recently ran into the issue of GLOBs being unsafe for source lists and
wrote a very simple piece of code to fix the problem. A generalized
version of that code is available here:
The following issue has been SUBMITTED.
==
http://cmake.org/Bug/view.php?id=14140
==
Reported By:Clinton Stimpson
Assigned To:
Hi,
I'm using the current WinCE support in the nightly build to build
various things through cmake generated VS2008 solutions. I wondered
about not beeing able to set the correct entry point for my executables
until I debugged the issue. The VS generator used always outputs
hardcoded
I'm converting a Fortran package that was using GNU make to build to CMake, but
I've run into a problem compiling F90 module code where the source code is
stored under many directories.
The package has a directory structure
src/
src/dir1
src/dir2
:
:
Each dir* has *.F
Hi,
I currently have a CMake project with multiple sub-projects where
the sub-projects are libraries and executables. The project works on
windows and iOS (via XCode). One such sub-project is an executable that can
only be run on OSX and must be run after every build. This executable makes
a few
Hi,
To download the common file(s) at configure time, you could follow the
approach discussed here:
http://cmake.3232098.n2.nabble.com/is-it-possible-to-download-CMake-modules-at-configure-time-td7583968.html#a7584113
Hth
Jc
On Mon, May 13, 2013 at 6:17 PM, Matthew Woehlke
Hello there.
Compiling open source project OpenCV-2.3.1 on Windows works with cmake 2.8.9.
The other day I updated to cmake 2.8.10, and it stopped working. If I go back
to cmake 2.8.9 it works again.
Has anyone seen this or can anyone point me in the right direction to start
investigating?
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 7b5450075384eb2ba170adf38632a4db2434fa2f (commit)
via
Stamp
diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index 47f1773..dc8aa44 100644
--- a/Source/CMakeVersion.cmake
+++ b/Source/CMakeVersion.cmake
@@ -2,5 +2,5 @@
set(CMake_VERSION_MAJOR 2)
set(CMake_VERSION_MINOR 8)
set(CMake_VERSION_PATCH 10)
-set(CMake_VERSION_TWEAK 20130513
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 e0d897c57be57b4a68fcfa377f3321bd7c5c20f1 (commit)
via
25 matches
Mail list logo
