Hello All, I hope everyone had a happy and safe holiday season.
Over the holiday break, I've made a series of major changes to what was formally known as JTSDK Nix, the conceptual prototype. The original scripts have been saved to a branch labeled ../branches/jtsdk-orig and the working branch ../branches/linux-1.0 has been merged --reintegrated back into ../trunk/linux. I've tested the current development /trunk/linux against: Debian Jessie (8.0) w/Gnome DE Ubuntu Trusty (14.04) w/Unity DE Mint Rebecca (17) w/Mate DE Other distro's will be enabled as time allows. Primary targets for WSJT, WSPR, WSJT-X v1.5 and WSJT-X v1.4 RC all build and run as expected. I've not performed an exhaustive list of tests, only basic operation in JT65, JT9 and WSPR2 mode. WSPR-X and MAP65 builds have not been enabled due to a series of compiler / library concerns. Package builds for WSJT-X (1.5 and 1.4) are not enabled at this time, but, they are functional for basic .deb generation. PER-INSTALLATION * If you were testing the previous version of JTSDK-Nix, you should remove it completely. Backup up any builds you want to keep for comparison, then remove (if they exist): ~/jtsdk-nix < jtsdk-nix checkout & build directories > ~/.local/share/applications/hamlib ~/.local.share/application/jtsdk CHECKOUT JTSDK * Bare in mind, the development branch will be subject to numerous changes in the coming weeks. The following steps are what I used on several Native and VM installs. I've not created a tar.gz yet as there are many items to tidy up / improve upon: * Open Terminal * mkdir -p ~/Projects/jtsdk-dev * cd ~/Projects/jtsdk-dev * svn co https://svn.code.sf.net/p/jtsdk/jtsdk/trunk/linux . - Do not forget the space and "." at the end. CONFIGURE & INSTALL DEPENDENCIES [1] The new build system uses Autotools to install dependencies, find & set paths, then configure the Bash build scripts, setup.sh is not longer used. [2] The new system also requires you to specify which distro you are using in order to properly check package dependencies. If you forget, it will remind you to do so. [3] --enable-parallel has a default of (1) core if not enabled. For those wishing to build WSJT-X using multi-core, enable parallel builds. WSPR and WSJT cannot use parallel builds, so it is not enabled in the builds scripts. * Open a terminal * cd ~/Projects/jtsdk-dev * Run autogen.sh: Ubuntu Example: ./autogen.sh --with-distro=ubuntu --enable-parallel=yes [4] If you have missing dependencies, a message will be displayed stating so. You can run " make simulate " to see what would be installed, or simply run " make " to install the dependencies. [5] If you installed any additional dependencies, you must re-run autogen.sh using the same parameters as before to pick up the new paths. * When prompted to install, type: sudo make install * If you want to uninstall, type: sudo make uninstall from ~/Projects/jtsdk-dev [6] Uninstall *will not*, by design, remove anything you've built, nor any package that was installed to resolve dependencies. This is to prevent inadvertent removal of packages possibly needed elsewhere. A list of installed packages (if any) will be saved to: ~/jtsdk/package-info/orig-needed.txt [7] The default installation paths are: For Scripts .: /usr/local/bin Build / Working Dir ..: ~/jtsdk/{wsjtx, wsjt, wspr, hamlib3, .. ..} If you change the --prefix=PATH, that path must be in $PATH in order for the scripts to be global. BUILD APPLICATIONS: * To run jtsdk, open a terminal, then type: jtsdk * To build WSJT-X, you must first build Hamlib3. Simply select Hamlib3 from the menu, then build whichever version of WSJT-X you prefer. * Command line builds ( no menu ) are also available. RUN APPLICATIONS: * WSPR and WSJT have custom build scripts in their install directory, either wspr.sh or wsjt.sh. for WSJT-X, browse to the install directory, then either type ./wsjtx or D-Click on the WSJT-X binary. That should do it. It sounds like allot, but it's not really. There are many more features available, but the above covers the basics. As always, if you have any problems with installation, builds, or the apps do not function properly, report it to the devel-list: Mail-To: [email protected] 73's Greg, KI7MT ------------------------------------------------------------------------------ Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net _______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
