Hi,
If it's of any help, I used the pcrecpp library by Google (it's part
of PCRE). With pcrecpp, most operations were only 1-3 lines long. The
only problem I found is PCRE provided no way to get the previous/next
match, which CMake needs.
On Tue, Nov 15, 2011 at 4:25 PM, Alexandru Ciobanu
On 11/11/2011 9:36 PM, Peter Collingbourne wrote:
Note that this generator is *nix only (it relies on POSIX shell
functionality), and will only be built on *nix platforms. I am not
interested in Windows support, but I understand that others have
expressed an interest in adding support.
How
On Tue, Nov 15, 2011 at 5:29 PM, Bill Hoffman bill.hoff...@kitware.comwrote:
On 11/11/2011 9:36 PM, Peter Collingbourne wrote:
Note that this generator is *nix only (it relies on POSIX shell
functionality), and will only be built on *nix platforms. I am not
interested in Windows support,
On 11/15/2011 12:54 PM, Nicolas Desprès wrote:
Too much in my opinion. Specially the operator of the shell. Using
cmake -E is the first step. I am planning to suggest an evolution of
Ninja to fix this issue. Actually, it is the main issue which stop me
while writing the beginning of this
On Monday 14 November 2011, you wrote:
On 11/14/2011 4:01 PM, Alexander Neundorf wrote:
Instead of adding the code to the bottom of GenerateImportPropertyCode
please create a separate method next to it for that part.
Done, in an updated version of the
On Tue, Nov 15, 2011 at 1:19 PM, Alexander Neundorf neund...@kde.org wrote:
On Monday 14 November 2011, you wrote:
On 11/14/2011 4:01 PM, Alexander Neundorf wrote:
Instead of adding the code to the bottom of GenerateImportPropertyCode
please create a separate method next to it for that part.
On 11/15/2011 1:24 PM, David Cole wrote:
On Tue, Nov 15, 2011 at 1:19 PM, Alexander Neundorfneund...@kde.org wrote:
function(check_for_file _file _target)
if(NOT EXISTS _file)
message(FATAL_ERROR ... long error message...)
endfunction()
check_for_file(libFoo123.so Foo)
...
Hi all,
I'm did do some work in order to enhance CPack builtin documentation
support.
see:
http://www.cmake.org/Bug/view.php?id=10067
this is located in stage branch ImproveCPackDoc.
I think the first two commits of this branch are ready for master
so I did merge it to next.
Those basically
On Tuesday 15 November 2011, Brad King wrote:
On 11/15/2011 1:24 PM, David Cole wrote:
On Tue, Nov 15, 2011 at 1:19 PM, Alexander Neundorfneund...@kde.org
wrote:
function(check_for_file _file _target)
if(NOT EXISTS _file)
message(FATAL_ERROR ... long error message...)
On 11/15/2011 3:54 PM, Alexander Neundorf wrote:
Maybe you'll prefer a more map-like implementation ?
Yes.
I don't like the function because it pollutes the global namespace of
functions. I took great care to design imported targets so they only
affect a directory namespace. They are very
On 11/14/2011 09:15 PM, Robert Dailey wrote:
On Mon, Nov 14, 2011 at 1:59 PM, Michael Hertling mhertl...@online.dewrote:
On 11/14/2011 06:17 PM, Robert Dailey wrote:
Well maybe you can tell me I'm doing this wrong then, but based on how I
am
currently setting up my third party libraries, it
Hi all,
When using a custom command in a macro I see some strange behavior.
The following setup is used:
I have a macro, called bundle, in this macro a custom command is added.
This command uses a library as target, and executes cpack with a
configuration. I use cpack to create a zip file inside
The Open Source Electronic Health Record Agent (OSEHRA) will start a
weekly teleconference to discuss the current set of OSEHRA software
development tools on Wednesday, November 16 from 3:30pm to 4:30pm EST.
This first meeting will provide an introduction to the many software
development tools
On 11/14/2011 09:31 PM, Jookia wrote:
I have the following code:
# -- DOXYGEN
find_package(Doxygen)
set(docsDir ${CMAKE_BINARY_DIR}/docs/)
add_custom_command(OUTPUT ${docsDir}
COMMAND ${CMAKE_COMMAND} -E make_directory
${docsDir} VERBATIM)
add_custom_target(docs
On Tue, Nov 15, 2011 at 4:49 AM, Michael Hertling mhertl...@online.dewrote:
As David has outlined in the meantime, the advice is not about using
FIND_LIBRARY() - which has not been mentioned a single time - but to
assemble full paths from the libraries' directories and the libraries
Hello,
I think I've already found the problem. In the custom command I run a CPack
script, and CPack triggers a full build of the project, which in turn again
triggers the custom command (and thus the CPack command).
Is it possible to make the CPack config so that only a specific target is
being
On 11/14/2011 08:11 PM, Mathias Gaunard wrote:
What is the recommended way to define libraries with custom build commands?
This trick seems to be the only way:
if(NOT EXISTS ${CMAKE_CURRENT_BINARY_DIR}/dummy.cpp)
file(WRITE ${CMAKE_CURRENT_BINARY_DIR}/dummy.cpp)
endif()
On 11/12/2011 12:41 AM, david_bjorn...@agilent.com wrote:
I'm getting a Link error on Linux when I use CMake 2.8.6 or 2.8.5. If use
CMake 2.6.3, with the exact same configuration, the link works.
I did a diff on the build.make from 2.8.6 and 2.6.3 and found when I use
cmake 2.8.6 On
On 11/15/2011 11:52 AM, Michael Hertling wrote:
Could you boild down this issue to a minimal and self-sufficient example
- i.e. a project working with 2.6 (quite old) but failing with 2.8 - and
post it here for further investigation?
There was a bug created for this, and the problem found.
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.
Now, some of them put a
if(UNIX)
find_package(PkgConfig)
endif()
around it, some use it on all platforms.
In theory it
On 11/11/2011 3:21 PM, Robert Dailey wrote:
I'm using Cygwin with the MSVC toolchain and I need ccmake.exe. I can't
use the one from the Cygwin package manager because it's older than the
version I'm using. I'd like to build it myself through Visual Studio
like I did with cmake and cmake-gui if
The issue has been resolved
http://public.kitware.com/Bug/view.php?id=12575
++David-Bjornbak;
--
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:
Am Dienstag, 15. November 2011, 18:07:16 schrieb Alexander Neundorf:
But our (KDEs) Windows developer team says that even if pkg-config is found
under Windows, and even if it reports something, they actively want to
ignore it.
The reason for this is that for those packages under Windows the
On Tuesday 15 November 2011, Rolf Eike Beer wrote:
Am Dienstag, 15. November 2011, 18:07:16 schrieb Alexander Neundorf:
But our (KDEs) Windows developer team says that even if pkg-config is
found under Windows, and even if it reports something, they actively
want to ignore it.
The
On 11/15/2011 12:59 PM, Robert Dailey wrote:
The windows binaries unfortunately do not contain ccmake.exe.
You have to use cmake-gui. There is no version of ccmake that will work
for what you want to do, sorry...
-Bill
--
Powered by www.kitware.com
Visit other Kitware open-source
The windows binaries unfortunately do not contain ccmake.exe.
-
Robert Dailey
On Tue, Nov 15, 2011 at 11:24 AM, Bill Hoffman bill.hoff...@kitware.comwrote:
On 11/11/2011 3:21 PM, Robert Dailey wrote:
I'm using Cygwin with the MSVC toolchain and I need ccmake.exe. I can't
use the
Hi,
I am now having issues with finding the raptor software for the build
of the soprano project on Harmattan (N9 OS and distribution). It works
on desktop and in scratchbox. It does not work in qemu though.
It looks weird because redland was found properly, and the those
find_package lines are
I have tried to grab more debug outputs, and here are my relevant printouts:
statusPC_RAPTOR2_LIBDIR: /usr/lib
statusPC_RAPTOR2_LIBRARY_DIRS:
statusPC_RAPTOR2_INCLUDEDIR: /usr/include/raptor2
statusPC_RAPTOR2_INCLUDE_DIRS: /usr/include/raptor2
It seems okay to me, thus I am now even more lost..
On Mon, Nov 14, 2011 at 3:37 PM, Dan Kegel d...@kegel.com wrote:
On Sat, Nov 12, 2011 at 11:04 AM, Alexander Neundorf
a.neundorf-w...@gmx.net wrote:
* please give current cmake master a try, it has several improvements.
I'll give cmake master a spin sometime this week.
Tried it. It seems to
On Tue, Nov 15, 2011 at 1:28 PM, Dan Kegel d...@kegel.com wrote:
Tried it. It seems to get the linking right, though I'm not
sure how excited my users are going to be about how
deeply buried those source files are in the GUI. There's
a whole lot of visual cruft around them.
Worse, the Team
I'd still like to know how to explain to cmake that the command produces
2 files, but at least I can get rid of my hack.
That (assuming just a simple object file is produced by compilation)
is one of several general limitations with CMake language support. For
example, my understanding is
On 11/14/2011 3:24 PM, Alan W. Irwin wrote:
If you are willing to make such an OCaml summary, I would be willing
to do the same thing for Ada to make our joint case to the CMake
developers of what kind of additional generic language support is
needed by CMake to deal with the complicated build
On 11/15/2011 10:13 PM, Stefan Monnier wrote:
I'm trying to use CMake for a new project here. This project (a new
programming language, whose first implementation is in OCaml) is
currently in the very first stages (I have barely more than the lexer
written) and doesn't require anything
On 2011-11-15 22:13-0500 Stefan Monnier wrote:
I'd still like to know how to explain to cmake that the command produces
2 files, but at least I can get rid of my hack.
That (assuming just a simple object file is produced by compilation)
is one of several general limitations with CMake language
(Visual studio bug actually - as I was trying to find the actual
difference in the output, and finding none, I have to assume that
somehow visual studio is causing the addtion of .dll on a project
without a '.' in it )
Using visual studio 2010 as a generator...
The following fails to find the
On 15.11.11 21:30:45, Laszlo Papp wrote:
I have tried to grab more debug outputs, and here are my relevant printouts:
statusPC_RAPTOR2_LIBDIR: /usr/lib
statusPC_RAPTOR2_LIBRARY_DIRS:
statusPC_RAPTOR2_INCLUDEDIR: /usr/include/raptor2
statusPC_RAPTOR2_INCLUDE_DIRS: /usr/include/raptor2
It
-- RAPTOR_LIBRARIES: /usr/lib/libraptor2.so
-- RAPTOR_INCLUDE_DIR: /usr/include/raptor2
and
root@Kaname:/usr/src/packages/BUILD/Build# dpkg -S /usr/lib/libraptor2.so
libraptor2-dev: /usr/lib/libraptor2.so
root@Kaname:/usr/src/packages/BUILD/Build# dpkg -S /usr/include/raptor2/raptor.h
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 608d05b469a446aeb85c0d3374ccf2a3f397292b (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 f1197ff0dac1ab02b7515d79a2c46075538360c5 (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 1e055d374e08552522216c1dc4bc68ab876e922f (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 c616f46fc56ae1433b6dcc54270b652f99fb7904 (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 6ac35e5cb3538c40bbfa662c6485684c26c7297d (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 7efd93cd722d102d20602663536197904a8f29bf (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 a9e686d68b5375c471c7204b818fdd2c0a547000 (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 9a91ff528ba6dc5c11fdd84b3a8577d37d896f03 (commit)
via
45 matches
Mail list logo
