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. I don't understand the Hamlib comment. It also gets installed same as WSJT-X, which is /usr, maybe I am misunderstanding that bit. 73's Greg, KI7MT On 11/27/2015 09:03, Richard Shaw wrote: > On Fri, Nov 27, 2015 at 8:57 AM, Bill Somerville <[email protected] > <mailto:[email protected]>> wrote: > > On 27/11/2015 14:45, Richard Shaw wrote: > > I don't use the shell script, I just use the superbuild script directly. > > > > $ cmake -DWSJTX_TAG=tags/wsjtx-1.6.0-rc1 ~/svn/wsjtx-superbuild > > $ make source > A big green tick next to that from me! Although upstream source tarballs > for tags are already available in the SF files area. > > > Yeah, I do it for now due to the hamlib fork, when that's all sorted out > I'll change everything over to the release tarballs. > > > The CMAKE_INSTALL_PREFIX is not normally needed on a packing build host > as you are normally building into a fakeroot so the default of '/usr' is > OK. Maybe a prefix of '/usr/local' for BSD type systems or for private > packaging. > > > Exactly, I don't use it on the source build part (sorry if that wasn't > clear) but during the real build when I'm packaging it. Fedora (and I > assume other RPM distros) define a %cmake macro that takes care of > CMAKE_INSTALL_PREFIX and several other typical settings. > > Thanks, > Richard ------------------------------------------------------------------------------ _______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
