[cassioli]

I downloaded Keypress module and I tried to compile it.
I unpacked the keypress folder in D:\temp\pys60sources\src folder
I imported MMP file from within Carbide.c++ , and all works fine.
When I try to compile, I obtain this error:
'No tool found that can build the extension specified ith the build artifact name all'

I guess this is because of the "pyd" target in MMP file.

So, what's the procedure to compile new python modules???

[lfd]

Hi cassioli,

Here is a link to the official Wiki which describe the different steps http://wiki.opensource.nokia.com/pro...ing_extensions

If you still have problems after that, just ask.

LFD

[cassioli]

Originally Posted by lfd

Hi cassioli,

Here is a link to the official Wiki which describe the different steps http://wiki.opensource.nokia.com/pro...ing_extensions

If you still have problems after that, just ask.

LFD

I downloaded the Pys60 sdk and unpacked epoc32 folder in my emulator folder.
I donwloaded the Pys60 sources and I unpacked it somewhere.
Then I put Keypress folder (containing a SRC folder) in pys60 SRC folder.
I imported the MMP file in carbide.c++, and the project has been correctly created.
But when I try to compile, compiler complains about not finding any tool suitable to compile to "PYD" target. I tried changing PYD to EXE, but now compiler complains about not finding py[something].lib files, which actually are in the epoc32 folder I just unpacked.

[cassioli]

Besides that, can I compile a python extensions as a JNI module? I commented out the whole code of Keypress module, and I added just a couple of lines from a JNI module example, but with no success in compiling: JNIEXPORT is not recognized by the carbide compiler, and if I try with cl.exe compiler from Visual C++ 2005 Express Edition, it just does not do ANYTHING! Not an error message, not an output, just NOTHING.

[GameDude]

I recommend to build from the command line for both emulator and device since the Carbide's mmp import causes problems most of the time. Forget the mmp import. Carbide can still be used for debugging your extension. This works for me with Carbide.c++ Express v1.1:

• Setup your command line environment for building WINSCW using Carbide's tools
• Build your extension in command line( abld build winscw udeb )
• In Carbide, Select File->Import->Symbian OS Executable
• Select your dll(or exe) as the executable (in Epoc32\release\winscw\udeb)
• In Debug window, remember to set the Epoc32\release\winscw\udeb\epoc.exe as the emulator.
• There should be a new project containing the files of your extension
• Put breakpoint to somewhere
• Start the debugger
• It complains about not being able to set temporary breakpoint in main. This can be ignored
• Browse to Python and run a script using your extension.
• If all is well, Carbide should hit the breakpoint you set earlier.

Note: If you use the old imp.load_dynamic in your script pointing to C:\sys\bin you'll need to copy the PYD to \Epoc32\winscw\c\sys\bin

[cassioli]

Originally Posted by GameDude

I recommend to build from the command line for both emulator and device since the Carbide's mmp import causes problems most of the time. Forget the mmp import. Carbide can still be used for debugging your extension. This works for me with Carbide.c++ Express v1.1:
[list][*]Setup your command line environment for building WINSCW using Carbide's tools

It would be very interesting to know how to do this... I'm asking it myself since a long time...

[GameDude]

Check this thread:
http://discussion.forum.nokia.com/fo...ad.php?t=83677

If you use Carbide v1.1, you'll need to modify the version numbers of the paths.