Openembedded.org - User contributions [en]

RAD with FPC/Lazarus

2010-11-11T13:27:10Z

Michaelfung:

The Free Pascal Compiler and the Lazarus IDE are good alternatives for development.

[[File:Lazarus-ide-1.png]]

[[File:Lazarus-ide-2.png]]

[[File:Lazarus-ide-3.png]]

== Install FPC and Lazarus ==

Reference: http://wiki.lazarus.freepascal.org/Setup_Cross_Compile_For_ARM

But the binutils part should be omitted and instead use the binutils built by OE.

== Use OE built binutils ==

Bake the binutils-cross-sdk:

bitbake binutils-cross-sdk

Install the baked ipk, eg. ''binutils-cross-sdk_2.18-r13.1.6_i686-armv6-sdk.ipk'', on the host:

sudo dpkg --install --force-architecture binutils-cross-sdk_2.18-r13.1.6_i686-armv6-sdk.ipk

Create links to the binutils programs:

cd ~/lazarus/fpc/binutils
ln -s /usr/local/angstrom/arm/bin/arm-angstrom-linux-gnueabi-ld ld
ln -s /usr/local/angstrom/arm/bin/arm-angstrom-linux-gnueabi-ar ar
cat <<EOT > as
#!/bin/sh
/usr/local/angstrom/arm/bin/arm-angstrom-linux-gnueabi-as -meabi=5 \$@
EOT
chmod 755 as

Config fpc to use the binutils, edit ''~/.fpc.cfg'' to include:

#IFDEF CPUARM
-XP/home/mike/lazarus/fpc/binutils/

== Get target library files ==

Copy the target library files from OE to the host:

cd /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi
sudo mkdir -p {lib/gcc,usr/lib}
sudo rsync -av 192.168.0.24::oe/build/ok6410-tmp/sysroots/armv6-angstrom-linux-gnueabi/lib/* lib/
sudo rsync -av 192.168.0.24::oe/build/ok6410-tmp/sysroots/armv6-angstrom-linux-gnueabi/usr/lib/* usr/lib/
sudo rsync -av 192.168.0.24::oe/build/ok6410-tmp/sysroots/i686-linux/usr/armv6/lib/gcc/arm-angstrom-linux-gnueabi/4.3.3/* lib/gcc/

Config fpc to use the libraries, edit ''~/.fpc.cfg'' to include:

#IFDEF CPUARM
-Fl/usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/lib
-Fl/usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/usr/lib
-Fl/usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/lib/gcc

[[Category:User]]

File:Lazarus-ide-3.png

2010-11-11T13:24:04Z

Michaelfung:

File:Lazarus-ide-2.png

2010-11-11T13:23:27Z

Michaelfung:

RAD with FPC/Lazarus

2010-11-11T13:22:53Z

Michaelfung:

The Free Pascal Compiler and the Lazarus IDE are good alternatives for development.

[[File:Lazarus-ide-1.png]]

== Install FPC and Lazarus ==

Reference: http://wiki.lazarus.freepascal.org/Setup_Cross_Compile_For_ARM

But the binutils part should be omitted and instead use the binutils built by OE.

== Use OE built binutils ==

Bake the binutils-cross-sdk:

bitbake binutils-cross-sdk

Install the baked ipk, eg. ''binutils-cross-sdk_2.18-r13.1.6_i686-armv6-sdk.ipk'', on the host:

sudo dpkg --install --force-architecture binutils-cross-sdk_2.18-r13.1.6_i686-armv6-sdk.ipk

Create links to the binutils programs:

cd ~/lazarus/fpc/binutils
ln -s /usr/local/angstrom/arm/bin/arm-angstrom-linux-gnueabi-ld ld
ln -s /usr/local/angstrom/arm/bin/arm-angstrom-linux-gnueabi-ar ar
cat <<EOT > as
#!/bin/sh
/usr/local/angstrom/arm/bin/arm-angstrom-linux-gnueabi-as -meabi=5 \$@
EOT
chmod 755 as

Config fpc to use the binutils, edit ''~/.fpc.cfg'' to include:

#IFDEF CPUARM
-XP/home/mike/lazarus/fpc/binutils/

== Get target library files ==

Copy the target library files from OE to the host:

cd /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi
sudo mkdir -p {lib/gcc,usr/lib}
sudo rsync -av 192.168.0.24::oe/build/ok6410-tmp/sysroots/armv6-angstrom-linux-gnueabi/lib/* lib/
sudo rsync -av 192.168.0.24::oe/build/ok6410-tmp/sysroots/armv6-angstrom-linux-gnueabi/usr/lib/* usr/lib/
sudo rsync -av 192.168.0.24::oe/build/ok6410-tmp/sysroots/i686-linux/usr/armv6/lib/gcc/arm-angstrom-linux-gnueabi/4.3.3/* lib/gcc/

Config fpc to use the libraries, edit ''~/.fpc.cfg'' to include:

#IFDEF CPUARM
-Fl/usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/lib
-Fl/usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/usr/lib
-Fl/usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/lib/gcc

File:Lazarus-ide-1.png

2010-11-11T13:19:12Z

Michaelfung:

RAD with FPC/Lazarus

2010-11-11T13:18:03Z

Michaelfung: /* Install FPC and Lazarus */

