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.
On 5/22/06, Andreas Pakulat <[EMAIL PROTECTED]> wrote:
On 22.05.06 16:33:04, Patrick Stinson wrote:
> This happens because when you link objects into an executa
On 22.05.06 16:33:04, Patrick Stinson wrote:
> This happens because when you link objects into an executable, it
> links all the functions used in your program (setPrintRange in my
> example) to their implementations. If the trolltech build left out the
> implementation of setPrintRage, the linker
This falls into basic compiler/linker theory.
This happens because when you link objects into an executable, it
links all the functions used in your program (setPrintRange in my
example) to their implementations. If the trolltech build left out the
implementation of setPrintRage, the linker will
On 22.05.06 14:36:54, Patrick Stinson wrote:
> On 5/22/06, Patrick Stinson <[EMAIL PROTECTED]> wrote:
> >Hmm. I don't find PyQt4 to even come into the picture here, as the
> >following code shows the same error whne compiled w/o qt3 support.
Well, my gcc is happily linking PyQt4 against the Qt4 wi
On 5/22/06, Andreas Pakulat <[EMAIL PROTECTED]> wrote:
On 22.05.06 22:40:44, Phil Thompson wrote:
> On Monday 22 May 2006 9:48 pm, Andreas Pakulat wrote:
> > On 22.05.06 12:16:03, Patrick Stinson wrote:
> > > yeah, this is TrollTech's problem. I find it hard to imagine that a
> > > stitch like -n
On 22.05.06 22:40:44, Phil Thompson wrote:
> On Monday 22 May 2006 9:48 pm, Andreas Pakulat wrote:
> > On 22.05.06 12:16:03, Patrick Stinson wrote:
> > > yeah, this is TrollTech's problem. I find it hard to imagine that a
> > > stitch like -no-qt3support is broken in this ehemm...bugfix release.
>
On 5/22/06, Patrick Stinson <[EMAIL PROTECTED]> wrote:
Hmm. I don't find PyQt4 to even come into the picture here, as the
following code shows the same error whne compiled w/o qt3 support. I'm
just sticking with a full build for now.
int main()
{
QPrinter *p;
p->setPrintRange(QPrinter::AllPa
On Monday 22 May 2006 9:48 pm, Andreas Pakulat wrote:
> On 22.05.06 12:16:03, Patrick Stinson wrote:
> > yeah, this is TrollTech's problem. I find it hard to imagine that a
> > stitch like -no-qt3support is broken in this ehemm...bugfix release.
>
> Well, this is just an "oversight", however it's o
On 22.05.06 22:43:53, Sundance wrote:
> I heard Andreas Pakulat said:
>
> > > The last project should be the topmost entry.
> >
> > Seems I should've added: automatically upon startup :-)
>
> Please don't! :) Some can have several ongoing projects at once and
> don't necessarily want to work on
On 22.05.06 12:16:03, Patrick Stinson wrote:
> yeah, this is TrollTech's problem. I find it hard to imagine that a
> stitch like -no-qt3support is broken in this ehemm...bugfix release.
Well, this is just an "oversight", however it's one with a rather large
impact. There are other "oversights" fou
I heard Andreas Pakulat said:
> > The last project should be the topmost entry.
>
> Seems I should've added: automatically upon startup :-)
Please don't! :) Some can have several ongoing projects at once and
don't necessarily want to work on the last one opened when they fire up
Eric3.
However
yeah, this is TrollTech's problem. I find it hard to imagine that a
stitch like -no-qt3support is broken in this ehemm...bugfix release.
On 5/22/06, Andreas Pakulat <[EMAIL PROTECTED]> wrote:
On 22.05.06 10:50:45, Patrick Stinson wrote:
> qt-4.1.3 configured with "-release -qt-gif -no-qt3support
On 22.05.06 10:50:45, Patrick Stinson wrote:
> qt-4.1.3 configured with "-release -qt-gif -no-qt3support"
>
> c++ -c -pipe -fPIC -Os -Wall -W -DQT_NO_DEBUG -DQT_GUI_LIB
> -DQT_CORE_LIB -I.
> -I/System/Library/Frameworks/Python.framework/Versions/2.3/include/python2.3
> -I/usr/local/Trolltech/Qt-4.
qt-4.1.3 configured with "-release -qt-gif -no-qt3support"
c++ -c -pipe -fPIC -Os -Wall -W -DQT_NO_DEBUG -DQT_GUI_LIB
-DQT_CORE_LIB -I.
-I/System/Library/Frameworks/Python.framework/Versions/2.3/include/python2.3
-I/usr/local/Trolltech/Qt-4.1.3/mkspecs/default
-I/usr/local/Trolltech/Qt-4.1.3/incl
On 22.05.06 18:22:16, Detlev Offenbach wrote:
> Am Montag, 22. Mai 2006 01:15 schrieb Andreas Pakulat:
> > Hi,
> >
> > not sure wether this existed in earlier versions or maybe I'm just
> > overlooking something:
> >
> > Is there a way with eric 3.9.0 to reopen the project that was opened
> > when
Am Montag, 22. Mai 2006 01:15 schrieb Andreas Pakulat:
> Hi,
>
> not sure wether this existed in earlier versions or maybe I'm just
> overlooking something:
>
> Is there a way with eric 3.9.0 to reopen the project that was opened
> when I closed eric3?
>
> Andreas
Project menu -> Open Recent Proje
Hi,
I have no difficulties building and using Qt 3.3.6 with PyQt in a
Mac(intel), but when I try to use py2app to get a "distributable" file I
get errors of the type:
import qt
incorrect file type
The non distributable scripts run without problems in the machine.
I guess my problem is due
17 matches
Mail list logo