View source for Development Environment
From Openmoko
You do not have permission to edit this page, for the following reasons:
You can view and copy the source of this page:
Template used on this page:
Return to Development Environment.
You do not have permission to edit this page, for the following reasons:
You can view and copy the source of this page:
Template used on this page:
Return to Development Environment.
Languages: |
English • العربية • Български • Česky • Dansk • Deutsch • Esperanto • Eesti • Español • فارسی • Suomi • Français • עברית • Magyar • Italiano • 한국어 • Nederlands • Norsk (bokmål) • Polski • Português • Română • Русский • Svenska • Slovenčina • Українська • 中文(中国大陆) • 中文(台灣) • Euskara • Català |
If you want to create a new application, you might want to look at Toolchain first. However, if the dependency is complex or you want to modify something already in system, currently the easiest way to go is still using OpenEmbedded.
After setting up the OE environment, making it build the latest component of Openmoko is a must to avoid duplicated work. Refer to How to enable autorev to find out how to do it. Building for the first time will take a lot of time and occupy big disk space, but after that it will be reasonable. You will also need to remove the
INHERIT += "rm_work
line in your local.conf if it exists.
Now, for example, if you want to modify openmoko-sample2, you can do this to build it first:
bitbake openmoko-sample2
After that:
bitbake openmoko-sample2 -c devshell
You will be dropped to a shell that the environment is set to build the package. After the modification, usually a simple `make' will do the trick. You should be able to find the new binary under a hidden .libs directory if this package uses autotools.
We could make modification and manage it by `quilt'.
$ # no need to mkdir patches. already exists. $ quilt new foo.patch $ quilt add to_be_changed.c $ vi to_be_changed.c <coding monkey is working...> $ make $ scp foobar neo: # copy it to neo <test... wow it works> $ quilt refresh $ cp -r patches ~/miracle # keep it somewhere
Multiple ways to do this: