[big_pig]

Hi,
Ensymble works fine with one application for me.
Also I can as explained add multiple files.

But what about the case I want to package an Python
application and the interpreter to one sis-file, making installation
more easy for people not interersted to play with
techical extra work to find pieces from different sources?

An other question:
S60 Python needs to my understanding to have
importable pyc, pyd files to be in the library.This means to be
installed to RESOURCES. So, it is not good enough
to pack these files to an other kind directory
structure. Basic Python itself says it tries to find importable
files from home first and then from library but this is not probably case with S60?

Thanks

[jethro.fn]

Hello.

Ensymble does not currently offer any support for embedding SIS files within each other. SIS file structure is such that the embedded SIS files are not contained in their original form, but instead merged with the main SIS file and its metadata. This requires additional effort from the SIS writer, something not yet implemented in Ensymble.

Likewise, placing files somewhere else besides the application private directory (i.e. under "\sys\bin" or "\resource") is not yet supported. Adding support for this is fortunately much simpler than adding support for embedded SIS files. Future versions of Ensymble probably will support it.

Currently the only way to generate such complex SIS files is to use the original makesis.exe from Symbian.

[tsharju]

Embedded .SIS support for ensymble would be a really nice addition to already excellent software. Just wanted to let you know that there is more interest for this kind of feature. I don't mean to rush you, but...

- Teemu

[jethro.fn]

OK.

I'll try to add a new command "mergesis" to Ensymble whenever I get enough free time. (Don't hold your breath...)

Note, that although there is currently only one variant of PyS60 for 3rd Edition devices, this will probably not be the case in the future. Any packaged Python software that embeds the PyS60 SIS will need to be released separately for each PyS60 variant: 3rd Edition, 3rd Edition FP1 etc.

[jethro.fn]

Originally Posted by big_pig

An other question:
S60 Python needs to my understanding to have
importable pyc, pyd files to be in the library.This means to be
installed to RESOURCES. So, it is not good enough
to pack these files to an other kind directory
structure. Basic Python itself says it tries to find importable
files from home first and then from library but this is not probably case with S60?

I forgot to mention, that it is indeed possible to include *.py and *.pyc (but not *.pyd) modules within Python application SIS with Ensymble. See thread http://discussion.forum.nokia.com/fo...ad.php?t=98758 for details.