[Eric] Re: Simplified installation?

[techtonik]

Andreas Pakulat <apaku at ...> writes:

> First of all: This is the wrong list for this stuff, please use the pyqt
> mailinglist for things that are related to building pyqt.

I do not need neither Qt, nor PyQT - everything I need is to see if Eric is
better than PyDev. Considering the need to compile the code I thought that Eric
could need some specific PyQT build requirements, so compiling PyQT by
smb.elses' instructions could lead to problems similar to those I had trying to
run pygtk with GTK+ installed from GIMP for Windows package.

> Apart from that: MinGW only has gcc selected by default (IIRC), so you
> as well need to add g++ already.  Why is it a problem to also having to
> add make?

Because it wasn't mentioned anywhere.

> > 
> > Well, the last message was due to the absence of Qt4Core.dll in PATH.
> > Added it as well, but isn't it qmake what should have added it
> > automatically? 
> 
> No, why should qmake fiddle with your path? I don't know how the binary
> Qt package is laid out, but I guess its bin/ dir contains the dll's, so
> all you have to do is adding the bin/ dir to PATH (which is AFAIK what
> the Entry in the Qt/Trolltech menu does)

I've never used Qt up to this moment and learning it just to be able to use
Python editor is an overkill. I could add bin/ to PATH earlier when I run in
qmake.exe problem, but I was asked to specify path to qmake.exe explicitly via
cmdline parameters, so I could hope that it will find all the rest by itself.

> > Now the famous QMAKE_CFLAGS_THREAD. I doesn't seem that patching Qt4 is a
> > good idea, but there is no other choice so far.
> 
> Why is patching Qt4 not a good idea? Its the easiest workaround. You may
> of course also fix PyQt and send a patch to the pyqt mailinglist so Phil
> doesn't need to find the right way to handle this.

Because I haven't used to patching my developer's instruments like gcc or MinGW
to compile anything. Why do I need to know all the bloody unix/make/c++ details
if I program Python on windows? =/
 
> > At least I've managed to start compilation! Well, it took about 2 hours with
> > your hints. Good I've stumbled upon this group. Still waiting another 30
> > minutes to complete compilation.. I guess I have to check it tomorrow. 
> 
> Did you try the -c -j <num> flags? They increase compiling speed by
> large factors because mingw only has to compile n files not a couple
> dozens.

Noo, I haven't got this far yet, but if I ever decide to recompile everything
I'll follow your advice. =)
 
> > Thanks for support. Tomorrow I'll start with QScintilla and hopefully I
> > will see Eric by Wednesday. =)
> 
> I don't know what type of system you have, but the 1.5GHz AMD I have here
> for win32 took less than 2 hours to build and install PyQt, QScintilla
> and eric4.

Perhaps it was the matter of leaving the process in background. Finally it took
about an hour. The result of PyQt for Python 2.4 is here -
http://www2.turboshare.de/v/4688468/PyQt_gpl_4.2_Py2.4_Qt4.3.0.exe.html Since
J2EE it is the most lenghty process I've ever tried. =)
 
> Unfortunately I have to say that eric4 is close to unusable in parts on
> win32. The tree views are dead-slow on opening/closing branches, while
> they're fine in plain C++ apps and on linux.

I still would like to give it a try. PyDev is the only debugger I could use,
but it is too crippled.

WBR,
 anatoly t.