On 16/12/2015 21:27, KI7MT wrote:
> the use of DESTDIR, and I may have
> misunderstood what the need was.
Hi Greg,
DESTDIR is a bit confusing. It comes into play when you have a
pre-configured package and want to install it in some place other than
the prefix specified at install time. I believe this happens with some
packages where the upstream tarball is provided pre-configured, I
suspect this is so when the various destination directories cannot be
changed because they are hard coded. This is why using DESTDIR installs
a complete system root structure in an alternative location. So a
package configured to land in /usr/local/{bin,lib,share,...} will be
installed into $DESTDIR/usr/local/{bin,lib,share,...}. This is also
useful to test the layout of a package without having to use root privileges
In our case for developer builds we have full control of configuration
so I don't think DESTDIR is useful, just set a sensible
CMAKE_INSTALL_PREFIX at configure time (the same applies to Hamlib with
--prefix at configure time).
73
Bill
G4WJS.
------------------------------------------------------------------------------
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
