• <ins id="pjuwb"></ins>
    <blockquote id="pjuwb"><pre id="pjuwb"></pre></blockquote>
    <noscript id="pjuwb"></noscript>
          <sup id="pjuwb"><pre id="pjuwb"></pre></sup>
            <dd id="pjuwb"></dd>
            <abbr id="pjuwb"></abbr>
            Creative Commons License
            本Blog采用 知識共享署名-非商業(yè)性使用-禁止演繹 3.0 Unported許可協(xié)議 進行許可。 —— Fox <游戲人生>

            游戲人生

            游戲人生 != ( 人生 == 游戲 )
            站點遷移至:http://www.yulefox.com。請訂閱本博的朋友將RSS修改為http://feeds.feedburner.com/yulefox
            posts - 62, comments - 508, trackbacks - 0, articles - 7

            Autotools初體驗

            Posted on 2009-12-23 02:18 Fox 閱讀(6921) 評論(5)  編輯 收藏 引用 所屬分類: T技術(shù)碎語

            本文同步自游戲人生

            Writen by Fox(yulefox.at.gmail.com)


            從接觸和使用make以來,前前后后寫了不少Makefile(添添減減、修修補補,累計上千行是有的),今天在重新整理代碼的組織結(jié)構(gòu)之后,突然就想:我為什么不使用Autotools呢?

            在開始體驗功能強大的Autotools之前,簡單(詳細)回憶總結(jié)一下我使用make的經(jīng)歷和思考的過程,反省一下看看自己在接觸這些新鮮事物的時候到底走了多少彎路。

            o Cygwin

            今年3月份,拜Kevin Lynx所賜,每次對Linu淺嘗輒止的我終于下決心接觸了Cygwin環(huán)境,并一發(fā)不可收拾。

            剛開始的時候,就像大學(xué)剛接觸編程那樣,寫“hello, world”,在終端用gcc命令直接編譯,然后開始寫最簡單的只有一個all的Makefile。因為Emacs、GCC、make對我來說都是嶄新的 工具,后面重心就不是放在寫代碼上了,而是急于掌握他們,以求達到在Windows下的開發(fā)效率。

            去年11月底,當(dāng)時還沒有開始用Cygwin,就買了一本《Managing Projects with GNU Make》,此時也算物盡其用了。慢慢開始使用variables、macros、phony targets、functions,按步就班的系統(tǒng)學(xué)習(xí)應(yīng)用。

            o Ubuntu

            磨磨蹭蹭過了半年,其間因為忙著畢業(yè),對Cygwin和Emacs、GCC、make也算比較熟悉了。

            今年10月份,開始使用Ubuntu,剛開始在Windows下用wubi安裝,很快就直接用新的硬盤分區(qū)物理安裝,并隨著Ubuntu 9.10的發(fā)布,升級到了9.10

            這前后寫Makefile最大的區(qū)別就是,之前純粹是為了寫而寫,之后是為了用而寫。

            隨著整個代碼結(jié)構(gòu)的不斷膨脹和修改,Makefile也不斷的變化。

            Makefile自身的最大變化是從之前的因為編寫錯誤、通用性差而不斷修改,演變到最后代碼增減不會影響Makefile,只是為了增加tags、優(yōu)化結(jié)構(gòu)而改動。

            經(jīng)歷了這個過程后,對于Makefile的結(jié)構(gòu)就比較熟悉了,而且可以從其他使用automake的項目的Makefile中學(xué)習(xí)借鑒了。


            之所以想到使用autotools,是因為接觸的很多開源項目的代碼都使用了這一組工具。

            對于用戶而言,一般的項目編譯安裝的過程:

            o bootstrap:檢測autoconfautomakelibtool及其版本并完成初始化,生成configure;

            o configure:檢測系統(tǒng)平臺及軟硬件環(huán)境,確定適用本地環(huán)境的編譯策略,生成Makefiles;

            o make:編譯、鏈接;

            o make install:安裝;

            o ldconfig:配置環(huán)境變量。

            對于開發(fā)者而言,則需要通過autoconf、automake為用戶組織起上面的過程:

            Autoconf 流程
            Autoconf 流程

            對于這一流程,我的方法是照葫蘆畫瓢,參考OGRE等項目的相關(guān)文件和工具的GNU文檔。

            寫個Hello, Kitty。

            操作的流程和期間出現(xiàn)的幾個問題總結(jié)一下:

            o cd project_dir:轉(zhuǎn)到項目目錄;

            o emacs Hello.cpp

            #include <iostream>

            int main(int argc, char** argv)
            {
            std::cout << "Hello, Kitty!" << std::endl;
            return 0;
            }

            o autoscan:生成configure.scan

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

            AC_PREREQ([2.64])
            AC_INIT([FULL-PACKAGE-NAME], [VERSION], [BUG-REPORT-ADDRESS])
            AC_CONFIG_SRCDIR([Hello.cpp])
            AC_CONFIG_HEADERS([config.h])

            # Checks for programs.
            AC_PROG_CXX

            # Checks for libraries.

            # Checks for header files.

            # Checks for typedefs, structures, and compiler characteristics.

            # Checks for library functions.

            AC_OUTPUT

            o mv configure.scan configure.in:改名;

            O emacs configure.in:編輯configure.in

            AC_PREREQ([2.64])

            # 這個是自動生成的,因為代碼中沒有相關(guān)初始化信息,這里手動修改一下,非必要
            AC_INIT([CgFox], [0.0.1], [http://www.yulefox.com])

            # 這個是必須的,否則無法生成aclocal.m4
            AM_INIT_AUTOMAKE([CgFox], 0.0.1)

            AC_CONFIG_SRCDIR([Hello.cpp])

            o aclocal:生成aclocal.m4(太長了,還沒去仔細了解)和autom4te.cache;

            o autoconf:生成configure(也很長,先不看);

            o automake --add-missing。

            ……


            本來想等明天(今天)弄完了再詳細整理一下。不過我沒有打算把這個東西搞成一篇教程。記下來更多的只是為了給自己留下一個lable,知道自己這幾天在做什么。

            最近又是兩點左右睡。腦子里有個家伙告訴我這樣不好;另一個家伙告訴我他還不困;還一個家伙告訴我明天還要上班。

            我去你大爺?shù)模?/p>

            Feedback

            # re: Autotools初體驗[未登錄]  回復(fù)  更多評論   

            2009-12-23 08:15 by jacky
            autotools用起來太繁瑣,OGRE已經(jīng)用cmake來構(gòu)建了,很好用。

            # re: Autotools初體驗  回復(fù)  更多評論   

            2009-12-23 09:04 by Fox
            In practice, CMake not only lacks a rich platform tests suite, compared to autoconf, it also lacks a lot of features from automake and libtool.

            So why should you not switch an autotools-based project over to CMake?

            Tedious
            First and foremost, your configure.ac script may be large. Porting to CMake can be a time consuming and not so funnny task when it comes to the long tail.
            iconv support missing
            There are no standard tests for iconv(), neither for finding the compiler flags, nor whether it takes a const pointer.
            pkg-config support broken
            pkg-config support is reportedly broken as of cmake 2.4 patch 8.
            Exported symbols list not implemented
            There are no documented ways to specify the list of exported symbols for a shared libraries, so your libraries will unconditionnaly expose all their non-static APIs (libtool can use a flat list or a regular expression).
            C99 compiler check missing
            There is no built-in support to enable C99 support in the C compiler.
            Objective-C flags not supported
            You can add flags for the Objective-C compiler, but they propagate to C compilation as well.
            Compiler feature checks missing
            There are no built-in checks for any of the C99 features, such as variable-sized arrays, restricted pointers, macros with variable number of arguments, etc. nor for GCCisms.
            Monolithic installation prefix
            There is only one global installation prefix. So the typical Linux distro cannot set the global prefix to /usr while the system configuration (automake's sysconfdir) would be /etc. Very nice for "downstream" Linux packagers...
            Installation paths hard-coding
            As a consequence of the single prefix, you need to hard-code all paths from the prefix. Instead of ${docdir}, you need to hard-code ${prefix}/share/doc/${package} (${CMAKE_INSTALL_PREFIX}/share/doc/foobar in CMake parliance) and so on and so forth. BSD porters are going to have fun tweaking the paths manually...
            Uninstallation not supported
            There is sipport for uninstalling. That is a design choice. You'd better never ever try to install a package straight from the build tree, without a proper packaging system.
            Installation testsuite not supported
            Since there is no uninstallation, there is no of course no distcheck target either. How often did you get your source tarball right from the first attempt before a new release?
            No cross-compilation
            There is no documented support for cross-compilation. This is scheduled for a future release.
            Limited documentation
            Compared to autotools, the documentation feels a bit light. At least, there is a wiki, but that cannot replace a good offline reference.
            Limited executable renaming
            CMake is not quite as powerful as automake (with program-prefix, program-suffix and program-transform-name) when it comes to on-the-fly executable renaming. This little-known feature of automake can be extremely useful when building an operating system distribution with possibly conflicting executable names from different projects. For instance, it is very conveniant along with the Debian alternatives system.
            No source tarball packaging
            There is no built-in support for making a tarball (make dist). Some Version Control Systems can do it themselves (git does, Subversion does not). This is quite critical a feature for open-source projects.
            No source tarball testing
            As there is no replacement for make dist, there is no replacement for make distcheck either. From my not-so-humble experience, that is tremendously useful before doing a new release. (NOTE: when I write distcheck, I mean distcheck. I don't mean check which becomes test with CMake)
            No gettext integration
            Gettext is not supported. Targets for .po and .mo files must be added manually. Nevermind that this is the most widely used localization subsystem in the open-source community.
            Awkward feature listing
            Whereby ./configure --help gives the list of build option, cmake --help prints the CMake options only. Instead, it seems you have to run cmake in "interactive" mode and answer a question for each and every setting (much like Linux kernel make config).
            ---------------------------
            當(dāng)然這些問題對于我不是必需的,不過還是等我autotools用一段時間再說:)

            # re: Autotools初體驗  回復(fù)  更多評論   

            2009-12-24 10:31 by 飯中淹
            這個相對于IDE來說,有什么優(yōu)勢?

            # re: Autotools初體驗  回復(fù)  更多評論   

            2009-12-24 10:52 by Fox
            @飯中淹
            這套工具現(xiàn)在對于我更多的是一個學(xué)習(xí)和試驗,如果希望和別人交流和共同開發(fā)跨平臺(尤其是non-win)的代碼的話,由于需要對依賴庫進行檢測,這個工作可以由autoconf+automake來完成。
            国产一久久香蕉国产线看观看| 99久久做夜夜爱天天做精品| 中文字幕乱码人妻无码久久| 97精品伊人久久久大香线蕉| aaa级精品久久久国产片| 嫩草伊人久久精品少妇AV| 欧美牲交A欧牲交aⅴ久久| 久久精品国产亚洲av水果派| 996久久国产精品线观看| 人人狠狠综合久久亚洲88| 国产精品久久久久乳精品爆| 久久免费99精品国产自在现线 | 久久亚洲AV成人无码软件| 久久久久久久免费视频| 亚洲第一极品精品无码久久| 久久精品a亚洲国产v高清不卡| 久久精品国产福利国产秒| 狠狠精品久久久无码中文字幕| 欧美无乱码久久久免费午夜一区二区三区中文字幕 | 思思久久99热免费精品6| 亚洲美日韩Av中文字幕无码久久久妻妇 | 久久久久久精品成人免费图片| 久久午夜福利无码1000合集| 久久久久av无码免费网| 国产精品久久久久久影院 | 欧美日韩成人精品久久久免费看 | 久久久久亚洲国产| 精品蜜臀久久久久99网站| 久久精品夜色噜噜亚洲A∨| 综合久久国产九一剧情麻豆| 久久精品国产99国产精品澳门| 久久久久亚洲AV综合波多野结衣| 人妻无码αv中文字幕久久琪琪布| 久久婷婷五月综合97色一本一本| 久久精品这里只有精99品| 奇米影视7777久久精品| 性做久久久久久久久久久| 久久精品国产91久久综合麻豆自制| 亚洲精品综合久久| 精品无码人妻久久久久久| 久久w5ww成w人免费|