[CMake] Problem with DESTDIR in with ExternalProject

[Vivek Goel]

OK, thanks.
regards
Vivek Goel



On Tue, Sep 11, 2012 at 5:43 PM, David Cole <david.cole at kitware.com> wrote:

> The most reasonable way to achieve this goal would be to write scripts
> that replace the configure/build/install steps of the projects that
> you want to isolate with DESTDIR.
>
> Then, inside the script (which will only be executed at build time of
> the outer project), use set(ENV{DESTDIR} "...") to set it
> appropriately just for that project.
>
> Unfortunately, CMake's add_custom_command does not yet have a
> mechanism for specifying environment variables just for a single
> custom command.
>
> So, for now, the best work-around is to write scripts as needed.
>
>
> HTH,
> David
>
>
> On Mon, Sep 10, 2012 at 1:57 PM, Vivek Goel <goelvivek2011 at gmail.com>
> wrote:
> > Currently I am using cmake to auto build third party library c-ares using
> > ExternalProject module.
> > Before starting cmake I am setting DESTDIR variable.
> > export DESTDIR=`pwd`/dest
> >
> > Problem is that third party library are also reading this variable. Is
> there
> > a way I can avoiding mixing of DESTDIR variable with my cmake
> configuration
> > and ExternalProject_Add ?
> >
> >
> > regards
> > Vivek Goel
> >
> >
> > --
> >
> > 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://www.cmake.org/mailman/listinfo/cmake
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.cmake.org/pipermail/cmake/attachments/20120912/9814f499/attachment-0001.htm>