around qt lib and c++. this shouldn't normally be a problem, but
given the mess of c++/rtp6.1, i will just shy away from it. there
are more qualified people in this group than me, hope someone
can do it. rumors said someone from qssl already had kde/kdeveloper
I am still scratching my head on the ddd port. no surprise it is
written in c++. see my posts in the "qdn.public.qnxrtp.devtools" group...
On Sat, 13 Oct 2001, Miguel Simon wrote:
I see your port now. Great work! Thanks.
I wonder if you are thinking about porting KDevelop? Would this be a
difficult task? Has someone done this before?
Also, where you successful in porting ddd with your XFree86 4.1 port?
Frank Liu wrote:
ok, it is up there now.
any quesitons, please join the mailing list at
http://lists.sourceforge.net/lists/list ... -developer
On Sat, 13 Oct 2001, Armin wrote:
David Alessio wrote:
I don't know exactly what the problem was, but if I adjust Armin's
procedure, it works for me. I even have Tkinter working (on 8.3.2) with
most of Guido's and Matt's demos.
Now if we can only get XPhoton fixed, it'd stay up longer...
Hmmm ... add the neccessary X server, libs a.s.o to the X11R6
directories of XPhoton and you can run XFree86 if you have a
critical X application. (~ 2-3 MB of binaries ... )
BTW ... the port of XFree86 version 4.1 available at
Big thanks to Frank !!
Sorry ... too early. Version 4.1 will be available in a short time
David Alessio wrote:
This compiles and Python comes up, but
fails with a SIGSEGV three calls into libc from dlopen("math.so",
RTLD_NOW) in dynload_shlib.c
Does anyone else have this problem? Any ideas?
Armin Steinhoff wrote:
the port of Python 2.1.1 can to be done with the following steps:
1) install the Python archive at /
then do the export cmds: export PYTHONPATH=/Python-2.1.1 ,
2) copy all *.py files from /Python-2.1.1/Lib to
(there is a curious fault in the UNIX distribution..)
Don't do the copy, instead, use a link:
2) cd /Python-2.1.1
ln -s /Python-2.1.1/Lib lib/python2.1
Yes ... of course that's better
3) configure: CC=qcc LDFLAGS=-Wl,-E CCSHARED="-shared -fPIC"
CFLAGSFORSHARED="-shared -fPIC" LDSHARED="qcc -shared"
BLDSHARED="qcc -shared" ./configure --with-threads
(in ONE cmd line ..)
4.5) You will now have a directory something like this:
Create a link Lib/lib-dynload that points to this directory:
ln -s /Python-2.1.1/build/lib.qnx-6.1.0-x86pc-2.1 Lib/lib-dynload
I will 'repare' in the next days the 'getpath' module ... so that
configure and make are only neccessary to build python 2.1.1
5) make install
6) export cmds: export PYTHONPATH=/usr/local/lib/python2.1
Hmmm, I don't need these.
At least one of them should be set .. IMHO
7) copy all shared objects from $PYTHONPATH/lib-dynload to
$PYTHONPATH/lib/python2.1 (as you know ... there is a curious
I didn't need to do this. I think this is necessary only if the Env
Vars are defined in (6)
my opinions are mine, only mine, solely mine, and they are not related
in any possible way to the institution(s) in which I study and work.
School of Aerospace and Mechanical Engineering
University of Oklahoma