I am a bit late to the thread but I also had this problem so I made it a
"policy" NOT to install the VS update that broke the Manifest thing. Easy for
me as I am a single guy shop :-) but it did get rid of the problem, or more
correctly worked around the problem. Of course the downside is that I
On Tue, May 3, 2011 at 12:17 PM, Bill Hoffman wrote:
> My blog entry might help:
>
> http://www.kitware.com/blog/home/post/4
Thanks, Bill. That's a good summary of the issues. It would have been
really useful to me a few days ago :), but hopefully this saves
someone else some time. The tip about
with absolutely no joy.
Whenever I try to build a solution for my project, the cmake test for
the fortran compiler generates a solution file for VS 8 that can't be
processed by VS 8.
So far I've pissed away about 2/3 of a day between trying to rebuild
CMake (I found a reference to something
I think the canonical way to do this is by handling this logic in a
wrapper script.
add_test -> wrapper script -> run test
-> check status and delete if OK
hth,
tyler
On Sat, May 7, 2011 at 3:13 PM, Belcourt, K. Noel wrote:
> Hi,
>
> I apologize if th
Try searching for "notes" on this page:
http://www.cmake.org/cmake/help/ctest-2-8-docs.html
On Mon, May 9, 2011 at 5:06 AM, NoRulez wrote:
> Hi,
>
> can anyone tell me how I can add CDash notes which i can fill up in a
> CTestScript file?
>
> The Problem is that i want to add the library version
Hi,
I am using cmake 2.8.3 and the generator for vs2005.
How can I specify Additional Manifest file through cmakelist.txt . This
option is found in Project Properties -> Manifest Tool ->Input and
Output->Additional Manifest Files .
___
Powered by www.kitw
Hi,
can anyone tell me how I can add CDash notes which i can fill up in a
CTestScript file?
The Problem is that i want to add the library versions from the build slave to
know on which system the tests are running ok and on which the tests fails.
Thanks in advance
Best Regards
___
Hi Michael,
On Thu, May 5, 2011 at 10:48 PM, Michael Hertling wrote:
>
> IMO, your approach looks quite reasonable; however, I'm not completely
> happy with it... ;) Please note that the following remarks are just my
> personal point of view, and of course, one can have different notions.
>
> The
Hi Eric,
> You should use:
> execute_process(
> COMMAND ${CMAKE_COMMAND} -E create_symlink file link
> WORKING_DIRECTORY $ENV{DESTDIR}${CMAKE_INSTALL_PREFIX}/share/TestLink
> )
Thanks, it works fine.
> so the INSTALL(SCRIPT ...) should work for all of them as soon as symlinks
are supported (w
