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
#
11 matches
Mail list logo
