sij/mapnik
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Updated Using SCons with Mapnik 0.6.0 (markdown)

floledermann 2011-11-29 00:34:43 -08:00
parent 647d6abb01
commit 9f39e82c9d
1 changed files with 28 additions and 29 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

43
UsingScons.md

@ -1,56 +1,55 @@
<!-- Name: UsingScons --> # Using SCons with Mapnik
<!-- Version: 18 -->
<!-- Last-Modified: 2010/01/08 16:07:42 -->
<!-- Author: myselfhimself -->
# Using SCons with Mapnik 0.6.0
*NOTE: these instructions are for the 0.6.0 release*
Mapnik uses a python-based build system called [SCons](http://www.scons.org/wiki/TheBigPicture) to configure, build, and install Mapnik from source. Mapnik uses a python-based build system called [SCons](http://www.scons.org/wiki/TheBigPicture) to configure, build, and install Mapnik from source.
The build system is composed of a single *`SConstruct`* file in the main source directory and various *`SConscript`* files in subdirectories. The build system is composed of a single `SConstruct` file in the main source directory and various `SConscript` files in subdirectories.
For more details see on SCons see: For more details see on SCons see:
* SCons documentation: http://www.scons.org/documentation.php * SCons documentation: http://www.scons.org/documentation.php
* Good Overview: http://www.humanized.com/presentations/scons/ * Good Overview: http://www.humanized.com/presentations/scons/
For Details about the usage of SCons in the Mapnik build system, follow along... ## Quickstart
# Quickstart
For the impatient just do: For the impatient just do:
#!sh
$ cd mapnik_src_dir $ cd mapnik_src_dir
$ python scons/scons.py configure # will configure compilation and save out configuration to a python pickle $ python scons/scons.py configure # will configure compilation and save out configuration to a python pickle
$ python scons/scons.py # will compile mapnik sources (running configure first if not done yet) $ python scons/scons.py # will compile mapnik sources (running configure first if not done yet)
$ sudo python scons/scons.py install # will install Mapnik (running configure and compiling first if not done yet) $ sudo python scons/scons.py install # will install Mapnik (running configure and compiling first if not done yet)
If you are confident as to the mapnik project's dependencies, you should run the scons/scons.py install command right away.
# Common Questions ## Common Questions
### Do I need to install SCons?
* Do I need to install SCons? *
* No, for convenience Mapnik bundles a `scons-local` directory that includes all the SCons python modules needed to build Mapnik.. * No, for convenience Mapnik bundles a `scons-local` directory that includes all the SCons python modules needed to build Mapnik..
* This allows you to run scons locally within the Mapnik source folder like: * This allows you to run scons locally within the Mapnik source folder like:
$ python scons/scons.py $ python scons/scons.py
* I already have SCons installed, can I use it? * ### I already have SCons installed, can I use it?
* Yes, to use your installed version of SCons rather than the bundled version just run the command: * Yes, to use your installed version of SCons rather than the bundled version just run the command:
$ scons $ scons
* How does SCons compare to `make`? * ### How does SCons compare to `make`?
* SCons is less verbose, handles dependency checking more thoroughly, and caches configuration settings differently. * SCons is less verbose, handles dependency checking more thoroughly, and caches configuration settings differently.
* However, the basic user experience is quite similar to the common `make` commands: * However, the basic user experience is quite similar to the common `make` commands:
|| *Tool* || *Configure Step* || *Compile Step*|| *Install Step* || <table>
|| *make* || $ ./configure || $ make || $ sudo make install || <tr><th>Tool</th><th>Configure Step</th><th>Compile Step</th><th>Install Step</th></tr>
|| *SCons* || $ scons configure || $ scons || $ sudo scons install || <tr><th>make</th><td>$ ./configure</td><td>$ make</td><td>$ sudo make install</td></tr>
* For more details on SCons vs other build tools see: http://www.scons.org/wiki/SconsVsOtherBuildTools <tr><th>SCons</th><td>$ scons configure</td><td>$ scons</td><td>$ sudo scons install</td></tr>
</table>
For more details on SCons vs other build tools see: http://www.scons.org/wiki/SconsVsOtherBuildTools
---
# Old / outdated information
# Summary of Changes between 0.5.x and 0.6.0 ## Summary of Changes between 0.5.x and 0.6.0
* SCons now has an optional configure step which will configure your build, then exit. * SCons now has an optional configure step which will configure your build, then exit.
* To configure run $ python scons/scons.py configure SOMEVARIABLE=somevalue * To configure run $ python scons/scons.py configure SOMEVARIABLE=somevalue