fix windows compile links and remove unneeded or out of date pages

Dane Springmeyer 2011-12-11 11:12:06 -08:00
parent dcaca43eaf
commit 93988cd35b
10 changed files with 1 additions and 236 deletions

@ -1,109 +0,0 @@
<!-- Name: BuildingOnWindows -->
<!-- Version: 1 -->
<!-- Last-Modified: 2011/02/23 14:19:34 -->
<!-- Author: roel_v -->
To build mapnik on Windows with Visual Studio you need experience with Visual Studio and C++ development experience in general. Mapnik has a relatively large list of dependencies. I've tried to automate a large part of the process with the batch file below. I've only tested with the versions of the libraries listed below. Boost is not included here, it needs to be build separately.
This build includes all libraries statically. That way you can make one self-contained binary.
To build under MSVC, you need to patch the code a bit (as of mapnik 0.7.1). Search the trac for patches by me (roel_v), there are 4 of them.
For the libraries where no build system is available out of the box, you can download the project files from the mapnik php extension at https://github.com/roel-v/php_mapnik .
This setup assumes a directory structure where all libraries are stored under a 'thirdparty' directory, where the .lib files will be copied to.
Working as of Januari 2011. Don't just blindly copy and paste, it's more a recipe for the steps to take than an actual working script. You still need to follow the instructions in the comments.
@echo off
rem Script to build all prereq libraries for mapnik on Windows
rem using msvc, with as little external dependencies as possible.
rem For all these libraries, build the static version.
"c:\program files\microsoft visual Studio\vc\bin\vcvars32.bat"
cd thirdparty
rem zlib - www.zlib.org, 1.2.5
rem Uses standard makefile, build with nmake
rem Add to win32/Makefile.msc: LOC = -DGAS_COFF
rem Output: zlib.lib
cd zlib-1.2.5
nmake -f win32/Makefile.msc zlib.lib
copy zlib.lib ..
cd ..
rem freetype
rem Uses arcane Makefile (not sure what format) or jam. PITA
rem to get working, use own project. Check docs\INSTALL.ANY
rem because for some reason some files cannot be included in
rem the build.
rem Output: freetype.lib
cd freetype-2.4.4
copy ..\..\vs_project\Debug\freetype.lib ..
cd ..
rem icu
rem Uses autotools or MSVC 10 project files. Use own project.
rem Output: icu.lib
cd icu\source
cd data
nmake -f makedata.mak ICUMAKE="C: \tmp\mapnik-0.7.1\thirdparty\icu\source\data"
cd ..
copy ..\..\..\vs_project\Debug\icu.lib ..\..
cd ..\..
rem libjpeg
rem Makefile-based, provides VC version.
rem Output: libjpeg.lib
cd jpeg-8b
copy jconfig.vc jconfig.h
nmake -f makefile.vc
copy libjpeg.lib ..
cd ..
rem libxml2
rem Used an autotool emulation file based on cscript.
rem Note that it seems to have a bug, and the Makefile.msvc needs to
rem be edited to remove a + from some lines.
rem Output: bin.msvc\libxml2_a.lib
cd libxml2-2.7.8
cd win32
cscript configure.js zlib=yes icu=yes debug=yes static=yes iconv=no include=..\..\icu\source\common;..\..\zlib-1.2.5
nmake -f Makefile.msvc libxmla
copy bin.msvc\libxml2_a.lib ..\..
cd ..
cd ..
rem libpng
rem Uses hardcoded zlib header path in makefile.vcwin32, edit as needed
rem Output: libpng.lib
cd lpng145
nmake -f scripts/makefile.vcwin32 libpng.lib
copy libpng.lib ..
cd ..
rem proj4
rem Make-based system
rem Output: proj.lib
cd proj-4.7.0
nmake -f makefile.vc
copy src\proj.lib ..
cd ..
rem libtiff
rem Make based
rem Output:
cd tiff-3.9.4
nmake -f Makefile.vc
copy libtiff\libtiff.lib ..
cd..
rem Back into root directory
cd ..

