2012/7/2 David Cole <[email protected]>:
> On Mon, Jul 2, 2012 at 11:58 AM, Eric Noulard <[email protected]> wrote:
>> 2012/7/2 David Cole <[email protected]>:
>>>
>>> On our dashmacmini3 dashboards, we're getting:
>>>
>>>   DPKG_EXECUTABLE='/sw/bin/dpkg'
>>>
>>> It's found by find_program at CMake configure time, but cpack does not
>>> find this program (it's not in the PATH) at testing time.
>>>
>>> What should we do about this?
>>>
>>> I could just set DPKG_EXECUTABLE=OFF to circumvent the test on these 3
>>> dashboards for now... But I'd like a real fix for it. Seems like cpack
>>> should find it if CMake's find_program can find it.
>>
>> Yes I [apparently wrongly] supposed
>>
>> that
>> cmSystemTools::FindProgram("dpkg")
>>
>> would find 'dpkg' iff:
>> find_program(DPKG_EXECUTABLE NAMES dpkg)
>> did find it...
>>
>> Why is the result of this two commands differents?
>> Are there some env var that makes the behavior different?
>> Or may be the configure environement is different from
>> the test environment...
>>
>>
>> --
>> Erk
>> Le gouvernement représentatif n'est pas la démocratie --
>> http://www.le-message.org
>
>
> Probably because of this:
>
>   LIST(APPEND CMAKE_SYSTEM_PREFIX_PATH
>     /sw        # Fink
>     /opt/local # MacPorts
>     )
>
> from Darwin.cmake...

OK could you try my proposal I just pushed on stage:

To [email protected]:stage/cmake.git
   848f220..a8c659c  HEAD -> DoNotInvokeCPackAtCMakeTime-forCMakeTests

And of course you were right for the "get the list at test time"
because at least
the "non-finding" would have been consistent.

I'll do that but probably not for 2.8.9.
-- 
Erk
Le gouvernement représentatif n'est pas la démocratie --
http://www.le-message.org
--

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: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers

Reply via email to