The Free Pascal Compiler and the Lazarus IDE are good alternatives for development.

== Install FPC and Lazarus ==

Reference: http://wiki.lazarus.freepascal.org/Setup_Cross_Compile_For_ARM

But the binutils part should be omitted and instead use the binutils built by OE.

== Use OE built binutils ==

Bake the binutils-cross-sdk:

bitbake binutils-cross-sdk

Install the baked ipk, eg. ''binutils-cross-sdk_2.18-r13.1.6_i686-armv6-sdk.ipk'', on the host:

sudo dpkg --install --force-architecture binutils-cross-sdk_2.18-r13.1.6_i686-armv6-sdk.ipk

Create links to the binutils programs:

cd ~/lazarus/fpc/binutils
ln -s /usr/local/angstrom/arm/bin/arm-angstrom-linux-gnueabi-ld ld
ln -s /usr/local/angstrom/arm/bin/arm-angstrom-linux-gnueabi-ar ar
cat <<EOT > as
#!/bin/sh
/usr/local/angstrom/arm/bin/arm-angstrom-linux-gnueabi-as -meabi=5 \$@
EOT
chmod 755 as

Config fpc to use the binutils, edit ''~/.fpc.cfg'' to include:

#IFDEF CPUARM
-XP/home/mike/lazarus/fpc/binutils/

== Get target library files ==

Copy the target library files from OE to the host:

cd /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi
sudo mkdir -p {lib/gcc,usr/lib}
sudo rsync -av 192.168.0.24::oe/build/ok6410-tmp/sysroots/armv6-angstrom-linux-gnueabi/lib/* lib/
sudo rsync -av 192.168.0.24::oe/build/ok6410-tmp/sysroots/armv6-angstrom-linux-gnueabi/usr/lib/* usr/lib/
sudo rsync -av 192.168.0.24::oe/build/ok6410-tmp/sysroots/i686-linux/usr/armv6/lib/gcc/arm-angstrom-linux-gnueabi/4.3.3/* lib/gcc/

Config fpc to use the libraries, edit ''~/.fpc.cfg'' to include:

#IFDEF CPUARM
-Fl/usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/lib
-Fl/usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/usr/lib
-Fl/usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/lib/gcc

RAD with FPC/Lazarus

2010-11-11T13:14:57Z

Michaelfung: /* Use OE built binutils */

== Install FPC and Lazarus ==

Reference: http://wiki.lazarus.freepascal.org/Setup_Cross_Compile_For_ARM

But the binutils part should be omitted and instead use the binutils built by OE.

== Use OE built binutils ==

Bake the binutils-cross-sdk:

bitbake binutils-cross-sdk

Install the baked ipk, eg. ''binutils-cross-sdk_2.18-r13.1.6_i686-armv6-sdk.ipk'', on the host:

sudo dpkg --install --force-architecture binutils-cross-sdk_2.18-r13.1.6_i686-armv6-sdk.ipk

Create links to the binutils programs:

cd ~/lazarus/fpc/binutils
ln -s /usr/local/angstrom/arm/bin/arm-angstrom-linux-gnueabi-ld ld
ln -s /usr/local/angstrom/arm/bin/arm-angstrom-linux-gnueabi-ar ar
cat <<EOT > as
#!/bin/sh
/usr/local/angstrom/arm/bin/arm-angstrom-linux-gnueabi-as -meabi=5 \$@
EOT
chmod 755 as

