Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / lazarus / 2009-12

Win32 Qt dll version that works with Lazarus

12 messages · 4 people · –

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Luiz Americo Pereira Camara

Hi,

I'm trying to test the Qt Interface under win32.

I've got the intf binding (1.72) and QtCore.dll and QtGui.dll version 4.6.0 but i got an error loading the compiled app:

Original message (Brazillian)
"N?o foi poss?vel localizar o ponto de entrada do procedimento _ZN7QWidget17setAccessibleNameERK7QString na biblioteca de v?nculo din?mico QtGui4.dll."

Translate (Try)
"Could not find method entry point
_ZN7QWidget17setAccessibleNameERK7QString dynamic "something" QtGui4.dll."

Can someone point to a location where i can download a Lazarus compatible qt dll?

Using Lazarus 0.9.29 r22953 FPC 2.4.0 i386-win32-win32/win64

Luiz

Reply by email

zeljko
to Luiz Americo Pereira Camara
Luiz Americo Pereira Camara wrote 22 lines
Hi, I'm trying to test the Qt Interface under win32. I've got the intf binding (1.72) and QtCore.dll and QtGui.dll version 4.6.0 but i got an error loading the compiled app: Original message (Brazillian) "N?o foi poss?vel localizar o ponto de entrada do procedimento _ZN7QWidget17setAccessibleNameERK7QString na biblioteca de v?nculo din?mico QtGui4.dll." Translate (Try) "Could not find method entry point _ZN7QWidget17setAccessibleNameERK7QString dynamic "something" QtGui4.dll." Can someone point to a location where i can download a Lazarus compatible qt dll? Using Lazarus 0.9.29 r22953 FPC 2.4.0 i386-win32-win32/win64

I'm successfully using 4.6.0 and 1.72 dll.
QtCore.dll and QtGui.dll aren't enough.
You must have QtCore, QtGui, QtNetwork, QtWebKit, mingw10.dll, some_libc_.dll (cannot remember exact name now - not on windows), and I think that I'm using also QtXmlPatterns. Conclusion: you are missing some 4.6.0 dll or you have mismatched dll's (look at PATH env variables).

zeljko

Reply by email

Luiz Americo Pereira Camara
to zeljko
zeljko wrote 28 lines
On Sunday 06 December 2009 14:49, Luiz Americo Pereira Camara wrote: > Hi, > > I'm trying to test the Qt Interface under win32. > > I've got the intf binding (1.72) and QtCore.dll and QtGui.dll version > 4.6.0 but i got an error loading the compiled app: > > Original message (Brazillian) > "N?o foi poss?vel localizar o ponto de entrada do procedimento > _ZN7QWidget17setAccessibleNameERK7QString na biblioteca de v?nculo > din?mico QtGui4.dll." > > Translate (Try) > "Could not find method entry point > _ZN7QWidget17setAccessibleNameERK7QString dynamic "something" QtGui4.dll." > > > > Can someone point to a location where i can download a Lazarus > compatible qt dll? > > Using Lazarus 0.9.29 r22953 FPC 2.4.0 i386-win32-win32/win64 > I'm successfully using 4.6.0 and 1.72 dll.

Under win32?

QtCore.dll and QtGui.dll aren't enough. You must have QtCore, QtGui, QtNetwork, QtWebKit, mingw10.dll, some_libc_.dll (cannot remember exact name now - not on windows), and I think that I'm using also QtXmlPatterns.

QtWebKit is used (required) by LCL?

Conclusion: you are missing some 4.6.0 dll

The files that i have are QtCore, QtGui and mingw10. I found them in a program that uses Qt under win32. These are the only required files for that program and also for others programs based in Qt.

or you have mismatched dll's (look at PATH env variables).

I looked in the path and no conflict files

BTW: In Qt page i only found the option to download the entire dev files (>200MB). An overkill just to get the runtime files.

Luiz

Reply by email

Phil Hess
to Luiz Americo Pereira Camara

Yes, Webkit is used too, which drags in many of the other Qt libraries. QtGui and QtCore alone do not have any other dependencies on Qt libraries.

On Mac, the Qt4 frameworks are about 100MB. For Linux this may not be a problem if Qt comes pre-installed and is used by other apps, but it does seem a bit excessive on OS X and Windows.

Win API is a low-level C interface, but on Mac Cocoa is a high-level GUI framework. So that means high-level LCL wrapping high-level Qt wrapping high-level Cocoa.

Thanks.

-Phil

----- "Luiz Americo Pereira Camara" wrote 68 lines
zeljko escreveu: > On Sunday 06 December 2009 14:49, Luiz Americo Pereira Camara wrote: > >> Hi, >> >> I'm trying to test the Qt Interface under win32. >> >> I've got the intf binding (1.72) and QtCore.dll and QtGui.dll version >> 4.6.0 but i got an error loading the compiled app: >> >> Original message (Brazillian) >> "N?o foi poss?vel localizar o ponto de entrada do procedimento >> _ZN7QWidget17setAccessibleNameERK7QString na biblioteca de v?nculo >> din?mico QtGui4.dll." >> >> Translate (Try) >> "Could not find method entry point >> _ZN7QWidget17setAccessibleNameERK7QString dynamic "something" QtGui4.dll." >> >> >> >> Can someone point to a location where i can download a Lazarus >> compatible qt dll? >> >> Using Lazarus 0.9.29 r22953 FPC 2.4.0 i386-win32-win32/win64 >> > > I'm successfully using 4.6.0 and 1.72 dll. > Under win32? > QtCore.dll and QtGui.dll aren't enough. > You must have QtCore, QtGui, QtNetwork, QtWebKit, mingw10.dll, some_libc_.dll > (cannot remember exact name now - not on windows), and I think that I'm using > also QtXmlPatterns. QtWebKit is used (required) by LCL? > Conclusion: you are missing some 4.6.0 dll The files that i have are QtCore, QtGui and mingw10. I found them in a program that uses Qt under win32. These are the only required files for that program and also for others programs based in Qt. > or you have > mismatched dll's (look at PATH env variables). > I looked in the path and no conflict files BTW: In Qt page i only found the option to download the entire dev files (>200MB). An overkill just to get the runtime files. Luiz -- _______________________________________________ Lazarus mailing list http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Reply by email

