On Nov 15, 2008, at 12:01 PM, Martin Dobias wrote:
Victory!
I patched SIP to compile as a bundle, with no direct link to Python.
Rebuild PyQt and it followed. Rebuild Qgis, and the qgis-python
modules
are also now correct.
Then, changed libqgispython to drop the full path to Python binary
On Sat, Nov 15, 2008 at 5:03 AM, William Kyngesburye
[EMAIL PROTECTED] wrote:
On Nov 14, 2008, at 7:04 PM, William Kyngesburye wrote:
Hmmm... A possibility: compile and link statically as Qgis does now, use
install_name_tool to change the python link to drop the path (this is how
the Qt
On Fri, Nov 14, 2008 at 3:35 AM, William Kyngesburye
[EMAIL PROTECTED] wrote:
It would be nice if PyQt/SIP and Qgis properly linked to python (I think
Qgis takes its cue from SIP), then it would be easier to switch between the
system python 2.5 and python.org 2.5.
William,
do you have any
On Nov 14, 2008, at 4:41 AM, Martin Dobias wrote:
On Fri, Nov 14, 2008 at 3:35 AM, William Kyngesburye
[EMAIL PROTECTED] wrote:
It would be nice if PyQt/SIP and Qgis properly linked to python (I
think
Qgis takes its cue from SIP), then it would be easier to switch
between the
system
On Nov 14, 2008, at 9:18 AM, William Kyngesburye wrote:
do you have any ideas how to improve the situation of QGIS python
support on OS X?
I don't know much about specifics of OS X but we could tweak python
support with your assistence if you describe what's going wrong.
Martin
I think we're
On Nov 14, 2008, at 10:20 AM, William Kyngesburye wrote:
Hmm, I started poking around more... Where DOES Qgis get its python
compile flags from?
sipconfig.py:class ModuleMakefile(Makefile)
My python/core/makefile has:
LFLAGS = -headerpad_max_install_names -bundle -F/System/Library/
On Nov 14, 2008, at 11:07 AM, Martin Dobias wrote:
Am I right that the problem applies only to bindings (based on
SIP/PyQt4), while implementation of embedded python (libqgispython) is
okay?
Ah, there's a tricky one. Is libqgispython meant to be a library,
linked by other plugins or the
On Nov 14, 2008, at 3:58 PM, Martin Dobias wrote:
libqgispython is meant to be loaded dynamically by QGIS application on
startup. All python-related implementation is in this library, the
rest of application is python-free, i.e. it doesn't use any
functions directly from python libs.
On Nov 14, 2008, at 5:03 PM, Martin Dobias wrote:
So now the question is (and something I've wondered about) - just
how does
this python support work? Does it execute the python program (as
found in
the user's PATH)? Does it depend on linking to the python library
to find
some python
On Nov 14, 2008, at 7:04 PM, William Kyngesburye wrote:
Hmmm... A possibility: compile and link statically as Qgis does
now, use install_name_tool to change the python link to drop the
path (this is how the Qt frameworks are initially). The linker at
runtime then will use
I am unable to run QGIS 1.0 Preview 2 because the application quits
out before completely launching.
Numerous messages are left behind in the Console.
11/13/08 7:43:08 PM [0x0-0x1f01f].org.qgis.qgis[273] Warning:
Object::connect: No such slot QgsComposer::undo()
11/13/08 7:43:08 PM
On Nov 13, 2008, at 7:55 PM, Dan Dittmann wrote:
11/13/08 7:43:08 PM [0x0-0x1f01f].org.qgis.qgis[273] Warning:
Object::connect: (receiver name: 'QgsComposerBase')
11/13/08 7:43:08 PM [0x0-0x1f01f].org.qgis.qgis[273] Fatal Python
error: Interpreter not initialized (version mismatch?)
The
On Nov 13, 2008, at 8:35 PM, William Kyngesburye wrote:
On Nov 13, 2008, at 7:55 PM, Dan Dittmann wrote:
11/13/08 7:43:08 PM [0x0-0x1f01f].org.qgis.qgis[273] Warning:
Object::connect: (receiver name: 'QgsComposerBase')
11/13/08 7:43:08 PM [0x0-0x1f01f].org.qgis.qgis[273] Fatal Python
13 matches
Mail list logo