Config fpc to use the binutils, edit ''~/.fpc.cfg'' to include:

#IFDEF CPUARM
-XP/home/mike/lazarus/fpc/binutils/

== Get target library files ==

Copy the target library files from OE to the host:

cd /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi
sudo mkdir -p {lib/gcc,usr/lib}
sudo rsync -av 192.168.0.24::oe/build/ok6410-tmp/sysroots/armv6-angstrom-linux-gnueabi/lib/* lib/
sudo rsync -av 192.168.0.24::oe/build/ok6410-tmp/sysroots/armv6-angstrom-linux-gnueabi/usr/lib/* usr/lib/
sudo rsync -av 192.168.0.24::oe/build/ok6410-tmp/sysroots/i686-linux/usr/armv6/lib/gcc/arm-angstrom-linux-gnueabi/4.3.3/* lib/gcc/

Config fpc to use the libraries, edit ''~/.fpc.cfg'' to include:

#IFDEF CPUARM
-Fl/usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/lib
-Fl/usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/usr/lib
-Fl/usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/lib/gcc

RAD with FPC/Lazarus

2010-11-11T13:13:36Z

Michaelfung: Created page with '== Install FPC and Lazarus == Reference: http://wiki.lazarus.freepascal.org/Setup_Cross_Compile_For_ARM But the binutils part should be omitted and instead use the binutils bui…'

== Install FPC and Lazarus ==

Reference: http://wiki.lazarus.freepascal.org/Setup_Cross_Compile_For_ARM

But the binutils part should be omitted and instead use the binutils built by OE.

== Use OE built binutils ==

Bake the binutils-cross-sdk:

bitbake binutils-cross-sdk

Install the baked ipk, eg. ''binutils-cross-sdk_2.18-r13.1.6_i686-armv6-sdk.ipk'', on the host:

sudo dpkg --install --force-architecture binutils-cross-sdk_2.18-r13.1.6_i686-armv6-sdk.ipk

Create links to the binutils programs:

cd ~/lazarus/fpc/binutils
ln -s /usr/local/angstrom/arm/bin/arm-angstrom-linux-gnueabi-ld ld
ln -s /usr/local/angstrom/arm/bin/arm-angstrom-linux-gnueabi-ar ar
cat <<EOT > as
#!/bin/sh
/usr/local/angstrom/arm/bin/arm-angstrom-linux-gnueabi-as -meabi=5 \$@
EOT

chmod 755 as

Config fpc to use the binutils, edit ''~/.fpc.cfg'' to include:

#IFDEF CPUARM
-XP/home/mike/lazarus/fpc/binutils/

== Get target library files ==

Copy the target library files from OE to the host:

cd /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi
sudo mkdir -p {lib/gcc,usr/lib}
sudo rsync -av 192.168.0.24::oe/build/ok6410-tmp/sysroots/armv6-angstrom-linux-gnueabi/lib/* lib/
sudo rsync -av 192.168.0.24::oe/build/ok6410-tmp/sysroots/armv6-angstrom-linux-gnueabi/usr/lib/* usr/lib/
sudo rsync -av 192.168.0.24::oe/build/ok6410-tmp/sysroots/i686-linux/usr/armv6/lib/gcc/arm-angstrom-linux-gnueabi/4.3.3/* lib/gcc/

Config fpc to use the libraries, edit ''~/.fpc.cfg'' to include:

#IFDEF CPUARM
-Fl/usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/lib
-Fl/usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/usr/lib
-Fl/usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/lib/gcc

Kernel Building

2010-10-21T14:20:44Z

Michaelfung: /* Select kernel version */

== Default Build ==

For a default build, just run:
bitbake virtual/kernel

After done, you can collect the built image from under the deploy folder, for example: <tt>build/tmp/deploy/glibc/images/vmware/bzImage-vmware.bin</tt>.

== Kernel image type ==

What kind of kernel image to build is controlled by the variable <tt>KERNEL_IMAGETYPE</tt>, which is normally defined in the machine config file. For example, build image for u-boot
KERNEL_IMAGETYPE = "uImage"

== Select kernel version ==

FIXME.

== Default configuration ==

The default .config file used is normally placed somewhere under recipes/linux named '''defconfig'''.
You may want to search for it, say for vmware:

find recipes/linux -name "vmware*"

And you find it in:
recipes/linux/linux/vmware/defconfig

== Apply custom patches ==
FIXME

