Hello All,
UPDATE-1
I've updated the build script to remove the parallel build flags, and
change the invocation slightly. Rather than calling the release
candidate rc1, the script will build whatever rc version is in the
wsjtx-1.4 branch. At the moment, it looks to be rc2. I also changed the
folder names to better match the builds:
Output Folder Names:
~/temp/wsjtx-1.4.0 ~ latest release candidate
~/temp/wsjtx-dev ~ wsjtx head branch
New Binary Locations:
~/temp/wsjtx-1.4.0/install/Release/bin
~/temp/wsjtx-dev/install/Release/bin
*USAGE*
----------
Open a terminal
mkdir ~/temp
cd ~/temp
svn export
https://svn.code.sf.net/p/wsjt/wsjt/branches/jtsdk/nix/scripts/wsjtx-build.sh
* Build HEAD Branch:
*./wsjtx-build.sh*
Final Location: ~/temp/wsjtx-dev/install/Release/bin
* Build Current Release Candidate
*./wsjtx-build.sh rc*
Final location: ~/temp/wsjtx-1.4,0/install/Release/bin
You no longer need the "1" or "2" after rc, as it builds whatever is in
../wsjtx-1.4
*Parallel v.s. Single Build - General Build Info*
------------------------------------------------------------------
I timed both parallel and single builds. There's only a ~90 second or so
difference between the two on my Centrino Dual Core 2.0Ghz i686 Laptop,
4GB DDR2. The times include installing --reinstall of packages +
downloads, wsjtx svn checkout, hamlib3 clone & build, document and kvasd
downloads. (Faster Internet + Higher CPU Clock Speeds) == Faster Overall
Build Times.
Parallel Build
real 4m33.384s
user 4m11.936s
Standard Build
real 5m56.544s
user 3m55.716s
* Memory Usage
I had Gedit and Thunderbird open during the build to increase memory
usage just a bit. My base memory usage was 729MiB on a standard Ubuntu
i386 desktop install. Xubuntu and Lubuntu should be lower, somewhere in
the neighbourhood of 350~ 450MB with no applications running, maybe less.
( single core builds, not parallel )
During the Hamlib portion of the build, high mem usage peaked at 735MB.
During the Cmake portion of the build, there were several peaks within
the 830~920MB range, with the high peak coming in right at 1.1GB
If your running slower core clocks speeds + lower base memory =< 2GB,
more than likely, you will see increased build times and possibly run
into some paging / cache issues as the build process will start to use
the HD Swap partition, which is not an ideal situation. Running with 1GB
of RAM, having a base memory usage of ~350-450MB is right on the edge of
using Swap in a single core build scenario.
73's
Greg, KI7MT
On 09/26/2014 03:22 AM, ki7mt wrote:
Hi David, All,
I use a script on new VM's (clones from unmodified VM installs) to
perform quick build tests with. I added a modified version to
JTSDK-NIX that incorporates all of Bills latest updates for the rc1
build as well as, the HEAD development branch ../wsjtx This script is
only for WSJT-X.
It's a single stand-alone script (nothing fancy, with minimal error
handling), setup and tested on Ubuntu 14.04 amd64, i386 (which I'm on
now), Debian Sid and Jessie. With the exception of the package list
section, it should run on most Linux distros. Update that section as
needed for package manager / package list for other distro's. It
should be run from a temp location, does *not* install Hamlib3, only
builds it for use with Cmake. Deleting the temp folder rids the system
of everything other than the installed deps, which is better left to
the user to determine if they should be removed or not.
*EXPECTATIONS ( the scripts trys to )
*-------------------------------------------------------
-Install Build and Runtime Deps
-Checkout and Build Bill's Hamlib3
-Perform a Basic Hamlib3 test
-Checkout / Update WSJT-X from SVN
-Configure / Build Release Tree
-Build the WSJT-X Install Target
-Yield a fully working WSJT-X application
-It *does not* build the Manpages. If you want them, you can edit the
package list, add AsciiDoc and remove -D WSJT_SKIP_MANPAGES=ON from
the build tree config invocation.
*USAGE*
---------
Open a terminal
mkdir ~/temp
cd ~/temp
svn export
https://svn.code.sf.net/p/wsjt/wsjt/branches/jtsdk/nix/scripts/wsjtx-build.sh
* Two Build Options:
Build the Current Dev Branch
*./wsjtx-build.sh*
Final Location: ~/temp/wsjtx/install/Release/bin
and / or
Build The Release Candidate
*./wsjtx-build.sh rc1*
Final location: ~/temp/wsjtx-1.4.0-rc1/install/Release/bin
When your finished testing, simply delete ~/temp if you no longer need
it. If you have any troubles, let me know, I'm sure we can get it
sorted out.
73's
Greg, KI7MT
Hi Joe and all.....i have just done an update of WSJT-X using a script i
put together from the origional lines for cmake sent out by Bill
im now showing WSJT-X v1.5.0-c1 r4375
looks good....will check it all out and report any problems
Bill...im still using your origonal hamlib 3 files you sent out...do i
have to upgrade....the instructions you sent out for the upgrade look a
bit daunting
73 David VK4BDJ
On 26/09/14 05:50, Joe Taylor wrote:
Mike --
Credits mismatch between About window and the manual
Thanks for catching this discrepancy. The online manual has been fixed;
we'll need to correct the list in "About" in rc2.
-- Joe, K1JT
------------------------------------------------------------------------------
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
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
------------------------------------------------------------------------------
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
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
