QCA2 build problems under win32-msvc2008/Qt4.4

Hi,

I'm struggling to build a copy of QCA2 with the openssl
plugin under
the latest version of visual studio, and the Qt 4.4
pre-release code.

I've got a successful build working under linux so far, but
the
windows one is causing me trouble. Following the
instructions in the
respective INSTALL files, I've got both qca-2.0.0 and
qca-ossl-2.0.0-beta3 build successfully producing qcatool2
and the
qca-ossl2.dll files. I've moved them to the Qt directory.

qcatool shows no available providers, despite showing the
correct search paths.

I've single-stepped through the QPluginLoader source, and
its bailing
out while trying to find the
qt_plugin_query_verification_data symbol
and concludes the ossl dll is not a valid Qt plugin.

Is this a known issue or bug with QCA? Is building it in
this way
supported at all, or am I trying to do something that just
isn't
possible?

Any response would be greatly appreciated; if QCA can't be
made to
work I'll need to find an alternative asap.

Thanks,

Ben Roberts.
Electronics and Computer Science,
University of Southampton.
_______________________________________________
Delta mailing list
Deltalists.affinix.com
http://lists.affinix.com/listinfo.cgi/delta-affinix.com

Fraid so, no joy.
My single stepping shows me touching the ossl dlls makes Qt
recheck
them, however they are still definitely failing to load.

Oh, and I added a brief mod to the qca source to print out
the
QPluginLoader errorString() along with the failed to load
message,
which is shown below.

C:Program FilesMicrosoft SDKsWindowsv6.1>echo %PATH%
C:Program FilesMicrosoft Visual Studio
9.0VCBin;C:Program FilesMicrosoft V
isual Studio 9.0VCvcpackages;C:Program FilesMicrosoft
Visual Studio 9.0Comm
on7IDE;C:Program FilesMicrosoft
SDKsWindowsv6.1Bin;C:WindowsMicrosoft.NE
TFrameworkv3.5;C:WindowsMicrosoft.NETFrameworkv2.0.507
27;c:bin;c:binbin
;c:binusrlocalwbin;C:Perlsitebin;C:Perlbin;C:Progr
am FilesMicrosoft D
irectX SDK (November
2007)UtilitiesBinx86;C:Windowssystem32;C:Windows;C:W
indowsSystem32Wbem;c:qt4.4.0-beta1bin;c:buildbin

C:Program FilesMicrosoft SDKsWindowsv6.1>ls
c:buildbin
libeay32.dll  ssleay32.dll

C:Program FilesMicrosoft
SDKsWindowsv6.1>Qtqca-2.0.0binqcatool2.exe --de
bug plugins
Qt Library Paths:
  C:/Qt/4.4.0-beta1/plugins
  C:/Qt/qca-2.0.0/bin
plugin: checking in path: [C:/Qt/4.4.0-beta1/plugins]
plugin: checking file:
[C:/Qt/4.4.0-beta1/plugins/crypto/qca-ossl2.dll]
plugin: PluginInstance fromFile
[C:/Qt/4.4.0-beta1/plugins/crypto/qca-ossl2.dll]

plugin: failed to load: The file
'C:/Qt/4.4.0-beta1/plugins/crypto/qca-ossl2.dll
' is not a valid Qt plugin.
plugin: checking file:
[C:/Qt/4.4.0-beta1/plugins/crypto/qca-ossld2.dll]
plugin: PluginInstance fromFile
[C:/Qt/4.4.0-beta1/plugins/crypto/qca-ossld2.dll
]
plugin: failed to load: The file
'C:/Qt/4.4.0-beta1/plugins/crypto/qca-ossld2.dl
l' is not a valid Qt plugin.
plugin: checking in path: [C:/Qt/qca-2.0.0/bin]
Available Providers:
  (none)

On 16/03/2008, Norman Rasmussen <normanrasmussen.co.za> wrote:
> Are openssl's libeay32 and ssleay32 dll's findable in
the current folder
> and/or path env?
> If they're not then the openssl qca plugin fails to
load.
> This failure is generally cached in the registry too,
so you need to clean
> that out for Qt to re-detect the openssl provider.
>
>
> On Sun, Mar 16, 2008 at 9:30 PM, optimism_
<optiz0rgmail.com> wrote:
> >
> > Hi,
> >
> > I'm struggling to build a copy of QCA2 with the
openssl plugin under
> > the latest version of visual studio, and the Qt
4.4 pre-release code.
> >
> > I've got a successful build working under linux so
far, but the
> > windows one is causing me trouble. Following the
instructions in the
> > respective INSTALL files, I've got both qca-2.0.0
and
> > qca-ossl-2.0.0-beta3 build successfully producing
qcatool2 and the
> > qca-ossl2.dll files. I've moved them to the Qt
directory.
> >
> > qcatool shows no available providers, despite
showing the correct search
> paths.
> >
> > I've single-stepped through the QPluginLoader
source, and its bailing
> > out while trying to find the
> qt_plugin_query_verification_data symbol
> > and concludes the ossl dll is not a valid Qt
plugin.
> >
> > Is this a known issue or bug with QCA? Is building
it in this way
> > supported at all, or am I trying to do something
that just isn't
> > possible?
> >
> > Any response would be greatly appreciated; if QCA
can't be made to
> > work I'll need to find an alternative asap.
> >
> > Thanks,
> >
> > Ben Roberts.
> > Electronics and Computer Science,
> > University of Southampton.
> > _______________________________________________
> > Delta mailing list
> > Deltalists.affinix.com
> > http://lists.affinix.com/listinfo.cgi/delta-affinix.com
> >
>
>
>
> --
> - Norman Rasmussen
>  - Email: normanrasmussen.co.za
>  - Home page: http://norman.rasmusse
n.co.za/
> _______________________________________________
>  Delta mailing list
>  Deltalists.affinix.com
> http://lists.affinix.com/listinfo.cgi/delta-affinix.com
>
>
_______________________________________________
Delta mailing list
Deltalists.affinix.com
http://lists.affinix.com/listinfo.cgi/delta-affinix.com

The dumpbin tool seems to be looking for a missing dll, and
crashing
on my system. The Dependency walker tool also lists exported
functions
however, and the very big list does not include the above
methods. the
only qt_ prefixed methods listed in the exports list are
qt_metacast
and qt_metacalls...

