• <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>

            gcc 庫順序問題解決方法

            Posted on 2008-11-09 12:18 小蘇 閱讀(11050) 評論(3)  編輯 收藏 引用
                使用gcc生成可執(zhí)行文件時(shí),大部分時(shí)候我們需要連接我們自己打包(AR)好的一些庫文件,對于中大型(50萬代碼行以上)項(xiàng)目上,你將面對數(shù)個(gè)項(xiàng)目組,最好的情況是每個(gè)項(xiàng)目組發(fā)布自己的打包.ar文件,這些.ar文件之間沒有任何依賴關(guān)系, 然后由持續(xù)集成(ci)小組對這些包進(jìn)行連接,不幸的是,這幾乎是不可能的, 我們在連接時(shí)還是遇到了liba.ar和libb.ar相互依賴的情況。

            因?yàn)間cc的庫是個(gè)有點(diǎn)怪怪的特性,在看-l幫助時(shí)可以看到:
                   -l library
                       Search the library named library when linking.  (The second alter-
                       native with the library as a separate argument is only for POSIX
                       compliance and is not recommended.)

                       It makes a difference where in the command you write this option;
                       the linker searches and processes libraries and object files in the
                       order they are specified.  Thus, foo.o -lz bar.o searches library z
                       after file foo.o but before bar.o.  If bar.o refers to functions in
                       z, those functions may not be loaded.

                出于知識產(chǎn)權(quán)保護(hù)的考慮,每一個(gè)項(xiàng)目組可能只允許看到自己的代碼和別的項(xiàng)目組的頭文件,這給CI小組帶來了很頭痛的事情,很多時(shí)候你不得不把庫順序來回調(diào)整。我也遇到了這樣讓人崩潰的情形,問題是對于liba.ar和libb.ar相互以來的情形,你可能最終采取丑陋的做法,將其中一個(gè)庫在前后放兩次:
            gcc -o out.bin liba.ar libb.ar liba.ar -lrt
            否則,您將不得不面對 "xx not referenced"之類的錯(cuò)誤。

            看看gcc的幫助,有下面的選項(xiàng)
            -Xlinker option
                       Pass option as an option to the linker.  You can use this to supply
                       system-specific linker options which GCC does not know how to rec-
                       ognize.

                       If you want to pass an option that takes an argument, you must use
                       -Xlinker twice, once for the option and once for the argument.  For
                       example, to pass -assert definitions, you must write -Xlinker
                       -assert -Xlinker definitions.  It does not work to write -Xlinker
                       "-assert definitions", because this passes the entire string as a
                       single argument, which is not what the linker expects.

            也就是說,-Xlinker是將連接選項(xiàng)傳給連接器的,趕快看看ld的幫助有沒有解決庫順序的選項(xiàng)吧:
             -( archives -)
                   --start-group archives --end-group
                       The archives should be a list of archive files.  They may be either
                       explicit file names, or -l options.

                       The specified archives are searched repeatedly until no  new  unde-
                       fined  references  are  created.   Normally, an archive is searched
                       only once in the order that it is specified on  the  command  line.
                       If  a symbol in that archive is needed to resolve an undefined sym-
                       bol referred to by an object in an archive that  appears  later  on
                       the command line, the linker would not be able to resolve that ref-
                       erence.  By grouping the archives, they all be searched  repeatedly
                       until all possible references are resolved.

                       Using  this  option has a significant performance cost.  It is best
                       to use it only  when  there  are  unavoidable  circular  references
                       between two or more archives.


            不錯(cuò),我們有個(gè)有點(diǎn)怪異的選項(xiàng),-(和-),它能夠強(qiáng)制"The specified archives are searched repeatedly"
            god,這就是我們要找的啦。

            最終的做法:
            gcc -o output.bin -Xlinker "-(" liba.ar libb.ar -Xlinker "-)" -lrt

            這樣可以解決庫順序的問題了!問題是,如果你的庫相互間的依賴如果錯(cuò)綜復(fù)雜的話,可能會增加連接的時(shí)間,不過,做架構(gòu)設(shè)計(jì)的都應(yīng)該能考慮到這些問題吧。








            Feedback

            # re: gcc 庫順序問題解決方法  回復(fù)  更多評論   

            2008-11-09 18:43 by 踏雪赤兔
            好物,謝~

            # re: gcc 庫順序問題解決方法  回復(fù)  更多評論   

            2009-04-22 13:43 by sxg
            受教了,謝謝!

            # re: gcc 庫順序問題解決方法[未登錄]  回復(fù)  更多評論   

            2011-07-12 06:13 by Andrew
            Thanks!

            只有注冊用戶登錄后才能發(fā)表評論。
            網(wǎng)站導(dǎo)航: 博客園   IT新聞   BlogJava   博問   Chat2DB   管理


            国产精品99久久久久久宅男| 亚洲欧美日韩中文久久| 66精品综合久久久久久久| 国产午夜电影久久| 一本综合久久国产二区| 精品免费久久久久久久| 欧美精品福利视频一区二区三区久久久精品 | 狠狠人妻久久久久久综合蜜桃| 性做久久久久久久久老女人| 久久精品国产亚洲av麻豆色欲| 国产成人久久精品一区二区三区| 久久国产免费直播| 2022年国产精品久久久久| 久久精品免费全国观看国产| 色综合久久88色综合天天| 三上悠亚久久精品| 亚洲伊人久久成综合人影院 | 久久精品不卡| 国产精品免费久久久久电影网| 人妻无码αv中文字幕久久| 国产香蕉久久精品综合网| 久久久久国产日韩精品网站| 国产99久久久国产精品~~牛| 无码精品久久久久久人妻中字| 亚洲国产精品成人AV无码久久综合影院| 国产精品久久久福利| 久久精品中文字幕无码绿巨人| 久久久久亚洲精品日久生情| 久久久国产亚洲精品| 亚洲精品无码久久久| 国产一区二区久久久| 久久久久久精品无码人妻| 亚洲国产高清精品线久久 | 国内精品人妻无码久久久影院导航| 久久亚洲国产成人精品无码区| 国产成人精品久久综合 | 精品国产乱码久久久久久1区2区| 久久精品亚洲AV久久久无码| 久久国产精品波多野结衣AV | 成人免费网站久久久| 久久精品无码午夜福利理论片 |