-Precompiled builds of BNC are available for MS Windows, Linux, and Mac OS X systems and can be downloaded for installation from http://igs.bkg.bund.de/ntrip/download. Please ensure that you always use the latest version of the program. +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.
-MS Windows build: A dynamically compiled shared libary 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. After installation your 'bnc.exe' file shows up under 'All Programs'. -
- --Linux build: 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, unzip the archive and run the included BNC binary file. For Linux, static and shared builds of BNC are made available. A static build would be sufficient in case you don't want BNC to trace PPP results using Google Map (GM) or OpenStreetMap (OSM). Note that GM/OSM usage requires the QtWebKit library which can only be part of BNC builds from shared libraries. -
- --Mac OS X build: -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'. +MS Windows Build: A dynamically compiled shared libary 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'. +
+ ++Linux Build: 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. For Linux, static and shared builds of BNC are made available. A static build would be sufficient in case you don't want BNC to trace PPP results using Google Map (GM) or OpenStreetMap (OSM). Note that GM/OSM usage requires BNC builds from shared libraries. +
+ ++Mac OS X Build: +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'.
-BNC has been written under GNU General Public License (GPL). This ZIP archive provides the BNC source code Version 2.12.0 as developed using Qt Version 4.8.5. The latest source code is available from Subversion software archive http://software.rtcm-ntrip.org/svn/trunk/BNC. The following describes how to produce your builds of BNC on Windows, Linux, and Mac systems. -
- -- We used the MinGW Version 4.4.0 compiler to create the Windows binaries. It is likely that BNC can be compiled on other systems where a GNU compiler and Qt Version 4.8.4 or any later version are installed. -Using a shared library BNC build requires that you first install your own shared Qt library. -
- -Static and Shared Libraries
-You can produce static or shared builds of BNC. Static builds are sufficient in case you don't want BNC to produce track maps using Google Map (GM) or Open StreetMap (OSM). GM/OSM usage would requires the QtWebKit library which can only be part of BNC builds from shared libraries. So, using a shared library BNC build requires that you first install your own shared library of Qt.
-
Windows Systems, Shared Library
-How to install a shared QT 4.8.5 library on a Windows system to create your
-own shared build of BNC:
+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 used for BNC Version 2.12.0 and developed using Qt Version 4.8.5. 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 are installed.
+
Static versus Shared Libraries
+You can produce static or shared builds of BNC. Static builds are sufficient in case you don't want BNC to produce track maps using Google Map (GM) or Open StreetMap (OSM). GM/OSM usage would require the QtWebKit library which can only be part of BNC builds from shared libraries. Hence, producing a shared library BNC build requires that you first install your own shared library of Qt.
+
MS Windows Systems, Shared Library
+This explains how to install a shared QT 4.8.5 library on Windows systems to create your own shared build of BNC.