in an execute_process() function with ${ECHO} (/bin/echo)what does one
set for WORKING_DIRECTORY?
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on
Hi,
I have collected a few modules:
FindDL.cmake
FindGDAL.cmake
FindGeoTIFF.cmake
FindMySQL.cmake
FindOracle.cmake
FindPostgreSQL.cmake
FindPROJ4.cmake
FindSpatialIndex.cmake
FindSQLite3.cmake
Perhaps CMake would find some of them useful.
Some are already in CMake like FindGDAL.cmake, but in my
On 24/12/10 00:02, Mateusz Loskot wrote:
> Hi,
>
> I have collected a few modules:
> FindDL.cmake
> FindGDAL.cmake
> FindGeoTIFF.cmake
> FindMySQL.cmake
> FindOracle.cmake
> FindPostgreSQL.cmake
> FindPROJ4.cmake
> FindSpatialIndex.cmake
> FindSQLite3.cmake
>
> Perhaps CMake would find some of th
On 23 December 2010 22:05, David Cole wrote:
> Much easier on the eyes, much nicer in every respect except there's one
> extra file in your source tree now. Small price to pay for readability and
> future maintainability...
Agreed. I think what would be even nicer would be to be able to do
common
On Thu, Dec 23, 2010 at 3:59 PM, KC Jones wrote:
> > Thanks for your comments and questions. May we quote you on that? ("cmake
> is elegant in the extreme ... great tool")
>
> Of course. Since all the code I work with is published on multiple OSes,
> cmake is a godsend. I'm actively working on
Hi,
it seems that cmake doesn't properly escape the commandlines for custom
commands. I'm adding a list of strings which include whitespace and also
parenthesis "()" as arguments to a custom command. Additionally this
custom command is running a target built by the same project.
Unfortunately CMa
> Thanks for your comments and questions. May we quote you on that? ("cmake is
> elegant in the extreme ... great tool")
Of course. Since all the code I work with is published on multiple OSes, cmake
is a godsend. I'm actively working on replacing as much of our legacy build
methods with cmak
Hey,
I've got a library that provides several cmake modules and also uses
them. Some of these modules have additional files, e.g. to be used with
CONFIGURE_FILE. The question is, how do I locate these additional files
so that they work in both cases, in project and installed?
${CMAKE_ROOT}/Modules
-- Forwarded message --
From: John Drescher
Date: Thu, Dec 23, 2010 at 12:03 PM
Subject: Re: [CMake] Copying some files using CMake
To: Stormwind Dev
On Thu, Dec 23, 2010 at 11:53 AM, Stormwind Dev
wrote:
> Thanks for your reply John. There is one question left about your GetRu
Thanks for your reply John. There is one question left about your
GetRuntime module. The files you copy are located within the CMake
directory in your root source dir, right?
Best Michael
Am 23.12.2010 17:28, schrieb John Drescher:
On Thu, Dec 23, 2010 at 11:18 AM, Stormwind Dev
wrote:
Dear
On 12/23/2010 9:59 AM, Mike McQuaid wrote:
A few questions:
What platforms does it need to be tested on?
At least one. The important thing is that it actually has a test, that
will be run with make test on CMake after the code is merged into CMake.
The dashboards will take care of testing it
On Thu, Dec 23, 2010 at 11:18 AM, Stormwind Dev
wrote:
> Dear List,
>
> I've got a question on copying some files from one directory to another
> using CMake.
>
> Let's say, I got some libraries collected in a special directory. I want
> CMake to copy these libs to the distribution directory of my
Dear List,
I've got a question on copying some files from one directory to another
using CMake.
Let's say, I got some libraries collected in a special directory. I want
CMake to copy these libs to the distribution directory of my project.
Using add_custom_command, I managed to have CMake cop
Am 23.12.2010 12:39, schrieb Lukas Woodtli:
Everything builds without error.
But if I launch my application I get an error :
The procedure entry point _Z17qt_message_output9QtMsgTypePKc could not
be located in the dynamic link library QtCore4.dll
It's a common problem - you're using the wron
On 23 December 2010 14:47, Michael Wild wrote:
> Well, I also did some contributions to homebrew, and I have to agree
> that patches get picked up really quickly. There's one big "but",
> though: Writing a formula is fairly simple. Just copy an existing
> formula that is similar to your favourite
On 23 December 2010 14:30, Bill Hoffman wrote:
> Something like this perhaps:
>
> http://www.cmake.org/cmake/help/mailing.html
> http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Excuse my extreme ignorance, I had no idea that existed.
Subscribing!
> 1. you have some code.
>
On 12/23/2010 02:44 PM, Mike McQuaid wrote:
> On 23 December 2010 13:24, David Cole wrote:
>> How do we make it very hard? What about KDE and Homebrew make this very
>> easy? Specifics, please.
>
> Firstly, http://producingoss.com/ is a great read.
>
> Specifically though, Homebrew is pretty muc
Hi Mike and all,
On Thu, Dec 23, 2010 at 21:58, Mike McQuaid wrote:
> On 23 December 2010 12:43, David Cole wrote:
> I think the main problem is that you make it very hard for people to
> contribute. KDE and Homebrew (two other open-source projects I've
> written a lot of code for over the year
On 12/23/2010 8:44 AM, Mike McQuaid wrote:
On 23 December 2010 13:24, David Cole wrote:
How do we make it very hard? What about KDE and Homebrew make this very
easy? Specifics, please.
I think for you guys general guidelines on what patches would/wouldn't
be accepted would be a good start.
On 23 December 2010 13:24, David Cole wrote:
> How do we make it very hard? What about KDE and Homebrew make this very
> easy? Specifics, please.
Firstly, http://producingoss.com/ is a great read.
Specifically though, Homebrew is pretty much the golden child of
encouraging external contribution.
On Thu, Dec 23, 2010 at 8:23 AM, Johan Björk wrote:
>
>
> On Thu, Dec 23, 2010 at 1:43 PM, David Cole wrote:
>
>> On Wed, Dec 22, 2010 at 12:57 PM, KC Jones wrote:
>>
>>> Feeling really uneasy about putting this out there, but here goes...
>>>
>>> I have an app that I am building with cmake (2.8
On Thu, Dec 23, 2010 at 7:58 AM, Mike McQuaid wrote:
> On 23 December 2010 12:43, David Cole wrote:
> > Neither do we:
> > http://public.kitware.com/Bug/view.php?id=10067
>
> > As always, as developers we find ourselves constantly working to improve
> > what we have: fixing bugs, implementing ne
On Thu, Dec 23, 2010 at 1:43 PM, David Cole wrote:
> On Wed, Dec 22, 2010 at 12:57 PM, KC Jones wrote:
>
>> Feeling really uneasy about putting this out there, but here goes...
>>
>> I have an app that I am building with cmake (2.8) on both Mac (10.6.40 and
>> Linux (Ubuntu 10.04).
>> The app de
On 23 December 2010 12:43, David Cole wrote:
> Neither do we:
> http://public.kitware.com/Bug/view.php?id=10067
> As always, as developers we find ourselves constantly working to improve
> what we have: fixing bugs, implementing new features, answering questions on
> the mailing list, blogging/co
On Wed, Dec 22, 2010 at 12:57 PM, KC Jones wrote:
> Feeling really uneasy about putting this out there, but here goes...
>
> I have an app that I am building with cmake (2.8) on both Mac (10.6.40 and
> Linux (Ubuntu 10.04).
> The app depends on some libraries (Qt4.6 (no plugins) and a customized
On 12/22/2010 11:24 PM, Andreas Mohr wrote:
> On Wed, Dec 22, 2010 at 04:15:07PM -0500, cmake-requ...@cmake.org wrote:
>> Date: Wed, 22 Dec 2010 09:57:11 -0800
>> From: KC Jones
>> Subject: [CMake] CPack 101
>
>> And I just don't seem to get it. I know this is very possible. I know this
>> is m
Hi there
I tried to use CMake for a small Qt project.
Here is my CMalkeLists.txt
[CODE]
# set project's name
PROJECT(TeXular)
cmake_minimum_required(VERSION 2.8)
SET(CMAKE_BUILD_TYPE Release)
# enable warnings
# ADD_DEFINITIONS( -c -g -Wall -frtti -fexceptions -mthreads
-enable-stdcall-fixup -W
On 22 December 2010 22:24, Andreas Mohr wrote:
> To put it simply, I was just not happy the entire time while
> trying to implement this and not finding any satisfying (well-crafted)
> solution,
> only ugly, very bad or semi-failing workarounds.
> That kind of work should be _fun_, especially whe
To start with, Charm might be a good example of how to use CPack, it's
an internal tool we've written in Qt and use CPack to do all the
packaging:
https://github.com/KDAB/Charm
Check particularly the CMakeLists.txt and Charm/CMakeLists.txt for all
the CPack-relevant logic.
On 22 December 2010 17
On 22.12.10 23:24:35, Andreas Mohr wrote:
> - there's no cmake -E rename available (perhaps for reasons of build rule
> atomicity)
Hmm my cmake -E help tells me different:
...
rename oldname newname- rename a file or directory (on one volume)
...
This is cmake version 2.8.2.20100804-ga
30 matches
Mail list logo