On 17/03/2008, Norman Rasmussen <normanrasmussen.co.za> wrote:
> Hrm, the latest I've tried to compile is 4.3.4.   It is
possible that Qt
> have broken the plugin loading on 4.4.0-beta1 I guess.
>
> Double check that the functions are exported correctly
with dumpbin perhaps?
>
>  > dumpbin /exports
C:Qt4.4.0-beta1pluginscrypto*.dll
> | find /i "plugin"
>           1    0 000016C7 qt_plugin_instance =
> ILT+1730(_qt_plugin_instance)
>           2    1 000014F1
qt_plugin_query_verification_data
> = ILT+1260(_qt_plugin_query_verification_data)
>            1    0 000019FB qt_plugin_instance =
> ILT+2550(_qt_plugin_instance)
>           2    1 000016FE
qt_plugin_query_verification_data
> = ILT+1785(_qt_plugin_query_verification_data)
>
> is what is shown for my Qt 4.3.4 openssl + gnupg
plugins.
>
>
> On Mon, Mar 17, 2008 at 12:31 AM, optimism_
<optiz0rgmail.com> wrote:
> > Fraid so, no joy.
> > My single stepping shows me touching the ossl dlls
makes Qt recheck
> > them, however they are still definitely failing to
load.
> >
> > Oh, and I added a brief mod to the qca source to
print out the
> > QPluginLoader errorString() along with the failed
to load message,
> > which is shown below.
> >
> > C:Program FilesMicrosoft
SDKsWindowsv6.1>echo %PATH%
> > C:Program FilesMicrosoft Visual Studio
9.0VCBin;C:Program
> FilesMicrosoft V
> > isual Studio 9.0VCvcpackages;C:Program
FilesMicrosoft Visual Studio
> 9.0Comm
> > on7IDE;C:Program FilesMicrosoft
> SDKsWindowsv6.1Bin;C:WindowsMicrosoft.NE
> >
>
TFrameworkv3.5;C:WindowsMicrosoft.NETFrameworkv2.0.507
27;c:bin;c:binbin
> >
>
;c:binusrlocalwbin;C:Perlsitebin;C:Perlbin;C:Progr
am
> FilesMicrosoft D
> > irectX SDK (November
>
2007)UtilitiesBinx86;C:Windowssystem32;C:Windows;C:W
> >
indowsSystem32Wbem;c:qt4.4.0-beta1bin;c:buildbin
> >
> > C:Program FilesMicrosoft SDKsWindowsv6.1>ls
c:buildbin
> > libeay32.dll  ssleay32.dll
> >
> > C:Program FilesMicrosoft
> SDKsWindowsv6.1>Qtqca-2.0.0binqcatool2.exe
--de
> > bug plugins
> > Qt Library Paths:
> >  C:/Qt/4.4.0-beta1/plugins
> >  C:/Qt/qca-2.0.0/bin
> > plugin: checking in path:
[C:/Qt/4.4.0-beta1/plugins]
> > plugin: checking file:
> [C:/Qt/4.4.0-beta1/plugins/crypto/qca-ossl2.dll]
> > plugin: PluginInstance fromFile
> [C:/Qt/4.4.0-beta1/plugins/crypto/qca-ossl2.dll]
> >
> > plugin: failed to load: The file
> 'C:/Qt/4.4.0-beta1/plugins/crypto/qca-ossl2.dll
> >
> > ' is not a valid Qt plugin.
> > plugin: checking file:
> [C:/Qt/4.4.0-beta1/plugins/crypto/qca-ossld2.dll]
> > plugin: PluginInstance fromFile
> [C:/Qt/4.4.0-beta1/plugins/crypto/qca-ossld2.dll
> > ]
> > plugin: failed to load: The file
> 'C:/Qt/4.4.0-beta1/plugins/crypto/qca-ossld2.dl
> > l' is not a valid Qt plugin.
> > plugin: checking in path: [C:/Qt/qca-2.0.0/bin]
> > Available Providers:
> >  (none)
> >
> >
> >
> >
> > On 16/03/2008, Norman Rasmussen <normanrasmussen.co.za> wrote:
> > > Are openssl's libeay32 and ssleay32 dll's
findable in the current folder
> > > and/or path env?
> > > If they're not then the openssl qca plugin
fails to load.
> > > This failure is generally cached in the
registry too, so you need to
> clean
> > > that out for Qt to re-detect the openssl
provider.
> > >
> > >
> > > On Sun, Mar 16, 2008 at 9:30 PM, optimism_
<optiz0rgmail.com> wrote:
> > > >
> > > > Hi,
> > > >
> > > > I'm struggling to build a copy of QCA2
with the openssl plugin under
> > > > the latest version of visual studio, and
the Qt 4.4 pre-release code.
> > > >
> > > > I've got a successful build working
under linux so far, but the
> > > > windows one is causing me trouble.
Following the instructions in the
> > > > respective INSTALL files, I've got both
qca-2.0.0 and
> > > > qca-ossl-2.0.0-beta3 build successfully
producing qcatool2 and the
> > > > qca-ossl2.dll files. I've moved them to
the Qt directory.
> > > >
> > > > qcatool shows no available providers,
despite showing the correct
> search
> > > paths.
> > > >
> > > > I've single-stepped through the
QPluginLoader source, and its bailing
> > > > out while trying to find the
> > > qt_plugin_query_verification_data symbol
> > > > and concludes the ossl dll is not a
valid Qt plugin.
> > > >
> > > > Is this a known issue or bug with QCA?
Is building it in this way
> > > > supported at all, or am I trying to do
something that just isn't
> > > > possible?
> > > >
> > > > Any response would be greatly
appreciated; if QCA can't be made to
> > > > work I'll need to find an alternative
asap.
> > > >
> > > > Thanks,
> > > >
> > > > Ben Roberts.
> > > > Electronics and Computer Science,
> > > > University of Southampton.
> > > >
_______________________________________________
> > > > Delta mailing list
> > > > Deltalists.affinix.com
> > > >
> http://lists.affinix.com/listinfo.cgi/delta-affinix.com
> > > >
> > >
> > >
> > >
> > > --
> > > - Norman Rasmussen
> > >  - Email: normanrasmussen.co.za
> > >  - Home page: http://norman.rasmusse
n.co.za/
> > >
_______________________________________________
> > >  Delta mailing list
> > >  Deltalists.affinix.com
> > > http://lists.affinix.com/listinfo.cgi/delta-affinix.com
> > >
> > >
> > _______________________________________________
> > Delta mailing list
> > Deltalists.affinix.com
> > http://lists.affinix.com/listinfo.cgi/delta-affinix.com
> >
>
>
>
> --
> - Norman Rasmussen
>  - Email: normanrasmussen.co.za
>  - Home page: http://norman.rasmusse
n.co.za/
> _______________________________________________
>  Delta mailing list
>  Deltalists.affinix.com
> http://lists.affinix.com/listinfo.cgi/delta-affinix.com
>
>
_______________________________________________
Delta mailing list
Deltalists.affinix.com
http://lists.affinix.com/listinfo.cgi/delta-affinix.com

Ah, yes running it from inside the vc command prompt makes
it find the
missing dll. Should have thought of that. Yes i get similar
output to
you, then.

C:Program FilesMicrosoft Visual Studio
9.0VCbin>dumpbin /exports C:Qt4.4.0
-beta1pluginscrypto*.dll | grep plugin
Dump of file C:Qt4.4.0-beta1pluginscryptoqca-ossl2.dll
          1    0 0000BC90 qt_plugin_instance
          2    1 00001CB0 qt_plugin_query_verification_data
Dump of file
C:Qt4.4.0-beta1pluginscryptoqca-ossld2.dll
          1    0 000019D8 qt_plugin_instance = ILT+2515(_qt_plugin_instance)
          2    1 000016E0 qt_plugin_query_verification_data
=
ILT+1755(_qt_plugin_query_verification_data)


