欧美偷拍一区二区,麻豆精品一区二区av白丝在线,亚洲日本欧美日韩高观看

@executable path, @load path and @rpath

RTY — Tue, 17 Apr 2012 22:14:00 GMT

@executable path, @load path and @rpath

2010�q?1�?�?/span> by Wincent Colaiuta

Note: this article is actually about the @executable_path, @load_path and @rpath install paths used by the linker on Mac OS X; wiki titles can't include underscores, however, because they are ambiguous with spaces.

Absolute paths

Useful for frameworks installed in shared locations. Example:

Install path: /Library/Frameworks/Foo.framework/Versions/A/Foo

`@executable_path`

Useful for frameworks embedded inside applications, because it allows you to specify the location of the framework relative to the application's executable:

Install path: @executable_path/../Frameworks/Foo.framework/Versions/A/Foo
Application location: /Applications/Foo.app
Executable path: /Applications/Foo.app/Contents/MacOS
Framework location: /Applications/Foo.app/Contents/Frameworks/Foo.framework
Linker puts all this together to figure out that the framework binary can be found at: /Applications/Foo.app/Contents/MacOS/../Frameworks/Foo.framework/Versions/A/Foo

@loader_path

Available from Mac OS X 10.4 Tiger onwards; useful for frameworks embedded inside plug-ins, because it allows you to specify the location of the framework relative to the plug-in's code (remember, plug-ins may not actually know where they are going to be installed, relative to the application, so knowing @executable_path doesn't help us in this case):

Install path: @loader_path/../Frameworks/Foo.framework/Versions/A/Foo
Application location: /Applications/Foo.app
Plug-in location: /Library/Application Support/Foo/Plug-Ins/Bar.bundle
Executable path: /Applications/Foo.app/Contents/MacOS
Loader path: /Library/Application Support/Foo/Plug-Ins/Bar.bundle/Contents/MacOS
Framework location: /Library/Application Support/Foo/Plug-Ins/Bar.bundle/Contents/Frameworks/Foo.framework
Linker puts all this together to figure out that the framework binary can be found at: /Library/Application Support/Foo/Plug-Ins/Bar.bundle/Contents/MacOS/../Frameworks/Foo.framework/Versions/A/Foo

Note that if the "loader" is an application rather than a plug-in, the @loader_path ends up being equivalent to @executable_path.

`@rpath`

New in Mac OS X 10.5 Leopard is @rpath. Key points:

@rpath instructs the dynamic linker to search a list of paths in order to locate the framework
critically, this list is embedded in the loading application
this means that a single framework with @rpath/Foo.framework/Versions/A/Foo can be made to work in a number of different ways; that is, you are effectively no longer limited by the choice of specifying your "install path" using either @executable_path or @loader_path
the down side: you now have to pass additional linker flags when building the host application (eg. -rpath @executable_path/../Frameworks or /Library/Frameworks; note that specifying both will cause the dynamic linker to try looking in both locations)

Sources

