Using the EDGELIB Builder tool

Home / Support / Tutorials / Using the EDGELIB Builder tool

The EDGELIB Builder tool (formerly called Edge IDE) for Windows desktop has a user friendly interface and is able to automatically build project files using external commandline programs for multiple platforms.

The EDGELIB Builder tool is still in beta stage.

Currently EDGELIB Builder supports the following platforms:

  • Google Android
  • Antix Game Player
  • Windows Mobile 2002, 2003 and 5.0
  • Symbian Series 60 first and third editions
  • Symbian Series 80 first and second edition
  • Symbian Series 90
  • Symbian UIQ 2.1 and UIQ 3.0
  • Windows desktop using Visual C++ 6.0 and Visual Studio 2005.
  • GP2X

The tool can be expanded with additional platforms by adding ini files to the platform folder.

Setting up EDGELIB Builder

After the SDK has been installed, the EDGELIB Builder tool can be found inside the tools folder. It contains a main INI file EdgeBuilder.ini and several INI files inside the platforms folder. Before starting the program, open these INI files to correctly set all path locations. First let's begin with EdgeBuilder.ini which contains the path to the EDGELIB SDK:

EdgeBuilder.ini (18 lines)
  1. # Edge IDE main configuration file
  2. # --------------------------------
  3.  
  4. # General options
  5. bldtmpfile       = "C:\edgeide_bldtmp_%appuid%"
  6.  
  7. # Paths
  8. edgepath         = "c:\projects\edge"
  9. incpath          = "%edgepath%\include"
  10.  
  11. # Macro list
  12. macrodef         = "__EDGEIDE__"
  13. macrodef         = "__EDGEBUILDER__"
  14.  
  15. # Configuration notices, remove this section when done editing
  16. notice           = "EDGELIB path is set to default value: c:\projects\edge"
  17. notice           = "Change default values by editing EdgeBuilder.ini"
  18. notice           = "Remove this notice by removing the notice section at the bottom of EdgeBuilder.ini"

Set the edgepath setting to the folder where EDGELIB has been installed and remove the notices section. After that, open the platforms folder and open each INI file. Set the paths to where the SDKs have been installed and remove the notices section as well.

Creating projects

Creating projects is easy, start the EDGELIB Builder tool and click on file -> new project. After creating a new project, right click on the source or header files folder to add existing source code files to the tree. Create source files with a text editor, or import the code base of a project written in Visual C++. When all files have been added, select the target platform and choose build from the menu.

Change project properties

Right click on the project name, select properties or access the project properties screen from project -> properties in the menu. You can change the name of the project and the unique identification number used by Symbian. When it is not defined, it takes the default value (0x10205d9d).

Adding additional include or library paths

To add extra include or library paths for a project, open the path configuration window through project -> Library/include paths. It's possible to add, edit and remove paths or change the priority of each path in the list.

Adding icons

It's also possible to add a program icon for every platform, except GP2X. This icon can have various sizes, for example for Windows Mobile you can have both an 16x16 pixel icon and an 32x32 pixel icon. Icons can be added by creating a new folder named "Icons" in the resource root. Add BMP, GIF or PNG files to generate the icon image. The transparent color for bitmap files is RGB 255, 0, 255.

Installation files

EDGELIB Builder supports building installation (.sis) files for all supported Symbian versions. Add installation files by creating a resource folder named "install". Create a folder structure if the installation files are separated into several paths. The application executable doesn't need to be added, it will be added to the installation automatically. Build the installation file by selecting it in the build menu.

Editing project files manually

It's also possible to create and edit project files with a text editor. These project files have an INI-file structure and can be easily edited. Here is a sample project file for an hello world project:

helloworld.epj (33 lines)
  1. # EDGELIB project file (edit at your own risk)
  2. # Copyright (c) 2005-2017 Elements Interactive Mobile B.V.
  3. # http://www.edgelib.com
  4. # -----------------------------------------
  5.  
  6. # General
  7. projectname = "Hello World"
  8. appuid = "0x10205d9d"
  9.  
  10. # Project tree
  11. sourcepath = "code"
  12.     sourcefile = "..\code\framework.cpp"
  13.     sourcefile = "..\code\util.cpp"
  14. endpath
  15. sourcefile = "..\code\hello.cpp"
  16.  
  17. headerpath = "include"
  18.     headerfile = "..\include\framework.h"
  19.     headerfile = "..\include\util.h"
  20. endpath
  21.  
  22. resourcepath = "icons"
  23.     resourcefile = "..\res\icon16.bmp"
  24.     resourcefile = "..\res\icon32.bmp"
  25. endpath
  26. resourcepath = "install"
  27.     resourcepath = "res"
  28.         resourcefile = "..\res\game.epk"
  29.     endpath
  30. endpath
  31.  
  32. # Project environment
  33. incpath = "..\include"

The projectname specifies the name of the project and executable. Using tabs in the project tree isn't necessary, but is recommended for clarity. The project environment contains environment values which will be interpreted by the compiler. For example, incpath defines an extra include path to search for header files when compiling. These environment values can be defined in EdgeBuilder.ini, a project file and each platform file. When compiling, the environment of all these files are combined and passed to the compiler.

Latest forum posts