×

Discussion Board

Results 1 to 5 of 5
  1. #1
    Registered User
    Join Date
    Apr 2006
    Location
    Prague, The Czech Republic
    Posts
    142

    Raptor (SBSv2) build problem with a large project and Symbian Belle 0.6 SDK

    Hello all,

    I am currently trying to builde a huge application (over 2 M lines of code) with ARMv5 compiler using Raptor + Carbide.c++ 3.4. The SDKs are Symbian Belle 0.6 and Symbian Anna.

    I am building it regularly it with older Nokia SDKs and SBSv1 (ABLD), for S60 3rd Ed, 5th Ed and Symbian Anna. The ABLD build runs well, though I had to modify the files cl_bpabi.pm and set DATA_SEGMENT_START to 0x400000. The .exe links successfully with ABLD.

    Nevertheless, when attempting to build it with Raptor, I get the following errors during the final linking stage:

    Code:
    Error: L6221E: Load region LR_1 overlaps with Load region LR_2.
    Error: L6221E: Execution region ER_RO overlaps with Execution region ER_RW.
    Error: L6221E: Execution region ER_RO overlaps with Execution region ER_ZI.
    The compilation itself is OK and, but the linker step fails. It seems that armlink.exe receives bad parameters regarding the EXE layout. The application is huge and thus contains a lot of symbols etc.

    I tried to fool around with the Raptor configuration (rvct.xml), to alter the flags to armlink.exe, but to no avail. I dug around the makefiles generated by ABLD and Raptor, experimented with their alterations, to no avail.

    Can anybody help me?

    Note that there was a similar problem on ABLD (see the thread http://www.developer.nokia.com/Commu...ot-yet-created), but it could be solved by tinkering with cl_bpabi.pm.

    There is no direct equivalent of this file in SBSv2, though. Only rvct.xml, where I didn't find the real magic.

    Should I try altering CODE_SEGMENT_START? Never done that before.

  2. #2
    Super Contributor
    Join Date
    Mar 2004
    Location
    Singapore
    Posts
    9,968

    Re: Raptor (SBSv2) build problem with a large project and Symbian Belle 0.6 SDK

    You can try changing the .config files but from my past experiance i suggest you convert parts of the code to dll.

  3. #3
    Registered User
    Join Date
    Apr 2006
    Location
    Prague, The Czech Republic
    Posts
    142

    Re: Raptor (SBSv2) build problem with a large project and Symbian Belle 0.6 SDK

    Quote Originally Posted by skumar_rao View Post
    You can try changing the .config files but from my past experiance i suggest you convert parts of the code to dll.
    That would be a logical thing to do, from the purely technical point of view. But it is rendered impossible by the (crazy) Symbian security model. The libraries are under development, and a DLL needs all the capabilities of the EXE which loads it. I can't imagine constantly re-signing > 20 DLLs for several Symbian platforms - it would be unmanageable and also very expensive.

  4. #4
    Nokia Developer Moderator
    Join Date
    Feb 2006
    Location
    Oslo, Norway
    Posts
    28,689

    Re: Raptor (SBSv2) build problem with a large project and Symbian Belle 0.6 SDK

    While I would like to see the 'proper' solution (for completeness reasons), from the signing point of view there is no difference: you sign a .sis/x file, and a single .sis/x file can deploy an arbitrary amount of .exe-s and .dll-s.
    Code split as a workaround for compiler/toolchain limitations will not result in re-usable components anyway, so there is no need to provide separate installables (testing them would not be easy either).

  5. #5
    Registered User
    Join Date
    Apr 2006
    Location
    Prague, The Czech Republic
    Posts
    142

    Re: Raptor (SBSv2) build problem with a large project and Symbian Belle 0.6 SDK

    Quote Originally Posted by wizard_hu_ View Post
    While I would like to see the 'proper' solution (for completeness reasons), from the signing point of view there is no difference: you sign a .sis/x file, and a single .sis/x file can deploy an arbitrary amount of .exe-s and .dll-s.
    Code split as a workaround for compiler/toolchain limitations will not result in re-usable components anyway, so there is no need to provide separate installables (testing them would not be easy either).
    I would like to see it as well. The ARM compilation toolchain has many properties that can be set. So I think that the EXE sectioning must be tweakable.

Similar Threads

  1. Raptor 2.17.4 release (raptor is the sbs build tool)
    By tnmurphy in forum Symbian Tools & SDKs
    Replies: 0
    Last Post: 2011-12-15, 11:04
  2. SBSv2 build log
    By vincent4443 in forum [Archived] Qt SDKs and Tools
    Replies: 3
    Last Post: 2011-11-22, 14:40
  3. SBSv2 mifconv problem in Symbian^3 sdk
    By nshenoy in forum Symbian Tools & SDKs
    Replies: 13
    Last Post: 2011-03-15, 15:34
  4. Symbian^3 SDK 0.8 build Qt 4.7 with sbs/raptor failed
    By cavendishqi in forum Tools and SDK Feedback (Closed)
    Replies: 9
    Last Post: 2010-12-31, 14:06

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
×