Re: [wsjt-devel] WSJT-X Hamlib 3 fork updates.

[Bill S. <g4...@cl...>]

On 24/09/2014 18:09, KI7MT wrote:

Hi Greg,
> HI Joe,
>
> I forgot to mention, when building the package:
>
> build wsjtx package
>
> the script will perform at build tree configure first, then, it runs:
>
> cmake --build . --target package
>
> %OPTION% is not set, so the default is Release
>
> I don't think you need to build the install target:
>
> build wsjtx rinstall
>
> as it appears, at least from what I can see on the screen, it's building
> it on its own.
>
> If this is not correct, then I need to change the build script for the
> package target to first perform an install target build, then package it.
No that's OK, the package target will do the right thing, there's no 
need to make an install target unless you specifically need a locally 
installed Release version for testing purposes. Best advice is use 
'rinstall' for testing and 'package' if you want a deployable package.
>
> 73's
> Greg, KI7MT
73
Bill
G4WJS.
>
>
> On 9/24/2014 16:31, Joe Taylor wrote:
>> Hi Bill and Greg,
>>
>> As you recognized, the procedure I went through installed the newly
>> built hamlib files, but not in the places I had expected.  My mistake.
>>
>> I have now changed the "--prefix=..." part of the command that invokes
>> autogen.sh to read "--prefix=C:/JTSDK-QT/hamlib3/mingw32", and all
>> appears to be well.  Newly built files appear in the bin, lib, include,
>> and share directories there, and the usual JTSDK-QT commands build
>> WSJT-X properly.
>>
>> The only complaint issued by any of the scripts is this one from  the
>> JTSDK-QT command "build wsjtx package":
>>
>> #######################################################################
>> CPack: Create package
>> CPack: - package:
>> C:/JTSDK-QT/wsjtx/build/Release/wsjtx-1.4.0-rc1-win32.exe gene
>> rated.
>>
>> -----------------------------------------------------------------
>>                      INSTALLER BUILD ERROR
>> -----------------------------------------------------------------
>>
>>    There was a problem building the package, or the script
>>    could not find:
>>
>>    C:\JTSDK-QT\wsjtx\build\Release\wsjtx-1.4.0-win32.exe
>>
>>    Check the Cmake logs for any errors, or correct any build
>>    script issues that were obverved and try to rebuild the package.
>> #######################################################################
>>
>> The message is completely benign: the script just did not understand
>> that the package name would include the modifier "-rc1".
>>
>>
>> For the record then, here's what I did to build the latest version of
>> hamlib3 in Windows:
>>
>> In an MSYS shell:-
>>
>> mkdir ~/hamib_g4wjs
>> cd ~/hamlib_g4wjs
>> git clone git://git.code.sf.net/u/bsomervi/hamlib src
>> cd src
>> git checkout integration
>> mkdir ../build
>> cd ../build
>> ../src/autogen.sh --prefix=C:/JTSDK-QT/hamlib3/mingw32 \
>>        --disable-shared --enable-static \
>>        --without-cxx-binding --disable-winradio \
>>        CC=C:/JTSDK-QT/qt5/Tools/mingw48_32/bin/gcc \
>>        CXX=C:/JTSDK-QT/qt5/Tools/mingw48_32/bin/g++ \
>>        CFLAGS="-fdata-sections -ffunction-sections" \
>>        LDFLAGS="-Wl,--gc-sections"
>> make
>> make install
>>
>> ... and then, in the JTSDK-QT environment CMD shell:
>>
>> build wsjtx rinstall
>> build wsjtx package
>>
>> 	-- Joe
>>
>> ------------------------------------------------------------------------------
>> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
>> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
>> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
>> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
>> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
>> _______________________________________________
>> wsjt-devel mailing list
>> wsj...@li...
>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>>