[cmake-developers] Perforce Patch for CTest

Pedro Navarro pnavarro at netflix.com
Tue Oct 15 19:39:51 EDT 2013


That's exactly my point. Is it ok to rely on environment variables (P4PORT,
P4HOST), ie, expect the build machine to be set up in a way before running
the tests or are those values passed in some kind of configuration file,
added to the CMake Cache or passed as -D?

Pedro


On Tue, Oct 15, 2013 at 4:16 PM, Matthew Woehlke <
matthew.woehlke at kitware.com> wrote:

> On 2013-10-15 18:44, Pedro Navarro wrote:
>
>> I'm imagining that, depending on the testing machine, we might need to be
>> able to specify where the perforce server is located, if it's not the
>> local
>> machine (using either a command line switch or an environment variable).
>> Is
>> there any infrastructure for that?
>>
>
> (IIRC) $P4PORT? IIRC perforce already has a convention for using
> environment variables to locate the server; you shouldn't need to invent
> something new.
>
> --
> Matthew
>
> --
>
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/**
> opensource/opensource.html<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<http://www.cmake.org/Wiki/CMake_FAQ>
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/cgi-**bin/mailman/listinfo/cmake-**developers<http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/cmake-developers/attachments/20131015/94113e2d/attachment.html>


More information about the cmake-developers mailing list