Sense and simplicity

There is an interesting phenomenon in the high-tech world: the simpler something is to use on the outside, the more horribly complex it is on the inside! A user does not need to know about that complexity, but a developer does. That is what I am looking for.

android build system

android’s build system is complex but very well designed, it is very convenient once you know where to start, here is some tips:

1. the first step, enter to android root directory, and run
   . build/envsetup.sh
   then run
   help
   to get some summary information
2. run
   lunch 1
   to set build environment
   the default item 1 is generic-eng, you can add customized item via add_lunch_combo, eg.
   add_lunch_combo mojo-eng
   to add item for mojo product with variant as engineer, and run
   lunch
   to choose the lunch items
3. run
   make
   to build the system
4. if you do not want to build the whole system, given the make a target name, such as, systemimage-nodeps, userdataimage-nodeps, etc. all the target name is defined in build/core/Makefile. you can also use mm or mmm function to achieve this, example, run
   mmm packages/apps/Launcher
   to build Launcher application, enter packages/apps/Launcher and run
   mm
   do the same thing.
5. some useful function, croot, godir, cd $OUT, cgrep, gettop,
   get_build_var
6. run emulator
   emulator&
   run ddms
   ddms&
7. see detail in build/core/build-system.html

the journey to Lua

I am on the journey to Lua.

1. go to http://www.lua.org/, and take a quick look at it
2. read the reference manual carefully
3. download the source code, and build Lua with the help of faq
4. setup Lua SDK, I think the KeplerProject is a good choice, you need to setup LuaRocks first though. There is also an all-in-one solution LuaForWindows.
5. setup Lua IDE, the LuaEdit is a good choice, but I like SciTE.
6. enjoy yourself to write and debug your own Lua code.

Hello world!

Welcome to my site
to be continue…