On 11/15/2011 4:50 PM, Brad King wrote:
On 11/15/2011 3:54 PM, Alexander Neundorf wrote:
Maybe you'll prefer a more map-like implementation ?
The commit you merged to next:
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=3c265207
looks pretty good. I think the message would look
I'm experimenting with using @rpath instead of @executable_path and
@loader_path, because @rpath is useful in some situations where the others
don't work as well. For example, I want to avoid setting DYLD_LIBRARY_PATH
when using a relocatable SDK. Using @rpath allows a user to embed a path
Hi everyone,[ CMake + TRE ]I was able to make CMake use TRE, by changing the RegularExpression.{cxx,hxx.in} files.I ran the CMake tests, and 100% pass. See the attached log file.(NOTE: Bootstrap, complex, complexOne were initially not aware of TRE dependency, but I fixed that easily).[ Impact of
On Thursday 17 November 2011, Alexandru Ciobanu wrote:
Hi everyone,
[ CMake + TRE ]
I was able to make CMake use TRE, by changing the
RegularExpression.{cxx,hxx.in} files.
I ran the CMake tests, and 100% pass. See the attached log file.
(NOTE: Bootstrap, complex, complexOne were
On 2011-11-17, at 3:26 PM, Alexander Neundorf wrote:
[ Regular expressions syntax ]
In terms of regular expressions syntax, the only difference that I've seen
is that TRE treats the curly brackets { and } as special characters,
because it uses them for its approximate matching. Details
On 11/17/2011 3:19 PM, Alexandru Ciobanu wrote:
I was able to make CMake use TRE, by changing the
RegularExpression.{cxx,hxx.in} files.
Those are down in Source/kwsys which is a directory shared by
projects other than just CMake. We cannot touch the files there.
Instead you will need to
On 11/17/2011 11:49 AM, Clinton Stimpson wrote:
I'm experimenting with using @rpath instead of @executable_path and
@loader_path, because @rpath is useful in some situations where the others
don't work as well. For example, I want to avoid setting DYLD_LIBRARY_PATH
when using a relocatable
On Thu, Nov 17, 2011 at 10:59 AM, Brad King brad.k...@kitware.com wrote:
looks pretty good. I think the message would look better if the generated
code looked like this:
The new version of the message you committed still didn't format
nicely for me with long file paths containing spaces.
On 11/17/2011 4:28 PM, Sean McBride wrote:
Has using the POSIX regex.h APIs been ruled out?
Windows?
-Brad
--
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:
On 11/15/2011 2:43 PM, Eric Noulard wrote:
The idea is to add extra CMake comment markup, i.e.
# CPACK_PACKAGE_NAME - The name of the package (or application). If
# not specified, defaults to the project name.
becomes:
##variable
# CPACK_PACKAGE_NAME - The name of the package (or
2011/11/17 Brad King brad.k...@kitware.com:
On 11/15/2011 2:43 PM, Eric Noulard wrote:
The idea is to add extra CMake comment markup, i.e.
# CPACK_PACKAGE_NAME - The name of the package (or application). If
# not specified, defaults to the project name.
becomes:
##variable
#
Hello everyone!
I found in previous message there is none option to specify to
find_library function to search just static library. It was for CMake 2.6.
Has it got any change with the new version of CMake?
I try to specify the name of the library like this:
find_library(MY_STATIC_LIB NAMES
From: Andreas Pakulat Sent: 16 November 2011 19:50
I'm just starting to use the cpack module in cmake to put together TGZ.
I use TARGET_LINK_LIBRARIES to specify which libs to use during linking.
Is there a way to get a list of the libs that are found and include them in
my TGZ?
I can
Hi,
the issue (http://public.kitware.com/Bug/view.php?id=11144) is already
closed but the problem still exists.
If I use the following:
SET(CPACK_NSIS_MUI_FINISHPAGE_RUN ${PROJECT_NAME}.exe)
Then the file project.nsi contains the following string and the application
isnt launched:
Hi,
the
issue (http://public.kitware.com/Bug/view.php?id=11144)
is already closed but the problem still exists.
If I use
the following:
SET(CPACK_NSIS_MUI_FINISHPAGE_RUN
"${PROJECT_NAME}.exe")
Then the
file project.nsi contains the following string and the application isn’t
launched:
On 11/17/2011 10:28 AM, Romain LEGUAY wrote:
Hello everyone!
I found in previous message there is none option to specify to
find_library function to search just static library. It was for CMake 2.6.
Has it got any change with the new version of CMake?
AFAIK, it hasn't, since the root of
On 11/17/2011 12:28 AM, Joe Brandt wrote:
I have a couple issues, that I'd like to help fix, with the current
FindTCL.cmake, FindTclsh.cmake, FindWish.cmake, and FindTclStub.cmake that
make them unusable for me. The first is they do not always find the
various components from the same Tcl
On 11/16/2011 06:36 PM, Jookia wrote:
I've actually used that workaround, but it seems dirty as it shows up in
IDE targets like Visual Studio or other IDEs or makefiles. In fact, I
kind of like the 'generating /docs' part of the makefile.
Would it just be smarter to rename the target
On 11/10/2011 06:48 PM, vagn scott wrote:
in my CMakeLists.txt file I have a statement
project(hello_foo_baz)
This defines PROJECT_NAME among other things.
is there something like
cmake --dump-var PROJECT_NAME
that would output the string
hello_foo_baz
On 11/16/2011 4:03 PM, Alan W. Irwin wrote:
Hi Bill:
Your summary shows you misunderstood what I said so I have to correct
that. The basic issue I have with your interpretation is additional
generic language support != Creating a generic way to add new
languages
OK, let me try again.
Hi
I have a project that has to be compiled with two different compilers on
the same computer.
Can I do that from the same CMakeLists.txt file?
Specifically I am wondering:
- CMake finds a compiler and makes a test. A colleague has tried to change
the compiler variables but CMake made the test
Hallo,
I'am currently in the process of converting a Visual Studio 2010 project
to CMake. There are three (sub) projects each of which results in a
staticaly linked library. This libraries are then combined into a
single .dll file.
Well actually that's how it should be (and is set up in CMake).
On 17 November 2011 16:30, Matthias Wieding-Drewes m...@wieding-drewes.de
wrote:
I'am currently in the process of converting a Visual Studio 2010 project
to CMake. There are three (sub) projects each of which results in a
staticaly linked library. This libraries are then combined into a
I totally agree with your #2. I was thinking that it would be easier to
try and update the existing ones, rather than create new ones, at least
from the perspective of getting something done more quickly. The main
issue with that is that a new FindTclTk doesn't need to deal with backwards
CMake Version: 2.8
Generator: Visual Studio 2008
Problem: Two install commands are used per library. First command
should only install libraries to lib/debug when the build type is
Debug. The second command should only install libraries to the
lib/release directory. When the build type is Debug
Hello guys!
There are lots of informations on internet about how to create DEPENDS on
CMake, but none of them answered my question.
I have a daemon being compiled very well with CMake. Now, i want to pack
this binary to distribution.
Once the clients have a wide variety of Linux distributions, i
On Thursday 17 November 2011, Alan W. Irwin wrote:
Hi Alex:
On 2011-11-15 18:07+0100 Alexander Neundorf wrote:
Hi,
cmake ships with a FindPkgConfig.cmake file, which is used by some Find-
modules.
Also in KDE, we have quite a lot of Find-modules which use
FindPkgConfig.cmake.
On Thu, Nov 17, 2011 at 12:26 PM, Alexander Neundorf
a.neundorf-w...@gmx.net wrote:
On Thursday 17 November 2011, Alan W. Irwin wrote:
Hi Alex:
On 2011-11-15 18:07+0100 Alexander Neundorf wrote:
Hi,
cmake ships with a FindPkgConfig.cmake file, which is used by some Find-
modules.
To use two different compilers, you simply need two different build
trees. Same CMakeLists file, but different build trees.
You should not specify the compiler in your CMakeLists.txt files at
all, but rather set CC and CXX env vars to control the compiler when
first generating a build tree.
See
On Thursday 17 November 2011, David Cole wrote:
...
If a project does something like this (distributes a file with
build/install time information in it) but then lets the end user of
the binary installation put it wherever they please.. then the
that's what I hear from our Windows
On Thu, Nov 17, 2011 at 2:06 PM, Alexander Neundorf
a.neundorf-w...@gmx.net wrote:
On Thursday 17 November 2011, David Cole wrote:
...
If a project does something like this (distributes a file with
build/install time information in it) but then lets the end user of
the binary installation put
http://label.heavyartillery.us/packages/email_list_signup/single_pages/dashboard/reports/fkgfhdol.htm
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages
Am Donnerstag, 17. November 2011, 14:36:00 schrieb David Cole:
On Thu, Nov 17, 2011 at 2:06 PM, Alexander Neundorf
a.neundorf-w...@gmx.net wrote:
On Thursday 17 November 2011, David Cole wrote:
...
If a project does something like this (distributes a file with
build/install time
Am Donnerstag, 17. November 2011, 18:26:08 schrieb Alexander Neundorf:
Let's say package Foo (unrelated to KDE, and unrelated to cmake) has been
ported from UNIX to Windows, and installs a pkgconfig file.
This pkgconfig file is generated at the time when the binary package for
Foo is
Am Donnerstag, 17. November 2011, 21:38:20 schrieb Hendrik Sattler:
Am Donnerstag, 17. November 2011, 18:26:08 schrieb Alexander Neundorf:
Let's say package Foo (unrelated to KDE, and unrelated to cmake) has been
ported from UNIX to Windows, and installs a pkgconfig file.
This pkgconfig
Hi Alex:
On 2011-11-17 18:26+0100 Alexander Neundorf wrote:
The [pkg-config Windows] issue is the following:
Let's say package Foo (unrelated to KDE, and unrelated to cmake) has been
ported from UNIX to Windows, and installs a pkgconfig file.
This pkgconfig file is generated at the time when
http://11thrru.org/admin/poefdg.htm
--
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:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to
On 2011-11-17 21:43+0100 Hendrik Sattler wrote:
Am Donnerstag, 17. November 2011, 21:38:20 schrieb Hendrik Sattler:
Am Donnerstag, 17. November 2011, 18:26:08 schrieb Alexander Neundorf:
Let's say package Foo (unrelated to KDE, and unrelated to cmake) has been
ported from UNIX to Windows, and
On 11/17/2011 06:12 PM, Stephen Torri wrote:
CMake Version: 2.8
Generator: Visual Studio 2008
Problem: Two install commands are used per library. First command
should only install libraries to lib/debug when the build type is
Debug. The second command should only install libraries to the
Hi,
sorry, I forgot to add the CMake/CPack Version.
I use cmake v2.8.6
Best Regards
Von: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] Im Auftrag von
NoRulez
Gesendet: Donnerstag, 17. November 2011 10:46
An: CMake MailingList
Betreff: [CMake] Problems with CPack/NSIS and
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 21469b65dd9238b1737acfcd57886f83578ecab7 (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 5999dd07a879f73a1e5e233a4a4ea88d3bc6afce (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 d9b78923e37166af378de4a9cb371c3410e82758 (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 db52df11959d67c43aa1f1f87782230fbb9471ef (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 d2a781d6324fcb0b0b5fa7ce69ffa169f8947318 (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 0555ea34fb72434d5c094945ffaf49f9af5a0c41 (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 81df5a65f1e6459ae0e6e82bd030b9acc037ca44 (commit)
via
47 matches
Mail list logo