On 17/03/2008, Norman Rasmussen <normanrasmussen.co.za> wrote:
> I think the dependency walker will show imports, not
exports, so that would
> be why the list is different.
>
> The dumpbin tool should work without any issues, if it
doesn't then it's
> possible that something else is broken.  (Are you
running it from the
> 'visual studio 2008 command prompt'? or do you not have
that?)
>
>
> On Mon, Mar 17, 2008 at 12:01 PM, optimism_
<optiz0rgmail.com> wrote:
> > The dumpbin tool seems to be looking for a missing
dll, and crashing
> > on my system. The Dependency walker tool also
lists exported functions
> > however, and the very big list does not include
the above methods. the
> > only qt_ prefixed methods listed in the exports
list are qt_metacast
> > and qt_metacalls...
> >
> >
> >
> >
> > On 17/03/2008, Norman Rasmussen <normanrasmussen.co.za> wrote:
> > > Hrm, the latest I've tried to compile is
4.3.4.   It is possible that Qt
> > > have broken the plugin loading on 4.4.0-beta1
I guess.
> > >
> > > Double check that the functions are exported
correctly with dumpbin
> perhaps?
> > >
> > >  > dumpbin /exports
> C:Qt4.4.0-beta1pluginscrypto*.dll
> > > | find /i "plugin"
> > >           1    0 000016C7 qt_plugin_instance
=
> > > ILT+1730(_qt_plugin_instance)
> > >           2    1 000014F1
> qt_plugin_query_verification_data
> > > = ILT+1260(_qt_plugin_query_verification_data)
> > >            1    0 000019FB qt_plugin_instance
=
> > > ILT+2550(_qt_plugin_instance)
> > >           2    1 000016FE
> qt_plugin_query_verification_data
> > > = ILT+1785(_qt_plugin_query_verification_data)
> > >
> > > is what is shown for my Qt 4.3.4 openssl +
gnupg plugins.
> > >
> > >
> > > On Mon, Mar 17, 2008 at 12:31 AM, optimism_
<optiz0rgmail.com> wrote:
> > > > Fraid so, no joy.
> > > > My single stepping shows me touching the
ossl dlls makes Qt recheck
> > > > them, however they are still definitely
failing to load.
> > > >
> > > > Oh, and I added a brief mod to the qca
source to print out the
> > > > QPluginLoader errorString() along with
the failed to load message,
> > > > which is shown below.
> > > >
> > > > C:Program FilesMicrosoft
SDKsWindowsv6.1>echo %PATH%
> > > > C:Program FilesMicrosoft Visual Studio
9.0VCBin;C:Program
> > > FilesMicrosoft V
> > > > isual Studio
9.0VCvcpackages;C:Program FilesMicrosoft Visual
> Studio
> > > 9.0Comm
> > > > on7IDE;C:Program FilesMicrosoft
> > >
SDKsWindowsv6.1Bin;C:WindowsMicrosoft.NE
> > > >
> > >
>
TFrameworkv3.5;C:WindowsMicrosoft.NETFrameworkv2.0.507
27;c:bin;c:binbin
> > > >
> > >
>
;c:binusrlocalwbin;C:Perlsitebin;C:Perlbin;C:Progr
am
> > > FilesMicrosoft D
> > > > irectX SDK (November
> > >
>
2007)UtilitiesBinx86;C:Windowssystem32;C:Windows;C:W
> > > >
>
indowsSystem32Wbem;c:qt4.4.0-beta1bin;c:buildbin
> > > >
> > > > C:Program FilesMicrosoft
SDKsWindowsv6.1>ls c:buildbin
> > > > libeay32.dll  ssleay32.dll
> > > >
> > > > C:Program FilesMicrosoft
> > >
SDKsWindowsv6.1>Qtqca-2.0.0binqcatool2.exe --de
> > > > bug plugins
> > > > Qt Library Paths:
> > > >  C:/Qt/4.4.0-beta1/plugins
> > > >  C:/Qt/qca-2.0.0/bin
> > > > plugin: checking in path:
[C:/Qt/4.4.0-beta1/plugins]
> > > > plugin: checking file:
> > >
[C:/Qt/4.4.0-beta1/plugins/crypto/qca-ossl2.dll]
> > > > plugin: PluginInstance fromFile
> > >
[C:/Qt/4.4.0-beta1/plugins/crypto/qca-ossl2.dll]
> > > >
> > > > plugin: failed to load: The file
> > >
'C:/Qt/4.4.0-beta1/plugins/crypto/qca-ossl2.dll
> > > >
> > > > ' is not a valid Qt plugin.
> > > > plugin: checking file:
> > >
[C:/Qt/4.4.0-beta1/plugins/crypto/qca-ossld2.dll]
> > > > plugin: PluginInstance fromFile
> > >
[C:/Qt/4.4.0-beta1/plugins/crypto/qca-ossld2.dll
> > > > ]
> > > > plugin: failed to load: The file
> > >
'C:/Qt/4.4.0-beta1/plugins/crypto/qca-ossld2.dl
> > > > l' is not a valid Qt plugin.
> > > > plugin: checking in path:
[C:/Qt/qca-2.0.0/bin]
> > > > Available Providers:
> > > >  (none)
> > > >
> > > >
> > > >
> > > >
> > > > On 16/03/2008, Norman Rasmussen
<normanrasmussen.co.za> wrote:
> > > > > Are openssl's libeay32 and ssleay32
dll's findable in the current
> folder
> > > > > and/or path env?
> > > > > If they're not then the openssl qca
plugin fails to load.
> > > > > This failure is generally cached in
the registry too, so you need to
> > > clean
> > > > > that out for Qt to re-detect the
openssl provider.
> > > > >
> > > > >
> > > > > On Sun, Mar 16, 2008 at 9:30 PM,
optimism_ <optiz0rgmail.com>
> wrote:
> > > > > >
> > > > > > Hi,
> > > > > >
> > > > > > I'm struggling to build a copy
of QCA2 with the openssl plugin
> under
> > > > > > the latest version of visual
studio, and the Qt 4.4 pre-release
> code.
> > > > > >
> > > > > > I've got a successful build
working under linux so far, but the
> > > > > > windows one is causing me
trouble. Following the instructions in
> the
> > > > > > respective INSTALL files, I've
got both qca-2.0.0 and
> > > > > > qca-ossl-2.0.0-beta3 build
successfully producing qcatool2 and the
> > > > > > qca-ossl2.dll files. I've
moved them to the Qt directory.
> > > > > >
> > > > > > qcatool shows no available
providers, despite showing the correct
> > > search
> > > > > paths.
> > > > > >
> > > > > > I've single-stepped through
the QPluginLoader source, and its
> bailing
> > > > > > out while trying to find the
> > > > > qt_plugin_query_verification_data
symbol
> > > > > > and concludes the ossl dll is
not a valid Qt plugin.
> > > > > >
> > > > > > Is this a known issue or bug
with QCA? Is building it in this way
> > > > > > supported at all, or am I
trying to do something that just isn't
> > > > > > possible?
> > > > > >
> > > > > > Any response would be greatly
appreciated; if QCA can't be made to
> > > > > > work I'll need to find an
alternative asap.
> > > > > >
> > > > > > Thanks,
> > > > > >
> > > > > > Ben Roberts.
> > > > > > Electronics and Computer
Science,
> > > > > > University of Southampton.
> > > > > >
_______________________________________________
> > > > > > Delta mailing list
> > > > > > Deltalists.affinix.com
> > > > > >
> > > http://lists.affinix.com/listinfo.cgi/delta-affinix.com
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > - Norman Rasmussen
> > > > >  - Email: normanrasmussen.co.za
> > > > >  - Home page: http://norman.rasmusse
n.co.za/
> > > > >
_______________________________________________
> > > > >  Delta mailing list
> > > > >  Deltalists.affinix.com
> > > > >
> http://lists.affinix.com/listinfo.cgi/delta-affinix.com
> > > > >
> > > > >
> > > >
_______________________________________________
> > > > Delta mailing list
> > > > Deltalists.affinix.com
> > > >
> http://lists.affinix.com/listinfo.cgi/delta-affinix.com
> > > >
> > >
> > >
> > >
> > > --
> > > - Norman Rasmussen
> > >  - Email: normanrasmussen.co.za
> > >  - Home page: http://norman.rasmusse
n.co.za/
> > >
_______________________________________________
> > >  Delta mailing list
> > >  Deltalists.affinix.com
> > > http://lists.affinix.com/listinfo.cgi/delta-affinix.com
> > >
> > >
> > _______________________________________________
> > Delta mailing list
> > Deltalists.affinix.com
> > http://lists.affinix.com/listinfo.cgi/delta-affinix.com
> >
>
>
>
> --
> - Norman Rasmussen
>  - Email: normanrasmussen.co.za
>  - Home page: http://norman.rasmusse
n.co.za/
> _______________________________________________
>  Delta mailing list
>  Deltalists.affinix.com
> http://lists.affinix.com/listinfo.cgi/delta-affinix.com
>
>
_______________________________________________
Delta mailing list
Deltalists.affinix.com
http://lists.affinix.com/listinfo.cgi/delta-affinix.com