== Customize configuration ==
If you need to customize the kernel configuration, you may run the menuconfig task by:
bitbake -c menuconfig virtual/kernel

'''Note:''' by default these command requires you to run in X Windows. If you want to work in text terminal only, here's a [[How_to_use_bitbake_without_X_Windows|how to]].

== Compile ==
After that, you can compile the kernel by:
bitbake -f -c compile virtual/kernel

== Fine control ==
If you need more control over the configuration and compile process, you can go to the shell by:
bitbake -c devshell virtual/kernel
The build environment will be well setup for you; you can run regular make commands like <tt>make bzImage</tt> ...etc

== Preserving the custom configuration ==
Changes are lost if you remove the tmpdir or do a "<tt>bitbake -c clean virtual/kernel</tt>", so you
may consider replacing the defconfig with it.

[[Category:User]]
[[Category:FAQ]]

Kernel Building

2010-10-21T14:19:25Z

Michaelfung: /* Kernel image type */

== Default Build ==

For a default build, just run:
bitbake virtual/kernel

After done, you can collect the built image from under the deploy folder, for example: <tt>build/tmp/deploy/glibc/images/vmware/bzImage-vmware.bin</tt>.

== Kernel image type ==

What kind of kernel image to build is controlled by the variable <tt>KERNEL_IMAGETYPE</tt>, which is normally defined in the machine config file. For example, build image for u-boot
KERNEL_IMAGETYPE = "uImage"

== Select kernel version ==

To select which kernel version to build, edit config file ??? and set variable ??? to , for example, 2.6.35.

== Default configuration ==

The default .config file used is normally placed somewhere under recipes/linux named '''defconfig'''.
You may want to search for it, say for vmware:

find recipes/linux -name "vmware*"

And you find it in:
recipes/linux/linux/vmware/defconfig

== Apply custom patches ==
FIXME

== Customize configuration ==
If you need to customize the kernel configuration, you may run the menuconfig task by:
bitbake -c menuconfig virtual/kernel

'''Note:''' by default these command requires you to run in X Windows. If you want to work in text terminal only, here's a [[How_to_use_bitbake_without_X_Windows|how to]].

== Compile ==
After that, you can compile the kernel by:
bitbake -f -c compile virtual/kernel

== Fine control ==
If you need more control over the configuration and compile process, you can go to the shell by:
bitbake -c devshell virtual/kernel
The build environment will be well setup for you; you can run regular make commands like <tt>make bzImage</tt> ...etc

== Preserving the custom configuration ==
Changes are lost if you remove the tmpdir or do a "<tt>bitbake -c clean virtual/kernel</tt>", so you
may consider replacing the defconfig with it.

[[Category:User]]
[[Category:FAQ]]

Kernel Building

2010-10-21T08:14:17Z

Michaelfung: /* Kernel patches */

== Default Build ==

For a default build, just run:
bitbake virtual/kernel

After done, you can collect the built image from under the deploy folder, for example: <tt>build/tmp/deploy/glibc/images/vmware/bzImage-vmware.bin</tt>.

== Kernel image type ==

What kind of kernel image to build is controlled by the variable <tt>KERNEL_IMAGETYPE</tt>. For example, build image for u-boot
KERNEL_IMAGETYPE = "uImage"

== Select kernel version ==

To select which kernel version to build, edit config file ??? and set variable ??? to , for example, 2.6.35.

== Default configuration ==

The default .config file used is normally placed somewhere under recipes/linux named '''defconfig'''.
You may want to search for it, say for vmware:

find recipes/linux -name "vmware*"

And you find it in:
recipes/linux/linux/vmware/defconfig

== Apply custom patches ==
FIXME

== Customize configuration ==
If you need to customize the kernel configuration, you may run the menuconfig task by:
bitbake -c menuconfig virtual/kernel

'''Note:''' by default these command requires you to run in X Windows. If you want to work in text terminal only, here's a [[How_to_use_bitbake_without_X_Windows|how to]].

== Compile ==
After that, you can compile the kernel by:
bitbake -f -c compile virtual/kernel

== Fine control ==
If you need more control over the configuration and compile process, you can go to the shell by:
bitbake -c devshell virtual/kernel
The build environment will be well setup for you; you can run regular make commands like <tt>make bzImage</tt> ...etc

