Re: [GD-CVS] cvs: gd /libgd/tests/freetype CMakeLists.txt /libgd/tests/gd2 CMakeLists.txt /libgd/tests/gdimagearc CMakeLists.txt
/libgd/tests/gdimagecolorclosest CMakeLists.txt /libgd/tests/gdimagecolordeallocate CMakeLists.txt /libgd/tests/gdimageco

From: Date: Sun, 04 Jan 2009 17:13:57 +0000
Subject: Re: [GD-CVS] cvs: gd /libgd/tests/freetype CMakeLists.txt /libgd/tests/gd2 CMakeLists.txt /libgd/tests/gdimagearc CMakeLists.txt
/libgd/tests/gdimagecolorclosest CMakeLists.txt /libgd/tests/gdimagecolordeallocate CMakeLists.txt /libgd/tests/gdimageco
References: 1  Groups: php.gd.cvs 
Request: Send a blank email to php-gd-cvs+get-562@lists.php.net to get a copy of this message
Hi Pierre, Thanks for your response. On Sun, 4 Jan 2009 15:28:53 +0100, "Pierre Joye" <pierre.php@gmail.com> wrote: > Are you sure it is necessary? > > - ADD_TEST(${test_name} ${EXECUTABLE_OUTPUT_PATH}/${test_name}) > + ADD_TEST(${test_name} ${test_name}) Yes, I was sure and noticed that with cmake 2.6.0 make test failed to find test executables unless EXECUTABLE_OUTPUT_PATH is specified (then the paths fell in like '/${test_name}'). > Or is it something happening using non default option? As you see the commit is so broken that non default EXECUTABLE_OUTPUT_PATH causes the same trouble again. Sorry, it is my fault. To recover from it there are some options: 1) fix to set the variable if unspecified 2) revert to the previous version 3) do nothing and avoid using the variable Any ideas? Cheers, -- Takeshi Abe

« previous php.gd.cvs (#562) next »