I've just spent all day building both todays daily snapshot
of the 4.4
series, and also 4.3.4 stable. I can't get the plugin to
load under
any qt version.

It's got to be a problem with my build environment
somewhere, but I am
at a loss as to what might cause it. Maybe msvc2008 is
broken.

On 17/03/2008, Norman Rasmussen <normanrasmussen.co.za> wrote:
> I think my knowledge runs out here, things I can think
to check are:
>  - Does this set up work with Qt 4.3.4?
>  - If so, let the trolls know that they've broken
plugins in 4.4.0-beta1
>
>
>  On Mon, Mar 17, 2008 at 12:41 PM, optimism_
<optiz0rgmail.com> wrote:
> > Ah, yes running it from inside the vc command
prompt makes it find the
> > missing dll. Should have thought of that. Yes i
get similar output to
> > you, then.
> >
> > C:Program FilesMicrosoft Visual Studio
9.0VCbin>dumpbin /exports
> C:Qt4.4.0
> > -beta1pluginscrypto*.dll | grep plugin
> > Dump of file
> C:Qt4.4.0-beta1pluginscryptoqca-ossl2.dll
> >          1    0 0000BC90 qt_plugin_instance
> >          2    1 00001CB0
> qt_plugin_query_verification_data
> > Dump of file
> C:Qt4.4.0-beta1pluginscryptoqca-ossld2.dll
> >          1    0 000019D8 qt_plugin_instance =
> ILT+2515(_qt_plugin_instance)
> >          2    1 000016E0
> qt_plugin_query_verification_data =
> > ILT+1755(_qt_plugin_query_verification_data)
> >
> >
> >
> >
> >
> > On 17/03/2008, Norman Rasmussen <normanrasmussen.co.za> wrote:
> > > I think the dependency walker will show
imports, not exports, so that
> would
> > > be why the list is different.
> > >
> > > The dumpbin tool should work without any
issues, if it doesn't then it's
> > > possible that something else is broken.  (Are
you running it from the
> > > 'visual studio 2008 command prompt'? or do
you not have that?)
> > >
> > >
> > > On Mon, Mar 17, 2008 at 12:01 PM, optimism_
<optiz0rgmail.com> wrote:
> > > > The dumpbin tool seems to be looking for
a missing dll, and crashing
> > > > on my system. The Dependency walker tool
also lists exported functions
> > > > however, and the very big list does not
include the above methods. the
> > > > only qt_ prefixed methods listed in the
exports list are qt_metacast
> > > > and qt_metacalls...
> > > >
> > > >
> > > >
> > > >
> > > > On 17/03/2008, Norman Rasmussen
<normanrasmussen.co.za> wrote:
> > > > > Hrm, the latest I've tried to
compile is 4.3.4.   It is possible
> that Qt
> > > > > have broken the plugin loading on
4.4.0-beta1 I guess.
> > > > >
> > > > > Double check that the functions are
exported correctly with dumpbin
> > > perhaps?
> > > > >
> > > > >  > dumpbin /exports
> > > C:Qt4.4.0-beta1pluginscrypto*.dll
> > > > > | find /i "plugin"
> > > > >           1    0 000016C7
qt_plugin_instance =
> > > > > ILT+1730(_qt_plugin_instance)
> > > > >           2    1 000014F1
> > > qt_plugin_query_verification_data
> > > > > = ILT+1260(_qt_plugin_query_verification_data)
> > > > >            1    0 000019FB
qt_plugin_instance =
> > > > > ILT+2550(_qt_plugin_instance)
> > > > >           2    1 000016FE
> > > qt_plugin_query_verification_data
> > > > > = ILT+1785(_qt_plugin_query_verification_data)
> > > > >
> > > > > is what is shown for my Qt 4.3.4
openssl + gnupg plugins.
> > > > >
> > > > >
> > > > > On Mon, Mar 17, 2008 at 12:31 AM,
optimism_ <optiz0rgmail.com>
> wrote:
> > > > > > Fraid so, no joy.
> > > > > > My single stepping shows me
touching the ossl dlls makes Qt
> recheck
> > > > > > them, however they are still
definitely failing to load.
> > > > > >
> > > > > > Oh, and I added a brief mod to
the qca source to print out the
> > > > > > QPluginLoader errorString()
along with the failed to load message,
> > > > > > which is shown below.
> > > > > >
> > > > > > C:Program FilesMicrosoft
SDKsWindowsv6.1>echo %PATH%
> > > > > > C:Program FilesMicrosoft
Visual Studio 9.0VCBin;C:Program
> > > > > FilesMicrosoft V
> > > > > > isual Studio
9.0VCvcpackages;C:Program FilesMicrosoft Visual
> > > Studio
> > > > > 9.0Comm
> > > > > > on7IDE;C:Program
FilesMicrosoft
> > > > >
SDKsWindowsv6.1Bin;C:WindowsMicrosoft.NE
> > > > > >
> > > > >
> > >
>
TFrameworkv3.5;C:WindowsMicrosoft.NETFrameworkv2.0.507
27;c:bin;c:binbin
> > > > > >
> > > > >
> > >
>
;c:binusrlocalwbin;C:Perlsitebin;C:Perlbin;C:Progr
am
> > > > > FilesMicrosoft D
> > > > > > irectX SDK (November
> > > > >
> > >
>
2007)UtilitiesBinx86;C:Windowssystem32;C:Windows;C:W
> > > > > >
> > >
indowsSystem32Wbem;c:qt4.4.0-beta1bin;c:buildbin
> > > > > >
> > > > > > C:Program FilesMicrosoft
SDKsWindowsv6.1>ls c:buildbin
> > > > > > libeay32.dll  ssleay32.dll
> > > > > >
> > > > > > C:Program FilesMicrosoft
> > > > >
SDKsWindowsv6.1>Qtqca-2.0.0binqcatool2.exe --de
> > > > > > bug plugins
> > > > > > Qt Library Paths:
> > > > > >  C:/Qt/4.4.0-beta1/plugins
> > > > > >  C:/Qt/qca-2.0.0/bin
> > > > > > plugin: checking in path:
[C:/Qt/4.4.0-beta1/plugins]
> > > > > > plugin: checking file:
> > > > >
[C:/Qt/4.4.0-beta1/plugins/crypto/qca-ossl2.dll]
> > > > > > plugin: PluginInstance
fromFile
> > > > >
[C:/Qt/4.4.0-beta1/plugins/crypto/qca-ossl2.dll]
> > > > > >
> > > > > > plugin: failed to load: The
file
> > > > >
'C:/Qt/4.4.0-beta1/plugins/crypto/qca-ossl2.dll
> > > > > >
> > > > > > ' is not a valid Qt plugin.
> > > > > > plugin: checking file:
> > > > >
[C:/Qt/4.4.0-beta1/plugins/crypto/qca-ossld2.dll]
> > > > > > plugin: PluginInstance
fromFile
> > > > >
[C:/Qt/4.4.0-beta1/plugins/crypto/qca-ossld2.dll
> > > > > > ]
> > > > > > plugin: failed to load: The
file
> > > > >
'C:/Qt/4.4.0-beta1/plugins/crypto/qca-ossld2.dl
> > > > > > l' is not a valid Qt plugin.
> > > > > > plugin: checking in path:
[C:/Qt/qca-2.0.0/bin]
> > > > > > Available Providers:
> > > > > >  (none)
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > On 16/03/2008, Norman
Rasmussen <normanrasmussen.co.za> wrote:
> > > > > > > Are openssl's libeay32
and ssleay32 dll's findable in the
> current
> > > folder
> > > > > > > and/or path env?
> > > > > > > If they're not then the
openssl qca plugin fails to load.
> > > > > > > This failure is generally
cached in the registry too, so you
> need to
> > > > > clean
> > > > > > > that out for Qt to
re-detect the openssl provider.
> > > > > > >
> > > > > > >
> > > > > > > On Sun, Mar 16, 2008 at
9:30 PM, optimism_ <optiz0rgmail.com>
> > > wrote:
> > > > > > > >
> > > > > > > > Hi,
> > > > > > > >
> > > > > > > > I'm struggling to
build a copy of QCA2 with the openssl plugin
> > > under
> > > > > > > > the latest version
of visual studio, and the Qt 4.4
> pre-release
> > > code.
> > > > > > > >
> > > > > > > > I've got a
successful build working under linux so far, but
> the
> > > > > > > > windows one is
causing me trouble. Following the instructions
> in
> > > the
> > > > > > > > respective INSTALL
files, I've got both qca-2.0.0 and
> > > > > > > > qca-ossl-2.0.0-beta3
build successfully producing qcatool2 and
> the
> > > > > > > > qca-ossl2.dll files.
I've moved them to the Qt directory.
> > > > > > > >
> > > > > > > > qcatool shows no
available providers, despite showing the
> correct
> > > > > search
> > > > > > > paths.
> > > > > > > >
> > > > > > > > I've single-stepped
through the QPluginLoader source, and its
> > > bailing
> > > > > > > > out while trying to
find the
> > > > > > >
qt_plugin_query_verification_data symbol
> > > > > > > > and concludes the
ossl dll is not a valid Qt plugin.
> > > > > > > >
> > > > > > > > Is this a known
issue or bug with QCA? Is building it in this
> way
> > > > > > > > supported at all, or
am I trying to do something that just
> isn't
> > > > > > > > possible?
> > > > > > > >
> > > > > > > > Any response would
be greatly appreciated; if QCA can't be
> made to
> > > > > > > > work I'll need to
find an alternative asap.
> > > > > > > >
> > > > > > > > Thanks,
> > > > > > > >
> > > > > > > > Ben Roberts.
> > > > > > > > Electronics and
Computer Science,
> > > > > > > > University of
Southampton.
> > > > > > > >
> _______________________________________________
> > > > > > > > Delta mailing list
> > > > > > > > Deltalists.affinix.com
> > > > > > > >
> > > > >
> http://lists.affinix.com/listinfo.cgi/delta-affinix.com
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > - Norman Rasmussen
> > > > > > >  - Email: normanrasmussen.co.za
> > > > > > >  - Home page: http://norman.rasmusse
n.co.za/
> > > > > > >
_______________________________________________
> > > > > > >  Delta mailing list
> > > > > > >  Deltalists.affinix.com
> > > > > > >
> > > http://lists.affinix.com/listinfo.cgi/delta-affinix.com
> > > > > > >
> > > > > > >
> > > > > >
_______________________________________________
> > > > > > Delta mailing list
> > > > > > Deltalists.affinix.com
> > > > > >
> > > http://lists.affinix.com/listinfo.cgi/delta-affinix.com
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > - Norman Rasmussen
> > > > >  - Email: normanrasmussen.co.za
> > > > >  - Home page: http://norman.rasmusse
n.co.za/
> > > > >
_______________________________________________
> > > > >  Delta mailing list
> > > > >  Deltalists.affinix.com
> > > > >
> http://lists.affinix.com/listinfo.cgi/delta-affinix.com
> > > > >
> > > > >
> > > >
_______________________________________________
> > > > Delta mailing list
> > > > Deltalists.affinix.com
> > > >
> http://lists.affinix.com/listinfo.cgi/delta-affinix.com
> > > >
> > >
> > >
> > >
> > > --
> > > - Norman Rasmussen
> > >  - Email: normanrasmussen.co.za
> > >  - Home page: http://norman.rasmusse
n.co.za/
> > >
_______________________________________________
> > >  Delta mailing list
> > >  Deltalists.affinix.com
> > > http://lists.affinix.com/listinfo.cgi/delta-affinix.com
> > >
> > >
> > _______________________________________________
> > Delta mailing list
> > Deltalists.affinix.com
> > http://lists.affinix.com/listinfo.cgi/delta-affinix.com
> >
>
>
>
> --
> - Norman Rasmussen
>  - Email: normanrasmussen.co.za
>  - Home page: http://norman.rasmusse
n.co.za/
> _______________________________________________
>  Delta mailing list
>  Deltalists.affinix.com
> http://lists.affinix.com/listinfo.cgi/delta-affinix.com
>
>
_______________________________________________
Delta mailing list
Deltalists.affinix.com
http://lists.affinix.com/listinfo.cgi/delta-affinix.com

