Discussion Board

Results 1 to 4 of 4
  1. #1
    Registered User jeffreyRyang's Avatar
    Join Date
    Oct 2008
    Posts
    25
    Hi Guys

    There is a problem about Embedded SIS in my project. Assumption I have 2 SISs named A.sis and B.sis, they all use glib.sis for Open C stuff. The glib.sis is not installed separately, it is embedded in A.sis and B.sis. If there is not glib.sis in the target device, it would be installed with A.sis(Assumption I install A.sis first, and then B.sis). The following installed sis doesn't install glib.sis, all because I use a function "package", it will check whether your specific sis is installed or not. I also declare dependency on glib.sis which A.sis and B.sis depend. Here the problem comes. When I remove A.sis, the glib.sis will be removed together with A.sis, even though B.sis depends on it, so that the problem causes that the B cannot start because of leak of necessary lib. On the help of S60 3rd FP1, Nokia says "An embedded SIS file is not removed if another installed component has declared a dependency upon it". I don't think it works.

    I don't know which side is wrong, Nokia or Me. Please help me. Thank you very much.

  2. #2
    Nokia Developer Moderator wizard_hu_'s Avatar
    Join Date
    Feb 2006
    Location
    Mallorca, Holiday
    Posts
    27,683
    Using such conditional parts (package or exists) in .pkg-s often result in strange outcome.
    What happens if you simply try unconditionally embedding glib.sis into both a and b, then embed them in your main installer file?

  3. #3
    Registered User Sorcery-ltd's Avatar
    Join Date
    Dec 2006
    Posts
    2,280
    This is a known bug in S60 3rd Edition right up to late firmware builds for FP1 devices if I remember correctly. The dependency checking doesn't work for embedded SIS files, it's not your fault.

    There is a workaround (which I think was documented on the Psiloc blog) involving copying the SIS file to the device rather than embedding it and then running a simple installer program to launch a separate install for it. This is just to avoid the user having to install two packages separately but that is effectively what it is doing.

    As far as I know this bug is fixed on all FP2 and later devices.

    Sorcery

  4. #4
    Registered User jeffreyRyang's Avatar
    Join Date
    Oct 2008
    Posts
    25
    Thank you very much. I am going to do it in an alternative way. The workaround you told me is good choice. It is to my surprise that nokia made this obvious mistake. There are so many devices with S60 FP1 in the world.

Similar Threads

  1. User abort of installation with embedded SIS file and FILERUN option.
    By tim_felser in forum Symbian Tools & SDKs
    Replies: 0
    Last Post: 2008-07-14, 12:32
  2. Replies: 0
    Last Post: 2008-02-14, 10:27
  3. Replies: 6
    Last Post: 2007-03-01, 18:15
  4. Replies: 0
    Last Post: 2006-03-16, 16:50
  5. Embedded SIS & App.Manager's "View Details"
    By vtatti in forum Symbian C++
    Replies: 1
    Last Post: 2004-09-30, 15:01

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Nokia Developer aims to help you create apps and publish them so you can connect with users around the world.

京ICP备05048969号  © Copyright Nokia 2013 All rights reserved