After messing around with redirecting the make output streams I've discovered
my grievous error of not putting the CTEST_USE_LAUNCHERS inside the CMake cache.
Everything looks good now.
Thanks again David.
Regards,
Ho Cheung
Research Assistant - University of Houston
hocheun...@gmail.com
(832)
The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=13484
==
Reported By:Mahendra Ladhe
Assigned To:
I was under the impression that CTest still greps correctly using multithreaded
make. The Linux dashboards do not seem to have a problem.
I implemented your suggestion of using CTEST_USE_LAUNCHER 1 but now I get a
completely successful build with 0 errors and 0 warnings, which I know for a
fact
On Mon, Aug 20, 2012 at 5:16 PM, Daniel Pfeifer wrote:
> 2012/8/20 David Cole :
> > Call for CMake developers! Please adopt one or more of these bugs if you
> > can.
> >
> > The following 11 bugs are on the CMake 2.8.10 roadmap, but they are
> > UNASSIGNED. They do not have anybody actively workin
ctest will mix stdout and stderr as the output occurs and merge them into a
single stream to send to CDash. *Unless* you use CTEST_USE_LAUNCHERS, in
which case, stdout and stderr are kept separate and sent to CDash as two
strings.
make -j is supported, but you should probably read up on using
CTES
On Monday 20 August 2012, Alexander Neundorf wrote:
> On Monday 20 August 2012, Alexander Neundorf wrote:
> ...
>
> > I'm looking at it right now...
> > I actually haven't figured out yet how that launchers feature works.
> > Should the string "launch" (or "--launch") appear somewhere in the
> > b
2012/8/20 David Cole :
> Call for CMake developers! Please adopt one or more of these bugs if you
> can.
>
> The following 11 bugs are on the CMake 2.8.10 roadmap, but they are
> UNASSIGNED. They do not have anybody actively working on them at the moment.
>
> ...
> http://public.kitware.com/Bug
Thanks David,
That seems to have been the problem.
However, now the error messages are now corrupted like it is some kind of
threading race condition. I assume make -j is supported by CTest/CDash?
http://open.cdash.org/viewBuildError.php?buildid=2525692
Regards,
Ho Cheung
Research Assistant -
David Cole wrote:
> So: fix the style problem, and then go ahead and merge it to 'next'.
>
> Unless you also want me to try it out with Visual Studio 6 just for good
> measure... :-)
>
>
> Let me know,
> David
Thanks for those tests. I've squashed it and merged it to next now.
Thanks,
Steve.
Brad King wrote:
> On 08/19/2012 05:43 PM, Stephen Kelly wrote:
>> Thanks, here are my findings so far, which relate to my extension of that
>> branch at
>> g...@gitorious.org:~steveire/cmake/steveires-
cmake.git:
>
> Thanks for working on this.
Thanks for the feedback. I've updated the branch.
It's probably because you have a "/" in your build name.
CDash uses the build name as one component of a file name on the backend,
so you should avoid using "/" characters (or other filename-problematic
characters) in your SITE and BUILD name values.
HTH,
David
On Mon, Aug 20, 2012 at 3:44 PM,
Apparently the submission isn't uploading my scripts either.
I've attached it in this email here.
release_continuous.cmake
Description: Binary data
Regards,
Ho Cheung
Research Assistant - University of Houston
hocheun...@gmail.com
(832) 215-6347
On Aug 20, 2012, at 2:15 PM, Ho Cheung wrote
2012/8/20 Rolf Eike Beer :
> Stephen Kelly wrote:
>> Stephen Kelly writes:
>> > Brad King wrote:
>> > >> I have pushed a std-cxx-target-property branch to my gitorious repo to
>> > >> illustrate the idea further, but I don't think there is any way to
>> > >> specify which c++ standard to restrict
Hello cmake-developers,
I've been trying to make a Continuous build machine, but my submissions always
get split into 2 separate submissions, one for the "update" and another for the
configure/build/test.
See the "tonic" and "bitcoin-miner1" machines on the Farsight Dashboard.
http://open.cda
On Mon, Aug 20, 2012 at 12:08 PM, David Cole wrote:
> On Mon, Aug 20, 2012 at 8:52 AM, Stephen Kelly wrote:
>
>> David Cole wrote:
>> >> First batch of (unfortunately) *build* errors from Visual Studio:
>> >>
>> >> http://open.cdash.org/viewBuildError.php?buildid=2525364
>> >>
>> >> c_str and
Stephen Kelly wrote:
> Stephen Kelly writes:
> > Brad King wrote:
> > >> I have pushed a std-cxx-target-property branch to my gitorious repo to
> > >> illustrate the idea further, but I don't think there is any way to
> > >> specify which c++ standard to restrict to with MSVC, so the idea may
> >
Call for CMake developers! Please adopt one or more of these bugs if you
can.
The following 11 bugs are on the CMake 2.8.10 roadmap, but they are
UNASSIGNED. They do not have anybody actively working on them at the moment.
http://public.kitware.com/Bug/view.php?id=8170
http://public.kitware.c
On Mon, Aug 20, 2012 at 8:52 AM, Stephen Kelly wrote:
> David Cole wrote:
> >> First batch of (unfortunately) *build* errors from Visual Studio:
> >>
> >> http://open.cdash.org/viewBuildError.php?buildid=2525364
> >>
> >> c_str and const_iterator issues...
> >>
> >> Let me know when you have th
The following issue is now in status NEW (again)
==
http://public.kitware.com/Bug/view.php?id=12998
==
Reported By:Amine Khaldi
Assigned To:
The following issue is now in status NEW (again)
==
http://public.kitware.com/Bug/view.php?id=12951
==
Reported By:Amine Khaldi
Assigned To:
The following issue is now in status NEW (again)
==
http://public.kitware.com/Bug/view.php?id=12264
==
Reported By:Amine Khaldi
Assigned To:
The following issue is now in status NEW (again)
==
http://public.kitware.com/Bug/view.php?id=11536
==
Reported By:Nikita Borodikhin
Assigned
On Sun, Aug 19, 2012 at 6:00 PM, Stephen Kelly wrote:
> Can I get some help to resolve the issues reported here:
>
> http://thread.gmane.org/gmane.comp.programming.tools.cmake.devel/4448/focus=4457
I think the main problem is that
Tests/Module/GenerateExportHeader/libshared/CMakeLists.txt
cons
On 08/19/2012 05:43 PM, Stephen Kelly wrote:
> Thanks, here are my findings so far, which relate to my extension of that
> branch at g...@gitorious.org:~steveire/cmake/steveires-cmake.git:
Thanks for working on this.
> 1) The result string of the $ expression does not allow lists.
> That means
David Cole wrote:
>> First batch of (unfortunately) *build* errors from Visual Studio:
>>
>> http://open.cdash.org/viewBuildError.php?buildid=2525364
>>
>> c_str and const_iterator issues...
>>
>> Let me know when you have the next commit on the stage, and I'll pull it
>> and try again.
I've fix
On Mon, Aug 20, 2012 at 8:37 AM, David Cole wrote:
> On Sun, Aug 19, 2012 at 6:03 PM, Stephen Kelly wrote:
>
>> David Cole wrote:
>> >
>> >
>> > I could run an Experimental based on this branch with Visual Studio and
>> > point you to the CDash results if you'd like.
>> >
>> > Maybe not till tom
On Sun, Aug 19, 2012 at 6:03 PM, Stephen Kelly wrote:
> David Cole wrote:
> >
> >
> > I could run an Experimental based on this branch with Visual Studio and
> > point you to the CDash results if you'd like.
> >
> > Maybe not till tomorrow, though.
>
> That works for me, thanks :)
>
>
> --
>
> Po
On 08/20/2012 08:24 AM, Rolf Eike Beer wrote:
> The gain in efficiency would be just a bonus. My main concern is that
> the current use may happily cause trouble in most cases when an input
> path contains spaces or semicolons because of missing quoting and
> escaping. And most of them build up
Am 2012-08-20 14:00, schrieb Brad King:
On 08/19/2012 08:09 AM, Rolf Eike Beer wrote:
I'm wondering if it makes sense to do a mass replace of
foreach(listvar ${somevar})
to
foreach(listvar IN LISTS somevar)
From what I see this should be more efficient as the variable is not
first
expanded
Stephen Kelly writes:
>
> Brad King wrote:
> >> I have pushed a std-cxx-target-property branch to my gitorious repo to
> >> illustrate the idea further, but I don't think there is any way to
> >> specify which c++ standard to restrict to with MSVC, so the idea may
> >> already be useless or dead
I need to create installer for a product fo Mac OS X using CPack with
PackageMaker as the generator. I have don some small work, but I have many
things that I want to find out.
set(CPACK_PACKAGE_NAME "MyApp")
set(CPACK_PACKAGE_VERSION "${CPACK_PACKAGE_VERSION}")
set(CMAKE_INSTALL_PREFIX /App
On 08/19/2012 04:17 PM, Stephen Kelly wrote:
> maybe the comment I pointed out should be
> removed or made more clear. It doesn't seem to relate to what the code is
> actually about. What do you think?
This is the code in question:
// Make the definition appear properly on the command line.
On 08/19/2012 08:09 AM, Rolf Eike Beer wrote:
> I'm wondering if it makes sense to do a mass replace of
>
> foreach(listvar ${somevar})
>
> to
>
> foreach(listvar IN LISTS somevar)
>
> From what I see this should be more efficient as the variable is not first
> expanded and then parsed again,
33 matches
Mail list logo
