Is the CMake mailing list dead?
Best Regards
Am 24.11.2011 um 15:45 schrieb "NoRulez" :
> So, nobody an idea?
>
> Do I only have to add an foreach loop like in the following example or is
> there more to do:
>
> #get all branches/tags into GIT_BRANCHES/GIT_TAGS
>
> FOREACH(GIT_BRANCH ${GIT_BR
On 11/28/2011 11:35 PM, Robert Dailey wrote:
> I haven't really seen a way to get a list of group matches in a regex. For
> example, string( REGEX MATCH ) only returns the whole string matched, not
> just what was in the capture groups. If I do this:
>
> (\\w+)\\,(\\w+)\\,(\\w+)
>
> and I match t
On 11/28/2011 08:43 PM, J Decker wrote:
> So the idea was, to make the build process a single click (or couple)
> or at least a single application to build. Since CMake knows how to
> build a project, it became easier to maintain a cmakelists.txt which
> does the build than a batch file...
>
> So
On Mon, Nov 28, 2011 at 12:01 PM, Alexander Neundorf
wrote:
> On Saturday 26 November 2011, J Decker wrote:
>> I don't find any documentation on the command that cmake uses with a
>> cmake -E --check-build-system Does this option happen to set any
>> specific cmake variable indicating that it
I haven't really seen a way to get a list of group matches in a regex. For
example, string( REGEX MATCH ) only returns the whole string matched, not
just what was in the capture groups. If I do this:
(\\w+)\\,(\\w+)\\,(\\w+)
and I match that regex against this string:
hello,world,today
I should
On 11/28/2011 03:54 PM, Felipe Lema wrote:
> Hello, everyone
>
> I was trying to use cmake to build python c++ extensions in win7, but
> couldn't get cmake to detect PythonLibs. At least, not without editing the
> windows registry. Since it could detect PythonInterp, I got it working
> using the d
Is it possible to have 2D arrays in CMake? As far as the core syntax is
concerned, it seems like only 1D arrays are supported. So far I've had to
work around this issue by using a flat array and skipping over elements
using foreach() with a range and step.
Any ideas? Thanks.
-
Robert Dail
On Saturday 26 November 2011, J Decker wrote:
> I don't find any documentation on the command that cmake uses with a
> cmake -E --check-build-system Does this option happen to set any
> specific cmake variable indicating that it is doing a check build?
>
> I'm inquiring and I saw a post about
So the idea was, to make the build process a single click (or couple)
or at least a single application to build. Since CMake knows how to
build a project, it became easier to maintain a cmakelists.txt which
does the build than a batch file...
So my top most level project now is a series of target
I have recently moved to using 64bit Kubuntu Oneiric when supports
multiarch. I understand that building 32 bit from my 64 install is as
simple as adding the "-m32" option to gcc. Asking cmake to add that
flag is easy but i don't know how to ask cmake to only look for 32 bit
libraries in FindPackag
Thanks a lot for the information. I would check the documentation and continue
working on this.
thanks again.
--
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:
Hello, everyone
I was trying to use cmake to build python c++ extensions in win7, but
couldn't get cmake to detect PythonLibs. At least, not without editing the
windows registry. Since it could detect PythonInterp, I got it working
using the directories provided from methods inside the interpreter
On Mon, Nov 28, 2011 at 9:15 AM, Nils Gladitz wrote:
> Yes, thank you, that fixed it.
>
> Maybe this should be updated in the default template generated by CDash(?).
>
> Nils
>
Yes, it should. :-)
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com
Hello,
I've found why it was not working: you just need to manually load the
macro with "load macro project" and then you need to find the
CMakeVSMacros2.vcmacros file and load it. You find the file in the
install dir of cmake e.g. under "share/cmake-2.8/Templates". Then
everything works with
Yes, thank you, that fixed it.
Maybe this should be updated in the default template generated by CDash(?).
Nils
--
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
If you're using 2.8.6 (you said you were, right?) ... do this:
set(CTEST_CONFIGURATION_TYPE "${JOB_BUILD_CONFIGURATION}")
instead of this:
set(CTEST_BUILD_CONFIGURATION "${JOB_BUILD_CONFIGURATION}")
Setting both will not hurt, but if both are set,
CTEST_CONFIGURATION_TYPE is used, and not C
On Mon, Nov 28, 2011 at 5:05 AM, J Decker wrote:
> On Sun, Nov 27, 2011 at 8:30 AM, Michael Hertling wrote:
>> On 11/26/2011 07:14 PM, J Decker wrote:
>>> Earlier I wondered if there was a way to stop recusive invocation of a
>>> build command in a cmake script - I found something like a solution
I'm using CDash's (1.8.2) test scheduling and have trouble with a few
tests added with the newer "add_test(NAME ..." signature.
Tests added with the new signature are "Not Run" and I get the following
test output:
Test not available without configuration. (Missing "-C "?)
On a client machi
On Sun, Nov 27, 2011 at 8:30 AM, Michael Hertling wrote:
> On 11/26/2011 07:14 PM, J Decker wrote:
>> Earlier I wondered if there was a way to stop recusive invocation of a
>> build command in a cmake script - I found something like a solution;
>> when I run the command, set an environment variabl
19 matches
Mail list logo