Everything but the final step to .sis

Login to reply to this topic.
Sun, 2006-01-29 11:39
djgtram
Joined: 2004-08-19
 Forum posts: 112
Hello,

I've just updated my SDK from edition 1 to 2 and I'm trying to reconstruct my earlier ways of operation. As of now, everything works but the final step of creating an ARMI UREL .sis. As it seems, one rather important file the .pkg file would call for, Application.app, can't be found in the location it is supposed to be in, namely, ...\data\z\system\apps\Application. The file is generated without any error message and it resides in ...\release\armi\urel\ . How is it supposed to be copied into the first directory for Makesis to be picked up and what might be the reason for not being copied in my case?

If it matters, I don't use any IDE, just plain old command line.

Thanks,
Gábor

Bye,
Gábor

Mon, 2006-01-30 16:25
alh
Joined: 2004-11-29
 Forum posts: 1233
Re: Everything but the final step to .sis
All current SDKs I have touched has generated its executable output into \epoc32\release\armi\urel for release (and \epoc32\release\wins(cw)\udeb for emulator), this is perfectly normal.

You should change your .pkg file to get it from this location instead.
 
Tue, 2006-01-31 23:10
djgtram
Joined: 2004-08-19
 Forum posts: 112
Re: Everything but the final step to .sis
Thanks, that was a nice idea. It never occured to me to put absolute paths into the .pkg file (it was not required with the previous SDK). It works now. The only remaining problem with the new SDK is the Unicode trouble with the help building process, as I described it in another thread...

Thanks,
  Gábor

Bye,
Gábor

 
Wed, 2006-02-01 17:11
alh
Joined: 2004-11-29
 Forum posts: 1233
Re: Everything but the final step to .sis
Well... You don't have to have it absolute. It can still be relative.

I didn't mean that you should make the path absolute, just that the file is now generated to \epoc32\release\armi\urel\ instead of \epoc32\data\z\system\apps\

\epoc32\release\<platform>\<urel|udeb>  is the standard place all current SDK uses for generating its output, therefore you should rather change your pkg, then try to copy your .app-file to a nonstandard location just because you don't want to change your .pkg...

If you then choose to point out this location with a relative path or an absolute path in your .pkg is entirely up to you.


EDITNOTE: I havn't used any SDK wich ouputs to \epoc32\data\z\system\apps\, but I have mainly used 7.0 and above. From your post it sounded like your old SDK generated its output there though
 
Wed, 2006-02-01 20:04
djgtram
Joined: 2004-08-19
 Forum posts: 112
Re: Everything but the final step to .sis
No, I wasn't that clear, it wasn't really the difference between relative and absolute, but to use any path at all. With my earlier .pkg file, I just specified Application.rNN, .app, .aif and .mbm and other related files, not even thinking about paths, yet it automagically worked. Not a big difference in hindsight but, as I was used to that way, it didn't even cross my mind to do it differently. I'm lost with these SDK version differences, I don't know exactly which it was but it named its directory 6.1, so this might be a tell-tale sign. As I was working on applications that should work back to Nokia 6600 and even earlier, it wasn't a problem for me.

Bye,
Gábor

 
  • Login to reply to this topic.