Windows binaries
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Poppler Python Bindings |
Confirmed
|
Medium
|
Unassigned |
Bug Description
There seems to be increased interest in Windows binaries, so it would be
great if they were officially maintained and released by the project, in
a similar fashion as PyGtk etc. windows versions are. For python-only
projects, it's rather tedious to set up a C toolchain just to getthe
poppler-python dependency fulfilled. As for the underlying poppler
dependency, maybe the poppler-dev* binaries from
ftp://ftp.
used?
(Personally, I'm working on a Windows port of Gourmet Recipe Manager --
http://
that requires poppler-python. Other apparently interested parties:
https:/
at http://
Update 2009-12-27:
I'll (ab)use this bug report for documenting my progress... If anyone feels like giving this a shot, feel free to add your helpful hints!
Windows build procedure for poppler-python:
1. Install prerequisites:
1a. Python (from python.org -- I'm using version 2.6)
1b. Gtk+ (use an up-to-date 2.16 (not 2.20, it's said to be buggy!) series development bundle as found in http://
1c. PyGtk (from pygtk.org, make sure to also install PyGObject and PyCairo from that website)
1d. poppler (poppler-
2. Get poppler-python ("pypoppler") sources from https:/
3. Setup msys.
3a. As their installer is lagging behind version-wise, get the "premade" bundle from http://
3b. It might be a good idea to link your User directory to msys's home. This is done by appending a line to C:\msys\
C:/Users/
(that's two tabstops in between)
4. Fix some flaws.
4a. To the top of pypoppler's configure.ac, add:
m4_pattern_
AC_CONFIG_
4b. To Makefile.am (after the line saying AUTOMAKE_
ACLOCAL_AMFLAGS=-I m4
4c. Paste pkg.m4 into pypoppler's ./m4/ directory (use eg the one from C:\GTK\
5. Configure paths
5a. Add your Gtk+ installation's /bin subdirectory to your PATH environment variable (eg from the Control Panel -> System -> Advanced System Settings -> Advanced -> Environment Variables)
5b. You need to tell pkg-config where to find the dependencies (via the corresponding .pc files), so open C:\msys\
export PKG_CONFIG_
export PATH=$PATH:
export CPPFLAGS=
export LDFLAGS+=" -L/c/Programme/
(if you installed python and gtk to a different location than C:\Program Files\Python26 and C:\GTK\, respectively, you'll need to adapt this line accordingly -- you get the idea how to encode paths for msys, right?)
5c. Follow comment #39 here: https:/
6. Configure and make
6a. Start C:\msys\
6b. cd to the pypoppler sources. If you followed steps 2 and 3b, that is just
cd ~/pypoppler-0.12.1
6c. autoreconf -i -f
6d. ./configure
6e. make
...and that's where I'm currently stuck.
(6f. would be: make install)
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
Great idea, any volunteers to maintain the Windows build? Bernhard, are you volunteering?