CubieBoard博客-HomeCubieTech公司网站

cubie.cc CubieBoard中文论坛

 找回密码
 立即注册
搜索
热搜: unable
查看: 2823|回复: 4

编译源码生成的out/target/product/.../obj文件的作用

[复制链接]

28

主题

6

好友

4617

积分

论坛元老

Rank: 8Rank: 8

贡献
860
金钱
1828
威望
860
买家信用
卖家信用
积分
4617
发表于 2014-8-7 10:08:18 |显示全部楼层
本帖最后由 f839903061 于 2014-8-8 10:51 编辑

现在有一个疑惑
编译android4.0以上版本的源码,经常能够看到out/target/product/.../obj里面的文件怎么怎么滴的
文件夹的作用不是很清楚
obj文件夹的目录结构如下:
---APPS
---ETC
---EXECUTABLES
---FAKE
---GYP
---JAVA_LIBRARIES
---KERNEL_OBJ
---NOTICE.html
---NOTICE.html.gz
---NOTICE.txt
---NOTICE_FILES
---PACKAGING
---SHARED_LIBRARIES
---STATIC_LIBRARIES
---UTILITY_EXECUTABLES
---hardware
---include
---lib


这个obj文件夹的功能我希望能够有朋友帮忙解惑!哪怕是拿出其中的一个单独的子文件夹解惑也是感激不尽的!谢谢

回复

使用道具 举报

8

主题

0

好友

7929

积分

论坛元老

Rank: 8Rank: 8

贡献
1459
金钱
3454
威望
1459
买家信用
卖家信用
积分
7929
发表于 2014-8-7 12:09:30 |显示全部楼层
understanding android build system out directory

The android build system keeps a clean seperation of source and output. All intermediates and final output are placed in the directory named out. So, the simple way to fully clean a build is deleting the out directory.
The hierarchy of the out directory is shown below:
out/
|-- host/                           # the directory containing all tools and libraries of build system
-- target/product/generic/         # the root of this product's out directory
    |-- data                        # the directory for creating data file system image
    |-- obj                         # the root directory of build process
    |   |-- APPS                    # android application
    |   |-- ETC
    |   |-- EXECUTABLES             # the root directory containing all native executable build output
    |   |-- include
    |   |-- JAVA_LIBRARIES
    |   |-- lib                     # the directory containing copies of stripped shared libraries,
    |   |                           # other modules will search this directory for libraries to resolve linkage
    |   |-- PACKAGING
    |   |-- SHARED_LIBRARIES        # the root directory containing all native shared library build output
    |   |   |-- {LOCAL_MODULE_NAME}_intermediates    # the direcotry containing all build output for {LOCAL_MODULE_NAME} module
    |   |       |                                    # this naming convention is followed by all subdirectories of module
    |   |        -- LINKED          # the directory containing the linked binary file, e.g, .so file
    |    -- STATIC_LIBRARIES        # the root directory containing all native static library build output
    |-- root                        # the directory for creating root file system, ramdisk image
    |   |-- data
    |   |-- dev
    |   |-- proc
    |   |-- sbin
    |   |-- sys
    |    -- system
    |-- symbols                     # the directory contains all binary images that has debugging symbols
    |   |-- data
    |   |-- sbin
    |    -- system
     -- system                      # the directory for creating system.img, where most of appications and libraries reside
        |-- app
        |-- bin
        |-- etc
        |-- fonts
        |-- framework
        |-- lib
        |-- media
        |-- tts
        |-- usr
         -- xbin
Under the out/target/product/generic/obj directory, there are several subdirectories, APPS, EXECUTABLES, SHARED_LIBRARIES, STATIC_LIBRARIES. They contain build output for modules of different type, java application, native executable, shared libraries and static libraries, respectively. Under the module type's directory, there is a directory for each module of corresponding type, named with the module's name catenating _intermediates. So, when we need to clean a specific module, we can simply delete the intermediate directory for the module.
For example, in the Android.mk for stlport, there is a LOCAL_MODULE defined as libstlport, which is a shared library (by including $(BUILD_SHARED_LIBRARY)). The output of this module will be placed in SHARED_LIBRARIES/libstlport_intermediates directory. The linker will generate the final shared library in the SHARED_LIBRARIES/libstlport_intermediates/LINKED directory.
After a module has been compiled the linked, it's to be stripped and copied to directory for creating file system image. The build system doesn't perform stripping in place. Instead, it will first copy the file with debugging symbol information (the file under LINKED directory) to correct place in symbols directory. Then strip the file and save in intermediate directory (for executable) or obj/lib directory (for shared library), meanwhile, the file without symbol and the file with symbol are associated with 'objcopy --add-gnu-debuglink' command. Finally, the stripped file will be copied to system directory.
Once all modules are built, the system directory should have been populated with necessary files. The build system will create three file system images, ramdisk.img, userdata.img, and system.img with system, root and data as source directories respectively. The default choice of file system is yaffs2.
回复

使用道具 举报

8

主题

0

好友

7929

积分

论坛元老

Rank: 8Rank: 8

贡献
1459
金钱
3454
威望
1459
买家信用
卖家信用
积分
7929
发表于 2014-8-7 12:10:04 |显示全部楼层
顺便问楼主,你的Android遥控开机搞好了吗?
回复

使用道具 举报

28

主题

6

好友

4617

积分

论坛元老

Rank: 8Rank: 8

贡献
860
金钱
1828
威望
860
买家信用
卖家信用
积分
4617
发表于 2014-8-8 10:38:26 |显示全部楼层
yanggis 发表于 2014-8-7 12:09
understanding android build system out directory

The android build system keeps a clean seperation  ...

非常感谢您的回复!
回复

使用道具 举报

28

主题

6

好友

4617

积分

论坛元老

Rank: 8Rank: 8

贡献
860
金钱
1828
威望
860
买家信用
卖家信用
积分
4617
发表于 2014-8-8 10:39:06 |显示全部楼层
yanggis 发表于 2014-8-7 12:10
顺便问楼主,你的Android遥控开机搞好了吗?

非常抱歉,后来没有做那个了!
回复

使用道具 举报

您需要登录后才可以回帖 登录 | 立即注册

QQ|Archiver|手机版|邮件群发|cubie.cc---深刻的嵌入式技术和应用讨论中文社区 ( 粤ICP备13051116号-1  

GMT+8, 2020-4-3 03:33 , Processed in 0.025922 second(s), 10 queries , Apc On.

Powered by Discuz! X2.5

© 2001-2012 Comsenz Inc. | Style by Coxxs

回顶部