Hi,

I released V2.0 of the FreePascal Qt4 Binding.

http://users.telenet.be/Jan.Van.hijfte/qtforfpc/fpcqt4.html

There should not be any problems, because
none were reported for the RC releases :-)

The binding source in this release comes with a
qmake project that should ease compilation.

The new library name was chosen to better reflect the usage of the binding.

The target variable in the qmake project defines the library core name that results in the following platform names :

qmake target = Qt4Pas
qmake Version = 5.2.0
(5 from Qt4.*5* and 2.0 from binding 2.0) ->

* Windows : Qt4Pas5.dll
* Osx : Qt4Pas.framework
* Linux : libQt4Pas.so.5.2.0

Known bug:
compilation for embedded is not correctly auto-detected by qmake project. So edit qmake project and change DEFINES += $$PLATFORM line into DEFINES += QTOPIA.
Use the appropriate qmake spec. E.g.:
/qt-embedded-linux-opensource-src-4.5.3/bin/qmake -spec qws/linux-arm-g++ /qt-embedded-linux-opensource-src-4.5.3/bin/qmake -spec linux-g++

Once the Lazarus svn is updated, we should update the wikis. (use links to old wiki version to keep old explanation accessible)

Note that there is README.txt in lazarus/lcl/interfaces/qt/ that needs to be updated as well.

regards,

Den Jean

Den Jean wrote

I released V2.0 of the FreePascal Qt4 Binding.

tnx :)

There's one small thing which I always forgot to ask. Is there any way to know what qt version is used (I mean dinamically) ?

I think that qt have such macro, but don't know if it can be added to bindings ..

I'll give my best to update laz svn during weekend (one of qtlcl issues depends on new bindings, so have to test it).

Note that there is README.txt in lazarus/lcl/interfaces/qt/ that needs to be updated as well.

tnx.

zeljko

you wrote

Is there any way to know what qt version is used (I mean dinamically) ?

Added it for next version

I think that qt have such macro, but don't know if it can be added to bindings ..

using the macro would not be dynamically
(it would return the Qt version of Qt Lib when libQt4Pas was compiled), actually it is not a macro but a #define

qt source: qglobal.h
...
#define QT_VERSION_STR "4.5.3"
...
Q_CORE_EXPORT const char *qVersion();
...

I have added the qVersion flat function (because it is not a method of a class -> it was not added)

regards,

Den Jean

Den Jean wrote

On Wednesday 20 January 2010 08:20:12 you wrote: > Is there any way to know what qt version is used (I mean dinamically) ? Added it for next version

Ahh...why I didn't say that few days ago :)))

Yes, Q_CORE exported .... so qVersion will be available in 2.01 ?

tnx.

zeljko

Hello,

What about making the DLL link only to what is used?

I am considering using Qt for a Mac project, but it's a huge problem if the user needs my 2MB software + 163MB of the full Qt-Mac frameworks (without debug info) from
http://get.qt.nokia.com/qt/source/qt-mac-cocoa-opensource-4.6.1.dmg

While I only need QtCore and QtGUI

I propose a very easy way to implement this: Just put some IFDEFs to remove code when compiling the DLL, so that you can choose which frameworks to include in the library. And we could somehow include the define in the shell script to build the framework.

thanks,