== Preserving the custom configuration ==
Changes are lost if you remove the tmpdir or do a "<tt>bitbake -c clean virtual/kernel</tt>", so you
may consider replacing the defconfig with it.

[[Category:User]]
[[Category:FAQ]]

Kernel Building

2010-10-21T08:13:07Z

Michaelfung: /* Kernel configuration */

== Default Build ==

For a default build, just run:
bitbake virtual/kernel

After done, you can collect the built image from under the deploy folder, for example: <tt>build/tmp/deploy/glibc/images/vmware/bzImage-vmware.bin</tt>.

== Kernel image type ==

What kind of kernel image to build is controlled by the variable <tt>KERNEL_IMAGETYPE</tt>. For example, build image for u-boot
KERNEL_IMAGETYPE = "uImage"

== Select kernel version ==

To select which kernel version to build, edit config file ??? and set variable ??? to , for example, 2.6.35.

== Kernel patches ==

Where to place the patch files and how to configure OE to apply them?

== Default configuration ==

The default .config file used is normally placed somewhere under recipes/linux named '''defconfig'''.
You may want to search for it, say for vmware:

find recipes/linux -name "vmware*"

And you find it in:
recipes/linux/linux/vmware/defconfig

== Apply custom patches ==
FIXME

== Customize configuration ==
If you need to customize the kernel configuration, you may run the menuconfig task by:
bitbake -c menuconfig virtual/kernel

'''Note:''' by default these command requires you to run in X Windows. If you want to work in text terminal only, here's a [[How_to_use_bitbake_without_X_Windows|how to]].

== Compile ==
After that, you can compile the kernel by:
bitbake -f -c compile virtual/kernel

== Fine control ==
If you need more control over the configuration and compile process, you can go to the shell by:
bitbake -c devshell virtual/kernel
The build environment will be well setup for you; you can run regular make commands like <tt>make bzImage</tt> ...etc

== Preserving the custom configuration ==
Changes are lost if you remove the tmpdir or do a "<tt>bitbake -c clean virtual/kernel</tt>", so you
may consider replacing the defconfig with it.

[[Category:User]]
[[Category:FAQ]]

Kernel Building

2010-10-21T08:11:19Z

Michaelfung: /* Kernel configuration */

== Default Build ==

For a default build, just run:
bitbake virtual/kernel

After done, you can collect the built image from under the deploy folder, for example: <tt>build/tmp/deploy/glibc/images/vmware/bzImage-vmware.bin</tt>.

== Kernel image type ==

What kind of kernel image to build is controlled by the variable <tt>KERNEL_IMAGETYPE</tt>. For example, build image for u-boot
KERNEL_IMAGETYPE = "uImage"

== Select kernel version ==

To select which kernel version to build, edit config file ??? and set variable ??? to , for example, 2.6.35.

== Kernel patches ==

Where to place the patch files and how to configure OE to apply them?

== Kernel configuration ==

=== Default configuration ===

The default .config file used is normally placed somewhere under recipes/linux named '''defconfig'''.
You may want to search for it, say for vmware:

find recipes/linux -name "vmware*"

And you find it in:
recipes/linux/linux/vmware/defconfig

=== Apply custom patches ===
FIXME

=== Customize configuration ===
If you need to customize the kernel configuration, you may run the menuconfig task by:
bitbake -c menuconfig virtual/kernel

'''Note:''' by default these command requires you to run in X Windows. If you want to work in text terminal only, here's a [[How_to_use_bitbake_without_X_Windows|how to]].

=== Compile ===
After that, you can compile the kernel by:
bitbake -f -c compile virtual/kernel

=== Fine control ===
If you need more control over the configuration and compile process, you can go to the shell by:
bitbake -c devshell virtual/kernel
The build environment will be well setup for you; you can run regular make commands like <tt>make bzImage</tt> ...etc

=== Preserving the custom configuration ===
Changes are lost if you remove the tmpdir or do a "<tt>bitbake -c clean virtual/kernel</tt>", so you
may consider replacing the defconfig with it.

[[Category:User]]
[[Category:FAQ]]

Kernel Building

2010-10-20T14:56:40Z

Michaelfung: /* Kernel configuration */

Kernel Building

2010-10-20T14:54:42Z

Michaelfung: /* Kernel image type */

Kernel Building

2010-10-20T14:43:51Z

Michaelfung: /* Custom config */

Kernel Building

2010-10-20T14:42:22Z

Michaelfung: /* Default Build */

