| 1 | .. index: BNC installation
|
|---|
| 2 |
|
|---|
| 3 | Installation
|
|---|
| 4 | ************
|
|---|
| 5 |
|
|---|
| 6 | .. index: BNC installation - pre-compiled builds (MS Windows, Linux, Mac OS)
|
|---|
| 7 |
|
|---|
| 8 | Pre-compiled builds
|
|---|
| 9 | ===================
|
|---|
| 10 |
|
|---|
| 11 | Precompiled builds of BNC are available for MS Windows, Linux, and Mac OS X systems. They can be downloaded for installation from http://igs.bkg.bund.de/ntrip/download. Please ensure that you always use the latest released version of the program.
|
|---|
| 12 |
|
|---|
| 13 | .. rubric:: MS Windows Build
|
|---|
| 14 |
|
|---|
| 15 | A dynamically compiled shared library build for Mircrosoft Windows systems is provided as Microsoft Installer (MSI) file. MSI files are used for installation, storage, and removal of programs. The BNC files are contained in a MSI package, which is used with the program's client-side installer service, an .EXE file, to open and install the program. We used the MinGW Version 4.4.0 compiler to create BNC for Windows. After installation your `bnc.exe` file shows up e.g. under 'All Programs'.
|
|---|
| 16 |
|
|---|
| 17 | .. rubric:: Linux Build
|
|---|
| 18 |
|
|---|
| 19 | Static library and shared library builds for BNC are provided for a selection of Linux distributions. Download the ZIP archive for a version which fits to your Linux system, unzip the archive and run the included BNC binary. A static build would be sufficient in case you do not want BNC to plot PPP results with Google Map (GM) or OpenStreetMap (OSM) maps in the background. GM/OSM usage requires BNC builds from shared libraries.
|
|---|
| 20 |
|
|---|
| 21 | .. rubric:: Mac OS X Build
|
|---|
| 22 |
|
|---|
| 23 | A shared library ``Disk iMaGe`` (DMG) file is provided for BNC on OS X systems; it also comes in a ZIP archive. The DMG file format is used in the Mac for distributing software. Mac install packages appear as a virtual disk drive. After download, when the DMG file icon is double clicked, the virtual drive is 'mounted' on the desktop. Install BNC by dragging the ``bnc.app`` icon to your ``Applications`` folder. To start BNC, double click on ``Applications/bnc.app``. You could also start BNC via Command Line Interface (CLI) using command ``Applications/bnc.app/Contents/MacOS/bnc``.
|
|---|
| 24 |
|
|---|
| 25 | .. index:: BNC compilation
|
|---|
| 26 |
|
|---|
| 27 | Compilation
|
|---|
| 28 | ===========
|
|---|
| 29 |
|
|---|
| 30 | BNC has been written as Open Source and published under GNU General Public License (GPL). The latest source code can be checked out from Subversion repository http://software.rtcm-ntrip.org/svn/trunk/BNC. A ZIP archive available from http://igs.bkg.bund.de/ntrip/download provides the source code for BNC Version 2.12, developed using Qt Version 4.8.5.
|
|---|
| 31 |
|
|---|
| 32 | The following describes how you can produce your own builds of BNC on MS Windows, Linux, and Mac systems. It is likely that BNC can also be compiled on other systems where a GNU compiler and Qt Version 4.8.5 or any later version is installed.
|
|---|
| 33 |
|
|---|
| 34 | .. index:: Static libraries, Shared libraries
|
|---|
| 35 |
|
|---|
| 36 | Static versus Shared Libraries
|
|---|
| 37 | ------------------------------
|
|---|
| 38 |
|
|---|
| 39 | You can produce static or shared library builds of BNC. Static builds are sufficient in case you do not want BNC to produce track maps on top of Google Map (GM) or OpenStreetMap (OSM). GM/OSM usage would require the QtWebKit library which can only be part of BNC builds from shared Qt libraries. Hence, having a shared library Qt installation available is a precondition for producing a shared library build of BNC.
|
|---|
| 40 |
|
|---|
| 41 | .. index:: BNC installation - MS Windows, MS Windows
|
|---|
| 42 |
|
|---|
| 43 | MS Windows Systems, Shared Library
|
|---|
| 44 | ----------------------------------
|
|---|
| 45 |
|
|---|
| 46 | This explains how to install a shared Qt 4.8.5 library on MS Windows systems to then create your own shared build of BNC.
|
|---|
| 47 |
|
|---|
| 48 | Supposing that 'Secure Socket Layer (SSL)' is not available on you system, you should install OpenSSL libraries in ``C:\OpenSSL-Win32``. They are available e.g. from http://igs.bkg.bund.de/root_ftp/NTRIP/software/Win32OpenSSL-1_0_1e.exe. See http://slproweb.com/products/Win32OpenSSL.html for other SSL resources. Ignore possibly occurring comments about missing components during installation.
|
|---|
| 49 |
|
|---|
| 50 | 1. Download MinGW compiler Version 4.4.0 e.g. from http://igs.bkg.bund.de/root_ftp/NTRIP/software/MinGW-gcc440_1.zip.
|
|---|
| 51 |
|
|---|
| 52 | 2. Unzip the ZIP archive and move its contents to a directory ``C:\MinGW``. Now you can do either (4) or (5, 6, 8, 9, 10). Following (4) is suggested.
|
|---|
| 53 |
|
|---|
| 54 | 3. Download file ``qt-win-opensource-4.8.5-mingw.exe`` (317 MB) e.g. from https://download.qt.io/archive/qt/4.8/4.8.5/.
|
|---|
| 55 |
|
|---|
| 56 | 4. Execute this file to install a pre-compiled shared Qt library.
|
|---|
| 57 |
|
|---|
| 58 | 5. Download file ``qt-everywhere-opensource-src-4.8.5.zip`` (269 MB) e.g. from https://download.qt.io/archive/qt/4.8/4.8.5/.
|
|---|
| 59 |
|
|---|
| 60 | 6. Unzip the ZIP archive and move the contents of the contained directory into a directory ``C:\Qt\4.8.5``.
|
|---|
| 61 |
|
|---|
| 62 | 7. Create somewhere a file ``QtEnv.bat`` with the following content
|
|---|
| 63 |
|
|---|
| 64 | .. code-block:: console
|
|---|
| 65 |
|
|---|
| 66 | set QTDIR=C:\Qt\4.8.5
|
|---|
| 67 | set PATH=%PATH%;C:\MinGW\bin;C:\Qt\4.8.5\bin
|
|---|
| 68 | set QMAKESPEC=C:\Qt\4.8.5\mkspecs\win32-g++
|
|---|
| 69 |
|
|---|
| 70 | 8. Open a command line window and execute file ``QtEnv.bat``.
|
|---|
| 71 |
|
|---|
| 72 | 9. Go to directory Qt directory and configure Qt using command
|
|---|
| 73 |
|
|---|
| 74 | .. code-block:: console
|
|---|
| 75 |
|
|---|
| 76 | cd Qt\4.8.5
|
|---|
| 77 | configure -fast -webkit -release -nomake examples -nomake tutorial
|
|---|
| 78 | -openssl -I C:\OpenSSL-Win32\include
|
|---|
| 79 |
|
|---|
| 80 | 10. Compile Qt using command ``mingw32-make``. This may take quite a long time. Don't worry if the compilation process runs into a problem after some time. It is likely that the libraries you require are already generated at that time. Should you want to reconfiguring Qt following steps (8)-(10) you first need to clean the previous configuration using command ``mingw32-make confclean``. Run command ``mingw32-make clean`` to delete previously compiled source code.
|
|---|
| 81 |
|
|---|
| 82 | 11. Download latest BNC from SVN repository http://software.rtcm-ntrip.org/svn/trunk/BNC.
|
|---|
| 83 |
|
|---|
| 84 | 12. Open command line window and execute file ``QtEnv.bat``, see (7).
|
|---|
| 85 |
|
|---|
| 86 | 13. Go to directory BNC and enter command ``qmake bnc.pro``.
|
|---|
| 87 |
|
|---|
| 88 | 14. Enter command ``mingw32-make``.
|
|---|
| 89 |
|
|---|
| 90 | 15. Find binary file ``bnc.exe`` in directory named ``src``.
|
|---|
| 91 |
|
|---|
| 92 | 16. Extend the Windows environment variable PATH by ``C:\Qt\4.8.5\bin``.
|
|---|
| 93 |
|
|---|
| 94 | Steps (11)-(15) can be repeated whenever a BNC update becomes available. Running ``bnc.exe`` on a windows system requires (1) when using the NTRIP Version 2s option for stream transfer over TLS/SSL.
|
|---|
| 95 |
|
|---|
| 96 | .. index:: BNC installation - Linux systems, Linux
|
|---|
| 97 |
|
|---|
| 98 | Linux Systems
|
|---|
| 99 | -------------
|
|---|
| 100 |
|
|---|
| 101 | On Linux systems you may use the following procedure to install a shared Qt version 4.8.5 library:
|
|---|
| 102 |
|
|---|
| 103 | Download file ``qt-everywhere-opensource-src-4.8.5.tar.gz`` (230 MB) available from https://download.qt.io/archive/qt/4.8/4.8.5/. Unzip file, extract tar archive and change to directory ``qt-everywhere-opensource-src-4.8.5``. Run commands
|
|---|
| 104 |
|
|---|
| 105 | .. code-block:: console
|
|---|
| 106 |
|
|---|
| 107 | ./configure -fast -webkit -nomake examples -nomake tutorial
|
|---|
| 108 | -prefix /usr/local/Trolltech/Qt-4.8.5
|
|---|
| 109 | gmake
|
|---|
| 110 | gmake install
|
|---|
| 111 |
|
|---|
| 112 | Qt will be installed into directory ``/usr/local/Trolltech/Qt-4.8.5``. To reconfigure, run ``gmake confclean`` and ``configure``. Note that the ``-prefix`` option allows you to specify a directory for saving the Qt libraries. This ensures that you do not run into conflicts with other Qt installations on your host. Note further that the following two lines
|
|---|
| 113 |
|
|---|
| 114 | .. code-block:: console
|
|---|
| 115 |
|
|---|
| 116 | export QTDIR="/usr/local/Trolltech/Qt-4.8.5"
|
|---|
| 117 | export PATH="$QTDIR/bin:$PATH"
|
|---|
| 118 |
|
|---|
| 119 | need to be added either to ``$HOME/.bash/profile`` or ``$HOME/.bashrc``. Once that is done, logout/login and start using Qt 4.8.5.
|
|---|
| 120 |
|
|---|
| 121 | To compile the BNC program, you first download the source code from SVN repository http://software.rtcm-ntrip.org/svn/trunk/BNC. Go to directory BNC and run the following commands:
|
|---|
| 122 |
|
|---|
| 123 | .. code-block:: console
|
|---|
| 124 |
|
|---|
| 125 | qmake bnc.pro
|
|---|
| 126 | make
|
|---|
| 127 |
|
|---|
| 128 | You will find a build of BNC in directory BNC.
|
|---|
| 129 |
|
|---|
| 130 | .. index:: BNC installation - Mac OS X systems, Mac OS
|
|---|
| 131 |
|
|---|
| 132 | Mac OS X Systems
|
|---|
| 133 | ----------------
|
|---|
| 134 |
|
|---|
| 135 | Xcode and Qt installation
|
|---|
| 136 | ^^^^^^^^^^^^^^^^^^^^^^^^^^
|
|---|
| 137 | Xcode and Qt are required to compile BNC on OS X. Both tools are freely available. Xcode can be downloaded from the App Store or the Apple Developer Connection website. Once installed, run Xcode, go to 'Preferences->Downloads' and install the Command Line Tools component. Qt can be downloaded from the Qt Project website. We suggest installing version 4.8.4 or higher. The Qt libraries for Mac can be downloaded from http://www.qt.io/download. Once downloaded, mount the disk image, run the Qt.mpkg package and follow instructions from the installation wizard.
|
|---|
| 138 |
|
|---|
| 139 | Compilation of bnc
|
|---|
| 140 | ^^^^^^^^^^^^^^^^^^
|
|---|
| 141 | The version of qmake supplied in the Qt binary package is configured to use the macx-xcode specification. This can be overridden with the ``-spec macx-g++`` option which makes it possible to use ``qmake`` to create a ``Makefile`` to be used by ``make``.
|
|---|
| 142 |
|
|---|
| 143 | From the directory where bnc.pro is located, run ``qmake`` to create the ``Makefile`` and then ``make`` to compile the binary:
|
|---|
| 144 |
|
|---|
| 145 | .. code-block:: console
|
|---|
| 146 |
|
|---|
| 147 | qmake -spec macx-g++ bnc.pro
|
|---|
| 148 | make
|
|---|
| 149 |
|
|---|
| 150 | Refer to the following webpage for further information: http://doc.qt.io/qt-4.8/qmake-platform-notes.html.
|
|---|
| 151 |
|
|---|
| 152 | Bundle Deployment
|
|---|
| 153 | ^^^^^^^^^^^^^^^^^
|
|---|
| 154 | When distributing BNC it is necessary to bundle in all related Qt resources in the package. The Mac Deployment Tool has been designed to automate the process of creating a deployable application bundle that contains the Qt libraries as private frameworks. To use it, issue the following commands where ``bnc.app`` is located.
|
|---|
| 155 |
|
|---|
| 156 | .. code-block:: console
|
|---|
| 157 |
|
|---|
| 158 | macdeployqt bnc.app -dmg
|
|---|
| 159 |
|
|---|
| 160 | Refer to the following webpage for further information: http://doc.qt.io/qt-4.8/deployment-mac.html.
|
|---|
| 161 |
|
|---|
| 162 | Once a DMG file for BNC is created, you can double click it and install BNC by dragging the ``bnc.app`` icon to your ``Applications`` folder. To start BNC, double click on ``Applications/bnc.app``. |
|---|