@ -1,27 +0,0 @@
<!-- Name: CamelCase -->
<!-- Version: 1 -->
<!-- Last-Modified: 2006/12/11 18:32:26 -->
<!-- Author: trac -->
# CamelCase
New words created by smashing together capitalized words.
CamelCase is the original wiki convention for creating hyperlinks, with the additional requirement that the capitals are followed by a lower-case letter; hence “AlabamA” and “ABc” will not be links.
## Customizing the Wiki behavior
Some people dislike linking by CamelCase. While Trac remains faithful to the original Wiki style, it provides a number of ways to accomodate users with different preferences:
* There's an option (`ignore_missing_pages` in `[wiki]`) to simply ignore links to missing pages when the link is written using the CamelCase style, instead of that word being replaced by a gray link followed by a question mark.[[BR]]
That can be useful when CamelCase style is used to name code artifacts like class names and there's no corresponding page for them.
* There's an option (`split_page_names` in `[wiki]`) to automatically insert space characters between the words of a CamelCase link when rendering the link.
* Creation of explicit Wiki links is also easy, see WikiPageNames for details.
* In addition, Wiki formatting can be disabled completely in some places (e.g. when rendering commit log messages)
See TracIni for more information on the available options.
## More information on CamelCase
* http://c2.com/cgi/wiki?WikiCase
* http://en.wikipedia.org/wiki/CamelCase
----
See also: WikiPageNames, WikiNewPage, WikiFormatting, TracWiki

@ -1,7 +0,0 @@
<!-- Name: DevFeature -->
<!-- Version: 1 -->
<!-- Last-Modified: 2010/10/05 11:23:25 -->
<!-- Author: springmeyer -->
#!html
<div style="border-style: solid;padding:5px;color:red;width:55%">Note: New feature in development.. help test beta snapshot here: <a href="http://trac.mapnik.org/wiki/Mapnik2">Mapnik2</a></div>

@ -1,11 +0,0 @@
<!-- Name: MapnikAdmin -->
<!-- Version: 1 -->
<!-- Last-Modified: 2009/12/16 12:44:16 -->
<!-- Author: springmeyer -->
When stuff breaks with trac...
error: 'No node trunk/bindings/python/mapnik_filter.cpp at revision 1495'
trac-admin mapnik_trac/ resync

@ -1,5 +0,0 @@
<!-- Name: OgcServer -->
<!-- Version: 16 -->
<!-- Last-Modified: 2010/11/22 10:08:09 -->
<!-- Author: springmeyer -->
See https://github.com/mapnik/OGCServer

@ -1,5 +0,0 @@
<!-- Name: OgcServerSvn -->
<!-- Version: 1 -->
<!-- Last-Modified: 2008/11/14 17:26:43 -->
<!-- Author: springmeyer -->
[[ReST(/trunk/docs/ogcserver/readme.txt)]]

@ -1,9 +0,0 @@
<!-- Name: SandBox -->
<!-- Version: 1 -->
<!-- Last-Modified: 2006/12/11 18:32:26 -->
<!-- Author: trac -->
# The Sandbox
This is just a page to practice and learn WikiFormatting.
Go ahead, edit it freely.

@ -1,55 +0,0 @@
<!-- Name: StableMergeQueue -->
<!-- Version: 36 -->
<!-- Last-Modified: 2008/09/24 13:04:33 -->
<!-- Author: springmeyer -->
Let's have a go at maintaining a stable series with consistent API.
This developer-oriented page is used to keep track of source code changes to be merged into the stable version of Mapnik.
* [change in trunk since 0.5.1](https://trac.mapnik.org/log/trunk?action=stop_on_copy&stop_rev=684&mode=stop_on_copy&verbose=on)
# Tickets with issues for stable
(reviewed up to #86)
* #81
* #87
* #92
* #94
# Direct commits to stable in 0.5.1
* [685]
# Commits to trunk which have been merged in 0.5.1
* [647]
* [653]
* [654]
* [661]
* [662]
* [672]
* [678]
* [679]
* [683]
# Commits to trunk which are merge candidates for stable
* [675] (but needs fixing - breaks text labels)
* [692], [693] (merge needs conflict fix)
* [698]
* [699]
* [700]
* [707]
* [708]
* [711]
* [712]
* [714]
* [718]
* [719]
* [720] (this temporarily breaks the cairo bindings, [726] fixes)
* [722]
* [723]
* [724]
(reviewed up to [724])

@ -10,7 +10,7 @@ Mapnik binaries can be installed and configured manually, or installed using OSG
If you are interested in installing Mapnik on other operating systems see: MapnikInstallation
If you an interested in compiling Mapnik from source on windows see: BuildingOnWindows
If you an interested in compiling Mapnik from source on windows see the windows scripts at https://github.com/mapnik/mapnik-packaging
## Supported Features

@ -1,7 +0,0 @@
<!-- Name: WindowsInstallation/Source -->
<!-- Version: 2 -->
<!-- Last-Modified: 2011/01/02 10:11:53 -->
<!-- Author: springmeyer -->
# Installing Mapnik and Dependencies from Source on Windows
TODO - if you have detailed build notes - even partial ones, please add here...