I've mostly completed updating to qt 2.3.0. I've linked against the qt lib as
shipped in K3 since I can't for the life of me find my K3 Enterprise CD
anywhere. As far as I know, the CD is the only place to get Borland's QT
patches from. If either of you have your CD handy, can you email me the files
in the patch directory?
I decided against going straight to 2.3.2 for two reasons. One is that I want
our first file release to be as close to the CLX that is released with Kylix 3
as possible. The second reason is that I'm not by any means an expert on QT.
I know CLX pretty well, but only know the rudiments about QT. I'd rather not
break something subtly trying to go to 2.3.2 until we have a release under our
belts.
Chris, what's your take on the language in DEPLOY? I've received no
clarification from Borland, so I think we're on our own. I'm inclined to take
the DEPLOY file at its word and include the DBCLX and VISUALDB source files as
shipped with K3 and use them until/unless Borland hollers. Any objections to
this plan?
Once we have this done, I think we can create an alpha release. Hristo, this
is where you will come in. Once we have the Alpha, I'd like you to compile
and run every program you can get your hands on for Kylix and link against our
CLX. What would be nice is to try and pick programs that excersize as many
different parts of the CLX as possible. If you could start looking around for
good programs now, it would help.
Kurt.
|
