[prev in list] [next in list] [prev in thread] [next in thread] 

List:       pykde
Subject:    Re: [PyKDE] undefined symbol: QPrinter::setPrintRange
From:       "Patrick Stinson" <patrickkidd.lists () gmail ! com>
Date:       2006-05-23 16:27:55
Message-ID: 664bf2b80605230927va16dc56v3a0e47e445d559e0 () mail ! gmail ! com
[Download RAW message or body]

gcc -framework whatever reports undefined symbols at the compile-time
intermediate linking phase. gcc -lwhatever does not.

See my previous post about run-time and compile-time linking.

When you import a module, it links the PyQt4 module with your qt4
libs. According to your trolltech announcement it is no suprise that
any shared library using those two functions (like PyQt4) will compile
correctly and fail on linking (like __import__('PyQt4')).


On 5/23/06, Andreas Pakulat <apaku@gmx.de> wrote:
> On 22.05.06 20:52:28, Patrick Stinson wrote:
> > Didn't you say that my example code didn't work for you? Any code that
> > uses that function should not link with the library in question.
>
> You're missing my point: Why does PyQt4 compilation fail for you, but
> not for me. Judging from a quick look at your first message, I guess
> it's du to different gcc on a different OS. That's all I wanted to know.
>
> Andreas
>
> --
> Don't read any sky-writing for the next two weeks.
>
> _______________________________________________
> PyKDE mailing list    PyKDE@mats.imk.fraunhofer.de
> http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
>


-- 
Patrick Kidd Stinson
http://www.patrickkidd.com/
http://pkaudio.sourceforge.net/
http://pksampler.sourceforge.net/

_______________________________________________
PyKDE mailing list    PyKDE@mats.imk.fraunhofer.de
http://mats.imk.fraunhofer.de/mailman/listinfo/pykde

[prev in list] [next in list] [prev in thread] [next in thread]