|
Tigris.org
Open Source Software Engineering Tools
|
|
|
IntroductionIn version 0.8.7, lightblue introduced a new build system which is based on GNU MAKE. The build process has been simplified again. By using this new system, you can
Table of contentsSetup the environmentUse the build system Build examples step by step Build examples in VS.NET IDE Setup the environmentBefore compiling lightblue, we need to install required compiler, SDK and tools. Below is a list of softwares that are needed:
Use the build systemThe new build system is designed for simplicity, so everything you need is: Configiure the tool path Generate the makefile Build the project Re generate the makefile Configure the tool pathIn the root directory of the lightblue project directory, there is a file called lb_env.cmd which contains all tool settings used by the build system. Currently the only variable that you should change is %make% which is set to the absolute path to the GNU make executable "make.exe". By default, this variable is set to %lb_root%\utils\make.exe which is a native win32 build of GNU MAKE 3.8.0 included in the package. You can change the %make% variable to the path you want the build system to use, for example, the one from the cygwin package. Also, the %lb_root% is automatically set to "%~dp0" which is expended to absolute path of the directory where lb_env.cmd resides.After the lb_env.cmd is updated correctly, there are compiler specific settings in following files: configure\cfg\rvct.cfg (for the real view 2.2 compiler) configure\cfg\gnuarm.cfg (for the GNU ARM compiler) confgure\cfg\gnuvc.cfg (for the Visual C++) Only update the compiler settings that are used. Usually, these files contain settings of the path to the compiler, linker and which BREW SDK is used. Check the comments in the file before changing them. One thing you have to awared is that these files are actually makefiles, so never put an '\' at the end of a line when you are writing an directory. Otherwise, weird errors will occur. Generate the makefileBefore generate the makefiles , please make sure that all tool settings are set correctly by previous step. In the "build" directory, call makegen.bat will generate all makefiles. After a sucessful generation which might take for a while, several batch files and directories are generated in the "build" directory, for example: make_rvct_runtime.bat rvct_runtime\ make_rvct_examples.bat rvct_examples\ Please check the next section for the usage of these batch files. Build the projectEach generated batch files is a shortcut of launching the actually makefile which resides in the sub directory. For example, make_rvct_runtime.bat will call makefile in rvct_runtime directory. All parameters are passed through to the makefile so you can indicate target to build in the command line, for example:"make_rvct_runtime.bat all" will build the "all" target in the makefile. Currently, two targets are implemented for each makefile: all -- to build the component clean -- clean the output and intermedia files. Every batch file has the name pattern of: build_<toolset>_<component>.bat. The <toolset> part indicates the toolset (the compiler and SDK combination) used, they could be: rvct -- the real view ARM compiler (ARM only) gnuarm -- the GNU ARM compiler (ARM only) vc -- Visual C++ (simulator only) Each tool set has its own configuration file in the "configure\cfg" with the same file name as the tool set and the extension of "cfg". The <component> part indicates which component to build: runtime -- the runtime (Must be built before other component could be built) examples -- the examples (Contains 5+ examples) You can easily determine which batch file to call by its name. For instance, if you are using the Realview ARM compiler and want to build the runtime component, you should call "make_rvct_runtime.bat" . The "runtime" component is always the first component to build which is depend by almost all other components. It is also a good idea to build the "examples" component right after the "runtime" component , so that you can determine the "runtime" is built correctly. Re generate the makefileEach time you move the lightblue project to a different directory or change the lb_env.cmd or cfg files in the configure\cfg directory, you need to re generated all the makefiles to reflect the changes. However, no regeneration is needed if you just added or removed some source files in the component.Build examples step by stepBelow is a step by step instruction of how to build the lightblue runtime and examples using the new build system. Both ARM and X86 emulator code could be generated.
After a successful build, following files and directories are created: bin\g++\entryptr.o bin\rv22\entryptr.o bin\vc\entryptr.obj build\out\g++\* -- The example programs compiled by the GNU ARM compiler. build\out\vc\* -- The example programs compiled by the Real View ARM Compiler. build\out\gnuarm\* -- The example programs compiled by the Visual C++ Compiler. Now you can test the example programs in the simulator or the handset: For the simulator, you just change the applet dir of the simulator to "build\out\vc". For the handset, beside the mifs and the mod files, you also need a signature files for each example programs. Install them to the handset like any other brew applications. If you prefer to compile using Visual studio IDE, please continue in the next section Build examples in VS.NET IDEBelow is a step by step instruction of how to build and run lightblue examples in the BREW emulator:
Notes: The supplied sln is in Visual Studio.net 2003 format, previous version of VS.net might not be able to open it. To run and debug the example programs on the simulator, you have to do following steps:
After the runtime and the examples are compiled and tested on your system, it is time to build your own programs using the lightblue library. |
|||||||||||||||||||||||||||||