Since you're already this deep, and you have copies of Qt
that you built 
yourself, you might debug QPluginLoader.  Find out exactly
where it is 
rejecting the plugin, and be sure to print out the
verification data of the 
plugin and whatever Qt expects the value to be.

On Monday 17 March 2008 11:15 am, optimism_ wrote:
> I've just spent all day building both todays daily
snapshot of the 4.4
> series, and also 4.3.4 stable. I can't get the plugin
to load under
> any qt version.
>
> It's got to be a problem with my build environment
somewhere, but I am
> at a loss as to what might cause it. Maybe msvc2008 is
broken.
>
> On 17/03/2008, Norman Rasmussen <normanrasmussen.co.za> wrote:
> > I think my knowledge runs out here, things I can
think to check are:
> >  - Does this set up work with Qt 4.3.4?
> >  - If so, let the trolls know that they've broken
plugins in 4.4.0-beta1
> >
> >  On Mon, Mar 17, 2008 at 12:41 PM, optimism_
<optiz0rgmail.com> wrote:
> > > Ah, yes running it from inside the vc command
prompt makes it find the
> > > missing dll. Should have thought of that. Yes
i get similar output to
> > > you, then.
> > >
> > > C:Program FilesMicrosoft Visual Studio
9.0VCbin>dumpbin /exports
> >
> > C:Qt4.4.0
> >
> > > -beta1pluginscrypto*.dll | grep plugin
> > > Dump of file
> >
> > C:Qt4.4.0-beta1pluginscryptoqca-ossl2.dll
> >
> > >          1    0 0000BC90 qt_plugin_instance
> > >          2    1 00001CB0
> >
> > qt_plugin_query_verification_data
> >
> > > Dump of file
> >
> > C:Qt4.4.0-beta1pluginscryptoqca-ossld2.dll
> >
> > >          1    0 000019D8 qt_plugin_instance
=
> >
> > ILT+2515(_qt_plugin_instance)
> >
> > >          2    1 000016E0
> >
> > qt_plugin_query_verification_data =
> >
> > > ILT+1755(_qt_plugin_query_verification_data)
> > >
> > > On 17/03/2008, Norman Rasmussen
<normanrasmussen.co.za> wrote:
> > > > I think the dependency walker will show
imports, not exports, so that
> >
> > would
> >
> > > > be why the list is different.
> > > >
> > > > The dumpbin tool should work without any
issues, if it doesn't then
> > > > it's possible that something else is
broken.  (Are you running it
> > > > from the 'visual studio 2008 command
prompt'? or do you not have
> > > > that?)
> > > >
> > > > On Mon, Mar 17, 2008 at 12:01 PM,
optimism_ <optiz0rgmail.com> wrote:
> > > > > The dumpbin tool seems to be
looking for a missing dll, and
> > > > > crashing on my system. The
Dependency walker tool also lists
> > > > > exported functions however, and the
very big list does not include
> > > > > the above methods. the only qt_
prefixed methods listed in the
> > > > > exports list are qt_metacast and
qt_metacalls...
> > > > >
> > > > > On 17/03/2008, Norman Rasmussen
<normanrasmussen.co.za> wrote:
> > > > > > Hrm, the latest I've tried to
compile is 4.3.4.   It is possible
> >
> > that Qt
> >
> > > > > > have broken the plugin loading
on 4.4.0-beta1 I guess.
> > > > > >
> > > > > > Double check that the
functions are exported correctly with
> > > > > > dumpbin
> > > >
> > > > perhaps?
> > > >
> > > > > >  > dumpbin /exports
> > > >
> > > > C:Qt4.4.0-beta1pluginscrypto*.dll
> > > >
> > > > > > | find /i "plugin"
> > > > > >
> > > > > >           1    0 000016C7
qt_plugin_instance =
> > > > > > ILT+1730(_qt_plugin_instance)
> > > > > >           2    1 000014F1
> > > >
> > > > qt_plugin_query_verification_data
> > > >
> > > > > > = ILT+1260(_qt_plugin_query_verification_data)
> > > > > >            1    0 000019FB
qt_plugin_instance =
> > > > > > ILT+2550(_qt_plugin_instance)
> > > > > >           2    1 000016FE
> > > >
> > > > qt_plugin_query_verification_data
> > > >
> > > > > > = ILT+1785(_qt_plugin_query_verification_data)
> > > > > >
> > > > > > is what is shown for my Qt
4.3.4 openssl + gnupg plugins.
> > > > > >
> > > > > >
> > > > > > On Mon, Mar 17, 2008 at 12:31
AM, optimism_ <optiz0rgmail.com>
> >
> > wrote:
> > > > > > > Fraid so, no joy.
> > > > > > > My single stepping shows
me touching the ossl dlls makes Qt
> >
> > recheck
> >
> > > > > > > them, however they are
still definitely failing to load.
> > > > > > >
> > > > > > > Oh, and I added a brief
mod to the qca source to print out the
> > > > > > > QPluginLoader
errorString() along with the failed to load
> > > > > > > message, which is shown
below.
> > > > > > >
> > > > > > > C:Program
FilesMicrosoft SDKsWindowsv6.1>echo %PATH%
> > > > > > > C:Program
FilesMicrosoft Visual Studio 9.0VCBin;C:Program
> > > > > >
> > > > > > FilesMicrosoft V
> > > > > >
> > > > > > > isual Studio
9.0VCvcpackages;C:Program FilesMicrosoft
> > > > > > > Visual
> > > >
> > > > Studio
> > > >
> > > > > > 9.0Comm
> > > > > >
> > > > > > > on7IDE;C:Program
FilesMicrosoft
> > > > > >
> > > > > >
SDKsWindowsv6.1Bin;C:WindowsMicrosoft.NE
> >
> >
TFrameworkv3.5;C:WindowsMicrosoft.NETFrameworkv2.0.507
27;c:bin;c:
> >binbin
> >
> >
> >
> >
;c:binusrlocalwbin;C:Perlsitebin;C:Perlbin;C:Progr
am
> >
> > > > > > FilesMicrosoft D
> > > > > >
> > > > > > > irectX SDK (November
> >
> >
2007)UtilitiesBinx86;C:Windowssystem32;C:Windows;C:W
> >
> > > >
indowsSystem32Wbem;c:qt4.4.0-beta1bin;c:buildbin
> > > >
> > > > > > > C:Program
FilesMicrosoft SDKsWindowsv6.1>ls c:buildbin
> > > > > > > libeay32.dll 
ssleay32.dll
> > > > > > >
> > > > > > > C:Program
FilesMicrosoft
> > > > > >
> > > > > >
SDKsWindowsv6.1>Qtqca-2.0.0binqcatool2.exe --de
> > > > > >
> > > > > > > bug plugins
> > > > > > > Qt Library Paths:
> > > > > > > 
C:/Qt/4.4.0-beta1/plugins
> > > > > > >  C:/Qt/qca-2.0.0/bin
> > > > > > > plugin: checking in path:
[C:/Qt/4.4.0-beta1/plugins]
> > > > > > > plugin: checking file:
> > > > > >
> > > > > >
[C:/Qt/4.4.0-beta1/plugins/crypto/qca-ossl2.dll]
> > > > > >
> > > > > > > plugin: PluginInstance
fromFile
> > > > > >
> > > > > >
[C:/Qt/4.4.0-beta1/plugins/crypto/qca-ossl2.dll]
> > > > > >
> > > > > > > plugin: failed to load:
The file
> > > > > >
> > > > > >
'C:/Qt/4.4.0-beta1/plugins/crypto/qca-ossl2.dll
> > > > > >
> > > > > > > ' is not a valid Qt
plugin.
> > > > > > > plugin: checking file:
> > > > > >
> > > > > >
[C:/Qt/4.4.0-beta1/plugins/crypto/qca-ossld2.dll]
> > > > > >
> > > > > > > plugin: PluginInstance
fromFile
> > > > > >
> > > > > >
[C:/Qt/4.4.0-beta1/plugins/crypto/qca-ossld2.dll
> > > > > >
> > > > > > > ]
> > > > > > > plugin: failed to load:
The file
> > > > > >
> > > > > >
'C:/Qt/4.4.0-beta1/plugins/crypto/qca-ossld2.dl
> > > > > >
> > > > > > > l' is not a valid Qt
plugin.
> > > > > > > plugin: checking in path:
[C:/Qt/qca-2.0.0/bin]
> > > > > > > Available Providers:
> > > > > > >  (none)
> > > > > > >
> > > > > > > On 16/03/2008, Norman
Rasmussen <normanrasmussen.co.za> wrote:
> > > > > > > > Are openssl's
libeay32 and ssleay32 dll's findable in the
> >
> > current
> >
> > > > folder
> > > >
> > > > > > > > and/or path env?
> > > > > > > > If they're not then
the openssl qca plugin fails to load.
> > > > > > > > This failure is
generally cached in the registry too, so you
> >
> > need to
> >
> > > > > > clean
> > > > > >
> > > > > > > > that out for Qt to
re-detect the openssl provider.
> > > > > > > >
> > > > > > > >
> > > > > > > > On Sun, Mar 16, 2008
at 9:30 PM, optimism_
> > > > > > > > <optiz0rgmail.com>
> > > >
> > > > wrote:
> > > > > > > > > Hi,
> > > > > > > > >
> > > > > > > > > I'm struggling
to build a copy of QCA2 with the openssl
> > > > > > > > > plugin
> > > >
> > > > under
> > > >
> > > > > > > > > the latest
version of visual studio, and the Qt 4.4
> >
> > pre-release
> >
> > > > code.
> > > >
> > > > > > > > > I've got a
successful build working under linux so far, but
> >
> > the
> >
> > > > > > > > > windows one is
causing me trouble. Following the
> > > > > > > > > instructions
> >
> > in
> >
> > > > the
> > > >
> > > > > > > > > respective
INSTALL files, I've got both qca-2.0.0 and
> > > > > > > > >
qca-ossl-2.0.0-beta3 build successfully producing qcatool2
> > > > > > > > > and
> >
> > the
> >
> > > > > > > > > qca-ossl2.dll
files. I've moved them to the Qt directory.
> > > > > > > > >
> > > > > > > > > qcatool shows
no available providers, despite showing the
> >
> > correct
> >
> > > > > > search
> > > > > >
> > > > > > > > paths.
> > > > > > > >
> > > > > > > > > I've
single-stepped through the QPluginLoader source, and
> > > > > > > > > its
> > > >
> > > > bailing
> > > >
> > > > > > > > > out while
trying to find the
> > > > > > > >
> > > > > > > >
qt_plugin_query_verification_data symbol
> > > > > > > >
> > > > > > > > > and concludes
the ossl dll is not a valid Qt plugin.
> > > > > > > > >
> > > > > > > > > Is this a known
issue or bug with QCA? Is building it in
> > > > > > > > > this
> >
> > way
> >
> > > > > > > > > supported at
all, or am I trying to do something that just
> >
> > isn't
> >
> > > > > > > > > possible?
> > > > > > > > >
> > > > > > > > > Any response
would be greatly appreciated; if QCA can't be
> >
> > made to
> >
> > > > > > > > > work I'll need
to find an alternative asap.
> > > > > > > > >
> > > > > > > > > Thanks,
> > > > > > > > >
> > > > > > > > > Ben Roberts.
> > > > > > > > > Electronics and
Computer Science,
> > > > > > > > > University of
Southampton.
> >
> > _______________________________________________
> >
> > > > > > > > > Delta mailing
list
> > > > > > > > > Deltalists.affinix.com
> >
> > http://lists.affinix.com/listinfo.cgi/delta-affinix.com
> >
> > > > > > > > --
> > > > > > > > - Norman Rasmussen
> > > > > > > >  - Email: normanrasmussen.co.za
> > > > > > > >  - Home page: http://norman.rasmusse
n.co.za/
> > > > > > > >
_______________________________________________
> > > > > > > >  Delta mailing list
> > > > > > > >  Deltalists.affinix.com
> > > >
> > > > http://lists.affinix.com/listinfo.cgi/delta-affinix.com
> > > >
> > > > > > >
_______________________________________________
> > > > > > > Delta mailing list
> > > > > > > Deltalists.affinix.com
> > > >
> > > > http://lists.affinix.com/listinfo.cgi/delta-affinix.com
> > > >
> > > > > > --
> > > > > > - Norman Rasmussen
> > > > > >  - Email: normanrasmussen.co.za
> > > > > >  - Home page: http://norman.rasmusse
n.co.za/
> > > > > >
_______________________________________________
> > > > > >  Delta mailing list
> > > > > >  Deltalists.affinix.com
> >
> > http://lists.affinix.com/listinfo.cgi/delta-affinix.com
> >
> > > > >
_______________________________________________
> > > > > Delta mailing list
> > > > > Deltalists.affinix.com
> >
> > http://lists.affinix.com/listinfo.cgi/delta-affinix.com
> >
> > > > --
> > > > - Norman Rasmussen
> > > >  - Email: normanrasmussen.co.za
> > > >  - Home page: http://norman.rasmusse
n.co.za/
> > > >
_______________________________________________
> > > >  Delta mailing list
> > > >  Deltalists.affinix.com
> > > > http://lists.affinix.com/listinfo.cgi/delta-affinix.com
> > >
> > >
_______________________________________________
> > > Delta mailing list
> > > Deltalists.affinix.com
> > > http://lists.affinix.com/listinfo.cgi/delta-affinix.com
> >
> > --
> > - Norman Rasmussen
> >  - Email: normanrasmussen.co.za
> >  - Home page: http://norman.rasmusse
n.co.za/
> > _______________________________________________
> >  Delta mailing list
> >  Deltalists.affinix.com
> > http://lists.affinix.com/listinfo.cgi/delta-affinix.com
>
> _______________________________________________
> Delta mailing list
> Deltalists.affinix.com
> http://lists.affinix.com/listinfo.cgi/delta-affinix.com
_______________________________________________
Delta mailing list
Deltalists.affinix.com
http://lists.affinix.com/listinfo.cgi/delta-affinix.com