Luiz Americo Pereira Camara
to Phil Hess
Phil Hess wrote
Yes, Webkit is used too, which drags in many of the other Qt libraries.

This (webkit support) could be provided as a separate package to minimize LCL-Qt requirements

QtGui and QtCore alone do not have any other dependencies on Qt libraries.

Most of win32 Qt applications i know use only those. Earlier, i thought that LCL-Qt/win32 requirement would be similar.

On Mac, the Qt4 frameworks are about 100MB. For Linux this may not be a problem if Qt comes pre-installed and is used by other apps, but it does seem a bit excessive on OS X and Windows.

It's sad. This can be an obstacle to Qt usage outside Linux

Win API is a low-level C interface, but on Mac Cocoa is a high-level GUI framework. So that means high-level LCL wrapping high-level Qt wrapping high-level Cocoa.

Good catch

Luiz

Reply by email

Phil Hess

I believe that originally only qtcore and qtgui were required for LCL-Qt, but the list has grown over time. Qt is starting to look like .NET/Mono in its all-encompassing, everything-but-the-kitchen-sink approach, as well as in its size (the entire Mono framework on OS X is only 200MB).

Thanks.

-Phil

----- "Luiz Americo Pereira Camara" wrote 36 lines
Phil Hess escreveu: > Yes, Webkit is used too, which drags in many of the other Qt libraries. This (webkit support) could be provided as a separate package to minimize LCL-Qt requirements > QtGui and QtCore alone do not have any other dependencies on Qt libraries. > Most of win32 Qt applications i know use only those. Earlier, i thought that LCL-Qt/win32 requirement would be similar. > On Mac, the Qt4 frameworks are about 100MB. For Linux this may not be a problem if Qt comes pre-installed and is used by other apps, but it does seem a bit excessive on OS X and Windows. > It's sad. This can be an obstacle to Qt usage outside Linux > Win API is a low-level C interface, but on Mac Cocoa is a high-level GUI framework. So that means high-level LCL wrapping high-level Qt wrapping high-level Cocoa. > Good catch Luiz -- _______________________________________________ Lazarus mailing list http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Reply by email

zeljko
to Phil Hess
Phil Hess wrote
I believe that originally only qtcore and qtgui were required for LCL-Qt, but the list has grown over time. Qt is starting to look like .NET/Mono in its all-encompassing, everything-but-the-kitchen-sink approach, as well as in its size (the entire Mono framework on OS X is only 200MB).

No it's not. Ppl. want webkit so that's the reason why we need QtNetwork + QtWekKit (instead of QtCore + QtGui).
There was already some questions about splitting C bindings into it's packages so:
libqt4intf-core is for QtCore
libqt4intf-gui is for QtGui
libqt4intf-network is for QtNetwork
etc etc
That will fix problems and I would like it so, but who will make such C bindings (for all lcl supported platforms !) ? Any volonteers here ? ;)

zeljko

Reply by email

zeljko
to Luiz Americo Pereira Camara: Under win32? QtWebKit is used (required) by LCL? The files that i have are QtCore, QtGui …
Luiz Americo Pereira Camara wrote
Under win32?

Yes, winXP SP2

Show quoted text 7 lines
> QtCore.dll and QtGui.dll aren't enough. > You must have QtCore, QtGui, QtNetwork, QtWebKit, mingw10.dll, > some_libc_.dll (cannot remember exact name now - not on windows), and I > think that I'm using also QtXmlPatterns. QtWebKit is used (required) by LCL?

Yes

Show quoted text 6 lines
> Conclusion: you are missing some 4.6.0 dll The files that i have are QtCore, QtGui and mingw10. I found them in a program that uses Qt under win32. These are the only required files for that program and also for others programs based in Qt.

That's not enough with bindings 1.72.

Show quoted text 8 lines
> or you have > mismatched dll's (look at PATH env variables). I looked in the path and no conflict files BTW: In Qt page i only found the option to download the entire dev files (>200MB). An overkill just to get the runtime files.

well, I cannot help you here :)

zeljko

Reply by email

Felipe Monteiro de Carvalho
to zeljko
zeljko wrote
> What is it used for in the LCL? for nothing, but it's in bindings (QWebPage, QNetworkXXX etc)

Then it's pretty clear that it would be a good idea to split the binding dll.

Den Jean?

Felipe Monteiro de Carvalho

Reply by email

zeljko
to Felipe Monteiro de Carvalho
Felipe Monteiro de Carvalho wrote 9 lines
On Mon, Dec 7, 2009 at 5:15 AM, zeljko wrote: >> What is it used for in the LCL? > > for nothing, but it's in bindings (QWebPage, QNetworkXXX etc) Then it's pretty clear that it would be a good idea to split the binding dll. Den Jean?

But if there will be any splitting, then core & gui should be splitted too (in separate dll's , so's or dylib's ... whatever).

Reply by email