Building a WinCE Runtime Image from command line

-
Step 1: Setting up the environment

 _WINCEROOT: This variable should point to the location where your windows ce folder is present

SET WINCEROOT= C:\WINCE700

 _OSDESIGNDIR: Should point to the OS Design Directory

SET _OSDESIGNDIR = %_WINCEROOT_%\OSDESIGNS\Test


 _OSDESIGN: This variable should point to the OS Design xml file

SET _OSDESIGN = %_WINCEROOT_%\OSDesigns\Test\Test\Test.xml

 Finally we have to set the _OSDESIGNCONFIG environmental variable

SET _OSDESIGNCONFIG = Test X86  Release

 To generate a batch file which sets up the environment we have to use utility provided by Platform Builder "PBXmlUtils' and pass the above environmental variables you set as arguments to it.

Eg; C:\Program Files (x86) \Microsoft Platform Builder \7.00\cepb\ideVS\PBXmlUtils.exe /getbuildenv /workspace "%_OSDESIGN%" /config "%_OSDESIGNCONFIG%" > Env.bat

Now you have to open a command prompt and run this batch file to set the environment for build

Step 2: Build OS (bldemo -c)

The build os is the first and longest step of the build process. Fortunately this step is already completed once the platform builder is installed. The output libraries and .dll files resulting from this step are included with platform builder - that's why size of each CPU Architecture will be in giga bytes.

Step 3: Sysgen OS (bldemo -q)

Sysgen OS step links together the libraries created during the Build OS step. It manages link dependencies and select only the components that are needed for the Operating System

Comments

Post a Comment

Popular posts from this blog

bb.utils.contains yocto

-
Image
bb.utils.contains  is most commonly used function in Yocto. grep in poky directory returned with 696 count. $ grep -nr 'bb.utils.contains' poky/ | wc -l 696 It's definition is present in 'poky/bitbake/lib/bb/utils.py' file This function returns third argument if the second argument is subset of the first argument else returns fourth argument Let's take an example to understand this. You can see from the above screenshot, when the second argument is a subset of first argument, "present" was returned, else "notpresent" was returned We can also use bb.utils.contains inside if loop. This we can use inside a recipe. if ${@bb.utils.contains('SOMEFLAG','NEWVALUE3','true','false',d)}; then     FOO = 'HELLO' fi
Read more

Difference between RDEPENDS and DEPENDS in Yocto

-
We normally observe these two (RDEPENDS and DEPENDS) whenever we open any recipe. What should we choose when we write our own recipe. DEPENDS -> Build Time Dependency RDEPENDS -> Run Time Dependency DEPENDS: When a recipe 'A' is DEPENDS on recipe 'B'. In this case, Bitbake first builds recipe 'B' and then recipe 'A' E.g. You need 'dbus' to be built before 'wpa_supplicant'. RDEPENDS: When a recipe 'A' is RDEPENDS on recipe 'B'. In this case, Bitbake deploys 'B' on the target system when it deploys 'A'.  E.g. 'perf' RDEPENDS on 'bash' In other words, DEPENDS are those set of packages that should be available while building package, whereas RDEPENDS are set of packages that should be available during execution of the program.
Read more

PR, PN and PV Variable in Yocto

-
PN : Represents the name of the recipe. The name is usually extracted from the recipe file name. PR:  Represents the revision of the recipe. Default value for this revision is "r0". Subsequent revisions of the recipe conventionally will have "r1", "r2" and so on. PV:  Represents the version of the recipe. Normally extracted from the recipe file name. For example: ffmpeg_3.4.2.bb recipe. ${PN} : ffmpeg ${PV} : 3.4.2
Read more