![](/uploads/1/2/7/5/127555234/946632359.jpg)
Is an open source geoinformation system which is developed by a globally distributed. Besides the source code developers also message translators, people who write documentation, those who report bugs and wishes and more are involved. Early days from pre-Internet to CVS and SVNWhile GRASS GIS is under development since (no typo!) it has been put into a centralized source code management system in December 1999. Because the World Wide Web (WWW) became available in the 1990s along with tools like browsers and such, followed by the development of distributed source code management tools. We moved on (think Y2K bug) the entire code into our instance of CVS (Concurrent Versioning System). With OSGeo being founded in 2006, we migrated the CVS repository to SVN (Subversion for the source code management) and trac (bug and wish tracker) on. Time to move on: gitNow, after more than 10 years using SVN/trac time had come to move on and join the large group of projects managing their source code in (see also our related ).
Destructuring a list containing two items to use it as arguments to a binary function Load extra fonts with lualatex QGIS and 1-to-many relationship.
Git comes with numerous advantages, yet we needed to decide which hosting platform to use. Options where github.com, gitlab.com, gitlab or gitea on OSGeo infrastructure, or other platforms. Through a survey we found out that the preference among contributors is GitHub. While not being open source itself it offers several advantages: it is widely known (good to get new developers interested and involved), numerous OSGeo projects are hosted there under the GitHub ““.If all fails (say, one day GitHub no longer being a reasonable choice) the import of our project from GitHub to GitLab is always.
What’s new in a nutshellAfter a bit more than four months of development the new update release GRASS GIS 7.4.2 is available. It provides more than 50 stability fixes and improvements compared to the previous stable version 7.4.1. An overview of the new features in the 7.4 release series is available at.Efforts have concentrated on making the user experience even better, providing many small, but useful additional functionalities to modules and further improving the graphical user interface. Segmentation now support extremely large raster maps.
Dockerfile and Windows support received updates. Also the manual was improved. For a detailed overview, see the. Today marks 35 years of GRASS GIS development – with the project keeps pushing the limits in terms of geospatial data processing quality and performance.GRASS (Geographic Resources Analysis Support System) is a free and open source Geographic Information System (GIS) software suite used for geospatial data management and analysis, image processing, graphics and map production, spatial modeling, and 3D visualization. Since the major GRASS GIS 7 version, it also comes with a feature rich engine for space-time cubes useful for time series processing of Landsat and Copernicus Sentinel satellite data and more.
GRASS GIS can be either used as a desktop application or as a backend for other software packages such as QGIS and R. Furthermore, it is frequently used on HPC and cloud infrastructures for massive parallelized data processing.Brief historyIn 1982, under the direction of Bill Goran at the U.S. Army Corps of Engineers Construction Engineering Research Laboratory (CERL), two GIS development efforts were undertaken. First, Lloyd Van Warren, a University of Illinois engineering student, began development on a new computer program that allowed analysis of mapped data. Second, Jim Westervelt (CERL) developed a GIS package called “ LAGRID – the Landscape Architecture Gridcell analysis system” as his master’s thesis. Thirty five years ago, on 29 July 1983, the user manual for this new system titled “ GIS Version 1 Reference Manual” was first published by J. Westervelt and M.
With the technical guidance of Michael Shapiro (CERL), the software continued its development at the U.S. Army Corps of Engineers Construction Engineering Research Laboratory (USA/CERL) in Champaign, Illinois; and after further expansion version 1.0 was released in 1985 under the name Geographic Resources Analysis Support System (GRASS). The GRASS GIS community was established the same year with the first annual user meeting and the launch of GRASSnet, one of the internet’s early mailing lists.
The user community expanded to a larger audience in 1991 with the “Grasshopper” mailing list and the introduction of the World Wide Web. The users’ and programmers’ mailing lists archives for these early years are still available.In the mid 1990s the development transferred from USA/CERL to The Open GRASS Consortium (a group who would later generalize to become today’s Open Geospatial Consortium — the ). The project coordination eventually shifted to the international development team made up of governmental and academic researchers and university scientists. Reflecting this shift to a project run by the users, for the users, in 1999 GRASS GIS was released under the terms of the GNU General Public License (GPL).
A detailed history of GRASS GIS can be found at.Where to next?The development on GRASS GIS continues with more energy and interest than ever. Parallel to the long-term maintenance of the GRASS 7.4 stable series, effort is well underway on the, which will bring many new features, enhancements, and cleanups. As in the past, the GRASS GIS community is open to any contribution, be it in the form of,. Please!About GRASS GISThe Geographic Resources Analysis Support System , commonly referred to as GRASS GIS, is an Open Source Geographic Information System providing powerful raster, vector and geospatial processing capabilities in a single integrated software suite.
GRASS GIS includes tools for spatial modeling, visualization of raster and vector data, management and analysis of geospatial data, and the processing of satellite and aerial imagery. It also provides the capability to produce sophisticated presentation graphics and hardcopy maps.
GRASS GIS has been translated into about twenty languages and supports a huge array of data formats. It can be used either as a stand-alone application or as backend for other software packages such as QGIS and R geostatistics.
It is distributed freely under the terms of the GNU General Public License (GPL). GRASS GIS is a founding member of the Open Source Geospatial Foundation (OSGeo).The GRASS Development Team, July 2018The post appeared first on. What’s new in a nutshellAfter three months of development the new update release GRASS GIS 7.2.2 is available. It provides more than 120 stability fixes and manual improvements compared to release version 7.2.1. An overview of new features in the 7.2 release series is available at.About GRASS GIS 7: Its graphical user interface supports the user to make complex GIS operations as simple as possible. The permits users to create new GRASS GIS-Python modules in a simple way while yet obtaining powerful and fast modules. Furthermore, the libraries were again significantly improved for speed and efficiency, along with support for.
A lot of effort has been invested to standardize parameter and flag names. Finally, GRASS GIS 7 comes with a series of new modules to analyse raster and vector data, along with a full temporal framework. For a detailed overview, see the list of. We are pleased to announce the stable release of GRASS GIS 7.2.0What’s new in a nutshellAfter almost two years of development the new stable major release GRASS GIS 7.2.0 is available.
It provides more than 1950 stability fixes and manual improvements compared to the former stable release version 7.0.5. The new version includes a series of new modules to analyse raster and vector data along with new temporal algebra functionality.More than 50 new addons are also available. A summary of the new features is available at.About GRASS GIS 7: Its graphical user interface supports the user to make complex GIS operations as simple as possible. The permits users to create new GRASS GIS-Python modules in a simple way while yet obtaining powerful and fast modules. Furthermore, the libraries were again significantly improved for speed and efficiency, along with support for.
A lot of effort has been invested to standardize parameter and flag names. Finally, GRASS GIS 7 comes with a series of new modules to analyse raster and vector data, along with a full temporal framework. For a detailed overview, see the list of. In the new release of QGIS 2.6.0 a series of new features have been added concerning. General: new features and bugfixes,. DXF export (improvements),.
Map Composer (enhancements),. Processing (including a new modeler implementation),.
QGIS Server (improvements),. Symbology (including user interface improvements),.
User Interface with improvements.A is available for more details with lots of screenshots.Congratulations to all QGIS developers! Looking forward to see the Fedora RPM availableYou can download QGIS 2.6 atThe post appeared first on. We are pleased to announce that the 50th ICA-OSGeo Lab has been established at the (Piattaforma GIS & Remote Sensing, PGIS), Research and Innovation Centre (CRI), Fondazione Edmund Mach (FEM), Italy. CRI is a multifaceted research organization established in 2008 under the umbrella of FEM, a private research foundation funded by the government of Autonomous Province of Trento. CRI focuses on studies and innovations in the fields of agriculture, nutrition, and environment, with the aim to generate new sharing knowledge and to contribute to economic growth, social development and the overall improvement of quality of life.The mission of the PGIS unit is to develop and provide multi-scale approaches for the description of 2-, 3- and 4-dimensional biological systems and processes. Core activities of the unit include acquisition, processing and validation of geo-physical, ecological and spatial datasets collected within various research projects and monitoring activities, along with advanced scientific analysis and data management. These studies involve multi-decadal change analysis of various ecological and physical parameters from continental to landscape level using satellite imagery and other climatic layers.
The lab focuses on the geostatistical analysis of such information layers, the creation and processing of indicators, and the production of ecological, landscape genetics, eco-epidemiological and physiological models. The team pursues actively the development of innovative methods and their implementation in a GIS framework including the time series analysis of proximal and remote sensing data.The GIS and Remote Sensing Unit (PGIS) members strongly support the which is perfectly in line with academic research. PGIS contributes extensively to the open source software development in geospatial (main contributors to GRASS GIS), often collaborating with various other developers and researchers around the globe. In the new ICA-OSGeo lab at FEM international PhD students, university students and trainees are present.PGIS is focused on knowledge dissemination of open source tools through a series of courses designed for specific user requirement (schools, universities, research institutes), blogs, workshops and conferences. Their recent publication in Trends in Ecology and Evolution underlines the need on using Free and Open Source Software (FOSS) for completely open science. Markus Neteler, who is leading the group since its formation, has two decades of experience in developing and promoting open source GIS software. Being founding member of the Open Source Geospatial Foundation (OSGeo.org, USA), he served on its board of directors from 2006-2011.
Luca Delucchi, focal point and responsible person for the new ICA-OSGeo Lab is member of the board of directors of the Associazione Italiana per l’Informazione Geografica Libera (GFOSS.it, the Italian Local Chapter of OSGeo). He contributes to several Free and Open Source software and open data projects as developer and trainer.Details about the GIS and Remote Sensing Unit atOpen Source Geospatial Foundation ( OSGeo) is a not-for-profit organisation founded in 2006 whose mission is to support and promote the collaborative development of open source geospatial technologies and data.International Cartographic Association ( ICA) is the world authoritative body for cartography and GIScience. See also the new.
Last Updated: 2020-01-16Last Change: 2020-01-161. IntroductionThis document is the original installation guide of the described softwareQGIS. The software and hardware descriptions named in thisdocument are in most cases registered trademarks and are therefore subjectto the legal requirements. QGIS is subject to the GNU General PublicLicense. Find more information on the QGIS Homepage:The details, that are given in this document have been written and verifiedto the best of knowledge and responsibility of the editors. Nevertheless,mistakes concerning the content are possible.
Therefore, all data are notliable to any duties or guarantees. The editors and publishers do not takeany responsibility or liability for failures and their consequences. You arealways welcome for indicating possible mistakes.Because the code of QGIS evolves from release to release, These instructions areregularly updated to match the corresponding release. Instructions for the currentmaster branch are available atIf you wish to build another version of QGIS, ensure to checkout the appropriaterelease branch. The QGIS source code can be found.Please visit for information on joining our mailing listsand getting involved in the project further./! Note to document writers: Please use this document as the centralplace for describing build procedures.
Please do not remove this notice./! Note to document writers: This document is generated fromdoc/INSTALL.t2t - if you need to edit this document, be sure to edit thatfile rather than the generated INSTALL document found in the root of thesource directory.2.
Sudo apt-get update3.3. Dpkg-buildpackage -us -uc -b/! Note: Install devscripts to get dch./! Note: If dpkg-buildpackage complains about unmet build dependenciesyou can install them using apt-get and re-run the command./! Note: If you have libqgis1-dev installed, you need to remove it firstusing dpkg -r libqgis1-dev. Otherwise dpkg-buildpackage will complain about abuild conflict./! Note: By default tests are run in the process of building and theirresults are uploaded toYou can turn the tests off using DEBBUILDOPTIONS=nocheck in front of thebuild command.
The upload of results can be avoided with DEBTESTTARGET=test.The packages are created in the parent directory (ie. One level up).Install them using dpkg.
Cat /.config/QtProject/qtlogging.ini./quickpackage.shAfter this you should now have a nsis installer containing your own buildof QGIS and all dependencies needed to run it on a windows machine.4.1.6. Osgeo4w packagingThe actual packaging process is currently not documented, for now please take alook at:ms-windows/osgeo4w/package.cmd 4.2.
Building using MinGWNote: This section might be outdated as nowadays Visual C is use to buildthe 'official' packages.Note: For a detailed account of building all the dependencies yourself youcan visit Marco Pasetti's website here:Read on to use the simplified approach with pre-built libraries.4.2.1. MSYSMSYS provides a unix style build environment under windows. We have created azip archive that contains just about all dependencies.Get this:and unpack to c:msysIf you wish to prepare your msys environment yourself rather than usingour pre-made one, detailed instructions are provided elsewhere in thisdocument.4.2.2.
QtDownload Qt opensource precompiled edition exe and install (including thedownload and install of mingw) from here:When the installer will ask for MinGW, you don't need to download and installit, just point the installer to c:msysmingwWhen Qt installation is complete:Edit C:Qt5.9.1binqtvars.bat and add the following lines. Set PATH=%PATH%;C:msyslocalbin;c:msyslocallibset PATH=%PATH%;'C:Program FilesSubversionbin'I suggest you also add C:Qt5.9.1bin to your Environment Variables Path inthe windows system preferences.If you plan to do some debugging, you'll need to compile debug version of Qt:C:Qt5.9.1binqtvars.bat compiledebugNote: there is a problem when compiling debug version of Qt 4.7, the script ends withthis message 'mingw32-make:.
No rule to make target `debug'. Tocompile the debug version you have to go out of src directory and execute thefollowing command. C:Qt5.9.1 make4.2.3. Flex and BisonGet Flex(the zip bin) and extract it into c:msysmingwbin4.2.4. PythonFollow this section in case you would like to use Python bindings for QGIS. Tobe able to compile bindings, you need to compile SIP and PyQt5 from sources astheir installer doesn't include some development files which are necessary.Note that even if you compile without the Python bindings, Python3 is stilla necessary dependency for building QGIS.4.2.4.1.
Download and install Python - use Windows installer(It doesn't matter to what folder you'll install it)4.2.4.2. Download SIP and PyQt5 sourcesExtract each of the above zip files in a temporary directory. Make sureto get versions that match your current Qt installed version.4.2.4.3.
C:Qt5.9.1binqtvars.batpython configure.pymakemake install4.2.4.5. Final python notes/! You can delete the directories with unpacked SIP and PyQt5 sources after asuccessful install, they're not needed anymore.4.2.5. GitIn order to check out QGIS sources from the repository, you need a git client.This installer should work fine:4.2.6. CMakeCMake is build system used by QGIS. Download it from here:4.2.7. QGISStart a cmd.exe window ( Start - Run - cmd.exe ) Create developmentdirectory and move into it.
Cmakesetup.Note: You must include the '.' Above.Click 'Configure' button. When asked, you should choose 'MinGW Makefiles' asgenerator.There's a problem with MinGW Makefiles on Win2K. If you're compiling on thisplatform, use 'MSYS Makefiles' generator instead.All dependencies should be picked up automatically, if you have set up thePaths correctly. The only thing you need to change is the installationdestination (CMAKEINSTALLPREFIX) and/or set 'Debug'.For compatibility with NSIS packaging scripts I recommend to leave the installprefix to its default c:program filesWhen configuration is done, click 'OK' to exit the setup utility.4.2.10.
Compilation and installation. Make make install4.2.11. Run qgis.exe from the directory where it's installed (CMAKEINSTALLPREFIX)Make sure to copy all.dll:s needed to the same directory as the qgis.exebinary is installed to, if not already done so, otherwise QGIS will complainabout missing libraries when started.A possibility is to run qgis.exe when your path contains c:msyslocalbin andc:msyslocallib directories, so the DLLs will be used from that place.4.2.12. Create the installation package: (optional)Download and install NSIS from Now using windows explorer, enter the winbuild directory in your QGIS sourcetree.
Read the READMEfile there and follow the instructions. Next right clickon qgis.nsi and choose the option 'Compile NSIS Script'.4.3. Creation of MSYS environment for compilation of QGIS 4.3.1.
Initial setup 4.3.1.1. MSYSThis is the environment that supplies many utilities from UNIX world in Windows and is neededby many dependencies to be able to compile.Download from here:Install to c:msysAll stuff we're going to compile is going to get to this directory (resp.
Its subdirs).4.3.1.2. MinGWDownload from here:Install to c:msysmingwIt suffices to download and install only g and mingw-make components.4.3.1.3.
Flex and BisonFlex and Bison are tools for generation of parsers, they're needed for GRASS and also QGIS compilation.Download the following packages:Unpack them all to c:msyslocal 4.3.2. Installing dependencies 4.3.2.1. Getting readyPaul Kelly did a great job and prepared a package of precompiled libraries for GRASS.The package currently includes:. zlib-1.2.3. libpng-1.2.16-noconfig.
xdr-4.0-mingw2. freetype-2.3.4. fftw-2.1.5. PDCurses-3.1. proj-4.5.0.
gdal-1.4.1It's available for download here:Moreover he also left the notes how to compile it (for those interested):Unpack the whole package to c:msyslocal 4.3.2.2. GRASSGrab sources from CVS or use a weekly snapshot, see:In MSYS console go to the directory where you've unpacked or checked out sources(e.g.
C:msyslocalsrcgrass-6.3.cvs)Run these commands./configuremakemake install4.3.2.7. POSTGRESWe're going to use precompiled binaries. Use the link below for download:copy contents of pgsql directory from the archive to c:msyslocal 4.3.3. CleanupWe're done with preparation of MSYS environment. Now you can delete all stuff in c:msyslocalsrc - it takes quite a lotof space and it's not necessary at all.4.4.
Building on Linux with mxeWith this approach you can cross build a Windows binary on Linux using MXE (M cross environment).You can find the build script and a README.md file in the ms-windows/mxe directory.For now, Python buildings cannot be built with mxe.4.4.1. Building with DockerThis is the simplest way, but you need to have Docker installedon your system.You can use a Docker image to cross build QGIS by callingthe script ms-windows/mxe/build.sh from the root directory of QGIS repository. Building without Docker This requires to install mxe toolchain on your system and buildall dependencies by yourself.4.4.1.1. Initial setupPlease follow the instructions on mxe website to setup your building toolchain,take note of the path where you have installed mxe.4.4.1.2. Building the dependenciesPlease see README.md under ms-windows/mxe for detailed instructions and for thelist of dependencies that need to be built in mxe before attempting to build QGIS.4.4.1.3.
Cross-Building QGISEdit the build-mxe.sh script and optionally adjust the path where your mxe installation is located, youcan also change the build and release directories.4.4.2. Testing QGISCopy and unzip on the Windows machine package produced by the build and launch the qgis binary: no installationis required.5. Building on MacOS XThis document is outdated and there is currently no up to date documentation for building on mac.You might want to consider to read an approach using Homebrew although not up to date either:In this approach I will try to avoid as much as possible building dependenciesfrom source and rather use frameworks wherever possible.' Universal', SDK and non-default arch builds require more complex options andsome fiddling with the system. It is best to stick with a single, default,architecture build and follow these instructions for an initial build.Included are notes for building on Mac OS X 10.5 ( Leopard), 10.6( Snow Leopard), 10.7 ( Lion), 10.8 ( Mt. Lion) and 10.9 ( Mavericks)(These names will be used throughout the instructions.)Make sure to read each section completely before typing the first command you see.General note on Terminal usage: When I say 'cd' to a folder in a Terminal,it means type 'cd ' (without the quotes, make sure to type a space after) andthen type the path to said folder, then. A simple way to do thiswithout having to know and type the full path is, after type the 'cd ' part,drag the folder (use the icon in its window title bar, or drag a folder fromwithin a window) from the Desktop to the Terminal, then tap.Parallel Compilation: On multiprocessor/multicore Macs, it's possible tospeed up compilation, but it's not automatic.
Whenever you type 'make' (butNOT 'make install'), instead type. Make -j $(/usr/sbin/sysctl -n hw.ncpu)Note: if you get an error in parallel compilation, try removing the -j # flag,so it's just 'make', or using a smaller number. Sometimes make can hiccup on toomany threads.5.1.
Install Developer ToolsDeveloper tools are not a part of a standard OS X installation. Up throughSnow Leopard, the Developer Tools, later called Xcode, were included with thesystem install disks, though it's best to download the latest version compatiblewith your system to get important updates fixing various issues.Starting with Lion, Xcode is available as a download and from the App Store.Downloading Xcode/Developer Tools for up through Snow Leopard requires a free developer account atdeveloper.apple.com.
Up through Snow Leopard, get the latest Xcode that issupported for your system. For Lion and above, you can get Xcode from either afree developer account or for a minimal fee from the app store.When installing Xcode up through Snow Leopard, make sure todo a custom install and install the Unix Development or Command Line Tools option.On Lion, if you have installed Xcode 4.0 - 4.2 and are upgrading to 4.3, it'sa good idea to uninstall the old version first with. Sudo /Developer/Library/uninstall-devtoolsOn Lion and Mt. Lion, using Xcode 4.4+, the developer command line tools can beinstalled via the Xcode preferences.Xcode 4.3+ also introduces the clang frontend to the LLVM compiler as default.Note: In XCODE 4.5 installed from the app store, you need to install thecommand line tools from XCode - Preferences - Downloads and choose command line tools.The supplied clang version 4 can compile QGIS, but presents many warningscompared to just using LLVM. You can specifically use LLVM by exporting paths tothe compilers in Terminal, or shell scripts, prior to building QGIS. Export CC=/usr/bin/llvm-gccexport CXX=/usr/bin/llvm-gIf you have trouble building some of the dependencies listed below with clang(e.g.
OSG & osgEarth), try using only the LLVM compilers.5.2. Install Qt4 from disk imageYou need a minimum of Qt-4.4.0. I suggest getting the latest (Qt 4, not 5). There is no needfor the full Qt SDK, so save yourself some download time and get the frameworksonly. This is available in the Libraries section of the Qt download page.Snow Leopard+ note: If you are building on Snow Leopard+, you will need todecide between 32-bit support in the older Qt Carbon branch, or 64-bitsupport in the Qt Cocoa branch. Appropriate installers are available for bothas of Qt-4.5.2, though they stopped making Carbon packages at Qt 4.7.4.Qt 4.6+ is recommended for Cocoa.Starting with Lion, Carbon may not work properly, if at all.Starting with Qt 4.8, only 64bit Cocoa installers are available.General note: Support for new system versions in any given Qt version maynot be present and may cause a 'This version of Mac OS Xis unsupported' error when building QGIS. Try the next Qt version.PPC note: The readymade Qt Cocoa installers don't include PPC support, you'dhave to compile Qt yourself.
But, there appear to be issues with Qt Cocoa onPPC Macs anyways. Qt Carbon is recommended on PPC Macs.If you want debug frameworks, Qt also provides a separate download with these.These are in addition to the non-debug frameworks.Earlier OS X systems may need an old Qt version - check the requirements of thecurrent Qt version. To get old Qt downloads, there is an FTP link at the bottomof the download page. Files are in the qt/source (yes, even the binary packages).Once downloaded open the disk image and run the installer. Note you need adminprivileges to install.Leopard+ note: Qt includes a couple non-framework libraries in /usr/lib.When using a system SDK these libraries will not be found. To fix this problem,add symlinks to /usr/local.
![Jamierob Jamierob](/uploads/1/2/7/5/127555234/522511967.jpg)
Sudo ln -s /usr/lib/libQtUiTools.a /usr/local/lib/sudo ln -s /usr/lib/libQtCLucene.dylib /usr/local/lib/These should then be found automatically. Earlier systemsmay need some help by adding '-L/usr/local/lib' to CMAKESHAREDLINKERFLAGS,CMAKEMODULELINKERFLAGS and CMAKEEXELINKERFLAGS in the cmake build.5.3. Install CMake for OSXGet the latest source release from here:Binary installers are available for OS X, but they are not recommended(2.4 versions install in /usr instead of /usr/local, and 2.6+ versions are astrange application). Instead, download the source.NOTE: 2.8.5 is broken for detecting part of Qt.
Fixed in 2.8.6.Double-click the source tarball to unpack it, then cd to the source folder./bootstrap -docdir=/share/doc/CMake -mandir=/share/manmake -j #cpussudo make install5.3.1. Optional setup: ccacheXcode 4.4+ note: You will probably not need to install ccache if you are usingthe clang frontend to LLVM compiler, a setup that already provides fairly quickcompile times.Setup ccache to significantly speed up compile times after initial build.(Switching git branches will again cause longer initial build times unlessseparate build directories are used for each branch.)Get the latest source release from here:Double-click the source tarball to unpack, then, in Terminal.app, cd to thesource folder.
Export PATH=/usr/local/bin/compilers:$PATHIf you have trouble building some of the dependencies listed below (e.g. OSG &osgEarth), try bypassing ccache.5.4. Install development frameworks for QGIS dependenciesDownload William Kyngesburye's excellent GDAL Complete package that includesPROJ, GEOS, GDAL, SQLite3, SpatiaLite, and image libraries, as frameworks.There are also GSL and FreeType frameworks.Once downloaded, open and install the frameworks.William provides an additional installer package for PostgreSQL (for PostGISsupport). QGIS just needs the libpq client library, so unless you want tosetup the full Postgres + PostGIS server, all you need is the client-onlypackage. It's available here:Also available is a GRASS application:Old versions of these packages for older systems are available in thesoftware archive section.5.4.1. Additional dependencies: General compatibility noteThere are some additional dependencies that, at the time of writing, are notprovided as frameworks or installers so we will need to build these from source.If you are wanting to build QGIS as a 64-bit application, you will need toprovide the appropriate build commands to produce 64-bit support in dependencies.Likewise, for 32-bit support on Snow Leopard, you will need to override thedefault system architecture, which is 64-bit, according to instructions forindividual dependency packages.Stable release versions are preferred.
Beta and other development versions mayhave problems and you are on your own with those.5.4.2. Additional dependencies: ExpatSnow Leopard+ note: Snow Leopard includes a usable expat, so this step isnot necessary on Snow Leopard or above.Get the expat sources:Double-click the source tarball to unpack, then, in Terminal.app, cd to thesource folder./configure -disable-dependency-tracking CFLAGS=-Osmakesudo make install5.4.4. Additional dependencies: PythonLeopard+ note: Starting with Leopard a usable Python is includedin the system. This is Python 2.5, 2.6 and 2.7, respectively for Leo, Snow and Lion+.So there is no need to install Python on Leopard and newer.You can still install Python from python.org if preferred.If installing from python.org, make sure you install the latest Python2.x fromPython 3 is a major change, and may have compatibility issues, so try it atyour own risk.5.4.5. Additional dependencies: SIPMt Lion note: SIP 4.15.7 appears to not work on Mt Lion.
Install eithera prior version to 4.14.6 or a later version 4.16.3+Retrieve the python bindings toolkit SIP fromDouble-click the source tarball to unpack it, then, in Terminal.app,cd to the source folder. Then for your chosen Python:python.org Python. Python configure.py -n -d /Library/Python/2.5/site-packages -b /usr/local/bin -e /usr/local/include -v /usr/local/share/sip -s MacOSX10.5.sdkSnow Leopard system PythonSimilar to Leopard, you should install outside the system Python path.Also, you need to specify the architecture you want and make sure to run theversioned python binary (this one responds to the 'arch' command, 'python' doesnot).
Substitute '2.7' for python version and 10.7 for SDK version below forLion.If you are using 32-bit Qt (Qt Carbon). Makesudo make install5.4.6. Additional dependencies: QScintilla2Retrieve the Qt version of the Scintilla-based text editor widget fromDouble-click the tarball to unpack it. Then, cd to the QScintilla2.x.x sourcefolder in a Terminal.QScintilla2 wants to install in the system path - with libraries going into/Library/Frameworks and headers into /usr/include/Qsci - this is not a goodidea, and it also basically breaks the QtDesigner plugin. More configurationis needed to install outside the system path, in /usr/local/. Python configure.py -d /Library/Python/2.5/site-packages -b /usr/local/bin -n /usr/local/Qt4.8/qsci -v /usr/local/share/sip/PyQt4Snow Leopard system PythonSimilar to Leopard, you should install outside the system Python path.Also, you need to specify the architecture you want (requires at least PyQt 4.6),and make sure to run the versioned python binary (this one responds to the'arch' command, which is important for pyuic4, 'python' does not).Substitute '2.7' for python version and 10.7 for SDK version below for Lion.If you are using 32-bit Qt (Qt Carbon).
Cd cd Pythonpython2.7 configure.py -o /usr/local/lib -n /usr/local/include -d /Library/Python/2.7/site-packages/PyQt4 -v /usr/local/share/sip/PyQt4 -sip-incdir=/usr/local/include -pyqt-sipdir=/usr/local/share/sip/PyQt4cat Qsci.pro. Cat qwtconfig.pri./configure -disable-dependency-tracking CFLAGS=-Osmakesudo make install5.4.11. Additional dependencies: gpsbabelFor integrated GPS Tools functions, a gpsbabel executable is required. You canfind this at:Download the GPSBabel OS X package, and copy GPSBabelFE.app from the disk image to/Applications.5.4.12. Optional dependencies: libfcgiIf you want to use the QGIS Mapserver, you need libfcgi. This is included onsystems up through Snow Leopard, but was dropped at Lion.
So, on Lion you needto get the source from:Grab the latest fcgi SNAP package there. Double-click the sourcetarball to unpack it, then cd to the source folder./configure -disable-dependency-tracking CFLAGS=-Osmakesudo make install5.4.13.
Optional dependencies: OSG & osgEarthIf you want the Globe plugin in QGIS (default OFF), OSG and osgEarth are needed.First, OpenSceneGraph. The main site is very out of date, just go togithub:Download the latest 3.1 version (you can select a tarball when you hover overthe entry). Double-click the source tarball to unpack it.(There is a version numbering oddity in the source, but since we'll bebundling OSG as it's meant to be, it really doesn't matter).Installation is a bit out of touch with OS X standards, so we'll stage it to atemporary location first.
You could stage it to the folder that the OSG sourcefolder is in, or a common staging area like /Users/Shared/unix/osg. Pick afolder not hidden and that doesn't need admin permissions to write to for simplicity.If you are building on Leopard, its configure forces a old ppc/i386 32bit build.If you want 64bit you need to fix CMakeLists.txt - in a text editor, find theif-block that starts with. Mkdir buildcd buildexport PATH='/path/to/osg/staging/folder/bin:$PATH'cmake -D CMAKEINSTALLPREFIX=/path/to/some/staging/folder -D CMAKEBUILDTYPE=MinSizeRel -D OSGEARTHBUILDFRAMEWORKS=true.makemake installsudo mkdir -p '/Library/Application Support/OpenSceneGraph/Headers'Open the staging folder you chose for the CMAKEINSTALLPREFIX option above.Also open the OSG staging path /bin folder from the OSG build.Move all the.frameworks from the lib/ folder to /Library/Frameworks.Move the files in the osgPlugins folder in the lib/ folder to/Library/Application Support/OpenSceneGraph/PlugIns.
Move the osgEarthDriversfolder in the include/ folder to /Library/Application Support/OpenSceneGraph/Headers.(you may need to create this folder)And as for OSG, you can leave the bin/ executables where they are.5.5. API documentationIf you want to build a local copy of the API docs (like those at) you will need Graphviz and Doxygen installed:Graphviz is simply installed via a regular Mac package installer. Install itfirst. It will place some of its binaries in /usr/local/bin/.For Doxygen, compiling the source is recommended over installing the app.Double-click the source tarball to unpack it, then cd to the source folder./configuremake -j #cpussudo make installThe documentation will be output to the build directory, and if using more completeQGIS.app bundling on install, inside the app in:QGIS.app/Contents/Resources/doc5.6.
QGIS sourceUnzip the QGIS source tarball to a working folder of your choice(/usr/somewhere is not a good choice as it's hidden and requires rootprivileges). If you are reading this from the source, you've already donethis.If you want to experiment with the latest development sources, go to the githubQGIS project page:It should default to the master branch. Click the Downloads button andselect Download.tar.gz. Double-click the tarball to unzip it.Alternatively, install git from and do the following.Make a specific repository directory somewhere, e.g.
/QGIS/QGIS, and cdinto it. The following will read-only clone the master branch to the directory. Mkdir buildcd buildcmake -D CMAKEINSTALLPREFIX=/Applications -D CMAKEBUILDTYPE=MINSIZEREL -D ENABLETESTS=FALSE -D SPATIALINDEXLIBRARY=/usr/local/lib/libspatialindex.dylib -D SPATIALINDEXINCLUDEDIR=/usr/local/include/spatialindex -D QWTLIBRARY=/usr/local/qwt-6.0.2/lib/libqwt.dylib -D QWTINCLUDEDIR=/usr/local/qwt-6.0.2/include -D BISONEXECUTABLE=/usr/local/bin/bison.Note: Don't forget the. On the last line, which tells CMake to look for thesource files in one directory up.After the initial Terminal configure, you can use ccmake to make further changes. D WITHGLOBE=true -D OSGEARTHINCLUDEDIR='/Library/Application Support/OpenSceneGraph/Headers' -D OSGPLUGINSPATH='/Library/Application Support/OpenSceneGraph/PlugIns' Bundling note: Older Qt versions may have problems with some Qt plugins andQGIS. The way to handle this is to bundle Qt inside the QGIS application. Thedefault is to bundle Qt (and osg/osgEarth, if configured).Even better for distribution purposes, to also bundle any extra non-framework,non-standard, libs (ie postgres' libpq) set the bundle value to 2.
Cp -fp /Applications/GPSBabelFE.app/Contents/MacOS/gpsbabel /QGIS.app/Contents/MacOS/bin/If you installed in /Applications, adjust the path accordingly and prefix thewhole command with 'sudo '.QGIS ServerSee the QGIS Server documentation page at:for instructions on setting up Apache fastcgi and testing qgis server, includinginstalling the mod-fastcgi that is missing on Lion.6. Setting up the WCS test server on GNU/LinuxRequires: Ubuntu / Debian derived distroThese notes are for Ubuntu - other versions and Debian derived distros mayrequire slight variations in package names.6.1.
PreparationNote the git repo below will change to the default QGIS repo once this workis integrated into master.git remote add blazek git://github.com/blazek/Quantum-GIS.gitgit fetch blazekgit branch -track wcs2 blazek/wcs2git checkout wcs2cd /var/www/sudo mkdir wcssudo chown timlinux wcscd wcs/mkdir cgi-bincd cgi-bin/6.2. Setup mapserver`sudo apt-get install cgi-mapserver`Set the contents of cgi-bin/wcstest-1.9.0 to. Sudo tail -f /var/log/apache2/wcsqgis.org/error.log7.
Setting up a Jenkins Build ServerAssumption: You know how to make a working build environment and want todeploy it under Jenkins for continuous integration testing now.These notes are terse, I will expand on them later as the need arises. Theprocedure is:. Install Jenkins and get it configured according to your own preferences. Make sure you have the git, github, junit etc plugins installed. Cd build# show listing of tests, without running themctest -show-only# run specific C or Python test(s) matching a regular expressionctest -verbose -tests-regex SomeTestName9.
![](/uploads/1/2/7/5/127555234/946632359.jpg)