I don't know what SExplorer is but I might guess that it opens, say, picture files with some picture viewer, movie files with some movie viewer etc and it doesn't start exe files.
Normally, after having created exe in Carbide you create a sis file and install it into the phone. Carbide can create sis file for you.
Or you can do everything from command line then you will need a pkg file and you will run 'makesis' utility and sometimes also 'signsis' utility. There are plenty of howtos regarding this on the Net
Well I did make a sis file at first, and signed it. I tried to install it and it failed install. My code is error free but I might have bugs.
What headers and libs do I need to implement a TRAPD?
It must have failed install because you didn't have a proper certificate to sign sis with. Also, as your program uses telephony and all that you must ensure that you have necessary CAPABILITY statement in your mmp file. You may need to go to www.symbiagnsigned.com and request a developer certificate then sign your program with it. It's more or less straightforward procedure. Surely, I don't remember all the details but it's straightforward maybe just confusing at first.
As to TRAPD I dunno, good idea make a default gui or console program with carbide then in your program use the same libraries as carbide places when creating the program
What is that CAPABILITY statment?
a random .key and .cert made with 'makekeys' arnt good enough? I HAVE managed to run some self compiled example apps and signed em a random key/cert.
Well I did make a sis file at first, and signed it. I tried to install it and it failed install.
What was the error. Depending on error, suggestions can be given.
What is that CAPABILITY statment?
You have to specify capability in the mmp file. Search for capability in SDK document for detailed explaination of the same.
a random .key and .cert made with 'makekeys' arnt good enough?
For most basic capabilities its enough, but not for all. If you are using basic capabilities like LocalServices, Location, NetworkServices, ReadUserData, WriteUserData and UserEnvironment, you can use self-signing.
Forum posts: 30
I don't know what SExplorer is but I might guess that it opens, say, picture files with some picture viewer, movie files with some movie viewer etc and it doesn't start exe files.
Normally, after having created exe in Carbide you create a sis file and install it into the phone. Carbide can create sis file for you.
Or you can do everything from command line then you will need a pkg file and you will run 'makesis' utility and sometimes also 'signsis' utility. There are plenty of howtos regarding this on the Net
Forum posts: 17
Well I did make a sis file at first, and signed it. I tried to install it and it failed install. My code is error free but I might have bugs.
What headers and libs do I need to implement a TRAPD?
Forum posts: 30
It must have failed install because you didn't have a proper certificate to sign sis with. Also, as your program uses telephony and all that you must ensure that you have necessary CAPABILITY statement in your mmp file. You may need to go to www.symbiagnsigned.com and request a developer certificate then sign your program with it. It's more or less straightforward procedure. Surely, I don't remember all the details but it's straightforward maybe just confusing at first.
As to TRAPD I dunno, good idea make a default gui or console program with carbide then in your program use the same libraries as carbide places when creating the program
Forum posts: 17
What is that CAPABILITY statment?
a random .key and .cert made with 'makekeys' arnt good enough? I HAVE managed to run some self compiled example apps and signed em a random key/cert.
Forum posts: 463
What was the error. Depending on error, suggestions can be given.
You have to specify capability in the mmp file. Search for capability in SDK document for detailed explaination of the same.
For most basic capabilities its enough, but not for all. If you are using basic capabilities like LocalServices, Location, NetworkServices, ReadUserData, WriteUserData and UserEnvironment, you can use self-signing.