[Psi-Devel] Link errors building Psi with Visual Studio 2008
Norka Lucena
norka.lucena at collabworx.com
Wed May 20 09:01:05 PDT 2009
Dear Norman,
Thanks again for your response.
> Do you need the static functionaltity? (I'm not sure if vs 2008 can
> build QCA+Psi properly in static mode - I've never tested it)
Well, based on observed behavior of Psi, I thought it needed to be
loaded statically. Am I wrong? For instance, this is the output from the
Security Plugins Diagnostic console given by the official Psi 0.12:
PluginInstance fromStatic
loaded as [opensslPlugin]
ProviderItem created: [qca-ossl]
item added [qca-ossl]
PluginInstance fromStatic
loaded as [gnupgPlugin]
ProviderItem created: [qca-gnupg]
item added [qca-gnupg]
PluginInstance fromStatic
loaded as [WinAmpPlugin]
not a QCAPlugin or wrong interface
PluginInstance deleted [WinAmpPlugin]
PluginInstance fromStatic
loaded as [PsiFilePlugin]
not a QCAPlugin or wrong interface
PluginInstance deleted [PsiFilePlugin]
checking in path: [C:/Documents and Settings/Norka Lucena/PsiData]
checking in path: [C:/Program Files/Psi]
checking in path: [C:/Documents and Settings/Norka Lucena/PsiData]
checking in path: [C:/Program Files/Psi]
adding pre-made provider: [simplesasl]
ProviderItem created: [simplesasl]
item added [simplesasl]
In addition, qca.pro suggests static building as well, doesn't it? If I
am not on the wrong track, I will appreciate some pointers.
Thanks for your suggestion though, I will try it building QCA dynamically.
--
Norka Lucena
CollabWorx, Inc.
CONFIDENTIALITY NOTICE - This email is ONLY for the person(s) named in
the message header. Unless otherwise indicated, it contains information
that is confidential, privileged or exempt from disclosure under
applicable law. If you have received it in error, please notify the
sender of the error and delete the message.
More information about the Psi-Devel
mailing list