Hi Barry, All, Just a couple things.
I build allot of different applications, not just WSJTX. So to keep things straight I use INSTALLD and BUILDD both on Windows and Linux. Folks can use whatever name they like or nothing at all if that's a better fit for their purposes. As for building the package along with the tarball, that's my choice, as I wont send anything to Launchpad without first having tested it locally, be it a stable branch or not. That's why it's in the script. It could easily be removed. For my needs, there is a specific naming conversion the tarball must meet in order to build it with pbuilder ( local chroot ) as well as the build servers ( Launchpad ). Thus the reason for the long tarball name. I build somewhere in the neighborhood of 18+ different packages from source on a routine basis (couple times per week at lease), times 4 different distributions versions. I don't feel like typing all that out on the command line, so I use scripts for each one of them. YMMV. I m not sure about the install directory issue /usr or /usr/local, I've not ran into that problems before and don't see that problem Locally or on Launchpad. Maybe that's specific to your Distro's FSH. 73's Greg, KI7MT On 11/27/2015 07:34, Barry Jackson wrote: > On 27/11/15 13:14, Richard Shaw wrote: >> Interesting, while I found many references to it using google, I'm not >> familiar with INSTALLD but what I did find I don't think that's what you >> want to use with DESTDIR. >> >> DESTDIR is to basically relocate where a package is installed for >> packaging purposes so a non-root user can do the install. The path in >> destdir would not be included in any RPATHs in libraries or anywhere >> else where the path is important. I think you're looking for >> CMAKE_INSTALL_PREFIX which you would pass to cmake, i.e.: >> >> cmake -DCMAKE_INSTALL_PREFIX=$INSTALLD >> >> Thanks, >> Richard >> >> >> ------------------------------------------------------------------------------ >> >> >> >> _______________________________________________ >> wsjt-devel mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/wsjt-devel >> > Hi Richard, > We meet again ;) > INSTALLD is just a variable name in Greg's script which does use > CMAKE_INSTALL_PREFIX - see the extract below: > > -----------snip----------- > # set install locaiton > if [ $SEPARATE == "Yes" ] ; then > INSTALLD="$PREFIXD/$APP_NAME/$VERSION/$WSJTXV" > else > INSTALLD="$PREFIXD/$APP_NAME/$VERSION" > fi > > # Configure the build > cmake -Wno-dev -D CMAKE_INSTALL_PREFIX="$INSTALLD" "$SRCD" > > > # Compile and Install the Release Target > echo '' > echo "-------------------------------------------" > echo -e ${C_Y} "COMPILING WSJTX v$VERSION r$WSJTXV"${C_NC} > echo "-------------------------------------------" > echo '' > cd $BUILDD > export DESTDIR=$INSTALLD > cmake --build . --target install -- -j "$JJ" > ---------snip---------- > > Adding the export... stopped the install path defaulting to /usr/local/bin. > > I have had similar issues with other packages using CMake recently with > rpm specs and had to pass DESTDIR at the make install stage as otherwise > CMAKE_INSTALL_PREFIX has been ignored, so I was guessing that it may be > a CMake bug. > > Barry ------------------------------------------------------------------------------ _______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
