Hi Richard,

 From what I've read, and I may be way off on this, DESTDIR has no 
bearing on CMAKE_INSTALL_PREFIX or RPATH, for example:

If I set:

CMAKE_INSTALL_PREFIX=/home/ki7mt/wsjtx

and prefix it with DESTDIR=/tmp/example1

I'd end up with an install located at:

/tmp/example1/home/ki7mt/wsjtx

Maybe I'm confused on DESTDIR usage or something, but I thought it was 
the same as autotools.


73's
Greg, KI7MT


On 11/27/2015 09:21, Richard Shaw wrote:
> On Fri, Nov 27, 2015 at 10:17 AM, Greg Beam <[email protected]
> <mailto:[email protected]>> wrote:
>
>     Hi Richard,
>
>     As far as I'm aware, I do not pass any CMAKE_INSTALL_PREFIX in a chroot
>     or build server environment. Whatever is set by Cmake or the server is
>     what gets used, which I am pretty sure is /usr.
>
>     The only time I pass the CMAKE_INSTALL_PREFIX variable is when I *do
>     not* want the install target going into the system folders; local build
>     testing and things.
>
>
> If you want to do that, it's better to use DESTDIR during install for
> the reasons mentioned earlier in this thread. You may get away with it
> if there's no RPATH issues (not typically a problem with binaries but
> more with libraries).
>
> $ make install DESTDIR=/home/user/test
>
>     I don't understand the Hamlib comment. It also gets installed same as
>     WSJT-X, which is /usr, maybe I am misunderstanding that bit.
>
>
> That was in reference to the superbuild cmake script... Sorry I wasn't
> clear, both got pulled into this discussion :)
>
> Thanks,
> Richard
>
>
> ------------------------------------------------------------------------------
>
>
>
> _______________________________________________
> wsjt-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>

------------------------------------------------------------------------------
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Reply via email to