Discussion Board

Results 1 to 3 of 3
  1. #1
    Registered User
    Join Date
    Jul 2007

    Angry Automated Build with Several Build Configurations

    Dear experts,

    The straightforwardness(*) of the S60 API unfortunately requires changes in source code, MMP and PKG file based on an individual basis for each of the supported phone devices. Since my application runs on different phone which require different build configurations (e.g. use RRSensorAPI.lib or not, use sensrvclient.lib or not, link S60 3rd FP1 or FP2 libraries) I'm interested in finding out how an automated build system with configuration management is ought to be created.

    Unfortunately, the S60 SDK help mentions the use of '#ifdef' statements in the MMP file, but doesn neither explain other statements nor the scope of those definitions. The only suitable way I found was a definition of an environment variable which is checked in the MMP file. Unfortunately, this way seems not to be usable for the PKG file! There is a way to use IF(...) ... ENDIF, but I have no access to the environment variables there.

    The old-fashioned way would be a Makefile which dynamically generates the MMP and PKG files and starts the compile process for each of the configurations. This wouldn't make the process of modifying the MMP file for both interactive and automated build much easier.

    How do you ease your pain to maintain a dozen of different configurations?


    (*) E.g. E66 is FP1-based but requires the FP2 accelerator API, N96 is FP2-based but requires the FP1 autofocus API. How do you solve that?

  2. #2
    Registered User
    Join Date
    Jul 2007

    Re: Automated Build with Several Build Configurations

    Just noticed that the way to create a Build Configuration for each of my supported phones isn't suitable either, since I can't define as many configurations as I want to. So, there is no way to differentiate between the confoguration of a N96 and a 'real' FP2 phone.

  3. #3
    Nokia Developer Moderator
    Join Date
    Feb 2006
    Oslo, Norway

    Re: Automated Build with Several Build Configurations

    We have separate "group" and "sis" folder for each builds, that is how. Remember that bld.inf and .mmp-s are pre-processed, thus you do not have to replicate everything, just something like
    // groupN96\HelloWorldN96.mmp
    #define __N96__
    MACRO __N96__
    #include "..\group\HelloWorld.mmp"

Similar Threads

  1. Automated build for Jar and Jad
    By vipinmenontp in forum Mobile Java General
    Replies: 2
    Last Post: 2008-06-17, 07:48
  2. Carbide.C++ Missing Active Build Configurations?
    By stellion in forum Carbide.c++ IDE and plug-ins (Closed)
    Replies: 5
    Last Post: 2007-04-27, 10:06
  3. Build configurations in Carbide.c++ Developer Edition
    By cartman_ume in forum Carbide.c++ IDE and plug-ins (Closed)
    Replies: 4
    Last Post: 2007-04-12, 22:27
  4. Add new build configurations to existing project for new SDKs in Carbide.c++. How?
    By dschwabe in forum Carbide.c++ IDE and plug-ins (Closed)
    Replies: 1
    Last Post: 2006-11-09, 04:32
  5. armi build not working
    By lemody in forum Symbian
    Replies: 0
    Last Post: 2003-06-14, 15:04

Posting Permissions

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