#4397: GeoDjango Documentation for Windows
-----------------------------------------------+----------------------------
   Reporter:  [EMAIL PROTECTED]              |                Owner:  jbronn  
     Status:  new                              |            Component:  GIS     
    Version:  other branch                     |           Resolution:          
   Keywords:  geodjango windows documentation  |                Stage:  Accepted
  Has_patch:  0                                |           Needs_docs:  0       
Needs_tests:  0                                |   Needs_better_patch:  0       
-----------------------------------------------+----------------------------
Changes (by jbronn):

 * cc: [EMAIL PROTECTED] (added)
  * summary:  GeoDjango dependencies on Windows => GeoDjango Documentation
              for Windows
  * owner:  jdunck => jbronn
  * version:  SVN => other branch
  * keywords:  => geodjango windows documentation
  * stage:  Unreviewed => Accepted

Comment:

 Yes, formal docs need to be written about the GeoDjango installation on
 Windows.  I also want to provide a "battery pack" of the needed Windows
 library binaries in a Zip file.  The GEOS library I used was the latest
 version (3.0.0RC4).  I obtained my libraries from the
 [http://www.postgis.org/news/20070319/ PostGIS Windows technology
 preview].  Specifically, copy {{{libgeos-3-0-0rc4.dll}}},
 {{{libgeos_c-1.dll}}}, and {{{libproj.dll}}} to your Python directory
 (e.g. {{{C:\Python25}}}).

-- 
Ticket URL: <http://code.djangoproject.com/ticket/4397#comment:3>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to