Problem signing an aplication with a 3rd party DLL

[albgarse]

Hi!

I'm trying to sign an application who uses a 3rd party DLL (actually a python module). If i sign it using a developer certificate, it works right, but when I try to use Express Signed, it gives me a UID error. I supose that the DLL has an UID that is not in the range I reserved.
If I change the UID of the application with "ensymble.py altere32" the aplication can be signed via Express Signed and can be installed, but it fails when i try to run it in the phone.

What can I do to use this DLL in my own proyect and get it signed?

Best regards.

[wizard_hu_]

How does it fail? Have you checked the panic code (http://wiki.forum.nokia.com/index.ph...ded_panic_code) ?

[albgarse]

Hi wizard_hu,

It's a python module, and python return this error:

File "c:\resource\DMdecoder.py", line 5, in ?

_dmdecoder=imp.load_dynamic('_dmdecoder', 'c:\\sys\\bin\\_dmdecoder.pyd')

SymbianError: [Errno -5] KErrNotSupported

If I don't change de UID of the DLL and I sign it with a devcert, it works right. The problem become when I change the UID of the DLL and try to sign it (with devcert or express signed). I guess I need the DLL compiled with my own UID, but since it's a commercial DLL, I don't have the sources.

Best regards.

How does it fail? Have you checked the panic code (http://wiki.forum.nokia.com/index.ph...ded_panic_code) ?

[ltomuta]

To begin with you should not alter binaries you do not own. If that is my DLL and I found out that you have changed it and pretend to own it then you are in deep problems.

If the DLL is indeed commercially released it comes in a signed SIS file and that SIS file should be embedded in yours so that on install your application will have all its depencencies (including this DLL) available.

[albgarse]

We have bought the library, but the provider only gave us the DLL and the .h files to use it.
I don´t know if this is the habitual behavior since I´m new to symbian.
I guess we have to ask the provider for the .sis file to be embedded in our .sis installation.

Best regards.

To begin with you should not alter binaries you do not own. If that is my DLL and I found out that you have changed it and pretend to own it then you are in deep problems.

If the DLL is indeed commercially released it comes in a signed SIS file and that SIS file should be embedded in yours so that on install your application will have all its depencencies (including this DLL) available.

[wizard_hu_]

We have bought the library, but the provider only gave us the DLL and the .h files to use it.

In that case you should get the creator of the .dll to provide a signed .sisx for you, especially since you have paid for the component.

I don´t know if this is the habitual behavior since I´m new to symbian.

Even experienced developers would not like the idea of modifying binaries, the UID-s can appear in several locations.

I guess we have to ask the provider for the .sis file to be embedded in our .sis installation.

Indeed, that is the proper way of releasing .dll-s.