Nice overview: http://www.mikeash.com/pyblog/friday-qa-2009-11-06-linking-and-install-names.html
Docs for using PFiddlesoft Frameworks (I've never used these, but the manual itself makes some nice general points about using frameworks): http://pfiddlesoft.com/frameworks/downloads/Assistive_Application_Programming_Guide.pdf

Configure�Q�Makefile.am, Makefile.in, Makefile文�g之间关系

RTY — Tue, 03 Apr 2012 14:20:00 GMT

Configure�Q�Makefile.am, Makefile.in, Makefile文�g之间关系

2009-08-12 12:14

1.autoscan (autoconf): 扫描源代码以搜寻普通的可移植性问题，比如��查编译器�Q�库�Q�头文�g�{�，生成文�gconfigure.scan,它是configure.ac的一个雏形�?/p>

your source files --> [autoscan*] --> [configure.scan] --> configure.ac

2.aclocal (automake):�Ҏ��已经安装的宏�Q�用户定义宏和acinclude.m4文�g中的宏将configure.ac文�g所需要的宏集中定义到文�g aclocal.m4中。aclocal是一个perl 脚本�E�序�Q�它的定义是�Q?#8220;aclocal - create aclocal.m4 by scanning configure.ac”

user input files   optional input     process          output files
================   ==============     =======          ============

                    acinclude.m4 - - - - -.
                                          V
                                      .-------,
configure.ac ------------------------>|aclocal|
                 {user macro files} ->|       |------> aclocal.m4
                                      `-------'
3.autoheader(autoconf): �Ҏ��configure.ac中的某些宏，比如cpp宏定义，�q�行m4�Q�声�U�config.h.in

user input files    optional input     process          output files
================    ==============     =======          ============

                    aclocal.m4 - - - - - - - .
                                             |
                                             V
                                     .----------,
configure.ac ----------------------->|autoheader|----> autoconfig.h.in
                                     `----------'

4.automake: automake��Makefile.am中定义的�l�构建立Makefile.in�Q�然后configure脚本��生成的Makefile.in文�g转换为Makefile。如果在configure.ac中定义了一些特�D�的宏，比如AC_PROG_LIBTOOL�Q�它会调用libtoolize�Q�否则它会自�׃�生config.guess和config.sub

user input files   optional input   processes          output files
================   ==============   =========          ============

                                     .--------,
                                     |        | - - -> COPYING
                                     |        | - - -> INSTALL
                                     |        |------> install-sh
                                     |        |------> missing
                                     |automake|------> mkinstalldirs
configure.ac ----------------------->|        |
Makefile.am  ----------------------->|        |------> Makefile.in
                                     |        |------> stamp-h.in
                                 .---+        | - - -> config.guess
                                 |   |        | - - -> config.sub
                                 |   `------+-'
                                 |          | - - - -> config.guess
                                 |libtoolize| - - - -> config.sub
                                 |          |--------> ltmain.sh
                                 |          |--------> ltconfig
                                 `----------'

5.autoconf:��configure.ac中的宏展开�Q�生成configure脚本。这个过�E�可能要用到aclocal.m4中定义的宏�?/p>

user input files   optional input   processes          output files
================   ==============   =========          ============

aclocal.m4 ,autoconfig.h.in - - - - - - -.
                                         V
                                     .--------,
configure.ac ----------------------->|autoconf|------> configure

6. ./configure的过�E?/pre>
                                           .-------------> [config.cache]
     configure* --------------------------+-------------> config.log
                                          |
              [config.h.in] -.            v            .--> [autoconfig.h]
                             +-------> config.status* -+                   
              Makefile.in ---'                         `-->   Makefile
 
7. make�q�程
 
[autoconfig.h] -.
                     +--> make* --->  �E�序
        Makefile   ---'
 
.---------,
                   config.site - - ->|         |
                  config.cache - - ->|configure| - - -> config.cache
                                     |         +-,
                                     `-+-------' |
                                       |         |----> config.status
                   config.h.in ------->|config-  |----> config.h
                   Makefile.in ------->|  .status|----> Makefile
                                       |         |----> stamp-h
                                       |         +--,
                                     .-+         |  |
                                     | `------+--'  |
                   ltmain.sh ------->|ltconfig|-------> libtool
                                     |        |     |
                                     `-+------'     |
                                       |config.guess|
                                       | config.sub |
                                       `------------' 
.--------,
                   Makefile ------>|        |
                   config.h ------>|  make  |
{project sources} ---------------->|        |--------> {project targets}
                                 .-+        +--,
                                 | `--------'  |
                                 |   libtool   |
                                 |   missing   |
                                 |  install-sh |
                                 |mkinstalldirs|
                                 `-------------'

实例�Q?br />�?hello/目录下创��Z��个hello.c文�g�Q��ƈ�~�译�q�行它：

#cd /hello/

(1) �~�写源文件hello.c�Q?/p>

#include
int main(int argc, char** argv)
{
printf("Hello, GNU!n");
return 0;
}

[litao@vm0000131 hello]$ ll
total 4
-rw-rw-r-- 1 litao litao 68 Aug 12 12:02 hello.c

一、autoscan

[litao@vm0000131 hello]$ autoscan
autom4te: configure.ac: no such file or directory
autoscan: /usr/bin/autom4te failed with exit status: 1
[litao@vm0000131 hello]$ ll
total 8
-rw-rw-r-- 1 litao litao 0 Aug 12 12:03 autoscan.log
-rw-rw-r-- 1 litao litao 457 Aug 12 12:03 configure.scan
-rw-rw-r-- 1 litao litao 68 Aug 12 12:02 hello.c

已经生成了configure.scan�Q�autoscan.log文�g

��configure.scan 修改�?configure.in�Q�最后修改的内容如下�Q?/p>

[litao@vm0000131 hello]$ mv configure.scan configure.in
[litao@vm0000131 hello]$ vim configure.in

# -*- Autoconf -*-
# Process this file with autoconf to produce a configure script.

AC_PREREQ(2.59)
AC_INIT(FULL-PACKAGE-NAME, VERSION, BUG-REPORT-ADDRESS)
AC_CONFIG_SRCDIR([hello.c])
#AC_CONFIG_HEADER([config.h])
AM_INIT_AUTOMAKE(hello, 1.0)
# Checks for programs.
AC_PROG_CC

# Checks for libraries.

# Checks for header files.

# Checks for typedefs, structures, and compiler characteristics.

# Checks for library functions.
AC_OUTPUT(Makefile)

二、acloacl

[litao@vm0000131 hello]$ aclocal

生成 aclocal.m4 �?autom4te.cache (生成aclocal.m4的过�E�中涉及到configure.in)

[litao@vm0000131 hello]$ ll
total 44
-rw-rw-r-- 1 litao litao 31120 Aug 12 12:08 aclocal.m4
drwxr-xr-x 2 litao litao 4096 Aug 12 12:08 autom4te.cache
-rw-rw-r-- 1 litao litao 0 Aug 12 12:03 autoscan.log
-rw-rw-r-- 1 litao litao 496 Aug 12 12:08 configure.in
-rw-rw-r-- 1 litao litao 68 Aug 12 12:02 hello.c

三、antoconf

[litao@vm0000131 hello]$ autoconf
生成 configure (�Ҏ�� configure.in, �? aclocal.m4)
[litao@vm0000131 hello]$ ll
total 168
-rw-rw-r-- 1 litao litao 31120 Aug 12 12:08 aclocal.m4
drwxr-xr-x 2 litao litao 4096 Aug 12 12:11 autom4te.cache
-rw-rw-r-- 1 litao litao 0 Aug 12 12:03 autoscan.log
-rwxrwxr-x 1 litao litao 122297 Aug 12 12:11 configure
-rw-rw-r-- 1 litao litao 496 Aug 12 12:08 configure.in
-rw-rw-r-- 1 litao litao 68 Aug 12 12:02 hello.c

四、编写Makefile.am�Q?

AUTOMAKE_OPTIONS= foreign
bin_PROGRAMS= hello
hello_SOURCES= hello.c

五、automake

生成 Makefile.in�Q?depcomp�Q?install-sh�Q?�?missing (�Ҏ�� Makefile.am, �? aclocal.m4)

[litao@vm0000131 hello]$ automake
configure.in: required file `./install-sh' not found
configure.in: required file `./missing' not found
Makefile.am: required file `./depcomp' not found
[litao@vm0000131 hello]$ automake --add-missing
configure.in: installing `./install-sh'
configure.in: installing `./missing'
Makefile.am: installing `./depcomp'
[litao@vm0000131 hello]$ ll
total 192
-rw-rw-r-- 1 litao litao 31120 Aug 12 12:08 aclocal.m4
drwxr-xr-x 2 litao litao 4096 Aug 12 12:14 autom4te.cache
-rw-rw-r-- 1 litao litao 0 Aug 12 12:03 autoscan.log
-rwxrwxr-x 1 litao litao 122297 Aug 12 12:11 configure
-rw-rw-r-- 1 litao litao 496 Aug 12 12:08 configure.in
lrwxrwxrwx 1 litao litao 31 Aug 12 12:16 depcomp -> /usr/share/automake-1.9/depcomp
-rw-rw-r-- 1 litao litao 68 Aug 12 12:02 hello.c
lrwxrwxrwx 1 litao litao 34 Aug 12 12:16 install-sh -> /usr/share/automake-1.9/install-sh
-rw-rw-r-- 1 litao litao 69 Aug 12 12:15 Makefile.am
-rw-rw-r-- 1 litao litao 16561 Aug 12 12:16 Makefile.in
lrwxrwxrwx 1 litao litao 31 Aug 12 12:16 missing -> /usr/share/automake-1.9/missing

六、configure
生成 Makefile�Q?config.log�Q?�?config.status

�Ҏ��英客

zxjlwt

jazeltq

RTY 2012-04-03 22:20 发表评论

RTY — Thu, 01 Mar 2012 07:02:00 GMT

摘要: 1. �U�d��光标快捷键ctrl+f 向前�U�d��一个字�W�ctrl+b 向后�U�d��一个字�W�alt+f 向前�U�d��一个单词alt+b 向后�U�d��一个单词ctrl+a �U�d��到当前行首ctrl+e �U�d��到当前行��ctrl+l 清屏�Q��ƈ在屏�q�最上面开始一个新�?2. �~�辑命��o行快捷键ctrl+d 删除当前的字�W�ctrl+t 交换当前字符和前一个字�W�的位置alt+t 交换当前单词和前一个单词的位置alt+u 把当前单词变... 阅读全文

RTY 2012-03-01 15:02 发表评论

KBuild MakeFile介绍

RTY — Wed, 20 Jul 2011 23:24:00 GMT

从Linux内核2.6开始，Linux内核的编译采用Kbuild�pȝ��Q�这同过�ȝ��~�译�pȝ��有很大的不同�Q�尤其对于Linux内核模块的编译�?font color="#0000ff" style="word-wrap: break-word; line-height: normal; ">在新的系�l�下�Q�Linux�~�译�pȝ��会两�ơ扫描Linux的Makefile�Q�首先编译系�l�会��d��Linux内核��层的Makefile�Q�然后根据读到的内容�W�二�ơ读取Kbuild的Makefile来编译Linux内核�?/font>
Linux内核Makefile分类
·       Kernel Makefile
Kernel Makefile位于Linux内核源代码的��层目录�Q�也�?Top Makefile。它主要用于指定�~�译Linux Kernel目标文�g�Q�vmlinux�Q�和模块�Q�module�Q�。这�~�译内核或模块是�Q�这个文件会被首先读取，�q�根据读到的内容配置�~�译环境变量。对于内核或驱动开�?/span>人员来说�Q�这个文件几乎不用�Q何修攏V�?br style="word-wrap: break-word; line-height: normal; " />·       Kbuild Makefile
Kbuild�pȝ��使用Kbuild Makefile来编译内核或模块。当Kernel Makefile被解析完成后�Q�Kbuild会读取相关的Kbuild Makefile�q�行内核或模块的�~�译。Kbuild Makefile有特定的语法指定哪些�~�译�q�内�怸�、哪些编译�ؓ模块、及对应的源文�g是什么等。内核及驱动开发�h员需要编写这个Kbuild Makefile文�g�?br style="word-wrap: break-word; line-height: normal; " />·       ARCH Makefile
ARCH Makefile位于ARCH/$(ARCH)/Makefile�Q�是�pȝ��对应�q�_��的Makefile。Kernel Top Makefile会包含这个文件来指定�q�_��相关信息。只有��^台开发�h员会兛_��q�个文�g�?br style="word-wrap: break-word; line-height: normal; " />Kbuild Makefile
Kbuild Makefile的文件名不一定是Makefile�Q�尽��推荐��用Makefile�q�个名字。大多的Kbuild文�g的名字都是Makefile。�ؓ了与其他Makefile文�g相区别，你也可以指定Kbuild Makefile的名字�ؓKbuild。而且如果“Makefile”�?#8220;Kbuild”文�g同时存在�Q�则Kbuild�pȝ��会��?#8220;Kbuild”文�g�?br style="word-wrap: break-word; line-height: normal; " />·       目标定义
Kbuild Makefile的一个最主要功能��是指定�~�译什么，�q�个功能是通过下面两个对象指定的obj-?和xxx-objs�Q?br style="word-wrap: break-word; line-height: normal; " />·       obj-?
obj-?指定�~�译什么，怎么�~�译�Q�其中的“?”可能�?#8220;y”�?#8220;m”�Q?#8220;y”指定把对象编译进内核中，“m”指定把对象编译�ؓ模块。语法如�?
obj-? = $(target).o
target为编译对象的名字。如果没有指定xxx-objs�Q�这�~�译�q�个对象需要的源文件就�?(target).c�?(target).s。如果指定了$(target)-objs�Q�则�~�译�q�个对象需要的源文件由$(target)-objs指定�Q��ƈ且不能有$(target).c�?(target).s文�g�?br style="word-wrap: break-word; line-height: normal; " />·       xxx-objs
xxx-objs指定了编译对象需要的文�g�Q�一般只有在源文件是多个时才需要它�?br style="word-wrap: break-word; line-height: normal; " />只要包含了这两行�Q�Kbuild Makefile��应该可以工作了�?br style="word-wrap: break-word; line-height: normal; " />·       嵌套�~�译
有时一个对象可能嵌入到另一个对象的目录下，那个如何�~�译子目录下的对象呢?其实很简单，只要指定obj_?的对象�ؓ子目录的名字��可以了�Q?br style="word-wrap: break-word; line-height: normal; " />obj-? = $(sub_target)/
其中“?”可以�?#8220;y”�?#8220;m”�Q?(sub_target)是子目录名字�?br style="word-wrap: break-word; line-height: normal; " />·       �~�译器选项
��管在大多数情况下不需要指定编译器选项�Q�有时我们还是需要指定一些编译选项的�?br style="word-wrap: break-word; line-height: normal; " />·       ccflags-y, asflags-y and ldflags-y
�q�些�~�译选项用于指定cc、as和ld的编译选项
�~�译外部模块
有时候我们需要在内核源代码数的外面编译内核模块，�~�译的基本命令是�Q?br style="word-wrap: break-word; line-height: normal; " /> make -C $(KERNEL_DIR) M=`pwd` modules
我们可以把这个命令集成到Makefile里，�q�样我们��可以只输入“make”命��o��可以了。回想上一章的那个Makefile�Q�它把Normal Makefile 和Kbuild  Makefile集成��C��个文件中了。�ؓ了区别Kbuild Makefile 和Normal Makefile�Q�这��h��们改写Makefile为如下�Ş式，�q�且��d��Kbuild Makefile - “Kbuild”�?br style="word-wrap: break-word; line-height: normal; " />##Makefile
ifneq ($(KERNELRELEASE),)
include "Kbuild"
else
KERNEL_DIR = /lib/modules/`uname -r`/build
MODULEDIR := $(shell pwd)
.PHONY: modules
default: modules
modules:
      make -C $(KERNEL_DIR)  M=$(MODULEDIR) modules
clean distclean:
      rm -f *.o *.mod.c .*.*.cmd *.ko
      rm -rf .tmp_versions
endif

## Kbuild
MODULE_NAME = helloworld
$(MODULE_NAME)-objs := hello.o
obj-m := $(MODULE_NAME).o
一般不需要在Makefile里包含如下代�?�q�样写完全是��Z��兼容老版本的Kbuild�pȝ��。KERNELRELEASE变量在Kernel Makefile里定义的�Q�因此只有在�W�二�ơ由Kbuild��d��q�个Makefile文�g时才会解析到Kbuild的内宏V�?nbsp;
ifneq ($(KERNELRELEASE),)
include "Kbuild"
else
...
endif
外部头文�?/strong>
有时需要连接内核源代码外部的系�l�头文�g�Q�但Kbuild�pȝ��默认的系�l�头文�g都在内核源代码内部，如何使用外部的头文�g呢？�q�个可以借助于Kbuild�pȝ��的特�D�规�?
·       EXTRA_CFLAGS
EXTRA_CFLAGS可以�l�Kbuild�pȝ��d��外部�pȝ��头文�Ӟ��
EXTRA_CFLAGS += $(ext_include_path)
一般外部头文�g可能位于外部模块源文件的目录内，如何指定呢？�q�可以借助$(src)�?(obj)
·       $(src)/$(obj)
$(src)是一个相对�\径，它就是Makefile/Kbuild文�g所在的路径。同�?(obj)��是�~�译目标保存的�\径，默认��是源代码所在�\径�?br style="word-wrap: break-word; line-height: normal; " />因此�Q�我们修改Kbuild文�g��d�� EXTRA_CFLAGS 来包含外部头文�g��管在这个驱动里没有引用外部�pȝ��头文�Ӟ��
## Kbuild
MODULE_NAME = helloworld
$(MODULE_NAME)-objs := hello.o
EXTRA_CFLAGS := -I$(src)/include
obj-m := $(MODULE_NAME).o

·       Goal definitions
Example:
obj-y += foo.o
告诉kbuild�Q�在文�g夹中又一个叫做foo.o的object。foo.o��会被从foo.c或者foo.S被构建�?br style="word-wrap: break-word; line-height: normal; " />
如果foo.o被构建成一�?strong style="word-wrap: break-word; text-align: left; font-style: normal; line-height: normal; font-weight: bold; ">模块�Q�则��用变�?strong style="word-wrap: break-word; text-align: left; font-style: normal; line-height: normal; font-weight: bold; ">obj-m�?strong style="word-wrap: break-word; text-align: left; font-style: normal; line-height: normal; font-weight: bold; ">Example:
obj-$(CONFIG_FOO) += foo.o
$(CONFIG_FOO)要么是y(built-in)要么是m(module)。如果CONFIG_FOO既不是y也不是m�Q�那么文件将不会被编译也不会被连接�?br style="word-wrap: break-word; line-height: normal; " />·       Built-in object goals - obj-y
kbuild Makefiles�?strong style="word-wrap: break-word; text-align: left; font-style: normal; line-height: normal; font-weight: bold; ">$(obj-y)列表中�ؓvmlinux指明object文�g。这个列表依靠内核的配置�?br style="word-wrap: break-word; line-height: normal; " />�?strong style="word-wrap: break-word; text-align: left; font-style: normal; line-height: normal; font-weight: bold; ">$(obj-y)中的文�g的顺序是非常重要的。列表中允许两个相同的文�Ӟ��W�一�?/strong>实体��被�q�接到built-in.o�Q�后面的实体��会被忽略�?/strong>
�q�接的顺序也很重要，因�ؓ在boot�q�程中某些函�?module_init()/_initcall)��会按顺序出现�?/strong>因此�Q�如果改变了�q�接��序�Q�将会改变你的SCSI控制器的��顺序，你的��盘也同时被重新�~�号了�?br style="word-wrap: break-word; line-height: normal; " />Example:
  #drivers/isdn/i4l/Makefile
  # Makefile for the kernel ISDN subsystem and device drivers.
  # Each configuration option enables a list of files.
  obj-$(CONFIG_ISDN)          += isdn.o
  obj-$(CONFIG_ISDN_PPP_BSDCOMP) += isdn_bsdcomp.o
·       Loadable module goals - obj-m
$(obj-m)指明object文�g作�ؓ可装载的内核模块被构建。一个模块可能从一个或者多个源文�g被构建。kbuild maefile只是��单的��源文�g加到%(obj-m)
Example:
  #drivers/isdn/i4l/Makefile
  obj-$(CONFIG_ISDN_PPP_BSDCOMP) += isdn_bsdcomp.o
注意�q�里$(CONFIG_ISDN_PPP_BSDCOMP)是m.
Note: In this example $(CONFIG_ISDN_PPP_BSDCOMP) evaluates to 'm'�?br style="word-wrap: break-word; line-height: normal; " />如果一个内核模块从多个源文件构建，KBuild��必��要知道你想从哪些部分构建模块。因此，你不得不讄��$(-objs)变量来告诉KBuild�?br style="word-wrap: break-word; line-height: normal; " />Example:
  #drivers/isdn/i4l/Makefile
  obj-$(CONFIG_ISDN) += isdn.o
  isdn-objs := isdn_net_lib.o isdn_v110.o isdn_common.o
在这个例子中�Q�模块名是isdn.o,Kbuild��会�~�译列在$(isdn-objs)�?/strong>object文�g�Q�然后在�q�些文�g的列表中调用"$(LD) -r"来��生isdn.o�?br style="word-wrap: break-word; line-height: normal; " />Kbuild使用后缀-objs,-y来识别�؜合的object文�g。这允许Makefiles使用变量CONFIG_sambol来决定一个object是否是�؜合object的的一部分�?br style="word-wrap: break-word; line-height: normal; " />Example:
  #fs/ext2/Makefile
      obj-$(CONFIG_EXT2_FS)       += ext2.o
ext2-y                      := balloc.o bitmap.o
      ext2-$(CONFIG_EXT2_FS_XATTR) += xattr.o

在这个例子中�Q�如�?(CONFIG_EXT2_FS_XATTR)是y�Q�则xattr.o只是混合object文�gext2.o的一部分�?br style="word-wrap: break-word; line-height: normal; " />注意�Q�当你构造一个objects到内�怸��Ӟ��上面的语法当然也能够工作。因此，如果你让CONFIG_EXT2=Y,KBuild��会��Z��构徏一个独立的ext2.o文�g�Q��ƈ且连接到built-in.o�?br style="word-wrap: break-word; line-height: normal; " />·       Library file goals - lib-y
�?strong style="word-wrap: break-word; text-align: left; font-style: normal; line-height: normal; font-weight: bold; ">obj-*�q�接的Objects在指明的文�g夹中被用作模块或者综合进built-in.o。也又可能被列出的objects��会被包含进一个库,lib.a。所有用lib-y列出的objects在那个文件夹中被�l�合�q�单独的一个库。列在obj-y和附加列在lib-y中的Objects��不会被包含在库中，因�ؓ他们��会被�Q意的存取。对于被�q�接在lib-m中，�q�箋的objects��会被包含在lib.a中。值得注意的是kbuild makefile可能列出文�g用作built-in�Q��ƈ且作为库的一部分。因此，同一个文件夹可能包含一个built-in.o和lib.a文�g�?br style="word-wrap: break-word; line-height: normal; " />Example:
  #arch/i386/lib/Makefile
  lib-y := checksum.o delay.o
�q�里讲会创徏一个基于checksum.o和delay.o的库文�g。对于kbuild�Q�识别一个lib.a正在被构建，�q�个文�g夹应该被列在libs-y中�?strong style="word-wrap: break-word; text-align: left; font-style: normal; line-height: normal; font-weight: bold; ">lib-y的��用方法通常被限制在lib/和arc/*/lib中�?br style="word-wrap: break-word; line-height: normal; " />·       Descending down in directories
一个Makefile只负责在他自��q��文�g夹中构徏objects�?在子文�g夹中的文件应该由子文件夹中的Makefiles来照��。如果你知道他们�Q�build�pȝ��会自动递归地用在子文�g夹中的make�?br style="word-wrap: break-word; line-height: normal; " />在这�U�情况下obj-y�?strong style="word-wrap: break-word; text-align: left; font-style: normal; line-height: normal; font-weight: bold; ">obj-m��p��使用了。ext2存在于不同的文�g夹中�Q�Makefile出现在fs/�Q�则告诉kbuild从后面的参数下来�?br style="word-wrap: break-word; line-height: normal; " />Example:
  #fs/Makefile
  obj-$(CONFIG_EXT2_FS) += ext2/
如果CONFIG_EXT2_FS被设�|�成y(built-in)或者m(modular)�Q�相应的obj-变量��会被设�|�，�q�且kbuild��会从ext2文�g夹��承下来。Kbuild只会使用�q�些信息来决定它需要访问这些文件夹�Q�而在子文件夹中的Makefile来指明哪些是modules哪些是built-in�?br style="word-wrap: break-word; line-height: normal; " />当赋值文件夹名字的时候，使用CONFIG_variable是很好的选择。这允许kbuild完全的蟩�q�文件夹�Q�而不��CONFIG_option是否是y或者m�?br style="word-wrap: break-word; line-height: normal; " />·       Compilation flags
EXTRA_CFLAGS, EXTRA_AFLAGS, EXTRA_LDFLAGS, EXTRA_ARFLAGS�?br style="word-wrap: break-word; line-height: normal; " />所有的EXTRA_ variables�?span href="tag.php?name=%D3%A6%D3%C3" class="t_tag" style="word-wrap: break-word; line-height: normal; cursor: pointer; border-bottom-width: 1px; border-bottom-style: solid; border-bottom-color: #ff0000; white-space: nowrap; ">应用在kbuild中，他们被赋值的地方。EXTRA_variables应用在kbuild makefile中所有的可执行的命��o�?strong style="word-wrap: break-word; text-align: left; font-style: normal; line-height: normal; font-weight: bold; ">$(EXTRA_CFLAGS) 指明�?(CC)�~�译C文�g的时候的选项�?br style="word-wrap: break-word; line-height: normal; " />Example:
  # drivers/sound/emu10k1/Makefile
  EXTRA_CFLAGS += -I$(obj)
  ifdef DEBUG
   EXTRA_CFLAGS += -DEMU10K1_DEBUG
  endif
�q�里的变量是必须的，因�ؓ��层的Makefile拥有变量$(CFLAGS)�q�且用它来作为整个树的编译标志当�~�译汇编源文件的时�?strong style="word-wrap: break-word; text-align: left; font-style: normal; line-height: normal; font-weight: bold; ">$(EXTRA_AFLAGS)�Q�和每个文�g夹的选项是相似的�?br style="word-wrap: break-word; line-height: normal; " />Example:
  #arch/x86_64/kernel/Makefile
  EXTRA_AFLAGS := -traditional
$(EXTRA_LDFLAGS)�?strong style="word-wrap: break-word; text-align: left; font-style: normal; line-height: normal; font-weight: bold; ">$(EXTRA_ARFLAGS) 对于每个文�g夹的$(LD)�?(AR)选项是类似的�?br style="word-wrap: break-word; line-height: normal; " />Example:
  #arch/m68k/fpsp040/Makefile
  EXTRA_LDFLAGS := -x
CFLAGS_$@, AFLAGS_$@
CFLAGS_$@�?strong style="word-wrap: break-word; text-align: left; font-style: normal; line-height: normal; font-weight: bold; ">AFLAGS_$@只应用到当前kbuild makefile的命令�?br style="word-wrap: break-word; line-height: normal; " />$(CFLAGS_$@) 为每个文件的$(CC)指明选项�?strong style="word-wrap: break-word; text-align: left; font-style: normal; line-height: normal; font-weight: bold; ">$@
部分有一个字面上的��|��指明它是为那个文件�?br style="word-wrap: break-word; line-height: normal; " />Example:
  # drivers/scsi/Makefile
  CFLAGS_aha152x.o = -DAHA152X_STAT -DAUTOCONF
  CFLAGS_gdth.o = # -DDEBUG_GDTH=2 -D__SERIAL__ -D__COM2__ \
      -DGDTH_STATISTICS
  CFLAGS_seagate.o = -DARBITRATE -DPARITY -DSEAGATE_USE_ASM
These three lines specify compilation flags for aha152x.o,
gdth.o, and seagate.o
$(AFLAGS_$@) is a similar feature for source files in assembly
languages.
Example:
  # arch/arm/kernel/Makefile
  AFLAGS_head-armv.o := -DTEXTADDR=$(TEXTADDR) -traditional
  AFLAGS_head-armo.o := -DTEXTADDR=$(TEXTADDR) -traditional

RTY 2011-07-21 07:24 发表评论

Linux on Power 上的调试工具和技�?(gdb �Q�及valgrind

RTY — Mon, 18 Jul 2011 23:30:00 GMT

摘要: Linux on Power 上的调试工具和技术Calvin Sze (calvins@us.ibm.com), Linux ��N�� , EMC��介：调试是一��主要的软�g开发活动，作�ؓ应用�E�序开发�h员，您无法避免对�E�序�q�行调试。有效的调试不仅能羃短��Y件开发周期，而且可以节省成本。本文简要介�l�了在用��L��间的 C/C++ �?Java? 应用�E�序中查�?bug 的技术，�q�介�l�了一�?.. 阅读全文

RTY 2011-07-19 07:30 发表评论

VirtualBox 4.0.8 发布, 提升3D支持

RTY — Tue, 17 May 2011 10:55:00 GMT

VirtualBox 宣布�?4.0.8 版本�Q�该版本改进了对 Gnome 3 �?3D 支持。同时还修复了不��bug�Q�包括改�?guest �H�体大小时可能导致程序崩溃的问题以及 Ubuntu 11.04 以及 Fedora 15 �?Gnome 3 的渲染问题�?/p>

VirtualBox 是一�Ƒ֊�能强大的 x86 虚拟��Y�Ӟ��它不仅具有丰富的特色�Q�而且性能也很优异�?/p>

更多关于VirtualBox的详�l�信息，或者下载地址��L��q�里

RTY 2011-05-17 18:55 发表评论

Linux Python 好用的开发工具gecrit

RTY — Sat, 23 Apr 2011 10:07:00 GMT

下蝲地址�Q?a >http://sourceforge.net/projects/gecrit/files/

RTY 2011-04-23 18:07 发表评论

欧美偷拍一区二区,麻豆精品一区二区av白丝在线,亚洲日本欧美日韩高观看

@executable path, @load path and @rpath

@executable path, @load path and @rpath

Absolute paths

@executable_path

@loader_path

@rpath

Sources

Tags

Configure�Q�Makefile.am, Makefile.in, Makefile文�g之间关系

KBuild MakeFile介绍

Linux on Power 上的调试工具和技�?(gdb �Q�及valgrind

VirtualBox 4.0.8 发布, 提升3D支持

Linux Python 好用的开发工具gecrit

`@executable_path`

`@rpath`