kopia lustrzana https://github.com/Hamlib/Hamlib
Updated hamlib‐primer (markdown)
Michael Black
rodzic
0a4079e465
commit
0ff508ff41
|
|
@ -11,41 +11,41 @@ NAME
|
|||
DESCRIPTION
|
||||
<BR>There are several ways to obtain a working installation of Hamlib. The following sections discuss installing from a package manager, building from source, and installing Hamlib project supplied binaries on Microsoft Windows®
|
||||
|
||||
<BR>Installing binary packages on Linux and BSD
|
||||
Installing binary packages on Linux and BSD
|
||||
The easiest way to install a released version of Hamlib on a Linux based distribution or a BSD variant is through the provided package manager. While package managers vary according to the distribution (it’s easy to lump BSD variants in this group too) their end goal is to provide ready to use software packages. Since such a wide variety of package managers exist, it is best to recommend that the documentation for your chosen distribution be your guide.
|
||||
|
||||
<BR>A variety of Hamlib sources
|
||||
Distribution packages are most often official Hamlib releases and in some cases could be quite old and lacking support for newer radios or rotators. In some cases support is improved in existing radio or rotator back ends and bugs are fixed in newer releases. Often times to get the improved support/bug fixes, building from source will be required. Relax, it’s not hard. :-)
|
||||
A variety of Hamlib sources
|
||||
<BR>Distribution packages are most often official Hamlib releases and in some cases could be quite old and lacking support for newer radios or rotators. In some cases support is improved in existing radio or rotator back ends and bugs are fixed in newer releases. Often times to get the improved support/bug fixes, building from source will be required. Relax, it’s not hard. :-)
|
||||
|
||||
<BR>Source code is available as official releases, testing snapshots, daily development snapshots, and the bleeding edge of development directly from the [Git repository](https://github.com/Hamlib/Hamlib). As a rule, even the bleeding edge tarballs should configure and compile without error even though certain implementation work may be in progress and may be incomplete or have errors.
|
||||
Source code is available as official releases, testing snapshots, daily development snapshots, and the bleeding edge of development directly from the [Git repository](https://github.com/Hamlib/Hamlib). As a rule, even the bleeding edge tarballs should configure and compile without error even though certain implementation work may be in progress and may be incomplete or have errors.
|
||||
|
||||
<BR>Getting released source
|
||||
Official Hamlib source releases, commonly called tarballs can be found on the [SourceForge.net Hamlib files](http://sourceforge.net/projects/hamlib/files/hamlib/) Web page. The most recent release is listed first.
|
||||
Getting released source
|
||||
<BR>Official Hamlib source releases, commonly called tarballs can be found on the [SourceForge.net Hamlib files](http://sourceforge.net/projects/hamlib/files/hamlib/) Web page. The most recent release is listed first.
|
||||
|
||||
<BR>Getting source snapshots
|
||||
Testing release candidates (RCs) are posted during the period (often a few weeks) before a planned release. Beginning with the 4.0 release, RCs are hosted by the [SourceForge.net Hamlib files](http://sourceforge.net/projects/hamlib/files/hamlib/) Web page. RCs are identifed by having a ~rcX suffix where the X is replace by a numeral for successive release candidates.
|
||||
Getting source snapshots
|
||||
<BR>Testing release candidates (RCs) are posted during the period (often a few weeks) before a planned release. Beginning with the 4.0 release, RCs are hosted by the [SourceForge.net Hamlib files](http://sourceforge.net/projects/hamlib/files/hamlib/) Web page. RCs are identifed by having a ~rcX suffix where the X is replace by a numeral for successive release candidates.
|
||||
|
||||
<BR>Daily snapshots of the development repository are available via the World Wide Web from [Hamlib Git daily snapshots](http://n0nb.users.sourceforge.net/). These are not official releases but are provided for testing new features and bug fixes.
|
||||
Daily snapshots of the development repository are available via the World Wide Web from [Hamlib Git daily snapshots](http://n0nb.users.sourceforge.net/). These are not official releases but are provided for testing new features and bug fixes.
|
||||
|
||||
<BR>The daily development snapshot is made and posted each day by around 1030 UTC. Daily snapshots should compile but sometimes a bug creeps in that prevents compilation. If that should happen, please report it to the [hamlib-developer mailing list](mailto:hamlib-developer@@lists.sourceforge.net).
|
||||
The daily development snapshot is made and posted each day by around 1030 UTC. Daily snapshots should compile but sometimes a bug creeps in that prevents compilation. If that should happen, please report it to the [hamlib-developer mailing list](mailto:hamlib-developer@@lists.sourceforge.net).
|
||||
|
||||
<BR>Git repository
|
||||
Git repository
|
||||
<BR>The source repository can be cloned which copies the repository to your computer including its entire history, branches, and release tag information. In other words, once the git(1) clone command is finished a complete copy of the Hamlib development will be on your computer. You can do quite a lot with this as nothing is hidden from view since the entire history of Hamlib is right there all the way from the very first commit to the present. None of the meta-data is hidden away on some central server.
|
||||
|
||||
<BR>To clone the repository use the following command:
|
||||
To clone the repository use the following command:
|
||||
|
||||
<BR>git clone https://git.code.sf.net/p/hamlib/code hamlib
|
||||
git clone https://git.code.sf.net/p/hamlib/code hamlib
|
||||
|
||||
<BR>or:
|
||||
or:
|
||||
|
||||
<BR>git clone https://github.com/Hamlib/Hamlib.git
|
||||
git clone https://github.com/Hamlib/Hamlib.git
|
||||
|
||||
<BR>Odds are that you will want to run the above command in a sub directory of your home directory. The hamlib directory will be created by Git and the master branch will be checked out for you as the working copy. The master branch is one of several branches used in Hamlib development. It is the main branch of new features and bug fixes. The working copy will be the latest revision of every file at the time of the clone. Later updates from the developers will require using another Git command to update your local repository.
|
||||
Odds are that you will want to run the above command in a sub directory of your home directory. The hamlib directory will be created by Git and the master branch will be checked out for you as the working copy. The master branch is one of several branches used in Hamlib development. It is the main branch of new features and bug fixes. The working copy will be the latest revision of every file at the time of the clone. Later updates from the developers will require using another Git command to update your local repository.
|
||||
|
||||
<BR>Building from source
|
||||
Building from source
|
||||
<BR>Building from source will be required for various reasons. Perhaps only an older release is provided by your distribution, or you would like to test recent changes to Hamlib—either a specific back end or API changes—and offer a report to the developers, or you would like to take part in development and offer your contribution to the project, or you would just like to learn how to build a relatively comprehensive package from source. Any is a good reason to build from the source code archive.
|
||||
|
||||
<BR>Before going further, this manual assumes familiarity with working from the command prompt in a Linux/BSD/Unix like system’s Bourne shell environment (compatible Bourne shells include bash(1), ksh(1), zsh(1), and several more) either in a virtual console (a text only screen with no graphics) or in a terminal in a desktop environment (xterm(1), rxvt(1), konsole(1) (included with the KDE desktop), gnome-terminal(1), xfce4-terminal(1), terminal(1) (included in macOS), etc.). If this is new to you, take some time and read up on using the shell. A good tutorial can be found at [LinuxCommand.org](http://linuxcommand.org/) which also offers an in-depth book that can be purchased or downloaded for no cost (the Hamlib project is not associated with nor has any interest in the sale of this book, it just looks like a very good effort on the part of its author).
|
||||
Before going further, this manual assumes familiarity with working from the command prompt in a Linux/BSD/Unix like system’s Bourne shell environment (compatible Bourne shells include bash(1), ksh(1), zsh(1), and several more) either in a virtual console (a text only screen with no graphics) or in a terminal in a desktop environment (xterm(1), rxvt(1), konsole(1) (included with the KDE desktop), gnome-terminal(1), xfce4-terminal(1), terminal(1) (included in macOS), etc.). If this is new to you, take some time and read up on using the shell. A good tutorial can be found at [LinuxCommand.org](http://linuxcommand.org/) which also offers an in-depth book that can be purchased or downloaded for no cost (the Hamlib project is not associated with nor has any interest in the sale of this book, it just looks like a very good effort on the part of its author).
|
||||
|
||||
Let’s get started.
|
||||
|
||||
|
|
|
|||
Ładowanie…
Reference in New Issue