Kernel Building

2010-10-20T14:37:57Z

Michaelfung: /* Kernel configuration */

== Default Build ==

For a default build, just run:
bitbake virtual/kernel

After done, you can collect the built image from under the deploy folder, for example: <tt>build/tmp/deploy/glibc/images/vmware/bzImage-vmware.bin</tt>.

== Kernel configuration ==

The default .config file used is placed in ???/defconfig.

== Custom config ==

If you need to customize the kernel configuration, run the menuconfig task by:
bitbake -c menuconfig virtual/kernel

'''Note:''' by default this command requires you to run in X Windows.

After that, you can compile the kernel by:
bitbake -f -c compile virtual/kernel

[[Category:User]]

Kernel Building

2010-10-20T14:29:12Z

Michaelfung: /* Custom config */

== Default Build ==

For a default build, just run:
bitbake virtual/kernel

After done, you can collect the built image from under the deploy folder, for example: <tt>build/tmp/deploy/glibc/images/vmware/bzImage-vmware.bin</tt>.

== Kernel configuration ==

The default .config file used is placed in ???.

== Custom config ==

If you need to customize the kernel configuration, run the menuconfig task by:
bitbake -c menuconfig virtual/kernel

'''Note:''' by default this command requires you to run in X Windows.

After that, you can compile the kernel by:
bitbake -f -c compile virtual/kernel

[[Category:User]]

Kernel Building

2010-10-20T14:28:06Z

Michaelfung: /* Custom config */

== Default Build ==

For a default build, just run:
bitbake virtual/kernel

After done, you can collect the built image from under the deploy folder, for example: <tt>build/tmp/deploy/glibc/images/vmware/bzImage-vmware.bin</tt>.

== Kernel configuration ==

The default .config file used is placed in ???.

== Custom config ==

If you need to customize the kernel configuration, run the menuconfig task by:
bitbake -c menuconfig virtual/kernel

'''Note:''' by default this command requires you to run in X Windows.

After that, you can compile the kernel by:
bitbake -f -c compile virtual/kernel

Kernel Building

2010-10-20T14:25:19Z

Michaelfung: /* Build */

== Default Build ==

For a default build, just run:
bitbake virtual/kernel

After done, you can collect the built image from under the deploy folder, for example: <tt>build/tmp/deploy/glibc/images/vmware/bzImage-vmware.bin</tt>.

== Kernel configuration ==

The default .config file used is placed in ???.

== Custom config ==

If you need to customize the kernel configuration, run the menuconfig task by:
bitbake -c menuconfig virtual/kernel

'''Note:''' by default this command requires you to run in X Windows.

Kernel Building

2010-10-20T14:24:24Z

Michaelfung: /* Build */

== Build ==

For a default build, just run:
bitbake virtual/kernel

After done, you can collect the built image from under the deploy folder, for example: <tt>build/tmp/deploy/glibc/images/vmware/bzImage-vmware.bin</tt>.

== Kernel configuration ==

The default .config file used is placed in ???.

== Custom config ==

If you need to customize the kernel configuration, run the menuconfig task by:
bitbake -c menuconfig virtual/kernel

'''Note:''' by default this command requires you to run in X Windows.

Kernel Building

2010-10-20T14:20:58Z

Michaelfung: /* Custom config */

== Build ==

For fresh install, just run:
bitbake virtual/kernel

After done, you can collect the built image from under the deploy folder, for example: <tt>build/tmp/deploy/glibc/images/vmware/bzImage-vmware.bin</tt>.

== Custom config ==

If you need to customize the kernel configuration, run the menuconfig task by:
bitbake -c menuconfig virtual/kernel

'''Note:''' by default this command requires you to run in X Windows.

Kernel Building

2010-10-20T14:18:10Z

Michaelfung: Created page with '== Build == For fresh install, just run: bitbake virtual/kernel After done, you can collect the built image from under the deploy folder, for example: <tt>build/tmp/deploy/gl…'

== Build ==

For fresh install, just run:
bitbake virtual/kernel

After done, you can collect the built image from under the deploy folder, for example: <tt>build/tmp/deploy/glibc/images/vmware/bzImage-vmware.bin</tt>.

== Custom config ==

If you need to customize the kernel configuration with menuconfig, do:
bitbake -c menuconfig virtual/kernel

'''Note:''' by default that command requires you to run in X Windows.