Android system development (4) -- Autotools, androidautotools

Android system development (4) -- Autotools, androidautotools
Composition of Autotools

1. autoscan

Autoscan is used to scan the source code directory to generate the configure. san file. configure. san contains the basic options for system configuration, which are macro definitions. We need to change its name to configure. in.

2. aclocal

Aclocal is a perl script program. Aclocal automatically generates the aclocal. m4 file based on the content of the configure. in file. The generated aclocal. m4 file is a macro extension file.

3. autoconf

Autoconf is used to generate the configure file, configure. the in file contains some macros. These macros are processed by autoconf and become shell scripts that check system features, environment variables, and required software parameters.

4. autohead

Automatically generate config. h. in

5. automake

Use automake-add-missing to generate Makefile. in.

Document address: https://www.gnu.org/software/autoconf/manual/autoconf.html

Files used in preparing a software package for distribution, when using just Autoconf:

     your source files --> [autoscan*] --> [configure.scan] --> configure.ac          configure.ac --.                    |   .------> autoconf* -----> configure     [aclocal.m4] --+---+                    |   `-----> [autoheader*] --> [config.h.in]     [acsite.m4] ---'          Makefile.in

Additionally, if you use Automake, the following additional productions come into play:

     [acinclude.m4] --.                      |     [local macros] --+--> aclocal* --> aclocal.m4                      |     configure.ac ----'          configure.ac --.                    +--> automake* --> Makefile.in     Makefile.am ---'

Files used in processing a software package:

                            .-------------> [config.cache]     configure* ------------+-------------> config.log                            |     [config.h.in] -.       v            .-> [config.h] -.                    +--> config.status* -+               +--> make*     Makefile.in ---'                    `-> Makefile ---'

Autotools process demonstration 1. autoscan
Modify the configure. san file name to configure. ac or configure. in. Open the configuration and generate the makefile.
2. aclocal
Run the autoconf command to generate the configure executable file and create a new Makefile. am to edit the content.

bin_PROGRAMS = hellohello_SOURCES = hello.c

Install software
Run the make command and sudo make install
Go to/usr/local/bin and execute our Executable File hello
Generate a compressed package

What knowledge should I use for android system development?

Android technology insider system volume
Chapter 2 Preparations/1 1st in-depth understanding of android/2 1.1.1 android system architecture/2 1.1.2 android initialization process/5 1.1.3 relationship between various layers/8 1.1.4 android system development (porting) and app development/11 1.2 get and compile android source code/13 1.2.1 environment configuration/13 1.2.2 get android source code/14 1.2.3 compile android source code and its toolkit/16 1.2.4 run android/21 1.3 Development Environment Construction/23 1.3.1 Application Development Environment Construction/23 1.3.2 source code development environment construction/26 1.4 android source code structure/32 1.5 Summary/33 chapter 2nd android kernel mechanism and structure analysis/ 34. 2.1 relationship between linux and android/35. 2.1.1 why linux/35 2.1.2 android is not linux/35 2.2 android/37 2.2.1 goldfish/37 2.2.2 yaffs2/38 2.2.3 Bluetooth/39 2.2.4 scheduler (sched) /39 2.2.5 new android driver/40 2.2.6 power management/41 2.2.7 miscellaneous/41 2.3 android Linux kernel enhancement/42 2.3.1 alarm (hardware clock) /43 2.3.2 ashmem (anonymous memory Sharing)/46 2.3.3 low memory killer (low memory management)/52 2.3.4 logger (Log Device) /56 2.3.5 android pmem/65 2.3.6 switch/79 2.3.7 timed gpio/88 2.3.8 android ram console/94 2.4 Summary/99 chapter 3rd android ipc Mechanism -- binder/100 3.1 binder Overview/ 101 3.1.1 why choose binder/101 3.1.2 first recognized binder/102 3.2 binder driver Principle and Implementation/102 3.2.1 binder driver principle/102 3.2.2 binder driver Implementation/103 3.3 binder architecture and implementation/132 3.3.1 binder system architecture/132 3.3.2 binder Mechanism and principles/133 3.4 Summary/150 chapter 4th Power Management/151 4.1 power management overview/152 4.2 power management structure/152 4.3 android power management mechanism/153 4.4 android power management mechanism implementation/154 4.5 Summary/187 chapter 5th driver Working Principle and Implementation Mechanism/188 5.1 display driver (framebuffer) /189 5.1.1 framework of framebuffer/189 5.1.2 framework &...... remaining full text>

Where are the developer options of Android 43 Jelly Bean?

Open settings, click more or about the device. If it is version 4.3, click more and find the device. An interface is displayed, and the androidban version is displayed. There is a red BEAN, which says the jelly bean sliding mobile phone screen and dot. If you don't try again, then there will be a lot of beans, which is very fun. If I leave the question, you can check it out. (Not developer options)