Source tarball info =================== In this directory you'll find a daily snapshot of the Git repository of Hamlib. It is built automatically and a new snapshot should appear around 0930 or 1030 UTC daily (depending on US Daylight Saving Time as the build script runs at 0410 US Central time) and the prior day's is removed. It is built on a Debian Stable image runnning under Qemu using a fresh checkout of the Hamlib Git master branch each day. The archive file name includes both the shortened Git SHA1 commit ID and the date the archive was built. Even though a new snapshot is built each day, if the Git SHA1 commit ID has not changed from the previous download, nothing new is included in the archive. Compiling ========= Save the archive to your local computer (into a directory dedicated to compiling software, 'build' or tmp' or some name that has meaning to you is a good choice) and unpack it as follows: tar xvfz hamlib-4.7~git-20250901-9123d08a6.tar.gz You will find a new subdirectory named hamlib-4.7~git (it will change as the Hamlib version changes). Make this new directory your "working" directory: cd hamlib-4.7~git Be sure to read INSTALL and README.betatester for information on building and testing Hamlib. The first part of README.developer has information about which additional packages will need to be installed to compile Hamlib (not all listed packages are needed as they just allow special features of Hamlib to be built). Building Hamlib from this archive should consist of the familiar three-step: ./configure make make install Installation will likely require root privileges (sudo or su command to complete `make install'). For a list of the options and features used to build Hamlib use the --help option: ./configure --help which produces several screens of output. In a Linux console or Xterm, use the key combination to scroll back and to scroll down. A useful option is --disable-static which instructs Hamlib to only build the shared libraries. As of Git commit 9082a3a (16 Apr 2010), the scripting language bindings are disabled by default so they will need to be specifically enabled for language binding support (this has no effect on rigctld/rotctld). You may get a make error (which means it will quit before compilation is complete) if the --with-[perl|python]-binding or --enable-tcl-binding option(s) are used and the Swig package is not installed. Rationale ========= This snapshot is being made available to aid Hamlib development and for application developers wishing to write for the next release. If you want to use this file as the basis for a distribution's Hamlib package, please contact the Hamlib developers on our mailing list, hamlib-developer@lists.sourceforge.net before doing so. MD5SUM ====== As of 19 May 2010 (as posted to hamlib-developer): For those who rely on the daily snapshot file, I have added an md5sum file on the page. It is titled MD5SUM and will be deleted and a new one generated from the new Git daily tarball and uploaded to the site. This file is useful when downloaded into the same directory as the Git tarball and the following command is run: md5sum -c MD5SUM This will compare the tarball you downloaded to the checksum generated by the build script before it was uploaded to the Web site. This will provide a method to check for any file corruption that may have occurred during the upload or download process. A given MD5SUM file should be valid only for that day's tarball upload. There will likely be some days where the tarball and thus MD5SUM will be unchanged but that is due to no commits to the Git repository by the developers for that time. Have fun and please report bugs to the hamlib-developer@lists.sourceforge.net mailing list. 73, Nate, N0NB *~*~*~*~*~*~*~*~*~*~*~*~* Tarball archive notes: 05 May 2020: The source tarball and the Windows binary archive builds are now done on a Debian 10 (Buster) virtual machine using the MinGW64 tool chain based on GCC 8.3. This is effective as of Git commit dd5736c4. The Windows binaries no longer include the generated lib/mvc/libhamlib-4.lib file due to Wine not supporting current versions of MS Visual Studio tools. Sample commands for generating the file for local use has been included in the relevant README.w[32|64]-build file. Feedback is requested to correct errors in these sample commands. 08 Jun 2019: Binaries for MS Windows 32 and 64 bit builds are now done on a Debian Stretch virtual machine using the MinGW tool chain based on GCC 6.3. This is effective as of Git commit 1f6db444. 22 Mar 2016: As of Git commit 2a84990 the libusb-1.0 development library is required to build several of the kit backend models. Details about libusb 1.0 can be found at http://libusb.info/ 18 May 2013: The tarball is now built in a Debian 7.0 (Wheezy) virtual machine using the most recent Autotools versions in that release. 09 Jun 2011: The remainder of the removed bundled libtool files were removed as of Git commit 457472b. As the tarball is generated on a Debian Stable (Squeeze) machine, the included libtool file comes from libtool 2.2.6b of that host. 15 Mar 2010: Libtool version 2.2.6b is included in the archive. 08 Nov 2006: The uninstall target for the Perl bindings makefile has been commented out due to the fact that it is broken and braindead. It's broken since it can't find the .packlist it installed itself because it is looking in the wrong place because the called module is broken. Got that? Good. It's braindead because it won't uninstall installed files due to some policy on the part of the ExtUtils::MakeMaker module even if it could find .packlist. So, for now the Perl bindings files are left behind when the rest of Hamlib is uninstalled. 07 Nov 2006: make uninstall is broken by the Perl bindings makefile.