I can do further debugging tomorrow, but from memory, the
failure
happened at src/clorelib/plugin/qlibrary.cpp:603, where it
failed to
resolve qt_plugin_query_verification_data symbol.

It then updates the cache, and enters the if(!success),
setting
errorString to say the file is not a valid qt plugin, and
then returns
false.

That was under 4.4.0-beta1, haven't tested under 4.3.4 yet,
but the
symptoms are the same.

Im just currently installing vs2005 whereupon I'll recompile
all of Qt
and qca again to see if its a compiler bug in 2008.

Cheers for your help so far, though.

On 17/03/2008, Justin Karneges <justin-psi2affinix.com> wrote:
> Since you're already this deep, and you have copies of
Qt that you built
>  yourself, you might debug QPluginLoader.  Find out
exactly where it is
>  rejecting the plugin, and be sure to print out the
verification data of the
>  plugin and whatever Qt expects the value to be.
>
>
>  On Monday 17 March 2008 11:15 am, optimism_ wrote:
>  > I've just spent all day building both todays
daily snapshot of the 4.4
>  > series, and also 4.3.4 stable. I can't get the
plugin to load under
>  > any qt version.
>  >
>  > It's got to be a problem with my build
environment somewhere, but I am
>  > at a loss as to what might cause it. Maybe
msvc2008 is broken.
>  >
>  > On 17/03/2008, Norman Rasmussen <normanrasmussen.co.za> wrote:
>  > > I think my knowledge runs out here, things I
can think to check are:
>  > >  - Does this set up work with Qt 4.3.4?
>  > >  - If so, let the trolls know that they've
broken plugins in 4.4.0-beta1
>  > >
>  > >  On Mon, Mar 17, 2008 at 12:41 PM, optimism_
<optiz0rgmail.com> wrote:
>  > > > Ah, yes running it from inside the vc
command prompt makes it find the
>  > > > missing dll. Should have thought of
that. Yes i get similar output to
>  > > > you, then.
>  > > >
>  > > > C:Program FilesMicrosoft Visual
Studio 9.0VCbin>dumpbin /exports
>  > >
>  > > C:Qt4.4.0
>  > >
>  > > > -beta1pluginscrypto*.dll | grep
plugin
>  > > > Dump of file
>  > >
>  > >
C:Qt4.4.0-beta1pluginscryptoqca-ossl2.dll
>  > >
>  > > >          1    0 0000BC90
qt_plugin_instance
>  > > >          2    1 00001CB0
>  > >
>  > > qt_plugin_query_verification_data
>  > >
>  > > > Dump of file
>  > >
>  > >
C:Qt4.4.0-beta1pluginscryptoqca-ossld2.dll
>  > >
>  > > >          1    0 000019D8
qt_plugin_instance =
>  > >
>  > > ILT+2515(_qt_plugin_instance)
>  > >
>  > > >          2    1 000016E0
>  > >
>  > > qt_plugin_query_verification_data =
>  > >
>  > > > ILT+1755(_qt_plugin_query_verification_data)
>  > > >
>  > > > On 17/03/2008, Norman Rasmussen
<normanrasmussen.co.za> wrote:
>  > > > > I think the dependency walker will
show imports, not exports, so that
>  > >
>  > > would
>  > >
>  > > > > be why the list is different.
>  > > > >
>  > > > > The dumpbin tool should work
without any issues, if it doesn't then
>  > > > > it's possible that something else
is broken.  (Are you running it
>  > > > > from the 'visual studio 2008
command prompt'? or do you not have
>  > > > > that?)
>  > > > >
>  > > > > On Mon, Mar 17, 2008 at 12:01 PM,
optimism_ <optiz0rgmail.com> wrote:
>  > > > > > The dumpbin tool seems to be
looking for a missing dll, and
>  > > > > > crashing on my system. The
Dependency walker tool also lists
>  > > > > > exported functions however,
and the very big list does not include
>  > > > > > the above methods. the only
qt_ prefixed methods listed in the
>  > > > > > exports list are qt_metacast
and qt_metacalls...
>  > > > > >
>  > > > > > On 17/03/2008, Norman
Rasmussen <normanrasmussen.co.za> wrote:
>  > > > > > > Hrm, the latest I've
tried to compile is 4.3.4.   It is possible
>  > >
>  > > that Qt
>  > >
>  > > > > > > have broken the plugin
loading on 4.4.0-beta1 I guess.
>  > > > > > >
>  > > > > > > Double check that the
functions are exported correctly with
>  > > > > > > dumpbin
>  > > > >
>  > > > > perhaps?
>  > > > >
>  > > > > > >  > dumpbin /exports
>  > > > >
>  > > > >
C:Qt4.4.0-beta1pluginscrypto*.dll
>  > > > >
>  > > > > > > | find /i
"plugin"
>  > > > > > >
>  > > > > > >           1    0
000016C7 qt_plugin_instance =
>  > > > > > > ILT+1730(_qt_plugin_instance)
>  > > > > > >           2    1
000014F1
>  > > > >
>  > > > > qt_plugin_query_verification_data
>  > > > >
>  > > > > > > = ILT+1260(_qt_plugin_query_verification_data)
>  > > > > > >            1    0
000019FB qt_plugin_instance =
>  > > > > > > ILT+2550(_qt_plugin_instance)
>  > > > > > >           2    1
000016FE
>  > > > >
>  > > > > qt_plugin_query_verification_data
>  > > > >
>  > > > > > > = ILT+1785(_qt_plugin_query_verification_data)
>  > > > > > >
>  > > > > > > is what is shown for my
Qt 4.3.4 openssl + gnupg plugins.
>  > > > > > >
>  > > > > > >
>  > > > > > > On Mon, Mar 17, 2008 at
12:31 AM, optimism_ <optiz0rgmail.com>
>  > >
>  > > wrote:
>  > > > > > > > Fraid so, no joy.
>  > > > > > > > My single stepping
shows me touching the ossl dlls makes Qt
>  > >
>  > > recheck
>  > >
>  > > > > > > > them, however they
are still definitely failing to load.
>  > > > > > > >
>  > > > > > > > Oh, and I added a
brief mod to the qca source to print out the
>  > > > > > > > QPluginLoader
errorString() along with the failed to load
>  > > > > > > > message, which is
shown below.
>  > > > > > > >
>  > > > > > > > C:Program
FilesMicrosoft SDKsWindowsv6.1>echo %PATH%
>  > > > > > > > C:Program
FilesMicrosoft Visual Studio 9.0VCBin;C:Program
>  > > > > > >
>  > > > > > > FilesMicrosoft V
>  > > > > > >
>  > > > > > > > isual Studio
9.0VCvcpackages;C:Program FilesMicrosoft
>  > > > > > > > Visual
>  > > > >
>  > > > > Studio
>  > > > >
>  > > > > > > 9.0Comm
>  > > > > > >
>  > > > > > > > on7IDE;C:Program
FilesMicrosoft
>  > > > > > >
>  > > > > > >
SDKsWindowsv6.1Bin;C:WindowsMicrosoft.NE
>  > >
>  > >
TFrameworkv3.5;C:WindowsMicrosoft.NETFrameworkv2.0.507
27;c:bin;c:
>  > >binbin
>  > >
>  > >
>  > >
>  > >
;c:binusrlocalwbin;C:Perlsitebin;C:Perlbin;C:Progr
am
>  > >
>  > > > > > > FilesMicrosoft D
>  > > > > > >
>  > > > > > > > irectX SDK
(November
>  > >
>  > >
2007)UtilitiesBinx86;C:Windowssystem32;C:Windows;C:W
>  > >
>  > > > >
indowsSystem32Wbem;c:qt4.4.0-beta1bin;c:buildbin
>  > > > >
>  > > > > > > > C:Program
FilesMicrosoft SDKsWindowsv6.1>ls c:buildbin
>  > > > > > > > libeay32.dll 
ssleay32.dll
>  > > > > > > >
>  > > > > > > > C:Program
FilesMicrosoft
>  > > > > > >
>  > > > > > >
SDKsWindowsv6.1>Qtqca-2.0.0binqcatool2.exe --de
>  > > > > > >
>  > > > > > > > bug plugins
>  > > > > > > > Qt Library Paths:
>  > > > > > > > 
C:/Qt/4.4.0-beta1/plugins
>  > > > > > > > 
C:/Qt/qca-2.0.0/bin
>  > > > > > > > plugin: checking in
path: [C:/Qt/4.4.0-beta1/plugins]
>  > > > > > > > plugin: checking
file:
>  > > > > > >
>  > > > > > >
[C:/Qt/4.4.0-beta1/plugins/crypto/qca-ossl2.dll]
>  > > > > > >
>  > > > > > > > plugin:
PluginInstance fromFile
>  > > > > > >
>  > > > > > >
[C:/Qt/4.4.0-beta1/plugins/crypto/qca-ossl2.dll]
>  > > > > > >
>  > > > > > > > plugin: failed to
load: The file
>  > > > > > >
>  > > > > > >
'C:/Qt/4.4.0-beta1/plugins/crypto/qca-ossl2.dll
>  > > > > > >
>  > > > > > > > ' is not a valid Qt
plugin.
>  > > > > > > > plugin: checking
file:
>  > > > > > >
>  > > > > > >
[C:/Qt/4.4.0-beta1/plugins/crypto/qca-ossld2.dll]
>  > > > > > >
>  > > > > > > > plugin:
PluginInstance fromFile
>  > > > > > >
>  > > > > > >
[C:/Qt/4.4.0-beta1/plugins/crypto/qca-ossld2.dll
>  > > > > > >
>  > > > > > > > ]
>  > > > > > > > plugin: failed to
load: The file
>  > > > > > >
>  > > > > > >
'C:/Qt/4.4.0-beta1/plugins/crypto/qca-ossld2.dl
>  > > > > > >
>  > > > > > > > l' is not a valid
Qt plugin.
>  > > > > > > > plugin: checking in
path: [C:/Qt/qca-2.0.0/bin]
>  > > > > > > > Available
Providers:
>  > > > > > > >  (none)
>  > > > > > > >
>  > > > > > > > On 16/03/2008,
Norman Rasmussen <normanrasmussen.co.za> wrote:
>  > > > > > > > > Are openssl's
libeay32 and ssleay32 dll's findable in the
>  > >
>  > > current
>  > >
>  > > > > folder
>  > > > >
>  > > > > > > > > and/or path
env?
>  > > > > > > > > If they're not
then the openssl qca plugin fails to load.
>  > > > > > > > > This failure
is generally cached in the registry too, so you
>  > >
>  > > need to
>  > >
>  > > > > > > clean
>  > > > > > >
>  > > > > > > > > that out for
Qt to re-detect the openssl provider.
>  > > > > > > > >
>  > > > > > > > >
>  > > > > > > > > On Sun, Mar
16, 2008 at 9:30 PM, optimism_
>  > > > > > > > >
<opt