Ol%@}/"*"j@5pPT؟|{;mK{ٞ~t9Z?Uh}Н[ IENDB` jhbuild-3.5.91/buildbot/public_html/tab_right.png 0000644 0001750 0001750 00000002156 11243013407 021732 0 ustar 00fred fred 0000000 0000000 PNG
IHDR r bKGD pHYs
B(x tIME c% IDATxjTW ߉.ׅ>}XSQE-Ї(s#.%X"&sn(9dn>9"Ru;'y9+`i/^tWRDD:88P0pÝOwx[w<:ѻ?qk#" 0ӏsVDw<)Zֵs-Ξ]Ė>g7&_)I 麼umל#7=7Z0̕grr _|͙rs;ExR6U >_kN\D.
Rkm㺹rsۏH=9Kn>{nI `
傩 p o[sWNJ(=whumkΑϞol`jܘ>ל#7=7ߘ|{d>{nyϢ5k\s||Zql>{nay0/[{ֵi*~M L)sgrkۯ9On>{n)uOn9㷠znE2=79>sii +.o]=9Gn>{na:WVn?>5gg7< g7Q@ޮqef6O_8Ӑs9rs
\
o~;T{m\7Wn>{nyov6F
P0
P0P0 ` ` ` ( (@ (@
@
ZG^"M?#W"◽?[C:
;[Gƅ= DSut1s)^t _z
L(o >`}Nj'?& Q
P0P0 ` ` ` ( (@ (@
@
P0
P0P0P0 ` ` ` ( (@ (@
@
P0 c5*w_ IENDB` jhbuild-3.5.91/buildbot/public_html/offline.png 0000644 0001750 0001750 00000000650 11243013407 021406 0 ustar 00fred fred 0000000 0000000 PNG
IHDR a bKGD ]IDATxŐNA]lXh@|bGM#cIL,,}Ƃ *d nX3Ei䞹sgUs ʥ"֨V4VjS^^3u=#9vm\- @3 D 8donibgk{ں)sY ur|]t̜ƶX &b4L&>](+A
qT8suE?ir *=3O7 a.ï/.x} L:e%KE2 4[B81&ǀeO $@\R&s IENDB` jhbuild-3.5.91/buildbot/public_html/bar.png 0000644 0001750 0001750 00000000232 11243013407 020524 0 ustar 00fred fred 0000000 0000000 PNG
IHDR !p pHYs tIME LH8 tEXtComment Created with The GIMPd%n IDATc8s hg֊ IENDB` jhbuild-3.5.91/buildbot/public_html/building.png 0000644 0001750 0001750 00000001633 11243013407 021563 0 ustar 00fred fred 0000000 0000000 PNG
IHDR a sBIT|d pHYs
B(x tEXtSoftware www.inkscape.org< IDAT8mSMlTe=O{יN v~Z@!Ub+ݸfD722LBLXL2Lqacĕ@E%jjhmyﵔ7e Nr77''{.#"G; `;/3l/ax,~
48i|,"_Ƚ jkǶiٍ\ /kzگ mRbzf3_H)O0ƌZv*ή|!c1v(&J,80d2u{{519qV]wJُ J),-/D 5u Q_B `3L"b7o
j hܷ?ی]LFDrcŁ#B+.=o4 ~_{}d|ފ!Tl>4FZRvu M7:s ֭~~9jYHēeYb 9s.+H: Ni:#Cݕ U|G[[ n uu5 }K AW&A֎]TH|뭭 ]ӷ ~d3۶?0| $1i&JR;yuq .FGG|UinR !bavv|gj|" y ]U.
!v3 hMLaQR)277f&7EU*n*R8{e y'-<#a }=s\} + ]Ȥ?*|V r]jkH IENDB` jhbuild-3.5.91/buildbot/public_html/green-bar.png 0000644 0001750 0001750 00000000343 11243013407 021625 0 ustar 00fred fred 0000000 0000000 PNG
IHDR HlT bKGD pHYs tIME
tEXtComment Created with The GIMPd%n GIDATc`FR.mF,l! ,L ,0e````TCaR`R :_ IENDB` jhbuild-3.5.91/buildbot/public_html/error.png 0000644 0001750 0001750 00000001420 11243013407 021111 0 ustar 00fred fred 0000000 0000000 PNG
IHDR a bKGD pHYs tIME 01? tEXtComment Menu-sized icon
==========
(c) 2004 Jakub 'jimmac' Steiner,
http://jimmac.musichall.cz
created with the GIMP,
http://www.gimp.orgq IDATxڥKTQ?CkۄhE-j$D%- ο}6":!Z."%TZL͛ƙ{i1MM}r|9 1,@u)9~ |<0 b)[5J`(N0|{ld6C DA*|b$)[#C^:ƀ** (ϰYoqg\ 3F ^;3@<`~ Be5g3N}NjlٵZl\g 0u`?Cֲ\zam0\PU 42
TU)hO~lA+ L%ڭQE41~;jJ|6y)lwr0,-X[vnZ`iv|%qWS!" D{AZ3; x~?#G8ϢN(WԟP$5#x
qQ ̕93GfˬOk;t~ Ur _ IENDB` jhbuild-3.5.91/buildbot/public_html/figure.png 0000644 0001750 0001750 00000001034 11243013407 021242 0 ustar 00fred fred 0000000 0000000 PNG
IHDR \.& sRGB bKGD pHYs tIME &0Π tEXtComment Created with The GIMPd%n sIDAT8˵J@I?|%E{ īAg'/PKo-$mliY|Yg̉{sdaSkgڲf~afZ m_Z
zW]AYEX*8EU1@,ϯ~]~:WHx0stph=<bb,.ͮ:K-r1Ov Ġ
>9$L&Q;?_ 4D6Mdw"j2"#
xrt/bGIhݥM`3u}𭐩!I-0E-dHv:X պ BC/]\`QO.$0P IENDB` jhbuild-3.5.91/buildbot/public_html/gnome-gtp.png 0000644 0001750 0001750 00000010160 11243013407 021656 0 ustar 00fred fred 0000000 0000000 PNG
IHDR 0 < 9 sRGB bKGD pHYs
B4 tIME *
l IDAThZyxTUݷ՞JR@HB kؕAlAqkmfzF\vzFǥnQm{Pn\ !원 I*{%5#!$$"ǜ{~{~Tyi B ٯ'?4-5VmR7R8 !` jyfsQY7ػR/VJ2⠋S ŋvD LjZb_q-/77k`kf aӀb?M[j.X6~+7($K k)5h 'tOa;'Ѽ3_Ө,ў8hi;sO{0Jc$Iҏ7Џ?*`LvbEN8<0`HLR%A'hO.cLSq:%>RD9y] ml["P
pokZ=iM /* DGx|$ܦxw5;KlJȚ$h; V7k\Rze\WۡqIFy]L {NndGkع;$- K'㾋" .H4aHkslHUdʔpL Q<4d7 `;BN.N6KT
oDeY>+RUpHu]`Ƕ7QLJ-x!
vpoꗇ,˻ =ɹ )9Q6t_3 Dc)*yN~ MޝIuC jhirG&O
v9>|x_bdSB byMW
R/B,sb:JDf֜+ "HmYR{^~AT&Sc1ڜ۫zgcK=rFR*/hh -6{bQۊWD W W-/Z,ߵg0ԈYؓi456#~9K} ӥm6 P[v|sHAZZZ
vZqJڹWN[z D<7jrf:>'$( iT k^«ȁ` ;z}akk\r2 )T*I)C]4_ _г9F9
PJ4zy #QOުZgHF~2Htz{ ]. OoxnbYj ZqGC!Y;F Yݚúڬo)+32 DFpQY.,*AS+
x5Xfl6 BCSqv+\ /6BNg&iTL!}XF) (= rwԉ ħցdZ;D T$9|{oUj@~O;@GgF((RB;x/ 6Z ;2%Y
[+Y*{_k#md"Mn;cF+`X!=h(FjkX 5-b1B .ypٳw8,!9EpHBŁK8 =n*Ŵ!
u.$)zŽ 5 N*k*~&/R8kڏ!],t+XFG4Wt/
oXw?.ɆM @Q. }K@ۿ{)7aF, k4Y
6gڊY&<@JN@|*_oxl*80^+y3?;>7 jk5qF̩D?;?dp{~2 K@^iIOX
1k6O*!˱Iq 5 6W'ւCC(_"nJ<hS`Wnq}pI>h~)oX5*ڢTt U"PO ;ǭ@IC[OEC;r>8!EN@-U:خb=No@M^~]> ( Zgn~G #"Fq - @h|Q Lt ]
! 85n<+`y Z}_i (N\ e vka ~;-b_}1/ΠEDxZehR洐5'Du^ ͎$Š4q$98܄ۻy9MU!"O?ScK`1Ki64 ,K0( <酥9Ai@)pYBp,ɚ0D Ce7D g !0,{V
0 a4jk0%~0dN@gC<w ^ElɕA j@1J%SG"ql QЮFAh=TΦ4:=O<{獎X1!hLpE+!՞lᕠb;,]_M e'*`mYNJCXj "3 cE012wW4z ^;(z 5N* < rJVVb="܉f 9RBI\T5pъS3_2v_2I*22-%G~u vjVjW~"XH2p#<d H:@rIqO=9&'˨nrׁF.
ٜ]K9~9Ұ 'NZmӺj'BŖU#!z
+0u2gpD͍@0 mJOԹzMRV?X]-ƄUCJ´O?Zz-U
]X"Z@"|#-65G)q1Mfzxp@li{ymfu@0R`!'[O)TBjNx`WYfYۮ:ՕTҰșVgl0QǦ tz>^R5^}z^}nlV A\
%8v9UW0"0d.33vXӟ7 yI7* lr]c T͚+oË2ޞ[Vg5Ww`+?C#e?z`iOr~N2P=kcsd 2!H6rGT7Xc ᯐU6@jJeؽ (ee5'--]J 5:x|sӻU \-Of nȔ3ƦO m^DAl;U-T[?`}+ͰWZZse): g J) .6;QiulT2, dRU ώ O@* X;'۸cJ~NOպ IENDB` jhbuild-3.5.91/buildbot/public_html/purple-bar.png 0000644 0001750 0001750 00000000343 11243013407 022034 0 ustar 00fred fred 0000000 0000000 PNG
IHDR HlT bKGD pHYs tIME !wd tEXtComment Created with The GIMPd%n GIDATc`Xc3-6fPFF.z1^1000!m%() + IENDB` jhbuild-3.5.91/buildbot/public_html/robots.txt 0000644 0001750 0001750 00000000032 11243013407 021321 0 ustar 00fred fred 0000000 0000000 User-agent: *
Disallow: /
jhbuild-3.5.91/buildbot/public_html/general_separator.png 0000644 0001750 0001750 00000000324 11243013407 023457 0 ustar 00fred fred 0000000 0000000 PNG
IHDR v6 bKGD pHYs U U+Kp tIME 7
F aIDAT=ͱ
0EQ,x YEF|)RDJw1TPkͪ>nپ\}u
HlvS"b
xRDlv.zN IENDB` jhbuild-3.5.91/buildbot/public_html/emptyimg.png 0000644 0001750 0001750 00000015502 11243013407 021621 0 ustar 00fred fred 0000000 0000000 PNG
IHDR Rl gAMA OX2 tEXtSoftware Adobe ImageReadyqe< IDATx][\Wvwj],mc4x88$H^&!@^1?d^!0K$ f ~diƶ$쾩ꮾU,u.\뜪`sNv.Zk~ed4Ա!0202202=woܾ}[; [[nE9 {Ocs_02
F@6ѐ%F,fddhTaFF>aFDJu 駟Ghӻo/xu:/nhU|fNp P0J0?LՄ! ?L* sGgBSD0wń,4aX*mZSO!_gRQ"2A
%²D:+? 0Wyr.Ҳ {qUhO2Z,d0;N=a~i9'q4 3ԩ?vRË }w [
=Rr>%W0ͷ gЬ? !Ofc
&|q#b1vww߇Ckþ_=$9ͼVD@?a *ZW>X ￛFۇy~uDG B?^M| Exb W =]Gr FAFs
DXl1OD1{T+Lh]3ypk' O5{lg? P[
=K гt + atRÊ8D}|`uuIt@3@i@%XEg 럵z%B1~L=_0rrO0vtVid&
] "$j?m _pw ,@ۋr~eљld~}V4*G8vP_5|/{ 4
- /̯!M-0
7'PNS`1|[X",Z d|sqpNYM
DXE.}F2]k6DX5B ͯ=i2/ awZ//38yk> @ј_Bha|.u*JZy,!c%ɲuB@Kȣ5?AϿ* 0m jzYE`i oZ5X", l!@%9tpgF!ZwK= ! F5,bӘWYfuf~íQLE{i&P
^
u<,@Fͪ11{n?ˤcS~swh7{ ^ŕ }!u2̍%8i$+G6IR",on
^1'.x `,V(v Vvcр91w2~Țc'7|N- D^O G,f["@$K8 (niGѿO|,9@@Q1Vx5 DL rD}d-@ 66f8 8{T7wB0e
7oe%
]&]0Y~6z gOi4PHJzKhoAka
כYQ\obsg0Wq&XB\G0fmy=~ψWӣa
,eAfLQ f]":r }Bz Ǹ2E sO?0Z @ wi!U̪NHSBKoh]ϟ7 ˃?ƽWw]~1vxz cÇWk# uߺLhd-˲f~%-!O { % x+YY XO"P("eF_1d||Je*@G2O
<8_\K=C?L1i 3ea<21Y 47&' dYHK~XS8 ʚ]#ߛI֧h5CQX?I=3Al$Nwqv}4vj
%9iA[u%0g!|ʓcifQU('7 i!%B( ; QZ_U
w,X>1'VIYs806f@;pLDb'eZ{J Xi7J%SXS/- S s`=Ń;?#)C}S kYwt-
TSH3P-fU,m㚴 4|bmg ~ aN^&+TAZAS0 ksY[ tSxf=Aq2NdE-s=iXRa,D`R Z ԙ|5#< I') r ^7[0̬Aڑ8vqF *%*: ',b$?
uebgfʞǡS?p;qZZ]y$q~FNxR73i!"=f% x:fc$uHO
(`v-ty ,wȵigXSsNU8I}O l1l F ZgkUPF ,!jc,;Ӥ4 caz@.3nD3_
tC+[9ŁOsQ(f7Z` t
R
ۣtpR+:1uOeAoaϞ _ %i%&n9/w aD; '# JLѪT@ WP}7D-(mQ:'0DM9"Ga*ӷrjF ~ k Ʀ);zhӜU6fgg?de.; Q;¸VUnJ; bˏ,Uz"V*x :=Ml ayHQ(we3K0 `N #,~|
.{ Ra 6
Sm-/ }- kʬO,oqa Oc@u"9["Be1T`EKqRP}<}㲇d; |4ahp92݁5X1KĶ pV(s .c=:2'`0'^21VShKN/? =Y" K@ ô}
O}O'3rg*G :j{{땕V)xsP I5K̛$=.r1
+p~qc : >HJUIY4_DA %U[A@wꉴDX ' cHݞ8
xzUh(=Ghw>A ;_9
U"n¼:==}hN}6͑G >yR0?<34[N D(A dٴfPH J+aZM:7\ ! ƿ^ $M"5X@HOpb U}eshǏ [YY>R@!V 5.J ]X#DdB'̢jfE0[[OCwwu>VͩQ/PbK!&$Ck@h& nzI85K] \ ݂
AEç&TxФcCH[+wF
[AHG]_oll ti Y°Q?VHB" 8; "\7)Z
ѿU0``u!4X+:ُx7A0L4zDqF!nOOO;nfIq>ڨڝdB)Wk cCd 盛V yщ JG!jFjDhpoXt :gϞmCσ^]A;w* N#NϳlBgpQ3ϕ[h_} e;hbqZraht"ڵkwz,eI]Sm0ap~rrra46h,c&cBC%@/m?P+29%s'
R|B}fOLǴ. o߃ PB+( QF
SK! "/< ^ƽ;:Jq 8q p!{JMvUn b2>Ļ,(xmjs% @N J yzdcA
|A><#/ ]k[FYv.E%:64FLfF,fdc,f4Jd> ^222 `d42>ѐ%F,fddhTaFF>aFD XaFfF02RD%*Y"X"h| # +Y",( FFCJa @Xd4=y贑9FF& FF& FF 0 |cُ IENDB` jhbuild-3.5.91/buildbot/public_html/idle.png 0000644 0001750 0001750 00000000642 11243013407 020702 0 ustar 00fred fred 0000000 0000000 PNG
IHDR a bKGD WIDATxՓ=HA !591ZX% "ANK<@J ,--BBlB&IBQ3AӋE"z Rv̾مTU$ Ub; \r3"1M(s 1MZ{;l搩 լmT*(%xp7a1?FqVkuk@4:f!2w5j]EQX)rXcg'JwD6[zp
!@"ޥTҩJ`
˓3f=NsH(m fMHS!GY~ IENDB` jhbuild-3.5.91/buildbot/public_html/download.png 0000644 0001750 0001750 00000000670 11243013407 021575 0 ustar 00fred fred 0000000 0000000 PNG
IHDR a bKGD mIDATxڭR1K@}B RԔ"ĘM@]\2ttprѹFN]\$ $YȝCA\&?{w' hL88}:Fg~Ƀo[#x!
'3)ބ\NG ̢שu gd%Mz2>n欮6X{"~\VUkmEk ?sd^I҃F._n_Te
@J"ӐXgYzبwf3A2E۶a&,BTbx ] zEQ@`0@BtJq#Ϩ(
2 ǁ(0 cbSܓ8NG
r}?<*',^"ϊ;
IENDB` jhbuild-3.5.91/buildbot/public_html/gnome-16.png 0000644 0001750 0001750 00000001212 11243013407 021310 0 ustar 00fred fred 0000000 0000000 PNG
IHDR a pHYs d_ tIME3;m )IDATxc`ce```>}U FaQ9!Q!pAaakE
̙:z&tXX(++geggprrgae
deggbeggc066އaBjZ[mI~ӧ*IYF)YYy}֊`fe ,ϵPTظeՏY2oFFeX
orrtVJHy _}gHH|Ye̱73&0q21 aJ0000_2/(+:e
>n 2 ]++Cj\ԿبFNx
``f`jk24]VWMӰq YXgae0sek *x|Sq%vu1HQ$U y)4ʖۻwB&ͻwD<.Ul %TRPJ m
N ѧj)et2fI)`+ sĘ` ;V< >'Nx7Q3BغuksцmڽUa'j1!R ˹Dvww~juu&Ԥc
{ kK)%,e\]ϡ(< $GQc Ǐu;H8I8
3f̫۶mۘN/}_ϮIA$PE!3_RSSCl6Nkݯth4G3_ F ձ؛HG (0cƌ$|mDlYW K16\sT*Uw 3aHt' x [7'Q 8$ oJ ܇k_3}7j'' NvL금U9 d˙9,t"1E yW(? cRd2Ɏh{cs cʂ=@I+ٮ\!Z7deڶOq衇©T1ә6VD<V- e!\Xc(,V
3PBu";H*a/lKrsΙw=oF[-[vO ,+Jq!ۖ$PDŐvBJD>cF0lEA1ZѣN$}x BR)BpfSv k
5;ݡ
Ax|MFmOBP&PU&@) RFWqsKme
R "zP( f; Kp Ì.?~n'o i¹\n1hNr9X
8)2HL&ۮhhXwáelWλjթTqormX 1 'ޓlg4gEѭf㇑M`̘1C:;; ʞAR|;jkkWf\M\2|o ^~;3._q˿ԖJ^%"F 1`Mn6d:: :H,[a5}={v*Hi#W
A(d?H$fwwws{!['W\O ~;>dWw^uxmso[6@"85s Y7 D&0 vw}f^s̲g&M}X utļ]E!ֶY>h
~aӿߪS%m!L ag{mmB~\0?~j尐 *|mߘQ XED\|p8\E Ӕy$ĩ7:yǎ Q|yXlYǎ_
s<!)$HV՞i?wvvG߽d2fݹXtۦT*u Of~|M7]ছ wD/6 #NqB &xZ|LϿ'=GDkx#ᐐRBJK D#Hhm^n8pࡧ~UR[Nt;bث^2| "z~HD˅/Ӿ,XкE+
՞ę,:ٶBXuk72dc,[q_
߿ Dpg Y|TT*uɓ 1|-mzZ|w}9D\ϟ9sZ+P! )fcǎ- >|˲e˼E.^-p5t7 /j)Oͪр۶9
(~ e1̃mʏL[7l{Co"ϰ!7!y@[[[\fIJ%10$D`\co>Z| 0aB vh&셨d ޛ߰akg۰a d(!`Ii h' rk1f3 ¶@z"H fiy `60:־76ܸq f9sW^y%g /u˛7omik / <mWSNB0i431
JjeY LI0475?E3x%bY!u̙3~W/~v֭þTPM"(j;˹o_<^1xW_}u-yDPdS/lm\.sHģRJ,H%rqr/sJL0 Y
%K|>@Ggw"XJE,%aP%2JRT>W
^ҎG+ ض͖e@@=sӧ:VpJ.WrQ1_Ro.+|6GM%O
~d +1 }ch4BB
G١ܡl
WPl\=qH`SSBs >: @C,UA -UȊaxDnu? |cz>Ma+m{E2̕Zs]{&8
+"@|q-@yDZmP(x~L&
>K{omξ m1Uz* #8#`YZPt<]=q茔r#<$ Rt[𐭂=M@A驪/٣);r5h_k WW_wݬeijjI!_B)5}=C!+j 0W֠\Y_{G՚aFk t%OΙy "Zo~sKýP(Ty4l#m~,U`q]'i'=8l)f^կ~j۫`<1N6^> 2W>xkmdu<7ο~8B/.]>)ǁʔ+=^+5|7B}Çghk'CJQ7Z Qfe?RjeY/.^<'+W>4 v -A !*gT8e=~>ζ%1ƈHy֛nm~g1,YKw>4 K.V\ْL8udZzcN<2ZC d'O ;#xOӅL& )%E;ƎvK!c@گ2 ٜ0:=oIBzG `ŊV}}Ƙ1DtIPG"<_xRx㍻/
JWM2l8%$Ro'^_:1̆cWz- ~E4 Yfrn.Z~}}d:0ڤ,,öݱׯy^SF]vOWl{>`)eW*}/,H?;{V+Ν{tK/4G. 0DP\$RJVUw7 [ qy
DϙԶT)pƆ?=ƘʅߴiSڶk|wʑG))#m
\6sL dk;Z>/[Ǎ3\+7z^ J͛W1cpx;2
YYgWH+omgeYE4mo= Ng''NL|LL{,Cd `ISd.
0cƌfq>~U "w3y۶muӦM,8 [ HWx˶
rs (f2iR`>ul־?qW 577OinnjY֤_y Q!C55˲O4)sQ@sF)g-hS X3!{z t\5y3w-Q% ;ö
~,N!"ȲTsT J)gVlb/
'A]T*. f?mȑ?gf@&Ha:F k/ *])=W[[;~l6;B)uӪիcw2ciI]E-'?ZZNN\z1.şТ[n &"jh_c}# .ഴko8vvfՠA+wnj 67'th i $ C,c ^@+ IENDB` jhbuild-3.5.91/buildbot/public_html/info.png 0000644 0001750 0001750 00000001037 11243013407 020717 0 ustar 00fred fred 0000000 0000000 PNG
IHDR a bKGD pHYs tIME 7UB IDATxڵ=Ha wIFbA=IYE** `A XJqpk)-t @(P/E1 YD-X&i*jL.oF3:wz@m"^҄B{0>:l`tz݅(uFC*s#<Mf2nΞ MϑΨ|筄Y:S<-
~%.y;0樬pQr; 7& %8=O~ ;ٌ2BDRUU3$l6K4 BSuc oc1ގrGG '8 4/*qwx_;$n[lmoX=gg/:wԡnpY|yiLfo[xQ6JUgw IENDB` jhbuild-3.5.91/buildbot/public_html/webpage.png 0000644 0001750 0001750 00000001514 11243013407 021376 0 ustar 00fred fred 0000000 0000000 PNG
IHDR a bKGD C IDATx]Kk$eꪾ& $Nm:㘌q\
"b*wnAƭ? ^ r@$&LL\Ituݿʅ=zVy^*o*܅'f
jښcKvＳi9@<
c3 թW| L%%R{41yzp H 2eKŬg._˨ny @?kч /\Otť;ﾧT.L'bGFyy5egw~d $*' AJ##R d9 V~z; 5_T/]룅R-J#BFM:78
2B&k+ b4mz'lI\&+BTUf.N!|pnԞ~VH4H]il@F8~xx~cܽZgZV)wǭӀX2?[#%=q $1ipڙ 'e!OUljd>[]l˥^ bN8;iF@Xr~gA>c[iRrxH{: ` ;to;k&q>mc[mtacv' p j?(p+a}bv>@4_k +;S"=Ό>f
%-X jEX+[Uwx
0?e ET t7 ߛvW7B IENDB` jhbuild-3.5.91/buildbot/public_html/nobody.png 0000644 0001750 0001750 00000013105 11243013407 021255 0 ustar 00fred fred 0000000 0000000 PNG
IHDR F F q. bKGD tIME; t IDATxi uYYG3=G08%S(KzZZ+
ɖ)a-a\c%r8|( 2%ҮdYH$ " 螣*3CU 3~U]S_9r%"9_QVh[,à.`Z Fь
ɡ2;Ql_ƶ 4J/n/HK']*69 Tω(B ah~}d!N!즏г^ $C P-_tx讏y!0zo0 oMo!,q> cj`X]Hg)J Ǝ= )a_xZI5F 9Ƨ0߬O^MX݅-*+0:BmFmftW CVHQ*nM mVP(0=ƛ|a* kZPQ1VZk:^ F'-ᡢj[ +Qz=\ sNQ`!K è
AuVU *AGo Q5t0-0v̫h P-QxE~
a9t't0>FGze7Z'*ZUQfj(FE{*T|tT%ϐߪ
%ֆQGEUv~݃mbt in[ W*(5b0PT4VӨ$@8Ę:>B??;QQj9T8AB0 a7=`7Ch*c`h
M5 4:IT0
T*D$a aPNIwVZBu -.2-TTcr1PZ
cj]u
| N&`L4ZIEs }}W `zlmVe+A8A !l cjD8* iBX.B8 d< d6S-I| $ɦQcP3 6]TVMV`j'Q4B! ЪW.QTtqT44Z$3T #Fj&8vc%w?
6=rB 0)^pn84Be'Oo&_?I CЍ҃pOo!f~ D3[b[eҢɯp| fE$Y#$SXfbb(T2'e2]<浅ъ'>Bpw8
@QJIWosV ;n1Ql6X//{Q Am
#^YN fbLF x[,ZN !,2]HaSFg7 tat%0TzMn?B^cPh` z}w㦖!?y 0 9΅<#CTMaD( nH:7n,BeV]|]w tmw=rq֭]Moc Q^1@BlAJٱs= -[;L:ձ?N1| AۏiHqQ')әFcfȅD ljYTĞ{ٳw}[Yb%6 ZDo{u2 f˖-Z n+u0fF&]Ύ sa m;.-H ˊ)m '1 92Ķ/066EKYv G*fѢŬ_:x@{o
ټysķ u]j5 j<:fzs]aș)hPl\%4_ellcNdYjENdr),KX;:c{'3<^^ cY{{zz{ lۦZ$S I74㌎2|fL"]ݤ Ll6M*F)WǟY+_[2/c>(rAG>ZLjڌZ10Ln.<'p Kd(_@:dY2(Y6Xfs,[ڻφ_xnrvճ##ZLiݛOd< }zSߛWDʐBAP:{mM I)ⓗ4wNF= qk'sKqZZ|JZ° xVoh.(}[2#)E[Zm˖-'|R
mɒe" ('m \ST.} 5w RJcE?}M9qR!D:EEJJ2+ 0ktaPf?eBz0@q W*]`}!\;+R>}B9 }T{B }f Cz}oGCXk5F ]T3l 'OjFǔZ3Mu]&'(R"z
,!V]`z*~iI2 ߯1>>F>9|\Kَ9RycRi|%{B(ñcGd2tu}}{|>K ۖJ%,ˢZBԀpZ|#?H= #e\@}RL>ö4?;zv¦=r92r)Il(: JcgΞ1N&͒Myݗ~& CJ2J)0N6t2Q0x~a 'ϑeirk@;sӁv
BL0xG 1JegC.S0m[{v𰘜l&zlncΏY.d.s,:t{z
h(Hi3Q`bb:u> )cr_yXX,.ąJ67-ɐd0P(`;_ڡU+_w5o>Mv 9_`_oX|ާ37=s^4*14I;3gRR*M~zN:ɞЖv|x Z=9^tqk5߆<~5Wo[v AM1zCыK Liz{`wO/io}%-䥝/M+V/_Bz0&
JϾw~.y6[f &$p]\T*O _=Je
pɥi9as+>3nM鍮bq@ry i.۶Tdߥ%>o\ާS8n\.祩V+f;El=6@j\-
+HG.-co껗/[|pZbJS 奚 /_n( wӴ0d2~X ?~gΜVCbv̛-|{@i7֮]{W_omNJ5cNH)j5_LWԃz}D?8yd]E DkSծ+Ib`>{ VZog3k 첤l~%bJi 3O} 8[!-`"v6RU#HV IENDB` jhbuild-3.5.91/buildbot/public_html/tab_left.png 0000644 0001750 0001750 00000000563 11243013407 021547 0 ustar 00fred fred 0000000 0000000 PNG
IHDR r ˡ bKGD pHYs
B(x tIME уF IDATH핿J@ƿ ENWXݕ, B,ǰ$E.wl;Нj7,+`Y @Ђ# Ry@D fyxw0/fFfVcg0 l ɺ#]KY ٽ]Uk% #H Zmz\j=_P؎20 \XC>L}Eʔ[} ?P1\w@_y^y衇 -Yu
N IENDB` jhbuild-3.5.91/buildbot/public_html/general_bg.png 0000644 0001750 0001750 00000000262 11243013407 022050 0 ustar 00fred fred 0000000 0000000 PNG
IHDR Xt bKGD pHYs
B(x tIME *
ߊ ?IDATׅȱ
@!6 L0]Q헴{AqAQl>3k D5_̈́@ IENDB` jhbuild-3.5.91/buildbot/Makefile.in 0000644 0001750 0001750 00000037022 12021725530 017026 0 ustar 00fred fred 0000000 0000000 # Makefile.in generated by automake 1.11.6 from Makefile.am.
# @configure_input@
# Copyright (C) 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002,
# 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011 Free Software
# Foundation, Inc.
# This Makefile.in is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
# with or without modifications, as long as this notice is preserved.
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY, to the extent permitted by law; without
# even the implied warranty of MERCHANTABILITY or FITNESS FOR A
# PARTICULAR PURPOSE.
@SET_MAKE@
VPATH = @srcdir@
am__make_dryrun = \
{ \
am__dry=no; \
case $$MAKEFLAGS in \
*\\[\ \ ]*) \
echo 'am--echo: ; @echo "AM" OK' | $(MAKE) -f - 2>/dev/null \
| grep '^AM OK$$' >/dev/null || am__dry=yes;; \
*) \
for am__flg in $$MAKEFLAGS; do \
case $$am__flg in \
*=*|--*) ;; \
*n*) am__dry=yes; break;; \
esac; \
done;; \
esac; \
test $$am__dry = yes; \
}
pkgdatadir = $(datadir)/@PACKAGE@
pkgincludedir = $(includedir)/@PACKAGE@
pkglibdir = $(libdir)/@PACKAGE@
pkglibexecdir = $(libexecdir)/@PACKAGE@
am__cd = CDPATH="$${ZSH_VERSION+.}$(PATH_SEPARATOR)" && cd
install_sh_DATA = $(install_sh) -c -m 644
install_sh_PROGRAM = $(install_sh) -c
install_sh_SCRIPT = $(install_sh) -c
INSTALL_HEADER = $(INSTALL_DATA)
transform = $(program_transform_name)
NORMAL_INSTALL = :
PRE_INSTALL = :
POST_INSTALL = :
NORMAL_UNINSTALL = :
PRE_UNINSTALL = :
POST_UNINSTALL = :
build_triplet = @build@
host_triplet = @host@
subdir = buildbot
DIST_COMMON = README $(srcdir)/Makefile.am $(srcdir)/Makefile.in \
AUTHORS
ACLOCAL_M4 = $(top_srcdir)/aclocal.m4
am__aclocal_m4_deps = $(top_srcdir)/m4/gettext.m4 \
$(top_srcdir)/m4/iconv.m4 $(top_srcdir)/m4/intlmacosx.m4 \
$(top_srcdir)/m4/intltool.m4 $(top_srcdir)/m4/lib-ld.m4 \
$(top_srcdir)/m4/lib-link.m4 $(top_srcdir)/m4/lib-prefix.m4 \
$(top_srcdir)/m4/nls.m4 $(top_srcdir)/m4/po.m4 \
$(top_srcdir)/m4/progtest.m4 $(top_srcdir)/configure.ac
am__configure_deps = $(am__aclocal_m4_deps) $(CONFIGURE_DEPENDENCIES) \
$(ACLOCAL_M4)
mkinstalldirs = $(install_sh) -d
CONFIG_CLEAN_FILES =
CONFIG_CLEAN_VPATH_FILES =
SOURCES =
DIST_SOURCES =
am__can_run_installinfo = \
case $$AM_UPDATE_INFO_DIR in \
n|no|NO) false;; \
*) (install-info --version) >/dev/null 2>&1;; \
esac
am__vpath_adj_setup = srcdirstrip=`echo "$(srcdir)" | sed 's|.|.|g'`;
am__vpath_adj = case $$p in \
$(srcdir)/*) f=`echo "$$p" | sed "s|^$$srcdirstrip/||"`;; \
*) f=$$p;; \
esac;
am__strip_dir = f=`echo $$p | sed -e 's|^.*/||'`;
am__install_max = 40
am__nobase_strip_setup = \
srcdirstrip=`echo "$(srcdir)" | sed 's/[].[^$$\\*|]/\\\\&/g'`
am__nobase_strip = \
for p in $$list; do echo "$$p"; done | sed -e "s|$$srcdirstrip/||"
am__nobase_list = $(am__nobase_strip_setup); \
for p in $$list; do echo "$$p $$p"; done | \
sed "s| $$srcdirstrip/| |;"' / .*\//!s/ .*/ ./; s,\( .*\)/[^/]*$$,\1,' | \
$(AWK) 'BEGIN { files["."] = "" } { files[$$2] = files[$$2] " " $$1; \
if (++n[$$2] == $(am__install_max)) \
{ print $$2, files[$$2]; n[$$2] = 0; files[$$2] = "" } } \
END { for (dir in files) print dir, files[dir] }'
am__base_list = \
sed '$$!N;$$!N;$$!N;$$!N;$$!N;$$!N;$$!N;s/\n/ /g' | \
sed '$$!N;$$!N;$$!N;$$!N;s/\n/ /g'
am__uninstall_files_from_dir = { \
test -z "$$files" \
|| { test ! -d "$$dir" && test ! -f "$$dir" && test ! -r "$$dir"; } \
|| { echo " ( cd '$$dir' && rm -f" $$files ")"; \
$(am__cd) "$$dir" && rm -f $$files; }; \
}
am__installdirs = "$(DESTDIR)$(buildbotdir)" \
"$(DESTDIR)$(buildbothtmldir)"
DATA = $(buildbot_DATA) $(buildbothtml_DATA)
DISTFILES = $(DIST_COMMON) $(DIST_SOURCES) $(TEXINFOS) $(EXTRA_DIST)
ACLOCAL = @ACLOCAL@
ALL_LINGUAS = @ALL_LINGUAS@
AMTAR = @AMTAR@
AM_DEFAULT_VERBOSITY = @AM_DEFAULT_VERBOSITY@
AUTOCONF = @AUTOCONF@
AUTOHEADER = @AUTOHEADER@
AUTOMAKE = @AUTOMAKE@
AWK = @AWK@
CC = @CC@
CCDEPMODE = @CCDEPMODE@
CFLAGS = @CFLAGS@
CPPFLAGS = @CPPFLAGS@
CYGPATH_W = @CYGPATH_W@
DATADIRNAME = @DATADIRNAME@
DEFS = @DEFS@
DEPDIR = @DEPDIR@
ECHO_C = @ECHO_C@
ECHO_N = @ECHO_N@
ECHO_T = @ECHO_T@
EXEEXT = @EXEEXT@
GETTEXT_MACRO_VERSION = @GETTEXT_MACRO_VERSION@
GETTEXT_PACKAGE = @GETTEXT_PACKAGE@
GMSGFMT = @GMSGFMT@
GMSGFMT_015 = @GMSGFMT_015@
HELP_DIR = @HELP_DIR@
INSTALL = @INSTALL@
INSTALL_DATA = @INSTALL_DATA@
INSTALL_PROGRAM = @INSTALL_PROGRAM@
INSTALL_SCRIPT = @INSTALL_SCRIPT@
INSTALL_STRIP_PROGRAM = @INSTALL_STRIP_PROGRAM@
INTLLIBS = @INTLLIBS@
INTLTOOL_EXTRACT = @INTLTOOL_EXTRACT@
INTLTOOL_MERGE = @INTLTOOL_MERGE@
INTLTOOL_PERL = @INTLTOOL_PERL@
INTLTOOL_UPDATE = @INTLTOOL_UPDATE@
INTLTOOL_V_MERGE = @INTLTOOL_V_MERGE@
INTLTOOL_V_MERGE_OPTIONS = @INTLTOOL_V_MERGE_OPTIONS@
INTLTOOL__v_MERGE_ = @INTLTOOL__v_MERGE_@
INTLTOOL__v_MERGE_0 = @INTLTOOL__v_MERGE_0@
INTL_MACOSX_LIBS = @INTL_MACOSX_LIBS@
ITSTOOL = @ITSTOOL@
LDFLAGS = @LDFLAGS@
LIBICONV = @LIBICONV@
LIBINTL = @LIBINTL@
LIBOBJS = @LIBOBJS@
LIBS = @LIBS@
LN_S = @LN_S@
LTLIBICONV = @LTLIBICONV@
LTLIBINTL = @LTLIBINTL@
LTLIBOBJS = @LTLIBOBJS@
MAINT = @MAINT@
MAKEINFO = @MAKEINFO@
MKDIR_P = @MKDIR_P@
MSGFMT = @MSGFMT@
MSGFMT_015 = @MSGFMT_015@
MSGMERGE = @MSGMERGE@
OBJEXT = @OBJEXT@
PACKAGE = @PACKAGE@
PACKAGE_BUGREPORT = @PACKAGE_BUGREPORT@
PACKAGE_NAME = @PACKAGE_NAME@
PACKAGE_STRING = @PACKAGE_STRING@
PACKAGE_TARNAME = @PACKAGE_TARNAME@
PACKAGE_URL = @PACKAGE_URL@
PACKAGE_VERSION = @PACKAGE_VERSION@
PATH_SEPARATOR = @PATH_SEPARATOR@
PKG_CONFIG = @PKG_CONFIG@
PKG_CONFIG_LIBDIR = @PKG_CONFIG_LIBDIR@
PKG_CONFIG_PATH = @PKG_CONFIG_PATH@
POSUB = @POSUB@
PYTHON = @PYTHON@
PYTHON_EXEC_PREFIX = @PYTHON_EXEC_PREFIX@
PYTHON_PLATFORM = @PYTHON_PLATFORM@
PYTHON_PREFIX = @PYTHON_PREFIX@
PYTHON_VERSION = @PYTHON_VERSION@
SET_MAKE = @SET_MAKE@
SHELL = @SHELL@
STRIP = @STRIP@
USE_NLS = @USE_NLS@
VERSION = @VERSION@
XGETTEXT = @XGETTEXT@
XGETTEXT_015 = @XGETTEXT_015@
XGETTEXT_EXTRA_OPTIONS = @XGETTEXT_EXTRA_OPTIONS@
XMLLINT = @XMLLINT@
abs_builddir = @abs_builddir@
abs_srcdir = @abs_srcdir@
abs_top_builddir = @abs_top_builddir@
abs_top_srcdir = @abs_top_srcdir@
ac_ct_CC = @ac_ct_CC@
am__include = @am__include@
am__leading_dot = @am__leading_dot@
am__quote = @am__quote@
am__tar = @am__tar@
am__untar = @am__untar@
bindir = @bindir@
build = @build@
build_alias = @build_alias@
build_cpu = @build_cpu@
build_os = @build_os@
build_vendor = @build_vendor@
builddir = @builddir@
datadir = @datadir@
datarootdir = @datarootdir@
docdir = @docdir@
dvidir = @dvidir@
exec_prefix = @exec_prefix@
host = @host@
host_alias = @host_alias@
host_cpu = @host_cpu@
host_os = @host_os@
host_vendor = @host_vendor@
htmldir = @htmldir@
includedir = @includedir@
infodir = @infodir@
install_sh = @install_sh@
intltool__v_merge_options_ = @intltool__v_merge_options_@
intltool__v_merge_options_0 = @intltool__v_merge_options_0@
libdir = @libdir@
libexecdir = @libexecdir@
localedir = @localedir@
localstatedir = @localstatedir@
mandir = @mandir@
mkdir_p = @mkdir_p@
oldincludedir = @oldincludedir@
pdfdir = @pdfdir@
pkgpyexecdir = @pkgpyexecdir@
pkgpythondir = @pkgpythondir@
prefix = @prefix@
program_transform_name = @program_transform_name@
psdir = @psdir@
pyexecdir = @pyexecdir@
pythondir = @pythondir@
sbindir = @sbindir@
sharedstatedir = @sharedstatedir@
srcdir = @srcdir@
sysconfdir = @sysconfdir@
target_alias = @target_alias@
top_build_prefix = @top_build_prefix@
top_builddir = @top_builddir@
top_srcdir = @top_srcdir@
buildbotdir = $(pkgdatadir)/buildbot
buildbot_DATA = \
master.cfg \
template.html
buildbothtmldir = $(pkgdatadir)/buildbot/public_html
buildbothtml_DATA = \
public_html/bar.png \
public_html/building.png \
public_html/cyan-bar.png \
public_html/download.png \
public_html/emptyimg.png \
public_html/error.png \
public_html/feed-atom.png \
public_html/feed.png \
public_html/figure.png \
public_html/foot-16.png \
public_html/foot.png \
public_html/general_bg.png \
public_html/general_separator.png \
public_html/gnome-16.png \
public_html/gnome-64.png \
public_html/gnome-gtp.png \
public_html/green-bar.png \
public_html/idle.png \
public_html/images.jpeg \
public_html/index.html \
public_html/info.png \
public_html/lgo.css \
public_html/logo.png \
public_html/nobody.png \
public_html/offline.png \
public_html/purple-bar.png \
public_html/red-bar.png \
public_html/robot.png \
public_html/robots.txt \
public_html/star.png \
public_html/t.png \
public_html/tab_left.png \
public_html/tab_right.png \
public_html/top-header-gradient.png \
public_html/warn.png \
public_html/webpage.png
EXTRA_DIST = \
AUTHORS \
$(buildbot_DATA) \
$(buildbothtml_DATA)
all: all-am
.SUFFIXES:
$(srcdir)/Makefile.in: @MAINTAINER_MODE_TRUE@ $(srcdir)/Makefile.am $(am__configure_deps)
@for dep in $?; do \
case '$(am__configure_deps)' in \
*$$dep*) \
( cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh ) \
&& { if test -f $@; then exit 0; else break; fi; }; \
exit 1;; \
esac; \
done; \
echo ' cd $(top_srcdir) && $(AUTOMAKE) --foreign buildbot/Makefile'; \
$(am__cd) $(top_srcdir) && \
$(AUTOMAKE) --foreign buildbot/Makefile
.PRECIOUS: Makefile
Makefile: $(srcdir)/Makefile.in $(top_builddir)/config.status
@case '$?' in \
*config.status*) \
cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh;; \
*) \
echo ' cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@ $(am__depfiles_maybe)'; \
cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@ $(am__depfiles_maybe);; \
esac;
$(top_builddir)/config.status: $(top_srcdir)/configure $(CONFIG_STATUS_DEPENDENCIES)
cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh
$(top_srcdir)/configure: @MAINTAINER_MODE_TRUE@ $(am__configure_deps)
cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh
$(ACLOCAL_M4): @MAINTAINER_MODE_TRUE@ $(am__aclocal_m4_deps)
cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh
$(am__aclocal_m4_deps):
install-buildbotDATA: $(buildbot_DATA)
@$(NORMAL_INSTALL)
@list='$(buildbot_DATA)'; test -n "$(buildbotdir)" || list=; \
if test -n "$$list"; then \
echo " $(MKDIR_P) '$(DESTDIR)$(buildbotdir)'"; \
$(MKDIR_P) "$(DESTDIR)$(buildbotdir)" || exit 1; \
fi; \
for p in $$list; do \
if test -f "$$p"; then d=; else d="$(srcdir)/"; fi; \
echo "$$d$$p"; \
done | $(am__base_list) | \
while read files; do \
echo " $(INSTALL_DATA) $$files '$(DESTDIR)$(buildbotdir)'"; \
$(INSTALL_DATA) $$files "$(DESTDIR)$(buildbotdir)" || exit $$?; \
done
uninstall-buildbotDATA:
@$(NORMAL_UNINSTALL)
@list='$(buildbot_DATA)'; test -n "$(buildbotdir)" || list=; \
files=`for p in $$list; do echo $$p; done | sed -e 's|^.*/||'`; \
dir='$(DESTDIR)$(buildbotdir)'; $(am__uninstall_files_from_dir)
install-buildbothtmlDATA: $(buildbothtml_DATA)
@$(NORMAL_INSTALL)
@list='$(buildbothtml_DATA)'; test -n "$(buildbothtmldir)" || list=; \
if test -n "$$list"; then \
echo " $(MKDIR_P) '$(DESTDIR)$(buildbothtmldir)'"; \
$(MKDIR_P) "$(DESTDIR)$(buildbothtmldir)" || exit 1; \
fi; \
for p in $$list; do \
if test -f "$$p"; then d=; else d="$(srcdir)/"; fi; \
echo "$$d$$p"; \
done | $(am__base_list) | \
while read files; do \
echo " $(INSTALL_DATA) $$files '$(DESTDIR)$(buildbothtmldir)'"; \
$(INSTALL_DATA) $$files "$(DESTDIR)$(buildbothtmldir)" || exit $$?; \
done
uninstall-buildbothtmlDATA:
@$(NORMAL_UNINSTALL)
@list='$(buildbothtml_DATA)'; test -n "$(buildbothtmldir)" || list=; \
files=`for p in $$list; do echo $$p; done | sed -e 's|^.*/||'`; \
dir='$(DESTDIR)$(buildbothtmldir)'; $(am__uninstall_files_from_dir)
tags: TAGS
TAGS:
ctags: CTAGS
CTAGS:
distdir: $(DISTFILES)
@srcdirstrip=`echo "$(srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \
topsrcdirstrip=`echo "$(top_srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \
list='$(DISTFILES)'; \
dist_files=`for file in $$list; do echo $$file; done | \
sed -e "s|^$$srcdirstrip/||;t" \
-e "s|^$$topsrcdirstrip/|$(top_builddir)/|;t"`; \
case $$dist_files in \
*/*) $(MKDIR_P) `echo "$$dist_files" | \
sed '/\//!d;s|^|$(distdir)/|;s,/[^/]*$$,,' | \
sort -u` ;; \
esac; \
for file in $$dist_files; do \
if test -f $$file || test -d $$file; then d=.; else d=$(srcdir); fi; \
if test -d $$d/$$file; then \
dir=`echo "/$$file" | sed -e 's,/[^/]*$$,,'`; \
if test -d "$(distdir)/$$file"; then \
find "$(distdir)/$$file" -type d ! -perm -700 -exec chmod u+rwx {} \;; \
fi; \
if test -d $(srcdir)/$$file && test $$d != $(srcdir); then \
cp -fpR $(srcdir)/$$file "$(distdir)$$dir" || exit 1; \
find "$(distdir)/$$file" -type d ! -perm -700 -exec chmod u+rwx {} \;; \
fi; \
cp -fpR $$d/$$file "$(distdir)$$dir" || exit 1; \
else \
test -f "$(distdir)/$$file" \
|| cp -p $$d/$$file "$(distdir)/$$file" \
|| exit 1; \
fi; \
done
check-am: all-am
check: check-am
all-am: Makefile $(DATA)
installdirs:
for dir in "$(DESTDIR)$(buildbotdir)" "$(DESTDIR)$(buildbothtmldir)"; do \
test -z "$$dir" || $(MKDIR_P) "$$dir"; \
done
install: install-am
install-exec: install-exec-am
install-data: install-data-am
uninstall: uninstall-am
install-am: all-am
@$(MAKE) $(AM_MAKEFLAGS) install-exec-am install-data-am
installcheck: installcheck-am
install-strip:
if test -z '$(STRIP)'; then \
$(MAKE) $(AM_MAKEFLAGS) INSTALL_PROGRAM="$(INSTALL_STRIP_PROGRAM)" \
install_sh_PROGRAM="$(INSTALL_STRIP_PROGRAM)" INSTALL_STRIP_FLAG=-s \
install; \
else \
$(MAKE) $(AM_MAKEFLAGS) INSTALL_PROGRAM="$(INSTALL_STRIP_PROGRAM)" \
install_sh_PROGRAM="$(INSTALL_STRIP_PROGRAM)" INSTALL_STRIP_FLAG=-s \
"INSTALL_PROGRAM_ENV=STRIPPROG='$(STRIP)'" install; \
fi
mostlyclean-generic:
clean-generic:
distclean-generic:
-test -z "$(CONFIG_CLEAN_FILES)" || rm -f $(CONFIG_CLEAN_FILES)
-test . = "$(srcdir)" || test -z "$(CONFIG_CLEAN_VPATH_FILES)" || rm -f $(CONFIG_CLEAN_VPATH_FILES)
maintainer-clean-generic:
@echo "This command is intended for maintainers to use"
@echo "it deletes files that may require special tools to rebuild."
clean: clean-am
clean-am: clean-generic mostlyclean-am
distclean: distclean-am
-rm -f Makefile
distclean-am: clean-am distclean-generic
dvi: dvi-am
dvi-am:
html: html-am
html-am:
info: info-am
info-am:
install-data-am: install-buildbotDATA install-buildbothtmlDATA
install-dvi: install-dvi-am
install-dvi-am:
install-exec-am:
install-html: install-html-am
install-html-am:
install-info: install-info-am
install-info-am:
install-man:
install-pdf: install-pdf-am
install-pdf-am:
install-ps: install-ps-am
install-ps-am:
installcheck-am:
maintainer-clean: maintainer-clean-am
-rm -f Makefile
maintainer-clean-am: distclean-am maintainer-clean-generic
mostlyclean: mostlyclean-am
mostlyclean-am: mostlyclean-generic
pdf: pdf-am
pdf-am:
ps: ps-am
ps-am:
uninstall-am: uninstall-buildbotDATA uninstall-buildbothtmlDATA
.MAKE: install-am install-strip
.PHONY: all all-am check check-am clean clean-generic distclean \
distclean-generic distdir dvi dvi-am html html-am info info-am \
install install-am install-buildbotDATA \
install-buildbothtmlDATA install-data install-data-am \
install-dvi install-dvi-am install-exec install-exec-am \
install-html install-html-am install-info install-info-am \
install-man install-pdf install-pdf-am install-ps \
install-ps-am install-strip installcheck installcheck-am \
installdirs maintainer-clean maintainer-clean-generic \
mostlyclean mostlyclean-generic pdf pdf-am ps ps-am uninstall \
uninstall-am uninstall-buildbotDATA uninstall-buildbothtmlDATA
# Tell versions [3.59,3.63) of GNU make to not export all variables.
# Otherwise a system limit (for SysV at least) may be exceeded.
.NOEXPORT:
jhbuild-3.5.91/configure 0000755 0001750 0001750 00000763404 12021725530 015076 0 ustar 00fred fred 0000000 0000000 #! /bin/sh
# Guess values for system-dependent variables and create Makefiles.
# Generated by GNU Autoconf 2.69 for jhbuild 3.5.91.
#
# Report bugs to .
#
#
# Copyright (C) 1992-1996, 1998-2012 Free Software Foundation, Inc.
#
#
# This configure script is free software; the Free Software Foundation
# gives unlimited permission to copy, distribute and modify it.
## -------------------- ##
## M4sh Initialization. ##
## -------------------- ##
# Be more Bourne compatible
DUALCASE=1; export DUALCASE # for MKS sh
if test -n "${ZSH_VERSION+set}" && (emulate sh) >/dev/null 2>&1; then :
emulate sh
NULLCMD=:
# Pre-4.2 versions of Zsh do word splitting on ${1+"$@"}, which
# is contrary to our usage. Disable this feature.
alias -g '${1+"$@"}'='"$@"'
setopt NO_GLOB_SUBST
else
case `(set -o) 2>/dev/null` in #(
*posix*) :
set -o posix ;; #(
*) :
;;
esac
fi
as_nl='
'
export as_nl
# Printing a long string crashes Solaris 7 /usr/bin/printf.
as_echo='\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\'
as_echo=$as_echo$as_echo$as_echo$as_echo$as_echo
as_echo=$as_echo$as_echo$as_echo$as_echo$as_echo$as_echo
# Prefer a ksh shell builtin over an external printf program on Solaris,
# but without wasting forks for bash or zsh.
if test -z "$BASH_VERSION$ZSH_VERSION" \
&& (test "X`print -r -- $as_echo`" = "X$as_echo") 2>/dev/null; then
as_echo='print -r --'
as_echo_n='print -rn --'
elif (test "X`printf %s $as_echo`" = "X$as_echo") 2>/dev/null; then
as_echo='printf %s\n'
as_echo_n='printf %s'
else
if test "X`(/usr/ucb/echo -n -n $as_echo) 2>/dev/null`" = "X-n $as_echo"; then
as_echo_body='eval /usr/ucb/echo -n "$1$as_nl"'
as_echo_n='/usr/ucb/echo -n'
else
as_echo_body='eval expr "X$1" : "X\\(.*\\)"'
as_echo_n_body='eval
arg=$1;
case $arg in #(
*"$as_nl"*)
expr "X$arg" : "X\\(.*\\)$as_nl";
arg=`expr "X$arg" : ".*$as_nl\\(.*\\)"`;;
esac;
expr "X$arg" : "X\\(.*\\)" | tr -d "$as_nl"
'
export as_echo_n_body
as_echo_n='sh -c $as_echo_n_body as_echo'
fi
export as_echo_body
as_echo='sh -c $as_echo_body as_echo'
fi
# The user is always right.
if test "${PATH_SEPARATOR+set}" != set; then
PATH_SEPARATOR=:
(PATH='/bin;/bin'; FPATH=$PATH; sh -c :) >/dev/null 2>&1 && {
(PATH='/bin:/bin'; FPATH=$PATH; sh -c :) >/dev/null 2>&1 ||
PATH_SEPARATOR=';'
}
fi
# IFS
# We need space, tab and new line, in precisely that order. Quoting is
# there to prevent editors from complaining about space-tab.
# (If _AS_PATH_WALK were called with IFS unset, it would disable word
# splitting by setting IFS to empty value.)
IFS=" "" $as_nl"
# Find who we are. Look in the path if we contain no directory separator.
as_myself=
case $0 in #((
*[\\/]* ) as_myself=$0 ;;
*) as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
for as_dir in $PATH
do
IFS=$as_save_IFS
test -z "$as_dir" && as_dir=.
test -r "$as_dir/$0" && as_myself=$as_dir/$0 && break
done
IFS=$as_save_IFS
;;
esac
# We did not find ourselves, most probably we were run as `sh COMMAND'
# in which case we are not to be found in the path.
if test "x$as_myself" = x; then
as_myself=$0
fi
if test ! -f "$as_myself"; then
$as_echo "$as_myself: error: cannot find myself; rerun with an absolute file name" >&2
exit 1
fi
# Unset variables that we do not need and which cause bugs (e.g. in
# pre-3.0 UWIN ksh). But do not cause bugs in bash 2.01; the "|| exit 1"
# suppresses any "Segmentation fault" message there. '((' could
# trigger a bug in pdksh 5.2.14.
for as_var in BASH_ENV ENV MAIL MAILPATH
do eval test x\${$as_var+set} = xset \
&& ( (unset $as_var) || exit 1) >/dev/null 2>&1 && unset $as_var || :
done
PS1='$ '
PS2='> '
PS4='+ '
# NLS nuisances.
LC_ALL=C
export LC_ALL
LANGUAGE=C
export LANGUAGE
# CDPATH.
(unset CDPATH) >/dev/null 2>&1 && unset CDPATH
# Use a proper internal environment variable to ensure we don't fall
# into an infinite loop, continuously re-executing ourselves.
if test x"${_as_can_reexec}" != xno && test "x$CONFIG_SHELL" != x; then
_as_can_reexec=no; export _as_can_reexec;
# We cannot yet assume a decent shell, so we have to provide a
# neutralization value for shells without unset; and this also
# works around shells that cannot unset nonexistent variables.
# Preserve -v and -x to the replacement shell.
BASH_ENV=/dev/null
ENV=/dev/null
(unset BASH_ENV) >/dev/null 2>&1 && unset BASH_ENV ENV
case $- in # ((((
*v*x* | *x*v* ) as_opts=-vx ;;
*v* ) as_opts=-v ;;
*x* ) as_opts=-x ;;
* ) as_opts= ;;
esac
exec $CONFIG_SHELL $as_opts "$as_myself" ${1+"$@"}
# Admittedly, this is quite paranoid, since all the known shells bail
# out after a failed `exec'.
$as_echo "$0: could not re-execute with $CONFIG_SHELL" >&2
as_fn_exit 255
fi
# We don't want this to propagate to other subprocesses.
{ _as_can_reexec=; unset _as_can_reexec;}
if test "x$CONFIG_SHELL" = x; then
as_bourne_compatible="if test -n \"\${ZSH_VERSION+set}\" && (emulate sh) >/dev/null 2>&1; then :
emulate sh
NULLCMD=:
# Pre-4.2 versions of Zsh do word splitting on \${1+\"\$@\"}, which
# is contrary to our usage. Disable this feature.
alias -g '\${1+\"\$@\"}'='\"\$@\"'
setopt NO_GLOB_SUBST
else
case \`(set -o) 2>/dev/null\` in #(
*posix*) :
set -o posix ;; #(
*) :
;;
esac
fi
"
as_required="as_fn_return () { (exit \$1); }
as_fn_success () { as_fn_return 0; }
as_fn_failure () { as_fn_return 1; }
as_fn_ret_success () { return 0; }
as_fn_ret_failure () { return 1; }
exitcode=0
as_fn_success || { exitcode=1; echo as_fn_success failed.; }
as_fn_failure && { exitcode=1; echo as_fn_failure succeeded.; }
as_fn_ret_success || { exitcode=1; echo as_fn_ret_success failed.; }
as_fn_ret_failure && { exitcode=1; echo as_fn_ret_failure succeeded.; }
if ( set x; as_fn_ret_success y && test x = \"\$1\" ); then :
else
exitcode=1; echo positional parameters were not saved.
fi
test x\$exitcode = x0 || exit 1
test -x / || exit 1"
as_suggested=" as_lineno_1=";as_suggested=$as_suggested$LINENO;as_suggested=$as_suggested" as_lineno_1a=\$LINENO
as_lineno_2=";as_suggested=$as_suggested$LINENO;as_suggested=$as_suggested" as_lineno_2a=\$LINENO
eval 'test \"x\$as_lineno_1'\$as_run'\" != \"x\$as_lineno_2'\$as_run'\" &&
test \"x\`expr \$as_lineno_1'\$as_run' + 1\`\" = \"x\$as_lineno_2'\$as_run'\"' || exit 1"
if (eval "$as_required") 2>/dev/null; then :
as_have_required=yes
else
as_have_required=no
fi
if test x$as_have_required = xyes && (eval "$as_suggested") 2>/dev/null; then :
else
as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
as_found=false
for as_dir in /bin$PATH_SEPARATOR/usr/bin$PATH_SEPARATOR$PATH
do
IFS=$as_save_IFS
test -z "$as_dir" && as_dir=.
as_found=:
case $as_dir in #(
/*)
for as_base in sh bash ksh sh5; do
# Try only shells that exist, to save several forks.
as_shell=$as_dir/$as_base
if { test -f "$as_shell" || test -f "$as_shell.exe"; } &&
{ $as_echo "$as_bourne_compatible""$as_required" | as_run=a "$as_shell"; } 2>/dev/null; then :
CONFIG_SHELL=$as_shell as_have_required=yes
if { $as_echo "$as_bourne_compatible""$as_suggested" | as_run=a "$as_shell"; } 2>/dev/null; then :
break 2
fi
fi
done;;
esac
as_found=false
done
$as_found || { if { test -f "$SHELL" || test -f "$SHELL.exe"; } &&
{ $as_echo "$as_bourne_compatible""$as_required" | as_run=a "$SHELL"; } 2>/dev/null; then :
CONFIG_SHELL=$SHELL as_have_required=yes
fi; }
IFS=$as_save_IFS
if test "x$CONFIG_SHELL" != x; then :
export CONFIG_SHELL
# We cannot yet assume a decent shell, so we have to provide a
# neutralization value for shells without unset; and this also
# works around shells that cannot unset nonexistent variables.
# Preserve -v and -x to the replacement shell.
BASH_ENV=/dev/null
ENV=/dev/null
(unset BASH_ENV) >/dev/null 2>&1 && unset BASH_ENV ENV
case $- in # ((((
*v*x* | *x*v* ) as_opts=-vx ;;
*v* ) as_opts=-v ;;
*x* ) as_opts=-x ;;
* ) as_opts= ;;
esac
exec $CONFIG_SHELL $as_opts "$as_myself" ${1+"$@"}
# Admittedly, this is quite paranoid, since all the known shells bail
# out after a failed `exec'.
$as_echo "$0: could not re-execute with $CONFIG_SHELL" >&2
exit 255
fi
if test x$as_have_required = xno; then :
$as_echo "$0: This script requires a shell more modern than all"
$as_echo "$0: the shells that I found on your system."
if test x${ZSH_VERSION+set} = xset ; then
$as_echo "$0: In particular, zsh $ZSH_VERSION has bugs and should"
$as_echo "$0: be upgraded to zsh 4.3.4 or later."
else
$as_echo "$0: Please tell bug-autoconf@gnu.org and
$0: http://bugzilla.gnome.org/enter_bug.cgi?product=jhbuild
$0: about your system, including any error possibly output
$0: before this message. Then install a modern shell, or
$0: manually run the script under such a shell if you do
$0: have one."
fi
exit 1
fi
fi
fi
SHELL=${CONFIG_SHELL-/bin/sh}
export SHELL
# Unset more variables known to interfere with behavior of common tools.
CLICOLOR_FORCE= GREP_OPTIONS=
unset CLICOLOR_FORCE GREP_OPTIONS
## --------------------- ##
## M4sh Shell Functions. ##
## --------------------- ##
# as_fn_unset VAR
# ---------------
# Portably unset VAR.
as_fn_unset ()
{
{ eval $1=; unset $1;}
}
as_unset=as_fn_unset
# as_fn_set_status STATUS
# -----------------------
# Set $? to STATUS, without forking.
as_fn_set_status ()
{
return $1
} # as_fn_set_status
# as_fn_exit STATUS
# -----------------
# Exit the shell with STATUS, even in a "trap 0" or "set -e" context.
as_fn_exit ()
{
set +e
as_fn_set_status $1
exit $1
} # as_fn_exit
# as_fn_mkdir_p
# -------------
# Create "$as_dir" as a directory, including parents if necessary.
as_fn_mkdir_p ()
{
case $as_dir in #(
-*) as_dir=./$as_dir;;
esac
test -d "$as_dir" || eval $as_mkdir_p || {
as_dirs=
while :; do
case $as_dir in #(
*\'*) as_qdir=`$as_echo "$as_dir" | sed "s/'/'\\\\\\\\''/g"`;; #'(
*) as_qdir=$as_dir;;
esac
as_dirs="'$as_qdir' $as_dirs"
as_dir=`$as_dirname -- "$as_dir" ||
$as_expr X"$as_dir" : 'X\(.*[^/]\)//*[^/][^/]*/*$' \| \
X"$as_dir" : 'X\(//\)[^/]' \| \
X"$as_dir" : 'X\(//\)$' \| \
X"$as_dir" : 'X\(/\)' \| . 2>/dev/null ||
$as_echo X"$as_dir" |
sed '/^X\(.*[^/]\)\/\/*[^/][^/]*\/*$/{
s//\1/
q
}
/^X\(\/\/\)[^/].*/{
s//\1/
q
}
/^X\(\/\/\)$/{
s//\1/
q
}
/^X\(\/\).*/{
s//\1/
q
}
s/.*/./; q'`
test -d "$as_dir" && break
done
test -z "$as_dirs" || eval "mkdir $as_dirs"
} || test -d "$as_dir" || as_fn_error $? "cannot create directory $as_dir"
} # as_fn_mkdir_p
# as_fn_executable_p FILE
# -----------------------
# Test if FILE is an executable regular file.
as_fn_executable_p ()
{
test -f "$1" && test -x "$1"
} # as_fn_executable_p
# as_fn_append VAR VALUE
# ----------------------
# Append the text in VALUE to the end of the definition contained in VAR. Take
# advantage of any shell optimizations that allow amortized linear growth over
# repeated appends, instead of the typical quadratic growth present in naive
# implementations.
if (eval "as_var=1; as_var+=2; test x\$as_var = x12") 2>/dev/null; then :
eval 'as_fn_append ()
{
eval $1+=\$2
}'
else
as_fn_append ()
{
eval $1=\$$1\$2
}
fi # as_fn_append
# as_fn_arith ARG...
# ------------------
# Perform arithmetic evaluation on the ARGs, and store the result in the
# global $as_val. Take advantage of shells that can avoid forks. The arguments
# must be portable across $(()) and expr.
if (eval "test \$(( 1 + 1 )) = 2") 2>/dev/null; then :
eval 'as_fn_arith ()
{
as_val=$(( $* ))
}'
else
as_fn_arith ()
{
as_val=`expr "$@" || test $? -eq 1`
}
fi # as_fn_arith
# as_fn_error STATUS ERROR [LINENO LOG_FD]
# ----------------------------------------
# Output "`basename $0`: error: ERROR" to stderr. If LINENO and LOG_FD are
# provided, also output the error to LOG_FD, referencing LINENO. Then exit the
# script with STATUS, using 1 if that was 0.
as_fn_error ()
{
as_status=$1; test $as_status -eq 0 && as_status=1
if test "$4"; then
as_lineno=${as_lineno-"$3"} as_lineno_stack=as_lineno_stack=$as_lineno_stack
$as_echo "$as_me:${as_lineno-$LINENO}: error: $2" >&$4
fi
$as_echo "$as_me: error: $2" >&2
as_fn_exit $as_status
} # as_fn_error
if expr a : '\(a\)' >/dev/null 2>&1 &&
test "X`expr 00001 : '.*\(...\)'`" = X001; then
as_expr=expr
else
as_expr=false
fi
if (basename -- /) >/dev/null 2>&1 && test "X`basename -- / 2>&1`" = "X/"; then
as_basename=basename
else
as_basename=false
fi
if (as_dir=`dirname -- /` && test "X$as_dir" = X/) >/dev/null 2>&1; then
as_dirname=dirname
else
as_dirname=false
fi
as_me=`$as_basename -- "$0" ||
$as_expr X/"$0" : '.*/\([^/][^/]*\)/*$' \| \
X"$0" : 'X\(//\)$' \| \
X"$0" : 'X\(/\)' \| . 2>/dev/null ||
$as_echo X/"$0" |
sed '/^.*\/\([^/][^/]*\)\/*$/{
s//\1/
q
}
/^X\/\(\/\/\)$/{
s//\1/
q
}
/^X\/\(\/\).*/{
s//\1/
q
}
s/.*/./; q'`
# Avoid depending upon Character Ranges.
as_cr_letters='abcdefghijklmnopqrstuvwxyz'
as_cr_LETTERS='ABCDEFGHIJKLMNOPQRSTUVWXYZ'
as_cr_Letters=$as_cr_letters$as_cr_LETTERS
as_cr_digits='0123456789'
as_cr_alnum=$as_cr_Letters$as_cr_digits
as_lineno_1=$LINENO as_lineno_1a=$LINENO
as_lineno_2=$LINENO as_lineno_2a=$LINENO
eval 'test "x$as_lineno_1'$as_run'" != "x$as_lineno_2'$as_run'" &&
test "x`expr $as_lineno_1'$as_run' + 1`" = "x$as_lineno_2'$as_run'"' || {
# Blame Lee E. McMahon (1931-1989) for sed's syntax. :-)
sed -n '
p
/[$]LINENO/=
' <$as_myself |
sed '
s/[$]LINENO.*/&-/
t lineno
b
:lineno
N
:loop
s/[$]LINENO\([^'$as_cr_alnum'_].*\n\)\(.*\)/\2\1\2/
t loop
s/-\n.*//
' >$as_me.lineno &&
chmod +x "$as_me.lineno" ||
{ $as_echo "$as_me: error: cannot create $as_me.lineno; rerun with a POSIX shell" >&2; as_fn_exit 1; }
# If we had to re-execute with $CONFIG_SHELL, we're ensured to have
# already done that, so ensure we don't try to do so again and fall
# in an infinite loop. This has already happened in practice.
_as_can_reexec=no; export _as_can_reexec
# Don't try to exec as it changes $[0], causing all sort of problems
# (the dirname of $[0] is not the place where we might find the
# original and so on. Autoconf is especially sensitive to this).
. "./$as_me.lineno"
# Exit status is that of the last command.
exit
}
ECHO_C= ECHO_N= ECHO_T=
case `echo -n x` in #(((((
-n*)
case `echo 'xy\c'` in
*c*) ECHO_T=' ';; # ECHO_T is single tab character.
xy) ECHO_C='\c';;
*) echo `echo ksh88 bug on AIX 6.1` > /dev/null
ECHO_T=' ';;
esac;;
*)
ECHO_N='-n';;
esac
rm -f conf$$ conf$$.exe conf$$.file
if test -d conf$$.dir; then
rm -f conf$$.dir/conf$$.file
else
rm -f conf$$.dir
mkdir conf$$.dir 2>/dev/null
fi
if (echo >conf$$.file) 2>/dev/null; then
if ln -s conf$$.file conf$$ 2>/dev/null; then
as_ln_s='ln -s'
# ... but there are two gotchas:
# 1) On MSYS, both `ln -s file dir' and `ln file dir' fail.
# 2) DJGPP < 2.04 has no symlinks; `ln -s' creates a wrapper executable.
# In both cases, we have to default to `cp -pR'.
ln -s conf$$.file conf$$.dir 2>/dev/null && test ! -f conf$$.exe ||
as_ln_s='cp -pR'
elif ln conf$$.file conf$$ 2>/dev/null; then
as_ln_s=ln
else
as_ln_s='cp -pR'
fi
else
as_ln_s='cp -pR'
fi
rm -f conf$$ conf$$.exe conf$$.dir/conf$$.file conf$$.file
rmdir conf$$.dir 2>/dev/null
if mkdir -p . 2>/dev/null; then
as_mkdir_p='mkdir -p "$as_dir"'
else
test -d ./-p && rmdir ./-p
as_mkdir_p=false
fi
as_test_x='test -x'
as_executable_p=as_fn_executable_p
# Sed expression to map a string onto a valid CPP name.
as_tr_cpp="eval sed 'y%*$as_cr_letters%P$as_cr_LETTERS%;s%[^_$as_cr_alnum]%_%g'"
# Sed expression to map a string onto a valid variable name.
as_tr_sh="eval sed 'y%*+%pp%;s%[^_$as_cr_alnum]%_%g'"
test -n "$DJDIR" || exec 7<&0 &1
# Name of the host.
# hostname on some systems (SVR3.2, old GNU/Linux) returns a bogus exit status,
# so uname gets run too.
ac_hostname=`(hostname || uname -n) 2>/dev/null | sed 1q`
#
# Initializations.
#
ac_default_prefix=/usr/local
ac_clean_files=
ac_config_libobj_dir=.
LIBOBJS=
cross_compiling=no
subdirs=
MFLAGS=
MAKEFLAGS=
# Identity of this package.
PACKAGE_NAME='jhbuild'
PACKAGE_TARNAME='jhbuild'
PACKAGE_VERSION='3.5.91'
PACKAGE_STRING='jhbuild 3.5.91'
PACKAGE_BUGREPORT='http://bugzilla.gnome.org/enter_bug.cgi?product=jhbuild'
PACKAGE_URL=''
ac_unique_file="jhbuild/main.py"
ac_default_prefix=~/.local/
gt_needs=
ac_subst_vars='am__EXEEXT_FALSE
am__EXEEXT_TRUE
LTLIBOBJS
LIBOBJS
YELP_HELP_RULES
XMLLINT
ITSTOOL
HELP_DIR
LN_S
DOC_INSTALLATION_ENABLED_FALSE
DOC_INSTALLATION_ENABLED_TRUE
GETTEXT_PACKAGE
POSUB
LTLIBINTL
LIBINTL
INTLLIBS
LTLIBICONV
LIBICONV
INTL_MACOSX_LIBS
host_os
host_vendor
host_cpu
host
build_os
build_vendor
build_cpu
build
XGETTEXT_EXTRA_OPTIONS
XGETTEXT_015
GMSGFMT_015
MSGFMT_015
GETTEXT_MACRO_VERSION
DATADIRNAME
ALL_LINGUAS
INTLTOOL_PERL
GMSGFMT
MSGFMT
MSGMERGE
XGETTEXT
INTLTOOL_POLICY_RULE
INTLTOOL_SERVICE_RULE
INTLTOOL_THEME_RULE
INTLTOOL_SCHEMAS_RULE
INTLTOOL_CAVES_RULE
INTLTOOL_XML_NOMERGE_RULE
INTLTOOL_XML_RULE
INTLTOOL_KBD_RULE
INTLTOOL_XAM_RULE
INTLTOOL_UI_RULE
INTLTOOL_SOUNDLIST_RULE
INTLTOOL_SHEET_RULE
INTLTOOL_SERVER_RULE
INTLTOOL_PONG_RULE
INTLTOOL_OAF_RULE
INTLTOOL_PROP_RULE
INTLTOOL_KEYS_RULE
INTLTOOL_DIRECTORY_RULE
INTLTOOL_DESKTOP_RULE
intltool__v_merge_options_0
intltool__v_merge_options_
INTLTOOL_V_MERGE_OPTIONS
INTLTOOL__v_MERGE_0
INTLTOOL__v_MERGE_
INTLTOOL_V_MERGE
AM_DEFAULT_VERBOSITY
INTLTOOL_EXTRACT
INTLTOOL_MERGE
INTLTOOL_UPDATE
USE_NLS
PKG_CONFIG_LIBDIR
PKG_CONFIG_PATH
PKG_CONFIG
pkgpyexecdir
pyexecdir
pkgpythondir
pythondir
PYTHON_PLATFORM
PYTHON_EXEC_PREFIX
PYTHON_PREFIX
PYTHON_VERSION
PYTHON
am__fastdepCC_FALSE
am__fastdepCC_TRUE
CCDEPMODE
am__nodep
AMDEPBACKSLASH
AMDEP_FALSE
AMDEP_TRUE
am__quote
am__include
DEPDIR
OBJEXT
EXEEXT
ac_ct_CC
CPPFLAGS
LDFLAGS
CFLAGS
CC
MAINT
MAINTAINER_MODE_FALSE
MAINTAINER_MODE_TRUE
am__untar
am__tar
AMTAR
am__leading_dot
SET_MAKE
AWK
mkdir_p
MKDIR_P
INSTALL_STRIP_PROGRAM
STRIP
install_sh
MAKEINFO
AUTOHEADER
AUTOMAKE
AUTOCONF
ACLOCAL
VERSION
PACKAGE
CYGPATH_W
am__isrc
INSTALL_DATA
INSTALL_SCRIPT
INSTALL_PROGRAM
target_alias
host_alias
build_alias
LIBS
ECHO_T
ECHO_N
ECHO_C
DEFS
mandir
localedir
libdir
psdir
pdfdir
dvidir
htmldir
infodir
docdir
oldincludedir
includedir
localstatedir
sharedstatedir
sysconfdir
datadir
datarootdir
libexecdir
sbindir
bindir
program_transform_name
prefix
exec_prefix
PACKAGE_URL
PACKAGE_BUGREPORT
PACKAGE_STRING
PACKAGE_VERSION
PACKAGE_TARNAME
PACKAGE_NAME
PATH_SEPARATOR
SHELL'
ac_subst_files=''
ac_user_opts='
enable_option_checking
enable_maintainer_mode
enable_dependency_tracking
enable_nls
with_gnu_ld
enable_rpath
with_libiconv_prefix
with_libintl_prefix
enable_doc_installation
with_help_dir
'
ac_precious_vars='build_alias
host_alias
target_alias
CC
CFLAGS
LDFLAGS
LIBS
CPPFLAGS
PYTHON
PKG_CONFIG
PKG_CONFIG_PATH
PKG_CONFIG_LIBDIR
ITSTOOL
XMLLINT'
# Initialize some variables set by options.
ac_init_help=
ac_init_version=false
ac_unrecognized_opts=
ac_unrecognized_sep=
# The variables have the same names as the options, with
# dashes changed to underlines.
cache_file=/dev/null
exec_prefix=NONE
no_create=
no_recursion=
prefix=NONE
program_prefix=NONE
program_suffix=NONE
program_transform_name=s,x,x,
silent=
site=
srcdir=
verbose=
x_includes=NONE
x_libraries=NONE
# Installation directory options.
# These are left unexpanded so users can "make install exec_prefix=/foo"
# and all the variables that are supposed to be based on exec_prefix
# by default will actually change.
# Use braces instead of parens because sh, perl, etc. also accept them.
# (The list follows the same order as the GNU Coding Standards.)
bindir='${exec_prefix}/bin'
sbindir='${exec_prefix}/sbin'
libexecdir='${exec_prefix}/libexec'
datarootdir='${prefix}/share'
datadir='${datarootdir}'
sysconfdir='${prefix}/etc'
sharedstatedir='${prefix}/com'
localstatedir='${prefix}/var'
includedir='${prefix}/include'
oldincludedir='/usr/include'
docdir='${datarootdir}/doc/${PACKAGE_TARNAME}'
infodir='${datarootdir}/info'
htmldir='${docdir}'
dvidir='${docdir}'
pdfdir='${docdir}'
psdir='${docdir}'
libdir='${exec_prefix}/lib'
localedir='${datarootdir}/locale'
mandir='${datarootdir}/man'
ac_prev=
ac_dashdash=
for ac_option
do
# If the previous option needs an argument, assign it.
if test -n "$ac_prev"; then
eval $ac_prev=\$ac_option
ac_prev=
continue
fi
case $ac_option in
*=?*) ac_optarg=`expr "X$ac_option" : '[^=]*=\(.*\)'` ;;
*=) ac_optarg= ;;
*) ac_optarg=yes ;;
esac
# Accept the important Cygnus configure options, so we can diagnose typos.
case $ac_dashdash$ac_option in
--)
ac_dashdash=yes ;;
-bindir | --bindir | --bindi | --bind | --bin | --bi)
ac_prev=bindir ;;
-bindir=* | --bindir=* | --bindi=* | --bind=* | --bin=* | --bi=*)
bindir=$ac_optarg ;;
-build | --build | --buil | --bui | --bu)
ac_prev=build_alias ;;
-build=* | --build=* | --buil=* | --bui=* | --bu=*)
build_alias=$ac_optarg ;;
-cache-file | --cache-file | --cache-fil | --cache-fi \
| --cache-f | --cache- | --cache | --cach | --cac | --ca | --c)
ac_prev=cache_file ;;
-cache-file=* | --cache-file=* | --cache-fil=* | --cache-fi=* \
| --cache-f=* | --cache-=* | --cache=* | --cach=* | --cac=* | --ca=* | --c=*)
cache_file=$ac_optarg ;;
--config-cache | -C)
cache_file=config.cache ;;
-datadir | --datadir | --datadi | --datad)
ac_prev=datadir ;;
-datadir=* | --datadir=* | --datadi=* | --datad=*)
datadir=$ac_optarg ;;
-datarootdir | --datarootdir | --datarootdi | --datarootd | --dataroot \
| --dataroo | --dataro | --datar)
ac_prev=datarootdir ;;
-datarootdir=* | --datarootdir=* | --datarootdi=* | --datarootd=* \
| --dataroot=* | --dataroo=* | --dataro=* | --datar=*)
datarootdir=$ac_optarg ;;
-disable-* | --disable-*)
ac_useropt=`expr "x$ac_option" : 'x-*disable-\(.*\)'`
# Reject names that are not valid shell variable names.
expr "x$ac_useropt" : ".*[^-+._$as_cr_alnum]" >/dev/null &&
as_fn_error $? "invalid feature name: $ac_useropt"
ac_useropt_orig=$ac_useropt
ac_useropt=`$as_echo "$ac_useropt" | sed 's/[-+.]/_/g'`
case $ac_user_opts in
*"
"enable_$ac_useropt"
"*) ;;
*) ac_unrecognized_opts="$ac_unrecognized_opts$ac_unrecognized_sep--disable-$ac_useropt_orig"
ac_unrecognized_sep=', ';;
esac
eval enable_$ac_useropt=no ;;
-docdir | --docdir | --docdi | --doc | --do)
ac_prev=docdir ;;
-docdir=* | --docdir=* | --docdi=* | --doc=* | --do=*)
docdir=$ac_optarg ;;
-dvidir | --dvidir | --dvidi | --dvid | --dvi | --dv)
ac_prev=dvidir ;;
-dvidir=* | --dvidir=* | --dvidi=* | --dvid=* | --dvi=* | --dv=*)
dvidir=$ac_optarg ;;
-enable-* | --enable-*)
ac_useropt=`expr "x$ac_option" : 'x-*enable-\([^=]*\)'`
# Reject names that are not valid shell variable names.
expr "x$ac_useropt" : ".*[^-+._$as_cr_alnum]" >/dev/null &&
as_fn_error $? "invalid feature name: $ac_useropt"
ac_useropt_orig=$ac_useropt
ac_useropt=`$as_echo "$ac_useropt" | sed 's/[-+.]/_/g'`
case $ac_user_opts in
*"
"enable_$ac_useropt"
"*) ;;
*) ac_unrecognized_opts="$ac_unrecognized_opts$ac_unrecognized_sep--enable-$ac_useropt_orig"
ac_unrecognized_sep=', ';;
esac
eval enable_$ac_useropt=\$ac_optarg ;;
-exec-prefix | --exec_prefix | --exec-prefix | --exec-prefi \
| --exec-pref | --exec-pre | --exec-pr | --exec-p | --exec- \
| --exec | --exe | --ex)
ac_prev=exec_prefix ;;
-exec-prefix=* | --exec_prefix=* | --exec-prefix=* | --exec-prefi=* \
| --exec-pref=* | --exec-pre=* | --exec-pr=* | --exec-p=* | --exec-=* \
| --exec=* | --exe=* | --ex=*)
exec_prefix=$ac_optarg ;;
-gas | --gas | --ga | --g)
# Obsolete; use --with-gas.
with_gas=yes ;;
-help | --help | --hel | --he | -h)
ac_init_help=long ;;
-help=r* | --help=r* | --hel=r* | --he=r* | -hr*)
ac_init_help=recursive ;;
-help=s* | --help=s* | --hel=s* | --he=s* | -hs*)
ac_init_help=short ;;
-host | --host | --hos | --ho)
ac_prev=host_alias ;;
-host=* | --host=* | --hos=* | --ho=*)
host_alias=$ac_optarg ;;
-htmldir | --htmldir | --htmldi | --htmld | --html | --htm | --ht)
ac_prev=htmldir ;;
-htmldir=* | --htmldir=* | --htmldi=* | --htmld=* | --html=* | --htm=* \
| --ht=*)
htmldir=$ac_optarg ;;
-includedir | --includedir | --includedi | --included | --include \
| --includ | --inclu | --incl | --inc)
ac_prev=includedir ;;
-includedir=* | --includedir=* | --includedi=* | --included=* | --include=* \
| --includ=* | --inclu=* | --incl=* | --inc=*)
includedir=$ac_optarg ;;
-infodir | --infodir | --infodi | --infod | --info | --inf)
ac_prev=infodir ;;
-infodir=* | --infodir=* | --infodi=* | --infod=* | --info=* | --inf=*)
infodir=$ac_optarg ;;
-libdir | --libdir | --libdi | --libd)
ac_prev=libdir ;;
-libdir=* | --libdir=* | --libdi=* | --libd=*)
libdir=$ac_optarg ;;
-libexecdir | --libexecdir | --libexecdi | --libexecd | --libexec \
| --libexe | --libex | --libe)
ac_prev=libexecdir ;;
-libexecdir=* | --libexecdir=* | --libexecdi=* | --libexecd=* | --libexec=* \
| --libexe=* | --libex=* | --libe=*)
libexecdir=$ac_optarg ;;
-localedir | --localedir | --localedi | --localed | --locale)
ac_prev=localedir ;;
-localedir=* | --localedir=* | --localedi=* | --localed=* | --locale=*)
localedir=$ac_optarg ;;
-localstatedir | --localstatedir | --localstatedi | --localstated \
| --localstate | --localstat | --localsta | --localst | --locals)
ac_prev=localstatedir ;;
-localstatedir=* | --localstatedir=* | --localstatedi=* | --localstated=* \
| --localstate=* | --localstat=* | --localsta=* | --localst=* | --locals=*)
localstatedir=$ac_optarg ;;
-mandir | --mandir | --mandi | --mand | --man | --ma | --m)
ac_prev=mandir ;;
-mandir=* | --mandir=* | --mandi=* | --mand=* | --man=* | --ma=* | --m=*)
mandir=$ac_optarg ;;
-nfp | --nfp | --nf)
# Obsolete; use --without-fp.
with_fp=no ;;
-no-create | --no-create | --no-creat | --no-crea | --no-cre \
| --no-cr | --no-c | -n)
no_create=yes ;;
-no-recursion | --no-recursion | --no-recursio | --no-recursi \
| --no-recurs | --no-recur | --no-recu | --no-rec | --no-re | --no-r)
no_recursion=yes ;;
-oldincludedir | --oldincludedir | --oldincludedi | --oldincluded \
| --oldinclude | --oldinclud | --oldinclu | --oldincl | --oldinc \
| --oldin | --oldi | --old | --ol | --o)
ac_prev=oldincludedir ;;
-oldincludedir=* | --oldincludedir=* | --oldincludedi=* | --oldincluded=* \
| --oldinclude=* | --oldinclud=* | --oldinclu=* | --oldincl=* | --oldinc=* \
| --oldin=* | --oldi=* | --old=* | --ol=* | --o=*)
oldincludedir=$ac_optarg ;;
-prefix | --prefix | --prefi | --pref | --pre | --pr | --p)
ac_prev=prefix ;;
-prefix=* | --prefix=* | --prefi=* | --pref=* | --pre=* | --pr=* | --p=*)
prefix=$ac_optarg ;;
-program-prefix | --program-prefix | --program-prefi | --program-pref \
| --program-pre | --program-pr | --program-p)
ac_prev=program_prefix ;;
-program-prefix=* | --program-prefix=* | --program-prefi=* \
| --program-pref=* | --program-pre=* | --program-pr=* | --program-p=*)
program_prefix=$ac_optarg ;;
-program-suffix | --program-suffix | --program-suffi | --program-suff \
| --program-suf | --program-su | --program-s)
ac_prev=program_suffix ;;
-program-suffix=* | --program-suffix=* | --program-suffi=* \
| --program-suff=* | --program-suf=* | --program-su=* | --program-s=*)
program_suffix=$ac_optarg ;;
-program-transform-name | --program-transform-name \
| --program-transform-nam | --program-transform-na \
| --program-transform-n | --program-transform- \
| --program-transform | --program-transfor \
| --program-transfo | --program-transf \
| --program-trans | --program-tran \
| --progr-tra | --program-tr | --program-t)
ac_prev=program_transform_name ;;
-program-transform-name=* | --program-transform-name=* \
| --program-transform-nam=* | --program-transform-na=* \
| --program-transform-n=* | --program-transform-=* \
| --program-transform=* | --program-transfor=* \
| --program-transfo=* | --program-transf=* \
| --program-trans=* | --program-tran=* \
| --progr-tra=* | --program-tr=* | --program-t=*)
program_transform_name=$ac_optarg ;;
-pdfdir | --pdfdir | --pdfdi | --pdfd | --pdf | --pd)
ac_prev=pdfdir ;;
-pdfdir=* | --pdfdir=* | --pdfdi=* | --pdfd=* | --pdf=* | --pd=*)
pdfdir=$ac_optarg ;;
-psdir | --psdir | --psdi | --psd | --ps)
ac_prev=psdir ;;
-psdir=* | --psdir=* | --psdi=* | --psd=* | --ps=*)
psdir=$ac_optarg ;;
-q | -quiet | --quiet | --quie | --qui | --qu | --q \
| -silent | --silent | --silen | --sile | --sil)
silent=yes ;;
-sbindir | --sbindir | --sbindi | --sbind | --sbin | --sbi | --sb)
ac_prev=sbindir ;;
-sbindir=* | --sbindir=* | --sbindi=* | --sbind=* | --sbin=* \
| --sbi=* | --sb=*)
sbindir=$ac_optarg ;;
-sharedstatedir | --sharedstatedir | --sharedstatedi \
| --sharedstated | --sharedstate | --sharedstat | --sharedsta \
| --sharedst | --shareds | --shared | --share | --shar \
| --sha | --sh)
ac_prev=sharedstatedir ;;
-sharedstatedir=* | --sharedstatedir=* | --sharedstatedi=* \
| --sharedstated=* | --sharedstate=* | --sharedstat=* | --sharedsta=* \
| --sharedst=* | --shareds=* | --shared=* | --share=* | --shar=* \
| --sha=* | --sh=*)
sharedstatedir=$ac_optarg ;;
-site | --site | --sit)
ac_prev=site ;;
-site=* | --site=* | --sit=*)
site=$ac_optarg ;;
-srcdir | --srcdir | --srcdi | --srcd | --src | --sr)
ac_prev=srcdir ;;
-srcdir=* | --srcdir=* | --srcdi=* | --srcd=* | --src=* | --sr=*)
srcdir=$ac_optarg ;;
-sysconfdir | --sysconfdir | --sysconfdi | --sysconfd | --sysconf \
| --syscon | --sysco | --sysc | --sys | --sy)
ac_prev=sysconfdir ;;
-sysconfdir=* | --sysconfdir=* | --sysconfdi=* | --sysconfd=* | --sysconf=* \
| --syscon=* | --sysco=* | --sysc=* | --sys=* | --sy=*)
sysconfdir=$ac_optarg ;;
-target | --target | --targe | --targ | --tar | --ta | --t)
ac_prev=target_alias ;;
-target=* | --target=* | --targe=* | --targ=* | --tar=* | --ta=* | --t=*)
target_alias=$ac_optarg ;;
-v | -verbose | --verbose | --verbos | --verbo | --verb)
verbose=yes ;;
-version | --version | --versio | --versi | --vers | -V)
ac_init_version=: ;;
-with-* | --with-*)
ac_useropt=`expr "x$ac_option" : 'x-*with-\([^=]*\)'`
# Reject names that are not valid shell variable names.
expr "x$ac_useropt" : ".*[^-+._$as_cr_alnum]" >/dev/null &&
as_fn_error $? "invalid package name: $ac_useropt"
ac_useropt_orig=$ac_useropt
ac_useropt=`$as_echo "$ac_useropt" | sed 's/[-+.]/_/g'`
case $ac_user_opts in
*"
"with_$ac_useropt"
"*) ;;
*) ac_unrecognized_opts="$ac_unrecognized_opts$ac_unrecognized_sep--with-$ac_useropt_orig"
ac_unrecognized_sep=', ';;
esac
eval with_$ac_useropt=\$ac_optarg ;;
-without-* | --without-*)
ac_useropt=`expr "x$ac_option" : 'x-*without-\(.*\)'`
# Reject names that are not valid shell variable names.
expr "x$ac_useropt" : ".*[^-+._$as_cr_alnum]" >/dev/null &&
as_fn_error $? "invalid package name: $ac_useropt"
ac_useropt_orig=$ac_useropt
ac_useropt=`$as_echo "$ac_useropt" | sed 's/[-+.]/_/g'`
case $ac_user_opts in
*"
"with_$ac_useropt"
"*) ;;
*) ac_unrecognized_opts="$ac_unrecognized_opts$ac_unrecognized_sep--without-$ac_useropt_orig"
ac_unrecognized_sep=', ';;
esac
eval with_$ac_useropt=no ;;
--x)
# Obsolete; use --with-x.
with_x=yes ;;
-x-includes | --x-includes | --x-include | --x-includ | --x-inclu \
| --x-incl | --x-inc | --x-in | --x-i)
ac_prev=x_includes ;;
-x-includes=* | --x-includes=* | --x-include=* | --x-includ=* | --x-inclu=* \
| --x-incl=* | --x-inc=* | --x-in=* | --x-i=*)
x_includes=$ac_optarg ;;
-x-libraries | --x-libraries | --x-librarie | --x-librari \
| --x-librar | --x-libra | --x-libr | --x-lib | --x-li | --x-l)
ac_prev=x_libraries ;;
-x-libraries=* | --x-libraries=* | --x-librarie=* | --x-librari=* \
| --x-librar=* | --x-libra=* | --x-libr=* | --x-lib=* | --x-li=* | --x-l=*)
x_libraries=$ac_optarg ;;
-*) as_fn_error $? "unrecognized option: \`$ac_option'
Try \`$0 --help' for more information"
;;
*=*)
ac_envvar=`expr "x$ac_option" : 'x\([^=]*\)='`
# Reject names that are not valid shell variable names.
case $ac_envvar in #(
'' | [0-9]* | *[!_$as_cr_alnum]* )
as_fn_error $? "invalid variable name: \`$ac_envvar'" ;;
esac
eval $ac_envvar=\$ac_optarg
export $ac_envvar ;;
*)
# FIXME: should be removed in autoconf 3.0.
$as_echo "$as_me: WARNING: you should use --build, --host, --target" >&2
expr "x$ac_option" : ".*[^-._$as_cr_alnum]" >/dev/null &&
$as_echo "$as_me: WARNING: invalid host type: $ac_option" >&2
: "${build_alias=$ac_option} ${host_alias=$ac_option} ${target_alias=$ac_option}"
;;
esac
done
if test -n "$ac_prev"; then
ac_option=--`echo $ac_prev | sed 's/_/-/g'`
as_fn_error $? "missing argument to $ac_option"
fi
if test -n "$ac_unrecognized_opts"; then
case $enable_option_checking in
no) ;;
fatal) as_fn_error $? "unrecognized options: $ac_unrecognized_opts" ;;
*) $as_echo "$as_me: WARNING: unrecognized options: $ac_unrecognized_opts" >&2 ;;
esac
fi
# Check all directory arguments for consistency.
for ac_var in exec_prefix prefix bindir sbindir libexecdir datarootdir \
datadir sysconfdir sharedstatedir localstatedir includedir \
oldincludedir docdir infodir htmldir dvidir pdfdir psdir \
libdir localedir mandir
do
eval ac_val=\$$ac_var
# Remove trailing slashes.
case $ac_val in
*/ )
ac_val=`expr "X$ac_val" : 'X\(.*[^/]\)' \| "X$ac_val" : 'X\(.*\)'`
eval $ac_var=\$ac_val;;
esac
# Be sure to have absolute directory names.
case $ac_val in
[\\/$]* | ?:[\\/]* ) continue;;
NONE | '' ) case $ac_var in *prefix ) continue;; esac;;
esac
as_fn_error $? "expected an absolute directory name for --$ac_var: $ac_val"
done
# There might be people who depend on the old broken behavior: `$host'
# used to hold the argument of --host etc.
# FIXME: To remove some day.
build=$build_alias
host=$host_alias
target=$target_alias
# FIXME: To remove some day.
if test "x$host_alias" != x; then
if test "x$build_alias" = x; then
cross_compiling=maybe
elif test "x$build_alias" != "x$host_alias"; then
cross_compiling=yes
fi
fi
ac_tool_prefix=
test -n "$host_alias" && ac_tool_prefix=$host_alias-
test "$silent" = yes && exec 6>/dev/null
ac_pwd=`pwd` && test -n "$ac_pwd" &&
ac_ls_di=`ls -di .` &&
ac_pwd_ls_di=`cd "$ac_pwd" && ls -di .` ||
as_fn_error $? "working directory cannot be determined"
test "X$ac_ls_di" = "X$ac_pwd_ls_di" ||
as_fn_error $? "pwd does not report name of working directory"
# Find the source files, if location was not specified.
if test -z "$srcdir"; then
ac_srcdir_defaulted=yes
# Try the directory containing this script, then the parent directory.
ac_confdir=`$as_dirname -- "$as_myself" ||
$as_expr X"$as_myself" : 'X\(.*[^/]\)//*[^/][^/]*/*$' \| \
X"$as_myself" : 'X\(//\)[^/]' \| \
X"$as_myself" : 'X\(//\)$' \| \
X"$as_myself" : 'X\(/\)' \| . 2>/dev/null ||
$as_echo X"$as_myself" |
sed '/^X\(.*[^/]\)\/\/*[^/][^/]*\/*$/{
s//\1/
q
}
/^X\(\/\/\)[^/].*/{
s//\1/
q
}
/^X\(\/\/\)$/{
s//\1/
q
}
/^X\(\/\).*/{
s//\1/
q
}
s/.*/./; q'`
srcdir=$ac_confdir
if test ! -r "$srcdir/$ac_unique_file"; then
srcdir=..
fi
else
ac_srcdir_defaulted=no
fi
if test ! -r "$srcdir/$ac_unique_file"; then
test "$ac_srcdir_defaulted" = yes && srcdir="$ac_confdir or .."
as_fn_error $? "cannot find sources ($ac_unique_file) in $srcdir"
fi
ac_msg="sources are in $srcdir, but \`cd $srcdir' does not work"
ac_abs_confdir=`(
cd "$srcdir" && test -r "./$ac_unique_file" || as_fn_error $? "$ac_msg"
pwd)`
# When building in place, set srcdir=.
if test "$ac_abs_confdir" = "$ac_pwd"; then
srcdir=.
fi
# Remove unnecessary trailing slashes from srcdir.
# Double slashes in file names in object file debugging info
# mess up M-x gdb in Emacs.
case $srcdir in
*/) srcdir=`expr "X$srcdir" : 'X\(.*[^/]\)' \| "X$srcdir" : 'X\(.*\)'`;;
esac
for ac_var in $ac_precious_vars; do
eval ac_env_${ac_var}_set=\${${ac_var}+set}
eval ac_env_${ac_var}_value=\$${ac_var}
eval ac_cv_env_${ac_var}_set=\${${ac_var}+set}
eval ac_cv_env_${ac_var}_value=\$${ac_var}
done
#
# Report the --help message.
#
if test "$ac_init_help" = "long"; then
# Omit some internal or obsolete options to make the list less imposing.
# This message is too long to be a string in the A/UX 3.1 sh.
cat <<_ACEOF
\`configure' configures jhbuild 3.5.91 to adapt to many kinds of systems.
Usage: $0 [OPTION]... [VAR=VALUE]...
To assign environment variables (e.g., CC, CFLAGS...), specify them as
VAR=VALUE. See below for descriptions of some of the useful variables.
Defaults for the options are specified in brackets.
Configuration:
-h, --help display this help and exit
--help=short display options specific to this package
--help=recursive display the short help of all the included packages
-V, --version display version information and exit
-q, --quiet, --silent do not print \`checking ...' messages
--cache-file=FILE cache test results in FILE [disabled]
-C, --config-cache alias for \`--cache-file=config.cache'
-n, --no-create do not create output files
--srcdir=DIR find the sources in DIR [configure dir or \`..']
Installation directories:
--prefix=PREFIX install architecture-independent files in PREFIX
[$ac_default_prefix]
--exec-prefix=EPREFIX install architecture-dependent files in EPREFIX
[PREFIX]
By default, \`make install' will install all the files in
\`$ac_default_prefix/bin', \`$ac_default_prefix/lib' etc. You can specify
an installation prefix other than \`$ac_default_prefix' using \`--prefix',
for instance \`--prefix=\$HOME'.
For better control, use the options below.
Fine tuning of the installation directories:
--bindir=DIR user executables [EPREFIX/bin]
--sbindir=DIR system admin executables [EPREFIX/sbin]
--libexecdir=DIR program executables [EPREFIX/libexec]
--sysconfdir=DIR read-only single-machine data [PREFIX/etc]
--sharedstatedir=DIR modifiable architecture-independent data [PREFIX/com]
--localstatedir=DIR modifiable single-machine data [PREFIX/var]
--libdir=DIR object code libraries [EPREFIX/lib]
--includedir=DIR C header files [PREFIX/include]
--oldincludedir=DIR C header files for non-gcc [/usr/include]
--datarootdir=DIR read-only arch.-independent data root [PREFIX/share]
--datadir=DIR read-only architecture-independent data [DATAROOTDIR]
--infodir=DIR info documentation [DATAROOTDIR/info]
--localedir=DIR locale-dependent data [DATAROOTDIR/locale]
--mandir=DIR man documentation [DATAROOTDIR/man]
--docdir=DIR documentation root [DATAROOTDIR/doc/jhbuild]
--htmldir=DIR html documentation [DOCDIR]
--dvidir=DIR dvi documentation [DOCDIR]
--pdfdir=DIR pdf documentation [DOCDIR]
--psdir=DIR ps documentation [DOCDIR]
_ACEOF
cat <<\_ACEOF
Program names:
--program-prefix=PREFIX prepend PREFIX to installed program names
--program-suffix=SUFFIX append SUFFIX to installed program names
--program-transform-name=PROGRAM run sed PROGRAM on installed program names
System types:
--build=BUILD configure for building on BUILD [guessed]
--host=HOST cross-compile to build programs to run on HOST [BUILD]
_ACEOF
fi
if test -n "$ac_init_help"; then
case $ac_init_help in
short | recursive ) echo "Configuration of jhbuild 3.5.91:";;
esac
cat <<\_ACEOF
Optional Features:
--disable-option-checking ignore unrecognized --enable/--with options
--disable-FEATURE do not include FEATURE (same as --enable-FEATURE=no)
--enable-FEATURE[=ARG] include FEATURE [ARG=yes]
--disable-maintainer-mode disable make rules and dependencies not useful
(and sometimes confusing) to the casual installer
--disable-dependency-tracking speeds up one-time build
--enable-dependency-tracking do not reject slow dependency extractors
--disable-nls do not use Native Language Support
--disable-rpath do not hardcode runtime library paths
--enable-doc-installation=[no/yes]
install the documentation files
Optional Packages:
--with-PACKAGE[=ARG] use PACKAGE [ARG=yes]
--without-PACKAGE do not use PACKAGE (same as --with-PACKAGE=no)
--with-gnu-ld assume the C compiler uses GNU ld default=no
--with-libiconv-prefix[=DIR] search for libiconv in DIR/include and DIR/lib
--without-libiconv-prefix don't search for libiconv in includedir and libdir
--with-libintl-prefix[=DIR] search for libintl in DIR/include and DIR/lib
--without-libintl-prefix don't search for libintl in includedir and libdir
--with-help-dir=DIR path where help files are installed
Some influential environment variables:
CC C compiler command
CFLAGS C compiler flags
LDFLAGS linker flags, e.g. -L if you have libraries in a
nonstandard directory
LIBS libraries to pass to the linker, e.g. -l
CPPFLAGS (Objective) C/C++ preprocessor flags, e.g. -I if
you have headers in a nonstandard directory
PYTHON the Python interpreter
PKG_CONFIG path to pkg-config utility
PKG_CONFIG_PATH
directories to add to pkg-config's search path
PKG_CONFIG_LIBDIR
path overriding pkg-config's built-in search path
ITSTOOL Path to the `itstool` command
XMLLINT Path to the `xmllint` command
Use these variables to override the choices made by `configure' or to help
it to find libraries and programs with nonstandard names/locations.
Report bugs to .
_ACEOF
ac_status=$?
fi
if test "$ac_init_help" = "recursive"; then
# If there are subdirs, report their specific --help.
for ac_dir in : $ac_subdirs_all; do test "x$ac_dir" = x: && continue
test -d "$ac_dir" ||
{ cd "$srcdir" && ac_pwd=`pwd` && srcdir=. && test -d "$ac_dir"; } ||
continue
ac_builddir=.
case "$ac_dir" in
.) ac_dir_suffix= ac_top_builddir_sub=. ac_top_build_prefix= ;;
*)
ac_dir_suffix=/`$as_echo "$ac_dir" | sed 's|^\.[\\/]||'`
# A ".." for each directory in $ac_dir_suffix.
ac_top_builddir_sub=`$as_echo "$ac_dir_suffix" | sed 's|/[^\\/]*|/..|g;s|/||'`
case $ac_top_builddir_sub in
"") ac_top_builddir_sub=. ac_top_build_prefix= ;;
*) ac_top_build_prefix=$ac_top_builddir_sub/ ;;
esac ;;
esac
ac_abs_top_builddir=$ac_pwd
ac_abs_builddir=$ac_pwd$ac_dir_suffix
# for backward compatibility:
ac_top_builddir=$ac_top_build_prefix
case $srcdir in
.) # We are building in place.
ac_srcdir=.
ac_top_srcdir=$ac_top_builddir_sub
ac_abs_top_srcdir=$ac_pwd ;;
[\\/]* | ?:[\\/]* ) # Absolute name.
ac_srcdir=$srcdir$ac_dir_suffix;
ac_top_srcdir=$srcdir
ac_abs_top_srcdir=$srcdir ;;
*) # Relative name.
ac_srcdir=$ac_top_build_prefix$srcdir$ac_dir_suffix
ac_top_srcdir=$ac_top_build_prefix$srcdir
ac_abs_top_srcdir=$ac_pwd/$srcdir ;;
esac
ac_abs_srcdir=$ac_abs_top_srcdir$ac_dir_suffix
cd "$ac_dir" || { ac_status=$?; continue; }
# Check for guested configure.
if test -f "$ac_srcdir/configure.gnu"; then
echo &&
$SHELL "$ac_srcdir/configure.gnu" --help=recursive
elif test -f "$ac_srcdir/configure"; then
echo &&
$SHELL "$ac_srcdir/configure" --help=recursive
else
$as_echo "$as_me: WARNING: no configuration information is in $ac_dir" >&2
fi || ac_status=$?
cd "$ac_pwd" || { ac_status=$?; break; }
done
fi
test -n "$ac_init_help" && exit $ac_status
if $ac_init_version; then
cat <<\_ACEOF
jhbuild configure 3.5.91
generated by GNU Autoconf 2.69
Copyright (C) 2012 Free Software Foundation, Inc.
This configure script is free software; the Free Software Foundation
gives unlimited permission to copy, distribute and modify it.
_ACEOF
exit
fi
## ------------------------ ##
## Autoconf initialization. ##
## ------------------------ ##
# ac_fn_c_try_compile LINENO
# --------------------------
# Try to compile conftest.$ac_ext, and return whether this succeeded.
ac_fn_c_try_compile ()
{
as_lineno=${as_lineno-"$1"} as_lineno_stack=as_lineno_stack=$as_lineno_stack
rm -f conftest.$ac_objext
if { { ac_try="$ac_compile"
case "(($ac_try" in
*\"* | *\`* | *\\*) ac_try_echo=\$ac_try;;
*) ac_try_echo=$ac_try;;
esac
eval ac_try_echo="\"\$as_me:${as_lineno-$LINENO}: $ac_try_echo\""
$as_echo "$ac_try_echo"; } >&5
(eval "$ac_compile") 2>conftest.err
ac_status=$?
if test -s conftest.err; then
grep -v '^ *+' conftest.err >conftest.er1
cat conftest.er1 >&5
mv -f conftest.er1 conftest.err
fi
$as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5
test $ac_status = 0; } && {
test -z "$ac_c_werror_flag" ||
test ! -s conftest.err
} && test -s conftest.$ac_objext; then :
ac_retval=0
else
$as_echo "$as_me: failed program was:" >&5
sed 's/^/| /' conftest.$ac_ext >&5
ac_retval=1
fi
eval $as_lineno_stack; ${as_lineno_stack:+:} unset as_lineno
as_fn_set_status $ac_retval
} # ac_fn_c_try_compile
# ac_fn_c_try_link LINENO
# -----------------------
# Try to link conftest.$ac_ext, and return whether this succeeded.
ac_fn_c_try_link ()
{
as_lineno=${as_lineno-"$1"} as_lineno_stack=as_lineno_stack=$as_lineno_stack
rm -f conftest.$ac_objext conftest$ac_exeext
if { { ac_try="$ac_link"
case "(($ac_try" in
*\"* | *\`* | *\\*) ac_try_echo=\$ac_try;;
*) ac_try_echo=$ac_try;;
esac
eval ac_try_echo="\"\$as_me:${as_lineno-$LINENO}: $ac_try_echo\""
$as_echo "$ac_try_echo"; } >&5
(eval "$ac_link") 2>conftest.err
ac_status=$?
if test -s conftest.err; then
grep -v '^ *+' conftest.err >conftest.er1
cat conftest.er1 >&5
mv -f conftest.er1 conftest.err
fi
$as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5
test $ac_status = 0; } && {
test -z "$ac_c_werror_flag" ||
test ! -s conftest.err
} && test -s conftest$ac_exeext && {
test "$cross_compiling" = yes ||
test -x conftest$ac_exeext
}; then :
ac_retval=0
else
$as_echo "$as_me: failed program was:" >&5
sed 's/^/| /' conftest.$ac_ext >&5
ac_retval=1
fi
# Delete the IPA/IPO (Inter Procedural Analysis/Optimization) information
# created by the PGI compiler (conftest_ipa8_conftest.oo), as it would
# interfere with the next link command; also delete a directory that is
# left behind by Apple's compiler. We do this before executing the actions.
rm -rf conftest.dSYM conftest_ipa8_conftest.oo
eval $as_lineno_stack; ${as_lineno_stack:+:} unset as_lineno
as_fn_set_status $ac_retval
} # ac_fn_c_try_link
# ac_fn_c_check_func LINENO FUNC VAR
# ----------------------------------
# Tests whether FUNC exists, setting the cache variable VAR accordingly
ac_fn_c_check_func ()
{
as_lineno=${as_lineno-"$1"} as_lineno_stack=as_lineno_stack=$as_lineno_stack
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $2" >&5
$as_echo_n "checking for $2... " >&6; }
if eval \${$3+:} false; then :
$as_echo_n "(cached) " >&6
else
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h. */
/* Define $2 to an innocuous variant, in case declares $2.
For example, HP-UX 11i declares gettimeofday. */
#define $2 innocuous_$2
/* System header to define __stub macros and hopefully few prototypes,
which can conflict with char $2 (); below.
Prefer to if __STDC__ is defined, since
exists even on freestanding compilers. */
#ifdef __STDC__
# include
#else
# include
#endif
#undef $2
/* Override any GCC internal prototype to avoid an error.
Use char because int might match the return type of a GCC
builtin and then its argument prototype would still apply. */
#ifdef __cplusplus
extern "C"
#endif
char $2 ();
/* The GNU C library defines this for functions which it implements
to always fail with ENOSYS. Some functions are actually named
something starting with __ and the normal name is an alias. */
#if defined __stub_$2 || defined __stub___$2
choke me
#endif
int
main ()
{
return $2 ();
;
return 0;
}
_ACEOF
if ac_fn_c_try_link "$LINENO"; then :
eval "$3=yes"
else
eval "$3=no"
fi
rm -f core conftest.err conftest.$ac_objext \
conftest$ac_exeext conftest.$ac_ext
fi
eval ac_res=\$$3
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_res" >&5
$as_echo "$ac_res" >&6; }
eval $as_lineno_stack; ${as_lineno_stack:+:} unset as_lineno
} # ac_fn_c_check_func
# ac_fn_c_try_run LINENO
# ----------------------
# Try to link conftest.$ac_ext, and return whether this succeeded. Assumes
# that executables *can* be run.
ac_fn_c_try_run ()
{
as_lineno=${as_lineno-"$1"} as_lineno_stack=as_lineno_stack=$as_lineno_stack
if { { ac_try="$ac_link"
case "(($ac_try" in
*\"* | *\`* | *\\*) ac_try_echo=\$ac_try;;
*) ac_try_echo=$ac_try;;
esac
eval ac_try_echo="\"\$as_me:${as_lineno-$LINENO}: $ac_try_echo\""
$as_echo "$ac_try_echo"; } >&5
(eval "$ac_link") 2>&5
ac_status=$?
$as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5
test $ac_status = 0; } && { ac_try='./conftest$ac_exeext'
{ { case "(($ac_try" in
*\"* | *\`* | *\\*) ac_try_echo=\$ac_try;;
*) ac_try_echo=$ac_try;;
esac
eval ac_try_echo="\"\$as_me:${as_lineno-$LINENO}: $ac_try_echo\""
$as_echo "$ac_try_echo"; } >&5
(eval "$ac_try") 2>&5
ac_status=$?
$as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5
test $ac_status = 0; }; }; then :
ac_retval=0
else
$as_echo "$as_me: program exited with status $ac_status" >&5
$as_echo "$as_me: failed program was:" >&5
sed 's/^/| /' conftest.$ac_ext >&5
ac_retval=$ac_status
fi
rm -rf conftest.dSYM conftest_ipa8_conftest.oo
eval $as_lineno_stack; ${as_lineno_stack:+:} unset as_lineno
as_fn_set_status $ac_retval
} # ac_fn_c_try_run
cat >config.log <<_ACEOF
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
It was created by jhbuild $as_me 3.5.91, which was
generated by GNU Autoconf 2.69. Invocation command line was
$ $0 $@
_ACEOF
exec 5>>config.log
{
cat <<_ASUNAME
## --------- ##
## Platform. ##
## --------- ##
hostname = `(hostname || uname -n) 2>/dev/null | sed 1q`
uname -m = `(uname -m) 2>/dev/null || echo unknown`
uname -r = `(uname -r) 2>/dev/null || echo unknown`
uname -s = `(uname -s) 2>/dev/null || echo unknown`
uname -v = `(uname -v) 2>/dev/null || echo unknown`
/usr/bin/uname -p = `(/usr/bin/uname -p) 2>/dev/null || echo unknown`
/bin/uname -X = `(/bin/uname -X) 2>/dev/null || echo unknown`
/bin/arch = `(/bin/arch) 2>/dev/null || echo unknown`
/usr/bin/arch -k = `(/usr/bin/arch -k) 2>/dev/null || echo unknown`
/usr/convex/getsysinfo = `(/usr/convex/getsysinfo) 2>/dev/null || echo unknown`
/usr/bin/hostinfo = `(/usr/bin/hostinfo) 2>/dev/null || echo unknown`
/bin/machine = `(/bin/machine) 2>/dev/null || echo unknown`
/usr/bin/oslevel = `(/usr/bin/oslevel) 2>/dev/null || echo unknown`
/bin/universe = `(/bin/universe) 2>/dev/null || echo unknown`
_ASUNAME
as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
for as_dir in $PATH
do
IFS=$as_save_IFS
test -z "$as_dir" && as_dir=.
$as_echo "PATH: $as_dir"
done
IFS=$as_save_IFS
} >&5
cat >&5 <<_ACEOF
## ----------- ##
## Core tests. ##
## ----------- ##
_ACEOF
# Keep a trace of the command line.
# Strip out --no-create and --no-recursion so they do not pile up.
# Strip out --silent because we don't want to record it for future runs.
# Also quote any args containing shell meta-characters.
# Make two passes to allow for proper duplicate-argument suppression.
ac_configure_args=
ac_configure_args0=
ac_configure_args1=
ac_must_keep_next=false
for ac_pass in 1 2
do
for ac_arg
do
case $ac_arg in
-no-create | --no-c* | -n | -no-recursion | --no-r*) continue ;;
-q | -quiet | --quiet | --quie | --qui | --qu | --q \
| -silent | --silent | --silen | --sile | --sil)
continue ;;
*\'*)
ac_arg=`$as_echo "$ac_arg" | sed "s/'/'\\\\\\\\''/g"` ;;
esac
case $ac_pass in
1) as_fn_append ac_configure_args0 " '$ac_arg'" ;;
2)
as_fn_append ac_configure_args1 " '$ac_arg'"
if test $ac_must_keep_next = true; then
ac_must_keep_next=false # Got value, back to normal.
else
case $ac_arg in
*=* | --config-cache | -C | -disable-* | --disable-* \
| -enable-* | --enable-* | -gas | --g* | -nfp | --nf* \
| -q | -quiet | --q* | -silent | --sil* | -v | -verb* \
| -with-* | --with-* | -without-* | --without-* | --x)
case "$ac_configure_args0 " in
"$ac_configure_args1"*" '$ac_arg' "* ) continue ;;
esac
;;
-* ) ac_must_keep_next=true ;;
esac
fi
as_fn_append ac_configure_args " '$ac_arg'"
;;
esac
done
done
{ ac_configure_args0=; unset ac_configure_args0;}
{ ac_configure_args1=; unset ac_configure_args1;}
# When interrupted or exit'd, cleanup temporary files, and complete
# config.log. We remove comments because anyway the quotes in there
# would cause problems or look ugly.
# WARNING: Use '\'' to represent an apostrophe within the trap.
# WARNING: Do not start the trap code with a newline, due to a FreeBSD 4.0 bug.
trap 'exit_status=$?
# Save into config.log some information that might help in debugging.
{
echo
$as_echo "## ---------------- ##
## Cache variables. ##
## ---------------- ##"
echo
# The following way of writing the cache mishandles newlines in values,
(
for ac_var in `(set) 2>&1 | sed -n '\''s/^\([a-zA-Z_][a-zA-Z0-9_]*\)=.*/\1/p'\''`; do
eval ac_val=\$$ac_var
case $ac_val in #(
*${as_nl}*)
case $ac_var in #(
*_cv_*) { $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: cache variable $ac_var contains a newline" >&5
$as_echo "$as_me: WARNING: cache variable $ac_var contains a newline" >&2;} ;;
esac
case $ac_var in #(
_ | IFS | as_nl) ;; #(
BASH_ARGV | BASH_SOURCE) eval $ac_var= ;; #(
*) { eval $ac_var=; unset $ac_var;} ;;
esac ;;
esac
done
(set) 2>&1 |
case $as_nl`(ac_space='\'' '\''; set) 2>&1` in #(
*${as_nl}ac_space=\ *)
sed -n \
"s/'\''/'\''\\\\'\'''\''/g;
s/^\\([_$as_cr_alnum]*_cv_[_$as_cr_alnum]*\\)=\\(.*\\)/\\1='\''\\2'\''/p"
;; #(
*)
sed -n "/^[_$as_cr_alnum]*_cv_[_$as_cr_alnum]*=/p"
;;
esac |
sort
)
echo
$as_echo "## ----------------- ##
## Output variables. ##
## ----------------- ##"
echo
for ac_var in $ac_subst_vars
do
eval ac_val=\$$ac_var
case $ac_val in
*\'\''*) ac_val=`$as_echo "$ac_val" | sed "s/'\''/'\''\\\\\\\\'\'''\''/g"`;;
esac
$as_echo "$ac_var='\''$ac_val'\''"
done | sort
echo
if test -n "$ac_subst_files"; then
$as_echo "## ------------------- ##
## File substitutions. ##
## ------------------- ##"
echo
for ac_var in $ac_subst_files
do
eval ac_val=\$$ac_var
case $ac_val in
*\'\''*) ac_val=`$as_echo "$ac_val" | sed "s/'\''/'\''\\\\\\\\'\'''\''/g"`;;
esac
$as_echo "$ac_var='\''$ac_val'\''"
done | sort
echo
fi
if test -s confdefs.h; then
$as_echo "## ----------- ##
## confdefs.h. ##
## ----------- ##"
echo
cat confdefs.h
echo
fi
test "$ac_signal" != 0 &&
$as_echo "$as_me: caught signal $ac_signal"
$as_echo "$as_me: exit $exit_status"
} >&5
rm -f core *.core core.conftest.* &&
rm -f -r conftest* confdefs* conf$$* $ac_clean_files &&
exit $exit_status
' 0
for ac_signal in 1 2 13 15; do
trap 'ac_signal='$ac_signal'; as_fn_exit 1' $ac_signal
done
ac_signal=0
# confdefs.h avoids OS command line length limits that DEFS can exceed.
rm -f -r conftest* confdefs.h
$as_echo "/* confdefs.h */" > confdefs.h
# Predefined preprocessor variables.
cat >>confdefs.h <<_ACEOF
#define PACKAGE_NAME "$PACKAGE_NAME"
_ACEOF
cat >>confdefs.h <<_ACEOF
#define PACKAGE_TARNAME "$PACKAGE_TARNAME"
_ACEOF
cat >>confdefs.h <<_ACEOF
#define PACKAGE_VERSION "$PACKAGE_VERSION"
_ACEOF
cat >>confdefs.h <<_ACEOF
#define PACKAGE_STRING "$PACKAGE_STRING"
_ACEOF
cat >>confdefs.h <<_ACEOF
#define PACKAGE_BUGREPORT "$PACKAGE_BUGREPORT"
_ACEOF
cat >>confdefs.h <<_ACEOF
#define PACKAGE_URL "$PACKAGE_URL"
_ACEOF
# Let the site file select an alternate cache file if it wants to.
# Prefer an explicitly selected file to automatically selected ones.
ac_site_file1=NONE
ac_site_file2=NONE
if test -n "$CONFIG_SITE"; then
# We do not want a PATH search for config.site.
case $CONFIG_SITE in #((
-*) ac_site_file1=./$CONFIG_SITE;;
*/*) ac_site_file1=$CONFIG_SITE;;
*) ac_site_file1=./$CONFIG_SITE;;
esac
elif test "x$prefix" != xNONE; then
ac_site_file1=$prefix/share/config.site
ac_site_file2=$prefix/etc/config.site
else
ac_site_file1=$ac_default_prefix/share/config.site
ac_site_file2=$ac_default_prefix/etc/config.site
fi
for ac_site_file in "$ac_site_file1" "$ac_site_file2"
do
test "x$ac_site_file" = xNONE && continue
if test /dev/null != "$ac_site_file" && test -r "$ac_site_file"; then
{ $as_echo "$as_me:${as_lineno-$LINENO}: loading site script $ac_site_file" >&5
$as_echo "$as_me: loading site script $ac_site_file" >&6;}
sed 's/^/| /' "$ac_site_file" >&5
. "$ac_site_file" \
|| { { $as_echo "$as_me:${as_lineno-$LINENO}: error: in \`$ac_pwd':" >&5
$as_echo "$as_me: error: in \`$ac_pwd':" >&2;}
as_fn_error $? "failed to load site script $ac_site_file
See \`config.log' for more details" "$LINENO" 5; }
fi
done
if test -r "$cache_file"; then
# Some versions of bash will fail to source /dev/null (special files
# actually), so we avoid doing that. DJGPP emulates it as a regular file.
if test /dev/null != "$cache_file" && test -f "$cache_file"; then
{ $as_echo "$as_me:${as_lineno-$LINENO}: loading cache $cache_file" >&5
$as_echo "$as_me: loading cache $cache_file" >&6;}
case $cache_file in
[\\/]* | ?:[\\/]* ) . "$cache_file";;
*) . "./$cache_file";;
esac
fi
else
{ $as_echo "$as_me:${as_lineno-$LINENO}: creating cache $cache_file" >&5
$as_echo "$as_me: creating cache $cache_file" >&6;}
>$cache_file
fi
gt_needs="$gt_needs "
# Check that the precious variables saved in the cache have kept the same
# value.
ac_cache_corrupted=false
for ac_var in $ac_precious_vars; do
eval ac_old_set=\$ac_cv_env_${ac_var}_set
eval ac_new_set=\$ac_env_${ac_var}_set
eval ac_old_val=\$ac_cv_env_${ac_var}_value
eval ac_new_val=\$ac_env_${ac_var}_value
case $ac_old_set,$ac_new_set in
set,)
{ $as_echo "$as_me:${as_lineno-$LINENO}: error: \`$ac_var' was set to \`$ac_old_val' in the previous run" >&5
$as_echo "$as_me: error: \`$ac_var' was set to \`$ac_old_val' in the previous run" >&2;}
ac_cache_corrupted=: ;;
,set)
{ $as_echo "$as_me:${as_lineno-$LINENO}: error: \`$ac_var' was not set in the previous run" >&5
$as_echo "$as_me: error: \`$ac_var' was not set in the previous run" >&2;}
ac_cache_corrupted=: ;;
,);;
*)
if test "x$ac_old_val" != "x$ac_new_val"; then
# differences in whitespace do not lead to failure.
ac_old_val_w=`echo x $ac_old_val`
ac_new_val_w=`echo x $ac_new_val`
if test "$ac_old_val_w" != "$ac_new_val_w"; then
{ $as_echo "$as_me:${as_lineno-$LINENO}: error: \`$ac_var' has changed since the previous run:" >&5
$as_echo "$as_me: error: \`$ac_var' has changed since the previous run:" >&2;}
ac_cache_corrupted=:
else
{ $as_echo "$as_me:${as_lineno-$LINENO}: warning: ignoring whitespace changes in \`$ac_var' since the previous run:" >&5
$as_echo "$as_me: warning: ignoring whitespace changes in \`$ac_var' since the previous run:" >&2;}
eval $ac_var=\$ac_old_val
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: former value: \`$ac_old_val'" >&5
$as_echo "$as_me: former value: \`$ac_old_val'" >&2;}
{ $as_echo "$as_me:${as_lineno-$LINENO}: current value: \`$ac_new_val'" >&5
$as_echo "$as_me: current value: \`$ac_new_val'" >&2;}
fi;;
esac
# Pass precious variables to config.status.
if test "$ac_new_set" = set; then
case $ac_new_val in
*\'*) ac_arg=$ac_var=`$as_echo "$ac_new_val" | sed "s/'/'\\\\\\\\''/g"` ;;
*) ac_arg=$ac_var=$ac_new_val ;;
esac
case " $ac_configure_args " in
*" '$ac_arg' "*) ;; # Avoid dups. Use of quotes ensures accuracy.
*) as_fn_append ac_configure_args " '$ac_arg'" ;;
esac
fi
done
if $ac_cache_corrupted; then
{ $as_echo "$as_me:${as_lineno-$LINENO}: error: in \`$ac_pwd':" >&5
$as_echo "$as_me: error: in \`$ac_pwd':" >&2;}
{ $as_echo "$as_me:${as_lineno-$LINENO}: error: changes in the environment can compromise the build" >&5
$as_echo "$as_me: error: changes in the environment can compromise the build" >&2;}
as_fn_error $? "run \`make distclean' and/or \`rm $cache_file' and start over" "$LINENO" 5
fi
## -------------------- ##
## Main body of script. ##
## -------------------- ##
ac_ext=c
ac_cpp='$CPP $CPPFLAGS'
ac_compile='$CC -c $CFLAGS $CPPFLAGS conftest.$ac_ext >&5'
ac_link='$CC -o conftest$ac_exeext $CFLAGS $CPPFLAGS $LDFLAGS conftest.$ac_ext $LIBS >&5'
ac_compiler_gnu=$ac_cv_c_compiler_gnu
ac_aux_dir=
for ac_dir in build-aux "$srcdir"/build-aux; do
if test -f "$ac_dir/install-sh"; then
ac_aux_dir=$ac_dir
ac_install_sh="$ac_aux_dir/install-sh -c"
break
elif test -f "$ac_dir/install.sh"; then
ac_aux_dir=$ac_dir
ac_install_sh="$ac_aux_dir/install.sh -c"
break
elif test -f "$ac_dir/shtool"; then
ac_aux_dir=$ac_dir
ac_install_sh="$ac_aux_dir/shtool install -c"
break
fi
done
if test -z "$ac_aux_dir"; then
as_fn_error $? "cannot find install-sh, install.sh, or shtool in build-aux \"$srcdir\"/build-aux" "$LINENO" 5
fi
# These three variables are undocumented and unsupported,
# and are intended to be withdrawn in a future Autoconf release.
# They can cause serious problems if a builder's source tree is in a directory
# whose full name contains unusual characters.
ac_config_guess="$SHELL $ac_aux_dir/config.guess" # Please don't use this var.
ac_config_sub="$SHELL $ac_aux_dir/config.sub" # Please don't use this var.
ac_configure="$SHELL $ac_aux_dir/configure" # Please don't use this var.
am__api_version='1.11'
# Find a good install program. We prefer a C program (faster),
# so one script is as good as another. But avoid the broken or
# incompatible versions:
# SysV /etc/install, /usr/sbin/install
# SunOS /usr/etc/install
# IRIX /sbin/install
# AIX /bin/install
# AmigaOS /C/install, which installs bootblocks on floppy discs
# AIX 4 /usr/bin/installbsd, which doesn't work without a -g flag
# AFS /usr/afsws/bin/install, which mishandles nonexistent args
# SVR4 /usr/ucb/install, which tries to use the nonexistent group "staff"
# OS/2's system install, which has a completely different semantic
# ./install, which can be erroneously created by make from ./install.sh.
# Reject install programs that cannot install multiple files.
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for a BSD-compatible install" >&5
$as_echo_n "checking for a BSD-compatible install... " >&6; }
if test -z "$INSTALL"; then
if ${ac_cv_path_install+:} false; then :
$as_echo_n "(cached) " >&6
else
as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
for as_dir in $PATH
do
IFS=$as_save_IFS
test -z "$as_dir" && as_dir=.
# Account for people who put trailing slashes in PATH elements.
case $as_dir/ in #((
./ | .// | /[cC]/* | \
/etc/* | /usr/sbin/* | /usr/etc/* | /sbin/* | /usr/afsws/bin/* | \
?:[\\/]os2[\\/]install[\\/]* | ?:[\\/]OS2[\\/]INSTALL[\\/]* | \
/usr/ucb/* ) ;;
*)
# OSF1 and SCO ODT 3.0 have their own names for install.
# Don't use installbsd from OSF since it installs stuff as root
# by default.
for ac_prog in ginstall scoinst install; do
for ac_exec_ext in '' $ac_executable_extensions; do
if as_fn_executable_p "$as_dir/$ac_prog$ac_exec_ext"; then
if test $ac_prog = install &&
grep dspmsg "$as_dir/$ac_prog$ac_exec_ext" >/dev/null 2>&1; then
# AIX install. It has an incompatible calling convention.
:
elif test $ac_prog = install &&
grep pwplus "$as_dir/$ac_prog$ac_exec_ext" >/dev/null 2>&1; then
# program-specific install script used by HP pwplus--don't use.
:
else
rm -rf conftest.one conftest.two conftest.dir
echo one > conftest.one
echo two > conftest.two
mkdir conftest.dir
if "$as_dir/$ac_prog$ac_exec_ext" -c conftest.one conftest.two "`pwd`/conftest.dir" &&
test -s conftest.one && test -s conftest.two &&
test -s conftest.dir/conftest.one &&
test -s conftest.dir/conftest.two
then
ac_cv_path_install="$as_dir/$ac_prog$ac_exec_ext -c"
break 3
fi
fi
fi
done
done
;;
esac
done
IFS=$as_save_IFS
rm -rf conftest.one conftest.two conftest.dir
fi
if test "${ac_cv_path_install+set}" = set; then
INSTALL=$ac_cv_path_install
else
# As a last resort, use the slow shell script. Don't cache a
# value for INSTALL within a source directory, because that will
# break other packages using the cache if that directory is
# removed, or if the value is a relative name.
INSTALL=$ac_install_sh
fi
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $INSTALL" >&5
$as_echo "$INSTALL" >&6; }
# Use test -z because SunOS4 sh mishandles braces in ${var-val}.
# It thinks the first close brace ends the variable substitution.
test -z "$INSTALL_PROGRAM" && INSTALL_PROGRAM='${INSTALL}'
test -z "$INSTALL_SCRIPT" && INSTALL_SCRIPT='${INSTALL}'
test -z "$INSTALL_DATA" && INSTALL_DATA='${INSTALL} -m 644'
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether build environment is sane" >&5
$as_echo_n "checking whether build environment is sane... " >&6; }
# Just in case
sleep 1
echo timestamp > conftest.file
# Reject unsafe characters in $srcdir or the absolute working directory
# name. Accept space and tab only in the latter.
am_lf='
'
case `pwd` in
*[\\\"\#\$\&\'\`$am_lf]*)
as_fn_error $? "unsafe absolute working directory name" "$LINENO" 5;;
esac
case $srcdir in
*[\\\"\#\$\&\'\`$am_lf\ \ ]*)
as_fn_error $? "unsafe srcdir value: \`$srcdir'" "$LINENO" 5;;
esac
# Do `set' in a subshell so we don't clobber the current shell's
# arguments. Must try -L first in case configure is actually a
# symlink; some systems play weird games with the mod time of symlinks
# (eg FreeBSD returns the mod time of the symlink's containing
# directory).
if (
set X `ls -Lt "$srcdir/configure" conftest.file 2> /dev/null`
if test "$*" = "X"; then
# -L didn't work.
set X `ls -t "$srcdir/configure" conftest.file`
fi
rm -f conftest.file
if test "$*" != "X $srcdir/configure conftest.file" \
&& test "$*" != "X conftest.file $srcdir/configure"; then
# If neither matched, then we have a broken ls. This can happen
# if, for instance, CONFIG_SHELL is bash and it inherits a
# broken ls alias from the environment. This has actually
# happened. Such a system could not be considered "sane".
as_fn_error $? "ls -t appears to fail. Make sure there is not a broken
alias in your environment" "$LINENO" 5
fi
test "$2" = conftest.file
)
then
# Ok.
:
else
as_fn_error $? "newly created file is older than distributed files!
Check your system clock" "$LINENO" 5
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: yes" >&5
$as_echo "yes" >&6; }
test "$program_prefix" != NONE &&
program_transform_name="s&^&$program_prefix&;$program_transform_name"
# Use a double $ so make ignores it.
test "$program_suffix" != NONE &&
program_transform_name="s&\$&$program_suffix&;$program_transform_name"
# Double any \ or $.
# By default was `s,x,x', remove it if useless.
ac_script='s/[\\$]/&&/g;s/;s,x,x,$//'
program_transform_name=`$as_echo "$program_transform_name" | sed "$ac_script"`
# expand $ac_aux_dir to an absolute path
am_aux_dir=`cd $ac_aux_dir && pwd`
if test x"${MISSING+set}" != xset; then
case $am_aux_dir in
*\ * | *\ *)
MISSING="\${SHELL} \"$am_aux_dir/missing\"" ;;
*)
MISSING="\${SHELL} $am_aux_dir/missing" ;;
esac
fi
# Use eval to expand $SHELL
if eval "$MISSING --run true"; then
am_missing_run="$MISSING --run "
else
am_missing_run=
{ $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: \`missing' script is too old or missing" >&5
$as_echo "$as_me: WARNING: \`missing' script is too old or missing" >&2;}
fi
if test x"${install_sh}" != xset; then
case $am_aux_dir in
*\ * | *\ *)
install_sh="\${SHELL} '$am_aux_dir/install-sh'" ;;
*)
install_sh="\${SHELL} $am_aux_dir/install-sh"
esac
fi
# Installed binaries are usually stripped using `strip' when the user
# run `make install-strip'. However `strip' might not be the right
# tool to use in cross-compilation environments, therefore Automake
# will honor the `STRIP' environment variable to overrule this program.
if test "$cross_compiling" != no; then
if test -n "$ac_tool_prefix"; then
# Extract the first word of "${ac_tool_prefix}strip", so it can be a program name with args.
set dummy ${ac_tool_prefix}strip; ac_word=$2
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5
$as_echo_n "checking for $ac_word... " >&6; }
if ${ac_cv_prog_STRIP+:} false; then :
$as_echo_n "(cached) " >&6
else
if test -n "$STRIP"; then
ac_cv_prog_STRIP="$STRIP" # Let the user override the test.
else
as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
for as_dir in $PATH
do
IFS=$as_save_IFS
test -z "$as_dir" && as_dir=.
for ac_exec_ext in '' $ac_executable_extensions; do
if as_fn_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
ac_cv_prog_STRIP="${ac_tool_prefix}strip"
$as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5
break 2
fi
done
done
IFS=$as_save_IFS
fi
fi
STRIP=$ac_cv_prog_STRIP
if test -n "$STRIP"; then
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $STRIP" >&5
$as_echo "$STRIP" >&6; }
else
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
fi
fi
if test -z "$ac_cv_prog_STRIP"; then
ac_ct_STRIP=$STRIP
# Extract the first word of "strip", so it can be a program name with args.
set dummy strip; ac_word=$2
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5
$as_echo_n "checking for $ac_word... " >&6; }
if ${ac_cv_prog_ac_ct_STRIP+:} false; then :
$as_echo_n "(cached) " >&6
else
if test -n "$ac_ct_STRIP"; then
ac_cv_prog_ac_ct_STRIP="$ac_ct_STRIP" # Let the user override the test.
else
as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
for as_dir in $PATH
do
IFS=$as_save_IFS
test -z "$as_dir" && as_dir=.
for ac_exec_ext in '' $ac_executable_extensions; do
if as_fn_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
ac_cv_prog_ac_ct_STRIP="strip"
$as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5
break 2
fi
done
done
IFS=$as_save_IFS
fi
fi
ac_ct_STRIP=$ac_cv_prog_ac_ct_STRIP
if test -n "$ac_ct_STRIP"; then
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_ct_STRIP" >&5
$as_echo "$ac_ct_STRIP" >&6; }
else
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
fi
if test "x$ac_ct_STRIP" = x; then
STRIP=":"
else
case $cross_compiling:$ac_tool_warned in
yes:)
{ $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: using cross tools not prefixed with host triplet" >&5
$as_echo "$as_me: WARNING: using cross tools not prefixed with host triplet" >&2;}
ac_tool_warned=yes ;;
esac
STRIP=$ac_ct_STRIP
fi
else
STRIP="$ac_cv_prog_STRIP"
fi
fi
INSTALL_STRIP_PROGRAM="\$(install_sh) -c -s"
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for a thread-safe mkdir -p" >&5
$as_echo_n "checking for a thread-safe mkdir -p... " >&6; }
if test -z "$MKDIR_P"; then
if ${ac_cv_path_mkdir+:} false; then :
$as_echo_n "(cached) " >&6
else
as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
for as_dir in $PATH$PATH_SEPARATOR/opt/sfw/bin
do
IFS=$as_save_IFS
test -z "$as_dir" && as_dir=.
for ac_prog in mkdir gmkdir; do
for ac_exec_ext in '' $ac_executable_extensions; do
as_fn_executable_p "$as_dir/$ac_prog$ac_exec_ext" || continue
case `"$as_dir/$ac_prog$ac_exec_ext" --version 2>&1` in #(
'mkdir (GNU coreutils) '* | \
'mkdir (coreutils) '* | \
'mkdir (fileutils) '4.1*)
ac_cv_path_mkdir=$as_dir/$ac_prog$ac_exec_ext
break 3;;
esac
done
done
done
IFS=$as_save_IFS
fi
test -d ./--version && rmdir ./--version
if test "${ac_cv_path_mkdir+set}" = set; then
MKDIR_P="$ac_cv_path_mkdir -p"
else
# As a last resort, use the slow shell script. Don't cache a
# value for MKDIR_P within a source directory, because that will
# break other packages using the cache if that directory is
# removed, or if the value is a relative name.
MKDIR_P="$ac_install_sh -d"
fi
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $MKDIR_P" >&5
$as_echo "$MKDIR_P" >&6; }
mkdir_p="$MKDIR_P"
case $mkdir_p in
[\\/$]* | ?:[\\/]*) ;;
*/*) mkdir_p="\$(top_builddir)/$mkdir_p" ;;
esac
for ac_prog in gawk mawk nawk awk
do
# Extract the first word of "$ac_prog", so it can be a program name with args.
set dummy $ac_prog; ac_word=$2
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5
$as_echo_n "checking for $ac_word... " >&6; }
if ${ac_cv_prog_AWK+:} false; then :
$as_echo_n "(cached) " >&6
else
if test -n "$AWK"; then
ac_cv_prog_AWK="$AWK" # Let the user override the test.
else
as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
for as_dir in $PATH
do
IFS=$as_save_IFS
test -z "$as_dir" && as_dir=.
for ac_exec_ext in '' $ac_executable_extensions; do
if as_fn_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
ac_cv_prog_AWK="$ac_prog"
$as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5
break 2
fi
done
done
IFS=$as_save_IFS
fi
fi
AWK=$ac_cv_prog_AWK
if test -n "$AWK"; then
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $AWK" >&5
$as_echo "$AWK" >&6; }
else
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
fi
test -n "$AWK" && break
done
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether ${MAKE-make} sets \$(MAKE)" >&5
$as_echo_n "checking whether ${MAKE-make} sets \$(MAKE)... " >&6; }
set x ${MAKE-make}
ac_make=`$as_echo "$2" | sed 's/+/p/g; s/[^a-zA-Z0-9_]/_/g'`
if eval \${ac_cv_prog_make_${ac_make}_set+:} false; then :
$as_echo_n "(cached) " >&6
else
cat >conftest.make <<\_ACEOF
SHELL = /bin/sh
all:
@echo '@@@%%%=$(MAKE)=@@@%%%'
_ACEOF
# GNU make sometimes prints "make[1]: Entering ...", which would confuse us.
case `${MAKE-make} -f conftest.make 2>/dev/null` in
*@@@%%%=?*=@@@%%%*)
eval ac_cv_prog_make_${ac_make}_set=yes;;
*)
eval ac_cv_prog_make_${ac_make}_set=no;;
esac
rm -f conftest.make
fi
if eval test \$ac_cv_prog_make_${ac_make}_set = yes; then
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: yes" >&5
$as_echo "yes" >&6; }
SET_MAKE=
else
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
SET_MAKE="MAKE=${MAKE-make}"
fi
rm -rf .tst 2>/dev/null
mkdir .tst 2>/dev/null
if test -d .tst; then
am__leading_dot=.
else
am__leading_dot=_
fi
rmdir .tst 2>/dev/null
if test "`cd $srcdir && pwd`" != "`pwd`"; then
# Use -I$(srcdir) only when $(srcdir) != ., so that make's output
# is not polluted with repeated "-I."
am__isrc=' -I$(srcdir)'
# test to see if srcdir already configured
if test -f $srcdir/config.status; then
as_fn_error $? "source directory already configured; run \"make distclean\" there first" "$LINENO" 5
fi
fi
# test whether we have cygpath
if test -z "$CYGPATH_W"; then
if (cygpath --version) >/dev/null 2>/dev/null; then
CYGPATH_W='cygpath -w'
else
CYGPATH_W=echo
fi
fi
# Define the identity of the package.
PACKAGE='jhbuild'
VERSION='3.5.91'
# Some tools Automake needs.
ACLOCAL=${ACLOCAL-"${am_missing_run}aclocal-${am__api_version}"}
AUTOCONF=${AUTOCONF-"${am_missing_run}autoconf"}
AUTOMAKE=${AUTOMAKE-"${am_missing_run}automake-${am__api_version}"}
AUTOHEADER=${AUTOHEADER-"${am_missing_run}autoheader"}
MAKEINFO=${MAKEINFO-"${am_missing_run}makeinfo"}
# We need awk for the "check" target. The system "awk" is bad on
# some platforms.
# Always define AMTAR for backward compatibility. Yes, it's still used
# in the wild :-( We should find a proper way to deprecate it ...
AMTAR='$${TAR-tar}'
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking how to create a ustar tar archive" >&5
$as_echo_n "checking how to create a ustar tar archive... " >&6; }
# Loop over all known methods to create a tar archive until one works.
_am_tools='gnutar plaintar pax cpio none'
_am_tools=${am_cv_prog_tar_ustar-$_am_tools}
# Do not fold the above two line into one, because Tru64 sh and
# Solaris sh will not grok spaces in the rhs of `-'.
for _am_tool in $_am_tools
do
case $_am_tool in
gnutar)
for _am_tar in tar gnutar gtar;
do
{ echo "$as_me:$LINENO: $_am_tar --version" >&5
($_am_tar --version) >&5 2>&5
ac_status=$?
echo "$as_me:$LINENO: \$? = $ac_status" >&5
(exit $ac_status); } && break
done
am__tar="$_am_tar --format=ustar -chf - "'"$$tardir"'
am__tar_="$_am_tar --format=ustar -chf - "'"$tardir"'
am__untar="$_am_tar -xf -"
;;
plaintar)
# Must skip GNU tar: if it does not support --format= it doesn't create
# ustar tarball either.
(tar --version) >/dev/null 2>&1 && continue
am__tar='tar chf - "$$tardir"'
am__tar_='tar chf - "$tardir"'
am__untar='tar xf -'
;;
pax)
am__tar='pax -L -x ustar -w "$$tardir"'
am__tar_='pax -L -x ustar -w "$tardir"'
am__untar='pax -r'
;;
cpio)
am__tar='find "$$tardir" -print | cpio -o -H ustar -L'
am__tar_='find "$tardir" -print | cpio -o -H ustar -L'
am__untar='cpio -i -H ustar -d'
;;
none)
am__tar=false
am__tar_=false
am__untar=false
;;
esac
# If the value was cached, stop now. We just wanted to have am__tar
# and am__untar set.
test -n "${am_cv_prog_tar_ustar}" && break
# tar/untar a dummy directory, and stop if the command works
rm -rf conftest.dir
mkdir conftest.dir
echo GrepMe > conftest.dir/file
{ echo "$as_me:$LINENO: tardir=conftest.dir && eval $am__tar_ >conftest.tar" >&5
(tardir=conftest.dir && eval $am__tar_ >conftest.tar) >&5 2>&5
ac_status=$?
echo "$as_me:$LINENO: \$? = $ac_status" >&5
(exit $ac_status); }
rm -rf conftest.dir
if test -s conftest.tar; then
{ echo "$as_me:$LINENO: $am__untar &5
($am__untar &5 2>&5
ac_status=$?
echo "$as_me:$LINENO: \$? = $ac_status" >&5
(exit $ac_status); }
grep GrepMe conftest.dir/file >/dev/null 2>&1 && break
fi
done
rm -rf conftest.dir
if ${am_cv_prog_tar_ustar+:} false; then :
$as_echo_n "(cached) " >&6
else
am_cv_prog_tar_ustar=$_am_tool
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $am_cv_prog_tar_ustar" >&5
$as_echo "$am_cv_prog_tar_ustar" >&6; }
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether to enable maintainer-specific portions of Makefiles" >&5
$as_echo_n "checking whether to enable maintainer-specific portions of Makefiles... " >&6; }
# Check whether --enable-maintainer-mode was given.
if test "${enable_maintainer_mode+set}" = set; then :
enableval=$enable_maintainer_mode; USE_MAINTAINER_MODE=$enableval
else
USE_MAINTAINER_MODE=yes
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $USE_MAINTAINER_MODE" >&5
$as_echo "$USE_MAINTAINER_MODE" >&6; }
if test $USE_MAINTAINER_MODE = yes; then
MAINTAINER_MODE_TRUE=
MAINTAINER_MODE_FALSE='#'
else
MAINTAINER_MODE_TRUE='#'
MAINTAINER_MODE_FALSE=
fi
MAINT=$MAINTAINER_MODE_TRUE
# Check for programs
ac_ext=c
ac_cpp='$CPP $CPPFLAGS'
ac_compile='$CC -c $CFLAGS $CPPFLAGS conftest.$ac_ext >&5'
ac_link='$CC -o conftest$ac_exeext $CFLAGS $CPPFLAGS $LDFLAGS conftest.$ac_ext $LIBS >&5'
ac_compiler_gnu=$ac_cv_c_compiler_gnu
if test -n "$ac_tool_prefix"; then
# Extract the first word of "${ac_tool_prefix}gcc", so it can be a program name with args.
set dummy ${ac_tool_prefix}gcc; ac_word=$2
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5
$as_echo_n "checking for $ac_word... " >&6; }
if ${ac_cv_prog_CC+:} false; then :
$as_echo_n "(cached) " >&6
else
if test -n "$CC"; then
ac_cv_prog_CC="$CC" # Let the user override the test.
else
as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
for as_dir in $PATH
do
IFS=$as_save_IFS
test -z "$as_dir" && as_dir=.
for ac_exec_ext in '' $ac_executable_extensions; do
if as_fn_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
ac_cv_prog_CC="${ac_tool_prefix}gcc"
$as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5
break 2
fi
done
done
IFS=$as_save_IFS
fi
fi
CC=$ac_cv_prog_CC
if test -n "$CC"; then
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $CC" >&5
$as_echo "$CC" >&6; }
else
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
fi
fi
if test -z "$ac_cv_prog_CC"; then
ac_ct_CC=$CC
# Extract the first word of "gcc", so it can be a program name with args.
set dummy gcc; ac_word=$2
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5
$as_echo_n "checking for $ac_word... " >&6; }
if ${ac_cv_prog_ac_ct_CC+:} false; then :
$as_echo_n "(cached) " >&6
else
if test -n "$ac_ct_CC"; then
ac_cv_prog_ac_ct_CC="$ac_ct_CC" # Let the user override the test.
else
as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
for as_dir in $PATH
do
IFS=$as_save_IFS
test -z "$as_dir" && as_dir=.
for ac_exec_ext in '' $ac_executable_extensions; do
if as_fn_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
ac_cv_prog_ac_ct_CC="gcc"
$as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5
break 2
fi
done
done
IFS=$as_save_IFS
fi
fi
ac_ct_CC=$ac_cv_prog_ac_ct_CC
if test -n "$ac_ct_CC"; then
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_ct_CC" >&5
$as_echo "$ac_ct_CC" >&6; }
else
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
fi
if test "x$ac_ct_CC" = x; then
CC=""
else
case $cross_compiling:$ac_tool_warned in
yes:)
{ $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: using cross tools not prefixed with host triplet" >&5
$as_echo "$as_me: WARNING: using cross tools not prefixed with host triplet" >&2;}
ac_tool_warned=yes ;;
esac
CC=$ac_ct_CC
fi
else
CC="$ac_cv_prog_CC"
fi
if test -z "$CC"; then
if test -n "$ac_tool_prefix"; then
# Extract the first word of "${ac_tool_prefix}cc", so it can be a program name with args.
set dummy ${ac_tool_prefix}cc; ac_word=$2
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5
$as_echo_n "checking for $ac_word... " >&6; }
if ${ac_cv_prog_CC+:} false; then :
$as_echo_n "(cached) " >&6
else
if test -n "$CC"; then
ac_cv_prog_CC="$CC" # Let the user override the test.
else
as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
for as_dir in $PATH
do
IFS=$as_save_IFS
test -z "$as_dir" && as_dir=.
for ac_exec_ext in '' $ac_executable_extensions; do
if as_fn_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
ac_cv_prog_CC="${ac_tool_prefix}cc"
$as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5
break 2
fi
done
done
IFS=$as_save_IFS
fi
fi
CC=$ac_cv_prog_CC
if test -n "$CC"; then
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $CC" >&5
$as_echo "$CC" >&6; }
else
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
fi
fi
fi
if test -z "$CC"; then
# Extract the first word of "cc", so it can be a program name with args.
set dummy cc; ac_word=$2
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5
$as_echo_n "checking for $ac_word... " >&6; }
if ${ac_cv_prog_CC+:} false; then :
$as_echo_n "(cached) " >&6
else
if test -n "$CC"; then
ac_cv_prog_CC="$CC" # Let the user override the test.
else
ac_prog_rejected=no
as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
for as_dir in $PATH
do
IFS=$as_save_IFS
test -z "$as_dir" && as_dir=.
for ac_exec_ext in '' $ac_executable_extensions; do
if as_fn_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
if test "$as_dir/$ac_word$ac_exec_ext" = "/usr/ucb/cc"; then
ac_prog_rejected=yes
continue
fi
ac_cv_prog_CC="cc"
$as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5
break 2
fi
done
done
IFS=$as_save_IFS
if test $ac_prog_rejected = yes; then
# We found a bogon in the path, so make sure we never use it.
set dummy $ac_cv_prog_CC
shift
if test $# != 0; then
# We chose a different compiler from the bogus one.
# However, it has the same basename, so the bogon will be chosen
# first if we set CC to just the basename; use the full file name.
shift
ac_cv_prog_CC="$as_dir/$ac_word${1+' '}$@"
fi
fi
fi
fi
CC=$ac_cv_prog_CC
if test -n "$CC"; then
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $CC" >&5
$as_echo "$CC" >&6; }
else
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
fi
fi
if test -z "$CC"; then
if test -n "$ac_tool_prefix"; then
for ac_prog in cl.exe
do
# Extract the first word of "$ac_tool_prefix$ac_prog", so it can be a program name with args.
set dummy $ac_tool_prefix$ac_prog; ac_word=$2
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5
$as_echo_n "checking for $ac_word... " >&6; }
if ${ac_cv_prog_CC+:} false; then :
$as_echo_n "(cached) " >&6
else
if test -n "$CC"; then
ac_cv_prog_CC="$CC" # Let the user override the test.
else
as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
for as_dir in $PATH
do
IFS=$as_save_IFS
test -z "$as_dir" && as_dir=.
for ac_exec_ext in '' $ac_executable_extensions; do
if as_fn_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
ac_cv_prog_CC="$ac_tool_prefix$ac_prog"
$as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5
break 2
fi
done
done
IFS=$as_save_IFS
fi
fi
CC=$ac_cv_prog_CC
if test -n "$CC"; then
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $CC" >&5
$as_echo "$CC" >&6; }
else
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
fi
test -n "$CC" && break
done
fi
if test -z "$CC"; then
ac_ct_CC=$CC
for ac_prog in cl.exe
do
# Extract the first word of "$ac_prog", so it can be a program name with args.
set dummy $ac_prog; ac_word=$2
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5
$as_echo_n "checking for $ac_word... " >&6; }
if ${ac_cv_prog_ac_ct_CC+:} false; then :
$as_echo_n "(cached) " >&6
else
if test -n "$ac_ct_CC"; then
ac_cv_prog_ac_ct_CC="$ac_ct_CC" # Let the user override the test.
else
as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
for as_dir in $PATH
do
IFS=$as_save_IFS
test -z "$as_dir" && as_dir=.
for ac_exec_ext in '' $ac_executable_extensions; do
if as_fn_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
ac_cv_prog_ac_ct_CC="$ac_prog"
$as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5
break 2
fi
done
done
IFS=$as_save_IFS
fi
fi
ac_ct_CC=$ac_cv_prog_ac_ct_CC
if test -n "$ac_ct_CC"; then
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_ct_CC" >&5
$as_echo "$ac_ct_CC" >&6; }
else
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
fi
test -n "$ac_ct_CC" && break
done
if test "x$ac_ct_CC" = x; then
CC=""
else
case $cross_compiling:$ac_tool_warned in
yes:)
{ $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: using cross tools not prefixed with host triplet" >&5
$as_echo "$as_me: WARNING: using cross tools not prefixed with host triplet" >&2;}
ac_tool_warned=yes ;;
esac
CC=$ac_ct_CC
fi
fi
fi
test -z "$CC" && { { $as_echo "$as_me:${as_lineno-$LINENO}: error: in \`$ac_pwd':" >&5
$as_echo "$as_me: error: in \`$ac_pwd':" >&2;}
as_fn_error $? "no acceptable C compiler found in \$PATH
See \`config.log' for more details" "$LINENO" 5; }
# Provide some information about the compiler.
$as_echo "$as_me:${as_lineno-$LINENO}: checking for C compiler version" >&5
set X $ac_compile
ac_compiler=$2
for ac_option in --version -v -V -qversion; do
{ { ac_try="$ac_compiler $ac_option >&5"
case "(($ac_try" in
*\"* | *\`* | *\\*) ac_try_echo=\$ac_try;;
*) ac_try_echo=$ac_try;;
esac
eval ac_try_echo="\"\$as_me:${as_lineno-$LINENO}: $ac_try_echo\""
$as_echo "$ac_try_echo"; } >&5
(eval "$ac_compiler $ac_option >&5") 2>conftest.err
ac_status=$?
if test -s conftest.err; then
sed '10a\
... rest of stderr output deleted ...
10q' conftest.err >conftest.er1
cat conftest.er1 >&5
fi
rm -f conftest.er1 conftest.err
$as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5
test $ac_status = 0; }
done
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h. */
int
main ()
{
;
return 0;
}
_ACEOF
ac_clean_files_save=$ac_clean_files
ac_clean_files="$ac_clean_files a.out a.out.dSYM a.exe b.out"
# Try to create an executable without -o first, disregard a.out.
# It will help us diagnose broken compilers, and finding out an intuition
# of exeext.
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether the C compiler works" >&5
$as_echo_n "checking whether the C compiler works... " >&6; }
ac_link_default=`$as_echo "$ac_link" | sed 's/ -o *conftest[^ ]*//'`
# The possible output files:
ac_files="a.out conftest.exe conftest a.exe a_out.exe b.out conftest.*"
ac_rmfiles=
for ac_file in $ac_files
do
case $ac_file in
*.$ac_ext | *.xcoff | *.tds | *.d | *.pdb | *.xSYM | *.bb | *.bbg | *.map | *.inf | *.dSYM | *.o | *.obj ) ;;
* ) ac_rmfiles="$ac_rmfiles $ac_file";;
esac
done
rm -f $ac_rmfiles
if { { ac_try="$ac_link_default"
case "(($ac_try" in
*\"* | *\`* | *\\*) ac_try_echo=\$ac_try;;
*) ac_try_echo=$ac_try;;
esac
eval ac_try_echo="\"\$as_me:${as_lineno-$LINENO}: $ac_try_echo\""
$as_echo "$ac_try_echo"; } >&5
(eval "$ac_link_default") 2>&5
ac_status=$?
$as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5
test $ac_status = 0; }; then :
# Autoconf-2.13 could set the ac_cv_exeext variable to `no'.
# So ignore a value of `no', otherwise this would lead to `EXEEXT = no'
# in a Makefile. We should not override ac_cv_exeext if it was cached,
# so that the user can short-circuit this test for compilers unknown to
# Autoconf.
for ac_file in $ac_files ''
do
test -f "$ac_file" || continue
case $ac_file in
*.$ac_ext | *.xcoff | *.tds | *.d | *.pdb | *.xSYM | *.bb | *.bbg | *.map | *.inf | *.dSYM | *.o | *.obj )
;;
[ab].out )
# We found the default executable, but exeext='' is most
# certainly right.
break;;
*.* )
if test "${ac_cv_exeext+set}" = set && test "$ac_cv_exeext" != no;
then :; else
ac_cv_exeext=`expr "$ac_file" : '[^.]*\(\..*\)'`
fi
# We set ac_cv_exeext here because the later test for it is not
# safe: cross compilers may not add the suffix if given an `-o'
# argument, so we may need to know it at that point already.
# Even if this section looks crufty: it has the advantage of
# actually working.
break;;
* )
break;;
esac
done
test "$ac_cv_exeext" = no && ac_cv_exeext=
else
ac_file=''
fi
if test -z "$ac_file"; then :
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
$as_echo "$as_me: failed program was:" >&5
sed 's/^/| /' conftest.$ac_ext >&5
{ { $as_echo "$as_me:${as_lineno-$LINENO}: error: in \`$ac_pwd':" >&5
$as_echo "$as_me: error: in \`$ac_pwd':" >&2;}
as_fn_error 77 "C compiler cannot create executables
See \`config.log' for more details" "$LINENO" 5; }
else
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: yes" >&5
$as_echo "yes" >&6; }
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for C compiler default output file name" >&5
$as_echo_n "checking for C compiler default output file name... " >&6; }
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_file" >&5
$as_echo "$ac_file" >&6; }
ac_exeext=$ac_cv_exeext
rm -f -r a.out a.out.dSYM a.exe conftest$ac_cv_exeext b.out
ac_clean_files=$ac_clean_files_save
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for suffix of executables" >&5
$as_echo_n "checking for suffix of executables... " >&6; }
if { { ac_try="$ac_link"
case "(($ac_try" in
*\"* | *\`* | *\\*) ac_try_echo=\$ac_try;;
*) ac_try_echo=$ac_try;;
esac
eval ac_try_echo="\"\$as_me:${as_lineno-$LINENO}: $ac_try_echo\""
$as_echo "$ac_try_echo"; } >&5
(eval "$ac_link") 2>&5
ac_status=$?
$as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5
test $ac_status = 0; }; then :
# If both `conftest.exe' and `conftest' are `present' (well, observable)
# catch `conftest.exe'. For instance with Cygwin, `ls conftest' will
# work properly (i.e., refer to `conftest.exe'), while it won't with
# `rm'.
for ac_file in conftest.exe conftest conftest.*; do
test -f "$ac_file" || continue
case $ac_file in
*.$ac_ext | *.xcoff | *.tds | *.d | *.pdb | *.xSYM | *.bb | *.bbg | *.map | *.inf | *.dSYM | *.o | *.obj ) ;;
*.* ) ac_cv_exeext=`expr "$ac_file" : '[^.]*\(\..*\)'`
break;;
* ) break;;
esac
done
else
{ { $as_echo "$as_me:${as_lineno-$LINENO}: error: in \`$ac_pwd':" >&5
$as_echo "$as_me: error: in \`$ac_pwd':" >&2;}
as_fn_error $? "cannot compute suffix of executables: cannot compile and link
See \`config.log' for more details" "$LINENO" 5; }
fi
rm -f conftest conftest$ac_cv_exeext
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_exeext" >&5
$as_echo "$ac_cv_exeext" >&6; }
rm -f conftest.$ac_ext
EXEEXT=$ac_cv_exeext
ac_exeext=$EXEEXT
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h. */
#include
int
main ()
{
FILE *f = fopen ("conftest.out", "w");
return ferror (f) || fclose (f) != 0;
;
return 0;
}
_ACEOF
ac_clean_files="$ac_clean_files conftest.out"
# Check that the compiler produces executables we can run. If not, either
# the compiler is broken, or we cross compile.
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether we are cross compiling" >&5
$as_echo_n "checking whether we are cross compiling... " >&6; }
if test "$cross_compiling" != yes; then
{ { ac_try="$ac_link"
case "(($ac_try" in
*\"* | *\`* | *\\*) ac_try_echo=\$ac_try;;
*) ac_try_echo=$ac_try;;
esac
eval ac_try_echo="\"\$as_me:${as_lineno-$LINENO}: $ac_try_echo\""
$as_echo "$ac_try_echo"; } >&5
(eval "$ac_link") 2>&5
ac_status=$?
$as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5
test $ac_status = 0; }
if { ac_try='./conftest$ac_cv_exeext'
{ { case "(($ac_try" in
*\"* | *\`* | *\\*) ac_try_echo=\$ac_try;;
*) ac_try_echo=$ac_try;;
esac
eval ac_try_echo="\"\$as_me:${as_lineno-$LINENO}: $ac_try_echo\""
$as_echo "$ac_try_echo"; } >&5
(eval "$ac_try") 2>&5
ac_status=$?
$as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5
test $ac_status = 0; }; }; then
cross_compiling=no
else
if test "$cross_compiling" = maybe; then
cross_compiling=yes
else
{ { $as_echo "$as_me:${as_lineno-$LINENO}: error: in \`$ac_pwd':" >&5
$as_echo "$as_me: error: in \`$ac_pwd':" >&2;}
as_fn_error $? "cannot run C compiled programs.
If you meant to cross compile, use \`--host'.
See \`config.log' for more details" "$LINENO" 5; }
fi
fi
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $cross_compiling" >&5
$as_echo "$cross_compiling" >&6; }
rm -f conftest.$ac_ext conftest$ac_cv_exeext conftest.out
ac_clean_files=$ac_clean_files_save
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for suffix of object files" >&5
$as_echo_n "checking for suffix of object files... " >&6; }
if ${ac_cv_objext+:} false; then :
$as_echo_n "(cached) " >&6
else
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h. */
int
main ()
{
;
return 0;
}
_ACEOF
rm -f conftest.o conftest.obj
if { { ac_try="$ac_compile"
case "(($ac_try" in
*\"* | *\`* | *\\*) ac_try_echo=\$ac_try;;
*) ac_try_echo=$ac_try;;
esac
eval ac_try_echo="\"\$as_me:${as_lineno-$LINENO}: $ac_try_echo\""
$as_echo "$ac_try_echo"; } >&5
(eval "$ac_compile") 2>&5
ac_status=$?
$as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5
test $ac_status = 0; }; then :
for ac_file in conftest.o conftest.obj conftest.*; do
test -f "$ac_file" || continue;
case $ac_file in
*.$ac_ext | *.xcoff | *.tds | *.d | *.pdb | *.xSYM | *.bb | *.bbg | *.map | *.inf | *.dSYM ) ;;
*) ac_cv_objext=`expr "$ac_file" : '.*\.\(.*\)'`
break;;
esac
done
else
$as_echo "$as_me: failed program was:" >&5
sed 's/^/| /' conftest.$ac_ext >&5
{ { $as_echo "$as_me:${as_lineno-$LINENO}: error: in \`$ac_pwd':" >&5
$as_echo "$as_me: error: in \`$ac_pwd':" >&2;}
as_fn_error $? "cannot compute suffix of object files: cannot compile
See \`config.log' for more details" "$LINENO" 5; }
fi
rm -f conftest.$ac_cv_objext conftest.$ac_ext
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_objext" >&5
$as_echo "$ac_cv_objext" >&6; }
OBJEXT=$ac_cv_objext
ac_objext=$OBJEXT
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether we are using the GNU C compiler" >&5
$as_echo_n "checking whether we are using the GNU C compiler... " >&6; }
if ${ac_cv_c_compiler_gnu+:} false; then :
$as_echo_n "(cached) " >&6
else
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h. */
int
main ()
{
#ifndef __GNUC__
choke me
#endif
;
return 0;
}
_ACEOF
if ac_fn_c_try_compile "$LINENO"; then :
ac_compiler_gnu=yes
else
ac_compiler_gnu=no
fi
rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
ac_cv_c_compiler_gnu=$ac_compiler_gnu
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_c_compiler_gnu" >&5
$as_echo "$ac_cv_c_compiler_gnu" >&6; }
if test $ac_compiler_gnu = yes; then
GCC=yes
else
GCC=
fi
ac_test_CFLAGS=${CFLAGS+set}
ac_save_CFLAGS=$CFLAGS
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether $CC accepts -g" >&5
$as_echo_n "checking whether $CC accepts -g... " >&6; }
if ${ac_cv_prog_cc_g+:} false; then :
$as_echo_n "(cached) " >&6
else
ac_save_c_werror_flag=$ac_c_werror_flag
ac_c_werror_flag=yes
ac_cv_prog_cc_g=no
CFLAGS="-g"
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h. */
int
main ()
{
;
return 0;
}
_ACEOF
if ac_fn_c_try_compile "$LINENO"; then :
ac_cv_prog_cc_g=yes
else
CFLAGS=""
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h. */
int
main ()
{
;
return 0;
}
_ACEOF
if ac_fn_c_try_compile "$LINENO"; then :
else
ac_c_werror_flag=$ac_save_c_werror_flag
CFLAGS="-g"
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h. */
int
main ()
{
;
return 0;
}
_ACEOF
if ac_fn_c_try_compile "$LINENO"; then :
ac_cv_prog_cc_g=yes
fi
rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
fi
rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
fi
rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
ac_c_werror_flag=$ac_save_c_werror_flag
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_prog_cc_g" >&5
$as_echo "$ac_cv_prog_cc_g" >&6; }
if test "$ac_test_CFLAGS" = set; then
CFLAGS=$ac_save_CFLAGS
elif test $ac_cv_prog_cc_g = yes; then
if test "$GCC" = yes; then
CFLAGS="-g -O2"
else
CFLAGS="-g"
fi
else
if test "$GCC" = yes; then
CFLAGS="-O2"
else
CFLAGS=
fi
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $CC option to accept ISO C89" >&5
$as_echo_n "checking for $CC option to accept ISO C89... " >&6; }
if ${ac_cv_prog_cc_c89+:} false; then :
$as_echo_n "(cached) " >&6
else
ac_cv_prog_cc_c89=no
ac_save_CC=$CC
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h. */
#include
#include
struct stat;
/* Most of the following tests are stolen from RCS 5.7's src/conf.sh. */
struct buf { int x; };
FILE * (*rcsopen) (struct buf *, struct stat *, int);
static char *e (p, i)
char **p;
int i;
{
return p[i];
}
static char *f (char * (*g) (char **, int), char **p, ...)
{
char *s;
va_list v;
va_start (v,p);
s = g (p, va_arg (v,int));
va_end (v);
return s;
}
/* OSF 4.0 Compaq cc is some sort of almost-ANSI by default. It has
function prototypes and stuff, but not '\xHH' hex character constants.
These don't provoke an error unfortunately, instead are silently treated
as 'x'. The following induces an error, until -std is added to get
proper ANSI mode. Curiously '\x00'!='x' always comes out true, for an
array size at least. It's necessary to write '\x00'==0 to get something
that's true only with -std. */
int osf4_cc_array ['\x00' == 0 ? 1 : -1];
/* IBM C 6 for AIX is almost-ANSI by default, but it replaces macro parameters
inside strings and character constants. */
#define FOO(x) 'x'
int xlc6_cc_array[FOO(a) == 'x' ? 1 : -1];
int test (int i, double x);
struct s1 {int (*f) (int a);};
struct s2 {int (*f) (double a);};
int pairnames (int, char **, FILE *(*)(struct buf *, struct stat *, int), int, int);
int argc;
char **argv;
int
main ()
{
return f (e, argv, 0) != argv[0] || f (e, argv, 1) != argv[1];
;
return 0;
}
_ACEOF
for ac_arg in '' -qlanglvl=extc89 -qlanglvl=ansi -std \
-Ae "-Aa -D_HPUX_SOURCE" "-Xc -D__EXTENSIONS__"
do
CC="$ac_save_CC $ac_arg"
if ac_fn_c_try_compile "$LINENO"; then :
ac_cv_prog_cc_c89=$ac_arg
fi
rm -f core conftest.err conftest.$ac_objext
test "x$ac_cv_prog_cc_c89" != "xno" && break
done
rm -f conftest.$ac_ext
CC=$ac_save_CC
fi
# AC_CACHE_VAL
case "x$ac_cv_prog_cc_c89" in
x)
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: none needed" >&5
$as_echo "none needed" >&6; } ;;
xno)
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: unsupported" >&5
$as_echo "unsupported" >&6; } ;;
*)
CC="$CC $ac_cv_prog_cc_c89"
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_prog_cc_c89" >&5
$as_echo "$ac_cv_prog_cc_c89" >&6; } ;;
esac
if test "x$ac_cv_prog_cc_c89" != xno; then :
fi
ac_ext=c
ac_cpp='$CPP $CPPFLAGS'
ac_compile='$CC -c $CFLAGS $CPPFLAGS conftest.$ac_ext >&5'
ac_link='$CC -o conftest$ac_exeext $CFLAGS $CPPFLAGS $LDFLAGS conftest.$ac_ext $LIBS >&5'
ac_compiler_gnu=$ac_cv_c_compiler_gnu
DEPDIR="${am__leading_dot}deps"
ac_config_commands="$ac_config_commands depfiles"
am_make=${MAKE-make}
cat > confinc << 'END'
am__doit:
@echo this is the am__doit target
.PHONY: am__doit
END
# If we don't find an include directive, just comment out the code.
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for style of include used by $am_make" >&5
$as_echo_n "checking for style of include used by $am_make... " >&6; }
am__include="#"
am__quote=
_am_result=none
# First try GNU make style include.
echo "include confinc" > confmf
# Ignore all kinds of additional output from `make'.
case `$am_make -s -f confmf 2> /dev/null` in #(
*the\ am__doit\ target*)
am__include=include
am__quote=
_am_result=GNU
;;
esac
# Now try BSD make style include.
if test "$am__include" = "#"; then
echo '.include "confinc"' > confmf
case `$am_make -s -f confmf 2> /dev/null` in #(
*the\ am__doit\ target*)
am__include=.include
am__quote="\""
_am_result=BSD
;;
esac
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $_am_result" >&5
$as_echo "$_am_result" >&6; }
rm -f confinc confmf
# Check whether --enable-dependency-tracking was given.
if test "${enable_dependency_tracking+set}" = set; then :
enableval=$enable_dependency_tracking;
fi
if test "x$enable_dependency_tracking" != xno; then
am_depcomp="$ac_aux_dir/depcomp"
AMDEPBACKSLASH='\'
am__nodep='_no'
fi
if test "x$enable_dependency_tracking" != xno; then
AMDEP_TRUE=
AMDEP_FALSE='#'
else
AMDEP_TRUE='#'
AMDEP_FALSE=
fi
depcc="$CC" am_compiler_list=
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking dependency style of $depcc" >&5
$as_echo_n "checking dependency style of $depcc... " >&6; }
if ${am_cv_CC_dependencies_compiler_type+:} false; then :
$as_echo_n "(cached) " >&6
else
if test -z "$AMDEP_TRUE" && test -f "$am_depcomp"; then
# We make a subdir and do the tests there. Otherwise we can end up
# making bogus files that we don't know about and never remove. For
# instance it was reported that on HP-UX the gcc test will end up
# making a dummy file named `D' -- because `-MD' means `put the output
# in D'.
rm -rf conftest.dir
mkdir conftest.dir
# Copy depcomp to subdir because otherwise we won't find it if we're
# using a relative directory.
cp "$am_depcomp" conftest.dir
cd conftest.dir
# We will build objects and dependencies in a subdirectory because
# it helps to detect inapplicable dependency modes. For instance
# both Tru64's cc and ICC support -MD to output dependencies as a
# side effect of compilation, but ICC will put the dependencies in
# the current directory while Tru64 will put them in the object
# directory.
mkdir sub
am_cv_CC_dependencies_compiler_type=none
if test "$am_compiler_list" = ""; then
am_compiler_list=`sed -n 's/^#*\([a-zA-Z0-9]*\))$/\1/p' < ./depcomp`
fi
am__universal=false
case " $depcc " in #(
*\ -arch\ *\ -arch\ *) am__universal=true ;;
esac
for depmode in $am_compiler_list; do
# Setup a source with many dependencies, because some compilers
# like to wrap large dependency lists on column 80 (with \), and
# we should not choose a depcomp mode which is confused by this.
#
# We need to recreate these files for each test, as the compiler may
# overwrite some of them when testing with obscure command lines.
# This happens at least with the AIX C compiler.
: > sub/conftest.c
for i in 1 2 3 4 5 6; do
echo '#include "conftst'$i'.h"' >> sub/conftest.c
# Using `: > sub/conftst$i.h' creates only sub/conftst1.h with
# Solaris 8's {/usr,}/bin/sh.
touch sub/conftst$i.h
done
echo "${am__include} ${am__quote}sub/conftest.Po${am__quote}" > confmf
# We check with `-c' and `-o' for the sake of the "dashmstdout"
# mode. It turns out that the SunPro C++ compiler does not properly
# handle `-M -o', and we need to detect this. Also, some Intel
# versions had trouble with output in subdirs
am__obj=sub/conftest.${OBJEXT-o}
am__minus_obj="-o $am__obj"
case $depmode in
gcc)
# This depmode causes a compiler race in universal mode.
test "$am__universal" = false || continue
;;
nosideeffect)
# after this tag, mechanisms are not by side-effect, so they'll
# only be used when explicitly requested
if test "x$enable_dependency_tracking" = xyes; then
continue
else
break
fi
;;
msvc7 | msvc7msys | msvisualcpp | msvcmsys)
# This compiler won't grok `-c -o', but also, the minuso test has
# not run yet. These depmodes are late enough in the game, and
# so weak that their functioning should not be impacted.
am__obj=conftest.${OBJEXT-o}
am__minus_obj=
;;
none) break ;;
esac
if depmode=$depmode \
source=sub/conftest.c object=$am__obj \
depfile=sub/conftest.Po tmpdepfile=sub/conftest.TPo \
$SHELL ./depcomp $depcc -c $am__minus_obj sub/conftest.c \
>/dev/null 2>conftest.err &&
grep sub/conftst1.h sub/conftest.Po > /dev/null 2>&1 &&
grep sub/conftst6.h sub/conftest.Po > /dev/null 2>&1 &&
grep $am__obj sub/conftest.Po > /dev/null 2>&1 &&
${MAKE-make} -s -f confmf > /dev/null 2>&1; then
# icc doesn't choke on unknown options, it will just issue warnings
# or remarks (even with -Werror). So we grep stderr for any message
# that says an option was ignored or not supported.
# When given -MP, icc 7.0 and 7.1 complain thusly:
# icc: Command line warning: ignoring option '-M'; no argument required
# The diagnosis changed in icc 8.0:
# icc: Command line remark: option '-MP' not supported
if (grep 'ignoring option' conftest.err ||
grep 'not supported' conftest.err) >/dev/null 2>&1; then :; else
am_cv_CC_dependencies_compiler_type=$depmode
break
fi
fi
done
cd ..
rm -rf conftest.dir
else
am_cv_CC_dependencies_compiler_type=none
fi
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $am_cv_CC_dependencies_compiler_type" >&5
$as_echo "$am_cv_CC_dependencies_compiler_type" >&6; }
CCDEPMODE=depmode=$am_cv_CC_dependencies_compiler_type
if
test "x$enable_dependency_tracking" != xno \
&& test "$am_cv_CC_dependencies_compiler_type" = gcc3; then
am__fastdepCC_TRUE=
am__fastdepCC_FALSE='#'
else
am__fastdepCC_TRUE='#'
am__fastdepCC_FALSE=
fi
# Find any Python interpreter.
if test -z "$PYTHON"; then
for ac_prog in python python2 python3 python3.2 python3.1 python3.0 python2.7 python2.6 python2.5 python2.4 python2.3 python2.2 python2.1 python2.0
do
# Extract the first word of "$ac_prog", so it can be a program name with args.
set dummy $ac_prog; ac_word=$2
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5
$as_echo_n "checking for $ac_word... " >&6; }
if ${ac_cv_path_PYTHON+:} false; then :
$as_echo_n "(cached) " >&6
else
case $PYTHON in
[\\/]* | ?:[\\/]*)
ac_cv_path_PYTHON="$PYTHON" # Let the user override the test with a path.
;;
*)
as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
for as_dir in $PATH
do
IFS=$as_save_IFS
test -z "$as_dir" && as_dir=.
for ac_exec_ext in '' $ac_executable_extensions; do
if as_fn_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
ac_cv_path_PYTHON="$as_dir/$ac_word$ac_exec_ext"
$as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5
break 2
fi
done
done
IFS=$as_save_IFS
;;
esac
fi
PYTHON=$ac_cv_path_PYTHON
if test -n "$PYTHON"; then
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $PYTHON" >&5
$as_echo "$PYTHON" >&6; }
else
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
fi
test -n "$PYTHON" && break
done
test -n "$PYTHON" || PYTHON=":"
fi
am_display_PYTHON=python
if test "$PYTHON" = :; then
as_fn_error $? "no suitable Python interpreter found" "$LINENO" 5
else
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $am_display_PYTHON version" >&5
$as_echo_n "checking for $am_display_PYTHON version... " >&6; }
if ${am_cv_python_version+:} false; then :
$as_echo_n "(cached) " >&6
else
am_cv_python_version=`$PYTHON -c "import sys; sys.stdout.write(sys.version[:3])"`
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $am_cv_python_version" >&5
$as_echo "$am_cv_python_version" >&6; }
PYTHON_VERSION=$am_cv_python_version
PYTHON_PREFIX='${prefix}'
PYTHON_EXEC_PREFIX='${exec_prefix}'
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $am_display_PYTHON platform" >&5
$as_echo_n "checking for $am_display_PYTHON platform... " >&6; }
if ${am_cv_python_platform+:} false; then :
$as_echo_n "(cached) " >&6
else
am_cv_python_platform=`$PYTHON -c "import sys; sys.stdout.write(sys.platform)"`
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $am_cv_python_platform" >&5
$as_echo "$am_cv_python_platform" >&6; }
PYTHON_PLATFORM=$am_cv_python_platform
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $am_display_PYTHON script directory" >&5
$as_echo_n "checking for $am_display_PYTHON script directory... " >&6; }
if ${am_cv_python_pythondir+:} false; then :
$as_echo_n "(cached) " >&6
else
if test "x$prefix" = xNONE
then
am_py_prefix=$ac_default_prefix
else
am_py_prefix=$prefix
fi
am_cv_python_pythondir=`$PYTHON -c "import sys; from distutils import sysconfig; sys.stdout.write(sysconfig.get_python_lib(0,0,prefix='$am_py_prefix'))" 2>/dev/null`
case $am_cv_python_pythondir in
$am_py_prefix*)
am__strip_prefix=`echo "$am_py_prefix" | sed 's|.|.|g'`
am_cv_python_pythondir=`echo "$am_cv_python_pythondir" | sed "s,^$am__strip_prefix,$PYTHON_PREFIX,"`
;;
*)
case $am_py_prefix in
/usr|/System*) ;;
*)
am_cv_python_pythondir=$PYTHON_PREFIX/lib/python$PYTHON_VERSION/site-packages
;;
esac
;;
esac
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $am_cv_python_pythondir" >&5
$as_echo "$am_cv_python_pythondir" >&6; }
pythondir=$am_cv_python_pythondir
pkgpythondir=\${pythondir}/$PACKAGE
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $am_display_PYTHON extension module directory" >&5
$as_echo_n "checking for $am_display_PYTHON extension module directory... " >&6; }
if ${am_cv_python_pyexecdir+:} false; then :
$as_echo_n "(cached) " >&6
else
if test "x$exec_prefix" = xNONE
then
am_py_exec_prefix=$am_py_prefix
else
am_py_exec_prefix=$exec_prefix
fi
am_cv_python_pyexecdir=`$PYTHON -c "import sys; from distutils import sysconfig; sys.stdout.write(sysconfig.get_python_lib(1,0,prefix='$am_py_exec_prefix'))" 2>/dev/null`
case $am_cv_python_pyexecdir in
$am_py_exec_prefix*)
am__strip_prefix=`echo "$am_py_exec_prefix" | sed 's|.|.|g'`
am_cv_python_pyexecdir=`echo "$am_cv_python_pyexecdir" | sed "s,^$am__strip_prefix,$PYTHON_EXEC_PREFIX,"`
;;
*)
case $am_py_exec_prefix in
/usr|/System*) ;;
*)
am_cv_python_pyexecdir=$PYTHON_EXEC_PREFIX/lib/python$PYTHON_VERSION/site-packages
;;
esac
;;
esac
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $am_cv_python_pyexecdir" >&5
$as_echo "$am_cv_python_pyexecdir" >&6; }
pyexecdir=$am_cv_python_pyexecdir
pkgpyexecdir=\${pyexecdir}/$PACKAGE
fi
if test "x$ac_cv_env_PKG_CONFIG_set" != "xset"; then
if test -n "$ac_tool_prefix"; then
# Extract the first word of "${ac_tool_prefix}pkg-config", so it can be a program name with args.
set dummy ${ac_tool_prefix}pkg-config; ac_word=$2
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5
$as_echo_n "checking for $ac_word... " >&6; }
if ${ac_cv_path_PKG_CONFIG+:} false; then :
$as_echo_n "(cached) " >&6
else
case $PKG_CONFIG in
[\\/]* | ?:[\\/]*)
ac_cv_path_PKG_CONFIG="$PKG_CONFIG" # Let the user override the test with a path.
;;
*)
as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
for as_dir in $PATH
do
IFS=$as_save_IFS
test -z "$as_dir" && as_dir=.
for ac_exec_ext in '' $ac_executable_extensions; do
if as_fn_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
ac_cv_path_PKG_CONFIG="$as_dir/$ac_word$ac_exec_ext"
$as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5
break 2
fi
done
done
IFS=$as_save_IFS
;;
esac
fi
PKG_CONFIG=$ac_cv_path_PKG_CONFIG
if test -n "$PKG_CONFIG"; then
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $PKG_CONFIG" >&5
$as_echo "$PKG_CONFIG" >&6; }
else
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
fi
fi
if test -z "$ac_cv_path_PKG_CONFIG"; then
ac_pt_PKG_CONFIG=$PKG_CONFIG
# Extract the first word of "pkg-config", so it can be a program name with args.
set dummy pkg-config; ac_word=$2
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5
$as_echo_n "checking for $ac_word... " >&6; }
if ${ac_cv_path_ac_pt_PKG_CONFIG+:} false; then :
$as_echo_n "(cached) " >&6
else
case $ac_pt_PKG_CONFIG in
[\\/]* | ?:[\\/]*)
ac_cv_path_ac_pt_PKG_CONFIG="$ac_pt_PKG_CONFIG" # Let the user override the test with a path.
;;
*)
as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
for as_dir in $PATH
do
IFS=$as_save_IFS
test -z "$as_dir" && as_dir=.
for ac_exec_ext in '' $ac_executable_extensions; do
if as_fn_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
ac_cv_path_ac_pt_PKG_CONFIG="$as_dir/$ac_word$ac_exec_ext"
$as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5
break 2
fi
done
done
IFS=$as_save_IFS
;;
esac
fi
ac_pt_PKG_CONFIG=$ac_cv_path_ac_pt_PKG_CONFIG
if test -n "$ac_pt_PKG_CONFIG"; then
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_pt_PKG_CONFIG" >&5
$as_echo "$ac_pt_PKG_CONFIG" >&6; }
else
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
fi
if test "x$ac_pt_PKG_CONFIG" = x; then
PKG_CONFIG=""
else
case $cross_compiling:$ac_tool_warned in
yes:)
{ $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: using cross tools not prefixed with host triplet" >&5
$as_echo "$as_me: WARNING: using cross tools not prefixed with host triplet" >&2;}
ac_tool_warned=yes ;;
esac
PKG_CONFIG=$ac_pt_PKG_CONFIG
fi
else
PKG_CONFIG="$ac_cv_path_PKG_CONFIG"
fi
fi
if test -n "$PKG_CONFIG"; then
_pkg_min_version=0.9.0
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking pkg-config is at least version $_pkg_min_version" >&5
$as_echo_n "checking pkg-config is at least version $_pkg_min_version... " >&6; }
if $PKG_CONFIG --atleast-pkgconfig-version $_pkg_min_version; then
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: yes" >&5
$as_echo "yes" >&6; }
else
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
PKG_CONFIG=""
fi
fi
# i18n
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether NLS is requested" >&5
$as_echo_n "checking whether NLS is requested... " >&6; }
# Check whether --enable-nls was given.
if test "${enable_nls+set}" = set; then :
enableval=$enable_nls; USE_NLS=$enableval
else
USE_NLS=yes
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $USE_NLS" >&5
$as_echo "$USE_NLS" >&6; }
case "$am__api_version" in
1.01234)
as_fn_error $? "Automake 1.5 or newer is required to use intltool" "$LINENO" 5
;;
*)
;;
esac
INTLTOOL_REQUIRED_VERSION_AS_INT=`echo 0.40.0 | awk -F. '{ print $ 1 * 1000 + $ 2 * 100 + $ 3; }'`
INTLTOOL_APPLIED_VERSION=`intltool-update --version | head -1 | cut -d" " -f3`
INTLTOOL_APPLIED_VERSION_AS_INT=`echo $INTLTOOL_APPLIED_VERSION | awk -F. '{ print $ 1 * 1000 + $ 2 * 100 + $ 3; }'`
if test -n "0.40.0"; then
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for intltool >= 0.40.0" >&5
$as_echo_n "checking for intltool >= 0.40.0... " >&6; }
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $INTLTOOL_APPLIED_VERSION found" >&5
$as_echo "$INTLTOOL_APPLIED_VERSION found" >&6; }
test "$INTLTOOL_APPLIED_VERSION_AS_INT" -ge "$INTLTOOL_REQUIRED_VERSION_AS_INT" ||
as_fn_error $? "Your intltool is too old. You need intltool 0.40.0 or later." "$LINENO" 5
fi
# Extract the first word of "intltool-update", so it can be a program name with args.
set dummy intltool-update; ac_word=$2
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5
$as_echo_n "checking for $ac_word... " >&6; }
if ${ac_cv_path_INTLTOOL_UPDATE+:} false; then :
$as_echo_n "(cached) " >&6
else
case $INTLTOOL_UPDATE in
[\\/]* | ?:[\\/]*)
ac_cv_path_INTLTOOL_UPDATE="$INTLTOOL_UPDATE" # Let the user override the test with a path.
;;
*)
as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
for as_dir in $PATH
do
IFS=$as_save_IFS
test -z "$as_dir" && as_dir=.
for ac_exec_ext in '' $ac_executable_extensions; do
if as_fn_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
ac_cv_path_INTLTOOL_UPDATE="$as_dir/$ac_word$ac_exec_ext"
$as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5
break 2
fi
done
done
IFS=$as_save_IFS
;;
esac
fi
INTLTOOL_UPDATE=$ac_cv_path_INTLTOOL_UPDATE
if test -n "$INTLTOOL_UPDATE"; then
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $INTLTOOL_UPDATE" >&5
$as_echo "$INTLTOOL_UPDATE" >&6; }
else
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
fi
# Extract the first word of "intltool-merge", so it can be a program name with args.
set dummy intltool-merge; ac_word=$2
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5
$as_echo_n "checking for $ac_word... " >&6; }
if ${ac_cv_path_INTLTOOL_MERGE+:} false; then :
$as_echo_n "(cached) " >&6
else
case $INTLTOOL_MERGE in
[\\/]* | ?:[\\/]*)
ac_cv_path_INTLTOOL_MERGE="$INTLTOOL_MERGE" # Let the user override the test with a path.
;;
*)
as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
for as_dir in $PATH
do
IFS=$as_save_IFS
test -z "$as_dir" && as_dir=.
for ac_exec_ext in '' $ac_executable_extensions; do
if as_fn_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
ac_cv_path_INTLTOOL_MERGE="$as_dir/$ac_word$ac_exec_ext"
$as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5
break 2
fi
done
done
IFS=$as_save_IFS
;;
esac
fi
INTLTOOL_MERGE=$ac_cv_path_INTLTOOL_MERGE
if test -n "$INTLTOOL_MERGE"; then
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $INTLTOOL_MERGE" >&5
$as_echo "$INTLTOOL_MERGE" >&6; }
else
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
fi
# Extract the first word of "intltool-extract", so it can be a program name with args.
set dummy intltool-extract; ac_word=$2
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5
$as_echo_n "checking for $ac_word... " >&6; }
if ${ac_cv_path_INTLTOOL_EXTRACT+:} false; then :
$as_echo_n "(cached) " >&6
else
case $INTLTOOL_EXTRACT in
[\\/]* | ?:[\\/]*)
ac_cv_path_INTLTOOL_EXTRACT="$INTLTOOL_EXTRACT" # Let the user override the test with a path.
;;
*)
as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
for as_dir in $PATH
do
IFS=$as_save_IFS
test -z "$as_dir" && as_dir=.
for ac_exec_ext in '' $ac_executable_extensions; do
if as_fn_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
ac_cv_path_INTLTOOL_EXTRACT="$as_dir/$ac_word$ac_exec_ext"
$as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5
break 2
fi
done
done
IFS=$as_save_IFS
;;
esac
fi
INTLTOOL_EXTRACT=$ac_cv_path_INTLTOOL_EXTRACT
if test -n "$INTLTOOL_EXTRACT"; then
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $INTLTOOL_EXTRACT" >&5
$as_echo "$INTLTOOL_EXTRACT" >&6; }
else
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
fi
if test -z "$INTLTOOL_UPDATE" -o -z "$INTLTOOL_MERGE" -o -z "$INTLTOOL_EXTRACT"; then
as_fn_error $? "The intltool scripts were not found. Please install intltool." "$LINENO" 5
fi
if test -z "$AM_DEFAULT_VERBOSITY"; then
AM_DEFAULT_VERBOSITY=1
fi
INTLTOOL_V_MERGE='$(INTLTOOL__v_MERGE_$(V))'
INTLTOOL__v_MERGE_='$(INTLTOOL__v_MERGE_$(AM_DEFAULT_VERBOSITY))'
INTLTOOL__v_MERGE_0='@echo " ITMRG " $@;'
INTLTOOL_V_MERGE_OPTIONS='$(intltool__v_merge_options_$(V))'
intltool__v_merge_options_='$(intltool__v_merge_options_$(AM_DEFAULT_VERBOSITY))'
intltool__v_merge_options_0='-q'
INTLTOOL_DESKTOP_RULE='%.desktop: %.desktop.in $(INTLTOOL_MERGE) $(wildcard $(top_srcdir)/po/*.po) ; $(INTLTOOL_V_MERGE)LC_ALL=C $(INTLTOOL_MERGE) $(INTLTOOL_V_MERGE_OPTIONS) -d -u -c $(top_builddir)/po/.intltool-merge-cache $(top_srcdir)/po $< $@'
INTLTOOL_DIRECTORY_RULE='%.directory: %.directory.in $(INTLTOOL_MERGE) $(wildcard $(top_srcdir)/po/*.po) ; $(INTLTOOL_V_MERGE)LC_ALL=C $(INTLTOOL_MERGE) $(INTLTOOL_V_MERGE_OPTIONS) -d -u -c $(top_builddir)/po/.intltool-merge-cache $(top_srcdir)/po $< $@'
INTLTOOL_KEYS_RULE='%.keys: %.keys.in $(INTLTOOL_MERGE) $(wildcard $(top_srcdir)/po/*.po) ; $(INTLTOOL_V_MERGE)LC_ALL=C $(INTLTOOL_MERGE) $(INTLTOOL_V_MERGE_OPTIONS) -k -u -c $(top_builddir)/po/.intltool-merge-cache $(top_srcdir)/po $< $@'
INTLTOOL_PROP_RULE='%.prop: %.prop.in $(INTLTOOL_MERGE) $(wildcard $(top_srcdir)/po/*.po) ; $(INTLTOOL_V_MERGE)LC_ALL=C $(INTLTOOL_MERGE) $(INTLTOOL_V_MERGE_OPTIONS) -d -u -c $(top_builddir)/po/.intltool-merge-cache $(top_srcdir)/po $< $@'
INTLTOOL_OAF_RULE='%.oaf: %.oaf.in $(INTLTOOL_MERGE) $(wildcard $(top_srcdir)/po/*.po) ; $(INTLTOOL_V_MERGE)LC_ALL=C $(INTLTOOL_MERGE) $(INTLTOOL_V_MERGE_OPTIONS) -o -p $(top_srcdir)/po $< $@'
INTLTOOL_PONG_RULE='%.pong: %.pong.in $(INTLTOOL_MERGE) $(wildcard $(top_srcdir)/po/*.po) ; $(INTLTOOL_V_MERGE)LC_ALL=C $(INTLTOOL_MERGE) $(INTLTOOL_V_MERGE_OPTIONS) -x -u -c $(top_builddir)/po/.intltool-merge-cache $(top_srcdir)/po $< $@'
INTLTOOL_SERVER_RULE='%.server: %.server.in $(INTLTOOL_MERGE) $(wildcard $(top_srcdir)/po/*.po) ; $(INTLTOOL_V_MERGE)LC_ALL=C $(INTLTOOL_MERGE) $(INTLTOOL_V_MERGE_OPTIONS) -o -u -c $(top_builddir)/po/.intltool-merge-cache $(top_srcdir)/po $< $@'
INTLTOOL_SHEET_RULE='%.sheet: %.sheet.in $(INTLTOOL_MERGE) $(wildcard $(top_srcdir)/po/*.po) ; $(INTLTOOL_V_MERGE)LC_ALL=C $(INTLTOOL_MERGE) $(INTLTOOL_V_MERGE_OPTIONS) -x -u -c $(top_builddir)/po/.intltool-merge-cache $(top_srcdir)/po $< $@'
INTLTOOL_SOUNDLIST_RULE='%.soundlist: %.soundlist.in $(INTLTOOL_MERGE) $(wildcard $(top_srcdir)/po/*.po) ; $(INTLTOOL_V_MERGE)LC_ALL=C $(INTLTOOL_MERGE) $(INTLTOOL_V_MERGE_OPTIONS) -d -u -c $(top_builddir)/po/.intltool-merge-cache $(top_srcdir)/po $< $@'
INTLTOOL_UI_RULE='%.ui: %.ui.in $(INTLTOOL_MERGE) $(wildcard $(top_srcdir)/po/*.po) ; $(INTLTOOL_V_MERGE)LC_ALL=C $(INTLTOOL_MERGE) $(INTLTOOL_V_MERGE_OPTIONS) -x -u -c $(top_builddir)/po/.intltool-merge-cache $(top_srcdir)/po $< $@'
INTLTOOL_XML_RULE='%.xml: %.xml.in $(INTLTOOL_MERGE) $(wildcard $(top_srcdir)/po/*.po) ; $(INTLTOOL_V_MERGE)LC_ALL=C $(INTLTOOL_MERGE) $(INTLTOOL_V_MERGE_OPTIONS) -x -u -c $(top_builddir)/po/.intltool-merge-cache $(top_srcdir)/po $< $@'
if test "$INTLTOOL_APPLIED_VERSION_AS_INT" -ge 5000; then
INTLTOOL_XML_NOMERGE_RULE='%.xml: %.xml.in $(INTLTOOL_MERGE) ; $(INTLTOOL_V_MERGE)LC_ALL=C $(INTLTOOL_MERGE) $(INTLTOOL_V_MERGE_OPTIONS) -x -u --no-translations $< $@'
else
INTLTOOL_XML_NOMERGE_RULE='%.xml: %.xml.in $(INTLTOOL_MERGE) ; $(INTLTOOL_V_MERGE)_it_tmp_dir=tmp.intltool.$$RANDOM && mkdir $$_it_tmp_dir && LC_ALL=C $(INTLTOOL_MERGE) $(INTLTOOL_V_MERGE_OPTIONS) -x -u $$_it_tmp_dir $< $@ && rmdir $$_it_tmp_dir'
fi
INTLTOOL_XAM_RULE='%.xam: %.xml.in $(INTLTOOL_MERGE) $(wildcard $(top_srcdir)/po/*.po) ; $(INTLTOOL_V_MERGE)LC_ALL=C $(INTLTOOL_MERGE) $(INTLTOOL_V_MERGE_OPTIONS) -x -u -c $(top_builddir)/po/.intltool-merge-cache $(top_srcdir)/po $< $@'
INTLTOOL_KBD_RULE='%.kbd: %.kbd.in $(INTLTOOL_MERGE) $(wildcard $(top_srcdir)/po/*.po) ; $(INTLTOOL_V_MERGE)LC_ALL=C $(INTLTOOL_MERGE) $(INTLTOOL_V_MERGE_OPTIONS) -x -u -m -c $(top_builddir)/po/.intltool-merge-cache $(top_srcdir)/po $< $@'
INTLTOOL_CAVES_RULE='%.caves: %.caves.in $(INTLTOOL_MERGE) $(wildcard $(top_srcdir)/po/*.po) ; $(INTLTOOL_V_MERGE)LC_ALL=C $(INTLTOOL_MERGE) $(INTLTOOL_V_MERGE_OPTIONS) -d -u -c $(top_builddir)/po/.intltool-merge-cache $(top_srcdir)/po $< $@'
INTLTOOL_SCHEMAS_RULE='%.schemas: %.schemas.in $(INTLTOOL_MERGE) $(wildcard $(top_srcdir)/po/*.po) ; $(INTLTOOL_V_MERGE)LC_ALL=C $(INTLTOOL_MERGE) $(INTLTOOL_V_MERGE_OPTIONS) -s -u -c $(top_builddir)/po/.intltool-merge-cache $(top_srcdir)/po $< $@'
INTLTOOL_THEME_RULE='%.theme: %.theme.in $(INTLTOOL_MERGE) $(wildcard $(top_srcdir)/po/*.po) ; $(INTLTOOL_V_MERGE)LC_ALL=C $(INTLTOOL_MERGE) $(INTLTOOL_V_MERGE_OPTIONS) -d -u -c $(top_builddir)/po/.intltool-merge-cache $(top_srcdir)/po $< $@'
INTLTOOL_SERVICE_RULE='%.service: %.service.in $(INTLTOOL_MERGE) $(wildcard $(top_srcdir)/po/*.po) ; $(INTLTOOL_V_MERGE)LC_ALL=C $(INTLTOOL_MERGE) $(INTLTOOL_V_MERGE_OPTIONS) -d -u -c $(top_builddir)/po/.intltool-merge-cache $(top_srcdir)/po $< $@'
INTLTOOL_POLICY_RULE='%.policy: %.policy.in $(INTLTOOL_MERGE) $(wildcard $(top_srcdir)/po/*.po) ; $(INTLTOOL_V_MERGE)LC_ALL=C $(INTLTOOL_MERGE) $(INTLTOOL_V_MERGE_OPTIONS) -x -u -c $(top_builddir)/po/.intltool-merge-cache $(top_srcdir)/po $< $@'
# Check the gettext tools to make sure they are GNU
# Extract the first word of "xgettext", so it can be a program name with args.
set dummy xgettext; ac_word=$2
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5
$as_echo_n "checking for $ac_word... " >&6; }
if ${ac_cv_path_XGETTEXT+:} false; then :
$as_echo_n "(cached) " >&6
else
case $XGETTEXT in
[\\/]* | ?:[\\/]*)
ac_cv_path_XGETTEXT="$XGETTEXT" # Let the user override the test with a path.
;;
*)
as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
for as_dir in $PATH
do
IFS=$as_save_IFS
test -z "$as_dir" && as_dir=.
for ac_exec_ext in '' $ac_executable_extensions; do
if as_fn_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
ac_cv_path_XGETTEXT="$as_dir/$ac_word$ac_exec_ext"
$as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5
break 2
fi
done
done
IFS=$as_save_IFS
;;
esac
fi
XGETTEXT=$ac_cv_path_XGETTEXT
if test -n "$XGETTEXT"; then
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $XGETTEXT" >&5
$as_echo "$XGETTEXT" >&6; }
else
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
fi
# Extract the first word of "msgmerge", so it can be a program name with args.
set dummy msgmerge; ac_word=$2
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5
$as_echo_n "checking for $ac_word... " >&6; }
if ${ac_cv_path_MSGMERGE+:} false; then :
$as_echo_n "(cached) " >&6
else
case $MSGMERGE in
[\\/]* | ?:[\\/]*)
ac_cv_path_MSGMERGE="$MSGMERGE" # Let the user override the test with a path.
;;
*)
as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
for as_dir in $PATH
do
IFS=$as_save_IFS
test -z "$as_dir" && as_dir=.
for ac_exec_ext in '' $ac_executable_extensions; do
if as_fn_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
ac_cv_path_MSGMERGE="$as_dir/$ac_word$ac_exec_ext"
$as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5
break 2
fi
done
done
IFS=$as_save_IFS
;;
esac
fi
MSGMERGE=$ac_cv_path_MSGMERGE
if test -n "$MSGMERGE"; then
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $MSGMERGE" >&5
$as_echo "$MSGMERGE" >&6; }
else
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
fi
# Extract the first word of "msgfmt", so it can be a program name with args.
set dummy msgfmt; ac_word=$2
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5
$as_echo_n "checking for $ac_word... " >&6; }
if ${ac_cv_path_MSGFMT+:} false; then :
$as_echo_n "(cached) " >&6
else
case $MSGFMT in
[\\/]* | ?:[\\/]*)
ac_cv_path_MSGFMT="$MSGFMT" # Let the user override the test with a path.
;;
*)
as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
for as_dir in $PATH
do
IFS=$as_save_IFS
test -z "$as_dir" && as_dir=.
for ac_exec_ext in '' $ac_executable_extensions; do
if as_fn_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
ac_cv_path_MSGFMT="$as_dir/$ac_word$ac_exec_ext"
$as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5
break 2
fi
done
done
IFS=$as_save_IFS
;;
esac
fi
MSGFMT=$ac_cv_path_MSGFMT
if test -n "$MSGFMT"; then
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $MSGFMT" >&5
$as_echo "$MSGFMT" >&6; }
else
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
fi
# Extract the first word of "gmsgfmt", so it can be a program name with args.
set dummy gmsgfmt; ac_word=$2
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5
$as_echo_n "checking for $ac_word... " >&6; }
if ${ac_cv_path_GMSGFMT+:} false; then :
$as_echo_n "(cached) " >&6
else
case $GMSGFMT in
[\\/]* | ?:[\\/]*)
ac_cv_path_GMSGFMT="$GMSGFMT" # Let the user override the test with a path.
;;
*)
as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
for as_dir in $PATH
do
IFS=$as_save_IFS
test -z "$as_dir" && as_dir=.
for ac_exec_ext in '' $ac_executable_extensions; do
if as_fn_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
ac_cv_path_GMSGFMT="$as_dir/$ac_word$ac_exec_ext"
$as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5
break 2
fi
done
done
IFS=$as_save_IFS
test -z "$ac_cv_path_GMSGFMT" && ac_cv_path_GMSGFMT="$MSGFMT"
;;
esac
fi
GMSGFMT=$ac_cv_path_GMSGFMT
if test -n "$GMSGFMT"; then
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $GMSGFMT" >&5
$as_echo "$GMSGFMT" >&6; }
else
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
fi
if test -z "$XGETTEXT" -o -z "$MSGMERGE" -o -z "$MSGFMT"; then
as_fn_error $? "GNU gettext tools not found; required for intltool" "$LINENO" 5
fi
xgversion="`$XGETTEXT --version|grep '(GNU ' 2> /dev/null`"
mmversion="`$MSGMERGE --version|grep '(GNU ' 2> /dev/null`"
mfversion="`$MSGFMT --version|grep '(GNU ' 2> /dev/null`"
if test -z "$xgversion" -o -z "$mmversion" -o -z "$mfversion"; then
as_fn_error $? "GNU gettext tools not found; required for intltool" "$LINENO" 5
fi
# Extract the first word of "perl", so it can be a program name with args.
set dummy perl; ac_word=$2
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5
$as_echo_n "checking for $ac_word... " >&6; }
if ${ac_cv_path_INTLTOOL_PERL+:} false; then :
$as_echo_n "(cached) " >&6
else
case $INTLTOOL_PERL in
[\\/]* | ?:[\\/]*)
ac_cv_path_INTLTOOL_PERL="$INTLTOOL_PERL" # Let the user override the test with a path.
;;
*)
as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
for as_dir in $PATH
do
IFS=$as_save_IFS
test -z "$as_dir" && as_dir=.
for ac_exec_ext in '' $ac_executable_extensions; do
if as_fn_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
ac_cv_path_INTLTOOL_PERL="$as_dir/$ac_word$ac_exec_ext"
$as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5
break 2
fi
done
done
IFS=$as_save_IFS
;;
esac
fi
INTLTOOL_PERL=$ac_cv_path_INTLTOOL_PERL
if test -n "$INTLTOOL_PERL"; then
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $INTLTOOL_PERL" >&5
$as_echo "$INTLTOOL_PERL" >&6; }
else
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
fi
if test -z "$INTLTOOL_PERL"; then
as_fn_error $? "perl not found" "$LINENO" 5
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for perl >= 5.8.1" >&5
$as_echo_n "checking for perl >= 5.8.1... " >&6; }
$INTLTOOL_PERL -e "use 5.8.1;" > /dev/null 2>&1
if test $? -ne 0; then
as_fn_error $? "perl 5.8.1 is required for intltool" "$LINENO" 5
else
IT_PERL_VERSION=`$INTLTOOL_PERL -e "printf '%vd', $^V"`
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $IT_PERL_VERSION" >&5
$as_echo "$IT_PERL_VERSION" >&6; }
fi
if test "x" != "xno-xml"; then
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for XML::Parser" >&5
$as_echo_n "checking for XML::Parser... " >&6; }
if `$INTLTOOL_PERL -e "require XML::Parser" 2>/dev/null`; then
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: ok" >&5
$as_echo "ok" >&6; }
else
as_fn_error $? "XML::Parser perl module is required for intltool" "$LINENO" 5
fi
fi
# Substitute ALL_LINGUAS so we can use it in po/Makefile
# Set DATADIRNAME correctly if it is not set yet
# (copied from glib-gettext.m4)
if test -z "$DATADIRNAME"; then
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h. */
int
main ()
{
extern int _nl_msg_cat_cntr;
return _nl_msg_cat_cntr
;
return 0;
}
_ACEOF
if ac_fn_c_try_link "$LINENO"; then :
DATADIRNAME=share
else
case $host in
*-*-solaris*)
ac_fn_c_check_func "$LINENO" "bind_textdomain_codeset" "ac_cv_func_bind_textdomain_codeset"
if test "x$ac_cv_func_bind_textdomain_codeset" = xyes; then :
DATADIRNAME=share
else
DATADIRNAME=lib
fi
;;
*)
DATADIRNAME=lib
;;
esac
fi
rm -f core conftest.err conftest.$ac_objext \
conftest$ac_exeext conftest.$ac_ext
fi
GETTEXT_MACRO_VERSION=0.17
# Prepare PATH_SEPARATOR.
# The user is always right.
if test "${PATH_SEPARATOR+set}" != set; then
echo "#! /bin/sh" >conf$$.sh
echo "exit 0" >>conf$$.sh
chmod +x conf$$.sh
if (PATH="/nonexistent;."; conf$$.sh) >/dev/null 2>&1; then
PATH_SEPARATOR=';'
else
PATH_SEPARATOR=:
fi
rm -f conf$$.sh
fi
# Find out how to test for executable files. Don't use a zero-byte file,
# as systems may use methods other than mode bits to determine executability.
cat >conf$$.file <<_ASEOF
#! /bin/sh
exit 0
_ASEOF
chmod +x conf$$.file
if test -x conf$$.file >/dev/null 2>&1; then
ac_executable_p="test -x"
else
ac_executable_p="test -f"
fi
rm -f conf$$.file
# Extract the first word of "msgfmt", so it can be a program name with args.
set dummy msgfmt; ac_word=$2
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5
$as_echo_n "checking for $ac_word... " >&6; }
if ${ac_cv_path_MSGFMT+:} false; then :
$as_echo_n "(cached) " >&6
else
case "$MSGFMT" in
[\\/]* | ?:[\\/]*)
ac_cv_path_MSGFMT="$MSGFMT" # Let the user override the test with a path.
;;
*)
ac_save_IFS="$IFS"; IFS=$PATH_SEPARATOR
for ac_dir in $PATH; do
IFS="$ac_save_IFS"
test -z "$ac_dir" && ac_dir=.
for ac_exec_ext in '' $ac_executable_extensions; do
if $ac_executable_p "$ac_dir/$ac_word$ac_exec_ext"; then
echo "$as_me: trying $ac_dir/$ac_word..." >&5
if $ac_dir/$ac_word --statistics /dev/null >&5 2>&1 &&
(if $ac_dir/$ac_word --statistics /dev/null 2>&1 >/dev/null | grep usage >/dev/null; then exit 1; else exit 0; fi); then
ac_cv_path_MSGFMT="$ac_dir/$ac_word$ac_exec_ext"
break 2
fi
fi
done
done
IFS="$ac_save_IFS"
test -z "$ac_cv_path_MSGFMT" && ac_cv_path_MSGFMT=":"
;;
esac
fi
MSGFMT="$ac_cv_path_MSGFMT"
if test "$MSGFMT" != ":"; then
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $MSGFMT" >&5
$as_echo "$MSGFMT" >&6; }
else
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
fi
# Extract the first word of "gmsgfmt", so it can be a program name with args.
set dummy gmsgfmt; ac_word=$2
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5
$as_echo_n "checking for $ac_word... " >&6; }
if ${ac_cv_path_GMSGFMT+:} false; then :
$as_echo_n "(cached) " >&6
else
case $GMSGFMT in
[\\/]* | ?:[\\/]*)
ac_cv_path_GMSGFMT="$GMSGFMT" # Let the user override the test with a path.
;;
*)
as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
for as_dir in $PATH
do
IFS=$as_save_IFS
test -z "$as_dir" && as_dir=.
for ac_exec_ext in '' $ac_executable_extensions; do
if as_fn_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
ac_cv_path_GMSGFMT="$as_dir/$ac_word$ac_exec_ext"
$as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5
break 2
fi
done
done
IFS=$as_save_IFS
test -z "$ac_cv_path_GMSGFMT" && ac_cv_path_GMSGFMT="$MSGFMT"
;;
esac
fi
GMSGFMT=$ac_cv_path_GMSGFMT
if test -n "$GMSGFMT"; then
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $GMSGFMT" >&5
$as_echo "$GMSGFMT" >&6; }
else
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
fi
case `$MSGFMT --version | sed 1q | sed -e 's,^[^0-9]*,,'` in
'' | 0.[0-9] | 0.[0-9].* | 0.1[0-4] | 0.1[0-4].*) MSGFMT_015=: ;;
*) MSGFMT_015=$MSGFMT ;;
esac
case `$GMSGFMT --version | sed 1q | sed -e 's,^[^0-9]*,,'` in
'' | 0.[0-9] | 0.[0-9].* | 0.1[0-4] | 0.1[0-4].*) GMSGFMT_015=: ;;
*) GMSGFMT_015=$GMSGFMT ;;
esac
# Prepare PATH_SEPARATOR.
# The user is always right.
if test "${PATH_SEPARATOR+set}" != set; then
echo "#! /bin/sh" >conf$$.sh
echo "exit 0" >>conf$$.sh
chmod +x conf$$.sh
if (PATH="/nonexistent;."; conf$$.sh) >/dev/null 2>&1; then
PATH_SEPARATOR=';'
else
PATH_SEPARATOR=:
fi
rm -f conf$$.sh
fi
# Find out how to test for executable files. Don't use a zero-byte file,
# as systems may use methods other than mode bits to determine executability.
cat >conf$$.file <<_ASEOF
#! /bin/sh
exit 0
_ASEOF
chmod +x conf$$.file
if test -x conf$$.file >/dev/null 2>&1; then
ac_executable_p="test -x"
else
ac_executable_p="test -f"
fi
rm -f conf$$.file
# Extract the first word of "xgettext", so it can be a program name with args.
set dummy xgettext; ac_word=$2
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5
$as_echo_n "checking for $ac_word... " >&6; }
if ${ac_cv_path_XGETTEXT+:} false; then :
$as_echo_n "(cached) " >&6
else
case "$XGETTEXT" in
[\\/]* | ?:[\\/]*)
ac_cv_path_XGETTEXT="$XGETTEXT" # Let the user override the test with a path.
;;
*)
ac_save_IFS="$IFS"; IFS=$PATH_SEPARATOR
for ac_dir in $PATH; do
IFS="$ac_save_IFS"
test -z "$ac_dir" && ac_dir=.
for ac_exec_ext in '' $ac_executable_extensions; do
if $ac_executable_p "$ac_dir/$ac_word$ac_exec_ext"; then
echo "$as_me: trying $ac_dir/$ac_word..." >&5
if $ac_dir/$ac_word --omit-header --copyright-holder= --msgid-bugs-address= /dev/null >&5 2>&1 &&
(if $ac_dir/$ac_word --omit-header --copyright-holder= --msgid-bugs-address= /dev/null 2>&1 >/dev/null | grep usage >/dev/null; then exit 1; else exit 0; fi); then
ac_cv_path_XGETTEXT="$ac_dir/$ac_word$ac_exec_ext"
break 2
fi
fi
done
done
IFS="$ac_save_IFS"
test -z "$ac_cv_path_XGETTEXT" && ac_cv_path_XGETTEXT=":"
;;
esac
fi
XGETTEXT="$ac_cv_path_XGETTEXT"
if test "$XGETTEXT" != ":"; then
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $XGETTEXT" >&5
$as_echo "$XGETTEXT" >&6; }
else
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
fi
rm -f messages.po
case `$XGETTEXT --version | sed 1q | sed -e 's,^[^0-9]*,,'` in
'' | 0.[0-9] | 0.[0-9].* | 0.1[0-4] | 0.1[0-4].*) XGETTEXT_015=: ;;
*) XGETTEXT_015=$XGETTEXT ;;
esac
# Prepare PATH_SEPARATOR.
# The user is always right.
if test "${PATH_SEPARATOR+set}" != set; then
echo "#! /bin/sh" >conf$$.sh
echo "exit 0" >>conf$$.sh
chmod +x conf$$.sh
if (PATH="/nonexistent;."; conf$$.sh) >/dev/null 2>&1; then
PATH_SEPARATOR=';'
else
PATH_SEPARATOR=:
fi
rm -f conf$$.sh
fi
# Find out how to test for executable files. Don't use a zero-byte file,
# as systems may use methods other than mode bits to determine executability.
cat >conf$$.file <<_ASEOF
#! /bin/sh
exit 0
_ASEOF
chmod +x conf$$.file
if test -x conf$$.file >/dev/null 2>&1; then
ac_executable_p="test -x"
else
ac_executable_p="test -f"
fi
rm -f conf$$.file
# Extract the first word of "msgmerge", so it can be a program name with args.
set dummy msgmerge; ac_word=$2
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5
$as_echo_n "checking for $ac_word... " >&6; }
if ${ac_cv_path_MSGMERGE+:} false; then :
$as_echo_n "(cached) " >&6
else
case "$MSGMERGE" in
[\\/]* | ?:[\\/]*)
ac_cv_path_MSGMERGE="$MSGMERGE" # Let the user override the test with a path.
;;
*)
ac_save_IFS="$IFS"; IFS=$PATH_SEPARATOR
for ac_dir in $PATH; do
IFS="$ac_save_IFS"
test -z "$ac_dir" && ac_dir=.
for ac_exec_ext in '' $ac_executable_extensions; do
if $ac_executable_p "$ac_dir/$ac_word$ac_exec_ext"; then
echo "$as_me: trying $ac_dir/$ac_word..." >&5
if $ac_dir/$ac_word --update -q /dev/null /dev/null >&5 2>&1; then
ac_cv_path_MSGMERGE="$ac_dir/$ac_word$ac_exec_ext"
break 2
fi
fi
done
done
IFS="$ac_save_IFS"
test -z "$ac_cv_path_MSGMERGE" && ac_cv_path_MSGMERGE=":"
;;
esac
fi
MSGMERGE="$ac_cv_path_MSGMERGE"
if test "$MSGMERGE" != ":"; then
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $MSGMERGE" >&5
$as_echo "$MSGMERGE" >&6; }
else
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
fi
test -n "$localedir" || localedir='${datadir}/locale'
test -n "${XGETTEXT_EXTRA_OPTIONS+set}" || XGETTEXT_EXTRA_OPTIONS=
ac_config_commands="$ac_config_commands po-directories"
if test "X$prefix" = "XNONE"; then
acl_final_prefix="$ac_default_prefix"
else
acl_final_prefix="$prefix"
fi
if test "X$exec_prefix" = "XNONE"; then
acl_final_exec_prefix='${prefix}'
else
acl_final_exec_prefix="$exec_prefix"
fi
acl_save_prefix="$prefix"
prefix="$acl_final_prefix"
eval acl_final_exec_prefix=\"$acl_final_exec_prefix\"
prefix="$acl_save_prefix"
# Make sure we can run config.sub.
$SHELL "$ac_aux_dir/config.sub" sun4 >/dev/null 2>&1 ||
as_fn_error $? "cannot run $SHELL $ac_aux_dir/config.sub" "$LINENO" 5
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking build system type" >&5
$as_echo_n "checking build system type... " >&6; }
if ${ac_cv_build+:} false; then :
$as_echo_n "(cached) " >&6
else
ac_build_alias=$build_alias
test "x$ac_build_alias" = x &&
ac_build_alias=`$SHELL "$ac_aux_dir/config.guess"`
test "x$ac_build_alias" = x &&
as_fn_error $? "cannot guess build type; you must specify one" "$LINENO" 5
ac_cv_build=`$SHELL "$ac_aux_dir/config.sub" $ac_build_alias` ||
as_fn_error $? "$SHELL $ac_aux_dir/config.sub $ac_build_alias failed" "$LINENO" 5
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_build" >&5
$as_echo "$ac_cv_build" >&6; }
case $ac_cv_build in
*-*-*) ;;
*) as_fn_error $? "invalid value of canonical build" "$LINENO" 5;;
esac
build=$ac_cv_build
ac_save_IFS=$IFS; IFS='-'
set x $ac_cv_build
shift
build_cpu=$1
build_vendor=$2
shift; shift
# Remember, the first character of IFS is used to create $*,
# except with old shells:
build_os=$*
IFS=$ac_save_IFS
case $build_os in *\ *) build_os=`echo "$build_os" | sed 's/ /-/g'`;; esac
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking host system type" >&5
$as_echo_n "checking host system type... " >&6; }
if ${ac_cv_host+:} false; then :
$as_echo_n "(cached) " >&6
else
if test "x$host_alias" = x; then
ac_cv_host=$ac_cv_build
else
ac_cv_host=`$SHELL "$ac_aux_dir/config.sub" $host_alias` ||
as_fn_error $? "$SHELL $ac_aux_dir/config.sub $host_alias failed" "$LINENO" 5
fi
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_host" >&5
$as_echo "$ac_cv_host" >&6; }
case $ac_cv_host in
*-*-*) ;;
*) as_fn_error $? "invalid value of canonical host" "$LINENO" 5;;
esac
host=$ac_cv_host
ac_save_IFS=$IFS; IFS='-'
set x $ac_cv_host
shift
host_cpu=$1
host_vendor=$2
shift; shift
# Remember, the first character of IFS is used to create $*,
# except with old shells:
host_os=$*
IFS=$ac_save_IFS
case $host_os in *\ *) host_os=`echo "$host_os" | sed 's/ /-/g'`;; esac
# Check whether --with-gnu-ld was given.
if test "${with_gnu_ld+set}" = set; then :
withval=$with_gnu_ld; test "$withval" = no || with_gnu_ld=yes
else
with_gnu_ld=no
fi
# Prepare PATH_SEPARATOR.
# The user is always right.
if test "${PATH_SEPARATOR+set}" != set; then
echo "#! /bin/sh" >conf$$.sh
echo "exit 0" >>conf$$.sh
chmod +x conf$$.sh
if (PATH="/nonexistent;."; conf$$.sh) >/dev/null 2>&1; then
PATH_SEPARATOR=';'
else
PATH_SEPARATOR=:
fi
rm -f conf$$.sh
fi
ac_prog=ld
if test "$GCC" = yes; then
# Check if gcc -print-prog-name=ld gives a path.
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for ld used by GCC" >&5
$as_echo_n "checking for ld used by GCC... " >&6; }
case $host in
*-*-mingw*)
# gcc leaves a trailing carriage return which upsets mingw
ac_prog=`($CC -print-prog-name=ld) 2>&5 | tr -d '\015'` ;;
*)
ac_prog=`($CC -print-prog-name=ld) 2>&5` ;;
esac
case $ac_prog in
# Accept absolute paths.
[\\/]* | [A-Za-z]:[\\/]*)
re_direlt='/[^/][^/]*/\.\./'
# Canonicalize the path of ld
ac_prog=`echo $ac_prog| sed 's%\\\\%/%g'`
while echo $ac_prog | grep "$re_direlt" > /dev/null 2>&1; do
ac_prog=`echo $ac_prog| sed "s%$re_direlt%/%"`
done
test -z "$LD" && LD="$ac_prog"
;;
"")
# If it fails, then pretend we aren't using GCC.
ac_prog=ld
;;
*)
# If it is relative, then search for the first ld in PATH.
with_gnu_ld=unknown
;;
esac
elif test "$with_gnu_ld" = yes; then
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for GNU ld" >&5
$as_echo_n "checking for GNU ld... " >&6; }
else
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for non-GNU ld" >&5
$as_echo_n "checking for non-GNU ld... " >&6; }
fi
if ${acl_cv_path_LD+:} false; then :
$as_echo_n "(cached) " >&6
else
if test -z "$LD"; then
IFS="${IFS= }"; ac_save_ifs="$IFS"; IFS="${IFS}${PATH_SEPARATOR-:}"
for ac_dir in $PATH; do
test -z "$ac_dir" && ac_dir=.
if test -f "$ac_dir/$ac_prog" || test -f "$ac_dir/$ac_prog$ac_exeext"; then
acl_cv_path_LD="$ac_dir/$ac_prog"
# Check to see if the program is GNU ld. I'd rather use --version,
# but apparently some GNU ld's only accept -v.
# Break only if it was the GNU/non-GNU ld that we prefer.
case `"$acl_cv_path_LD" -v 2>&1 < /dev/null` in
*GNU* | *'with BFD'*)
test "$with_gnu_ld" != no && break ;;
*)
test "$with_gnu_ld" != yes && break ;;
esac
fi
done
IFS="$ac_save_ifs"
else
acl_cv_path_LD="$LD" # Let the user override the test with a path.
fi
fi
LD="$acl_cv_path_LD"
if test -n "$LD"; then
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $LD" >&5
$as_echo "$LD" >&6; }
else
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
fi
test -z "$LD" && as_fn_error $? "no acceptable ld found in \$PATH" "$LINENO" 5
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking if the linker ($LD) is GNU ld" >&5
$as_echo_n "checking if the linker ($LD) is GNU ld... " >&6; }
if ${acl_cv_prog_gnu_ld+:} false; then :
$as_echo_n "(cached) " >&6
else
# I'd rather use --version here, but apparently some GNU ld's only accept -v.
case `$LD -v 2>&1 &5
$as_echo "$acl_cv_prog_gnu_ld" >&6; }
with_gnu_ld=$acl_cv_prog_gnu_ld
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for shared library run path origin" >&5
$as_echo_n "checking for shared library run path origin... " >&6; }
if ${acl_cv_rpath+:} false; then :
$as_echo_n "(cached) " >&6
else
CC="$CC" GCC="$GCC" LDFLAGS="$LDFLAGS" LD="$LD" with_gnu_ld="$with_gnu_ld" \
${CONFIG_SHELL-/bin/sh} "$ac_aux_dir/config.rpath" "$host" > conftest.sh
. ./conftest.sh
rm -f ./conftest.sh
acl_cv_rpath=done
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $acl_cv_rpath" >&5
$as_echo "$acl_cv_rpath" >&6; }
wl="$acl_cv_wl"
acl_libext="$acl_cv_libext"
acl_shlibext="$acl_cv_shlibext"
acl_libname_spec="$acl_cv_libname_spec"
acl_library_names_spec="$acl_cv_library_names_spec"
acl_hardcode_libdir_flag_spec="$acl_cv_hardcode_libdir_flag_spec"
acl_hardcode_libdir_separator="$acl_cv_hardcode_libdir_separator"
acl_hardcode_direct="$acl_cv_hardcode_direct"
acl_hardcode_minus_L="$acl_cv_hardcode_minus_L"
# Check whether --enable-rpath was given.
if test "${enable_rpath+set}" = set; then :
enableval=$enable_rpath; :
else
enable_rpath=yes
fi
acl_libdirstem=lib
searchpath=`(LC_ALL=C $CC -print-search-dirs) 2>/dev/null | sed -n -e 's,^libraries: ,,p' | sed -e 's,^=,,'`
if test -n "$searchpath"; then
acl_save_IFS="${IFS= }"; IFS=":"
for searchdir in $searchpath; do
if test -d "$searchdir"; then
case "$searchdir" in
*/lib64/ | */lib64 ) acl_libdirstem=lib64 ;;
*) searchdir=`cd "$searchdir" && pwd`
case "$searchdir" in
*/lib64 ) acl_libdirstem=lib64 ;;
esac ;;
esac
fi
done
IFS="$acl_save_IFS"
fi
use_additional=yes
acl_save_prefix="$prefix"
prefix="$acl_final_prefix"
acl_save_exec_prefix="$exec_prefix"
exec_prefix="$acl_final_exec_prefix"
eval additional_includedir=\"$includedir\"
eval additional_libdir=\"$libdir\"
exec_prefix="$acl_save_exec_prefix"
prefix="$acl_save_prefix"
# Check whether --with-libiconv-prefix was given.
if test "${with_libiconv_prefix+set}" = set; then :
withval=$with_libiconv_prefix;
if test "X$withval" = "Xno"; then
use_additional=no
else
if test "X$withval" = "X"; then
acl_save_prefix="$prefix"
prefix="$acl_final_prefix"
acl_save_exec_prefix="$exec_prefix"
exec_prefix="$acl_final_exec_prefix"
eval additional_includedir=\"$includedir\"
eval additional_libdir=\"$libdir\"
exec_prefix="$acl_save_exec_prefix"
prefix="$acl_save_prefix"
else
additional_includedir="$withval/include"
additional_libdir="$withval/$acl_libdirstem"
fi
fi
fi
LIBICONV=
LTLIBICONV=
INCICONV=
LIBICONV_PREFIX=
rpathdirs=
ltrpathdirs=
names_already_handled=
names_next_round='iconv '
while test -n "$names_next_round"; do
names_this_round="$names_next_round"
names_next_round=
for name in $names_this_round; do
already_handled=
for n in $names_already_handled; do
if test "$n" = "$name"; then
already_handled=yes
break
fi
done
if test -z "$already_handled"; then
names_already_handled="$names_already_handled $name"
uppername=`echo "$name" | sed -e 'y|abcdefghijklmnopqrstuvwxyz./-|ABCDEFGHIJKLMNOPQRSTUVWXYZ___|'`
eval value=\"\$HAVE_LIB$uppername\"
if test -n "$value"; then
if test "$value" = yes; then
eval value=\"\$LIB$uppername\"
test -z "$value" || LIBICONV="${LIBICONV}${LIBICONV:+ }$value"
eval value=\"\$LTLIB$uppername\"
test -z "$value" || LTLIBICONV="${LTLIBICONV}${LTLIBICONV:+ }$value"
else
:
fi
else
found_dir=
found_la=
found_so=
found_a=
eval libname=\"$acl_libname_spec\" # typically: libname=lib$name
if test -n "$acl_shlibext"; then
shrext=".$acl_shlibext" # typically: shrext=.so
else
shrext=
fi
if test $use_additional = yes; then
dir="$additional_libdir"
if test -n "$acl_shlibext"; then
if test -f "$dir/$libname$shrext"; then
found_dir="$dir"
found_so="$dir/$libname$shrext"
else
if test "$acl_library_names_spec" = '$libname$shrext$versuffix'; then
ver=`(cd "$dir" && \
for f in "$libname$shrext".*; do echo "$f"; done \
| sed -e "s,^$libname$shrext\\\\.,," \
| sort -t '.' -n -r -k1,1 -k2,2 -k3,3 -k4,4 -k5,5 \
| sed 1q ) 2>/dev/null`
if test -n "$ver" && test -f "$dir/$libname$shrext.$ver"; then
found_dir="$dir"
found_so="$dir/$libname$shrext.$ver"
fi
else
eval library_names=\"$acl_library_names_spec\"
for f in $library_names; do
if test -f "$dir/$f"; then
found_dir="$dir"
found_so="$dir/$f"
break
fi
done
fi
fi
fi
if test "X$found_dir" = "X"; then
if test -f "$dir/$libname.$acl_libext"; then
found_dir="$dir"
found_a="$dir/$libname.$acl_libext"
fi
fi
if test "X$found_dir" != "X"; then
if test -f "$dir/$libname.la"; then
found_la="$dir/$libname.la"
fi
fi
fi
if test "X$found_dir" = "X"; then
for x in $LDFLAGS $LTLIBICONV; do
acl_save_prefix="$prefix"
prefix="$acl_final_prefix"
acl_save_exec_prefix="$exec_prefix"
exec_prefix="$acl_final_exec_prefix"
eval x=\"$x\"
exec_prefix="$acl_save_exec_prefix"
prefix="$acl_save_prefix"
case "$x" in
-L*)
dir=`echo "X$x" | sed -e 's/^X-L//'`
if test -n "$acl_shlibext"; then
if test -f "$dir/$libname$shrext"; then
found_dir="$dir"
found_so="$dir/$libname$shrext"
else
if test "$acl_library_names_spec" = '$libname$shrext$versuffix'; then
ver=`(cd "$dir" && \
for f in "$libname$shrext".*; do echo "$f"; done \
| sed -e "s,^$libname$shrext\\\\.,," \
| sort -t '.' -n -r -k1,1 -k2,2 -k3,3 -k4,4 -k5,5 \
| sed 1q ) 2>/dev/null`
if test -n "$ver" && test -f "$dir/$libname$shrext.$ver"; then
found_dir="$dir"
found_so="$dir/$libname$shrext.$ver"
fi
else
eval library_names=\"$acl_library_names_spec\"
for f in $library_names; do
if test -f "$dir/$f"; then
found_dir="$dir"
found_so="$dir/$f"
break
fi
done
fi
fi
fi
if test "X$found_dir" = "X"; then
if test -f "$dir/$libname.$acl_libext"; then
found_dir="$dir"
found_a="$dir/$libname.$acl_libext"
fi
fi
if test "X$found_dir" != "X"; then
if test -f "$dir/$libname.la"; then
found_la="$dir/$libname.la"
fi
fi
;;
esac
if test "X$found_dir" != "X"; then
break
fi
done
fi
if test "X$found_dir" != "X"; then
LTLIBICONV="${LTLIBICONV}${LTLIBICONV:+ }-L$found_dir -l$name"
if test "X$found_so" != "X"; then
if test "$enable_rpath" = no || test "X$found_dir" = "X/usr/$acl_libdirstem"; then
LIBICONV="${LIBICONV}${LIBICONV:+ }$found_so"
else
haveit=
for x in $ltrpathdirs; do
if test "X$x" = "X$found_dir"; then
haveit=yes
break
fi
done
if test -z "$haveit"; then
ltrpathdirs="$ltrpathdirs $found_dir"
fi
if test "$acl_hardcode_direct" = yes; then
LIBICONV="${LIBICONV}${LIBICONV:+ }$found_so"
else
if test -n "$acl_hardcode_libdir_flag_spec" && test "$acl_hardcode_minus_L" = no; then
LIBICONV="${LIBICONV}${LIBICONV:+ }$found_so"
haveit=
for x in $rpathdirs; do
if test "X$x" = "X$found_dir"; then
haveit=yes
break
fi
done
if test -z "$haveit"; then
rpathdirs="$rpathdirs $found_dir"
fi
else
haveit=
for x in $LDFLAGS $LIBICONV; do
acl_save_prefix="$prefix"
prefix="$acl_final_prefix"
acl_save_exec_prefix="$exec_prefix"
exec_prefix="$acl_final_exec_prefix"
eval x=\"$x\"
exec_prefix="$acl_save_exec_prefix"
prefix="$acl_save_prefix"
if test "X$x" = "X-L$found_dir"; then
haveit=yes
break
fi
done
if test -z "$haveit"; then
LIBICONV="${LIBICONV}${LIBICONV:+ }-L$found_dir"
fi
if test "$acl_hardcode_minus_L" != no; then
LIBICONV="${LIBICONV}${LIBICONV:+ }$found_so"
else
LIBICONV="${LIBICONV}${LIBICONV:+ }-l$name"
fi
fi
fi
fi
else
if test "X$found_a" != "X"; then
LIBICONV="${LIBICONV}${LIBICONV:+ }$found_a"
else
LIBICONV="${LIBICONV}${LIBICONV:+ }-L$found_dir -l$name"
fi
fi
additional_includedir=
case "$found_dir" in
*/$acl_libdirstem | */$acl_libdirstem/)
basedir=`echo "X$found_dir" | sed -e 's,^X,,' -e "s,/$acl_libdirstem/"'*$,,'`
LIBICONV_PREFIX="$basedir"
additional_includedir="$basedir/include"
;;
esac
if test "X$additional_includedir" != "X"; then
if test "X$additional_includedir" != "X/usr/include"; then
haveit=
if test "X$additional_includedir" = "X/usr/local/include"; then
if test -n "$GCC"; then
case $host_os in
linux* | gnu* | k*bsd*-gnu) haveit=yes;;
esac
fi
fi
if test -z "$haveit"; then
for x in $CPPFLAGS $INCICONV; do
acl_save_prefix="$prefix"
prefix="$acl_final_prefix"
acl_save_exec_prefix="$exec_prefix"
exec_prefix="$acl_final_exec_prefix"
eval x=\"$x\"
exec_prefix="$acl_save_exec_prefix"
prefix="$acl_save_prefix"
if test "X$x" = "X-I$additional_includedir"; then
haveit=yes
break
fi
done
if test -z "$haveit"; then
if test -d "$additional_includedir"; then
INCICONV="${INCICONV}${INCICONV:+ }-I$additional_includedir"
fi
fi
fi
fi
fi
if test -n "$found_la"; then
save_libdir="$libdir"
case "$found_la" in
*/* | *\\*) . "$found_la" ;;
*) . "./$found_la" ;;
esac
libdir="$save_libdir"
for dep in $dependency_libs; do
case "$dep" in
-L*)
additional_libdir=`echo "X$dep" | sed -e 's/^X-L//'`
if test "X$additional_libdir" != "X/usr/$acl_libdirstem"; then
haveit=
if test "X$additional_libdir" = "X/usr/local/$acl_libdirstem"; then
if test -n "$GCC"; then
case $host_os in
linux* | gnu* | k*bsd*-gnu) haveit=yes;;
esac
fi
fi
if test -z "$haveit"; then
haveit=
for x in $LDFLAGS $LIBICONV; do
acl_save_prefix="$prefix"
prefix="$acl_final_prefix"
acl_save_exec_prefix="$exec_prefix"
exec_prefix="$acl_final_exec_prefix"
eval x=\"$x\"
exec_prefix="$acl_save_exec_prefix"
prefix="$acl_save_prefix"
if test "X$x" = "X-L$additional_libdir"; then
haveit=yes
break
fi
done
if test -z "$haveit"; then
if test -d "$additional_libdir"; then
LIBICONV="${LIBICONV}${LIBICONV:+ }-L$additional_libdir"
fi
fi
haveit=
for x in $LDFLAGS $LTLIBICONV; do
acl_save_prefix="$prefix"
prefix="$acl_final_prefix"
acl_save_exec_prefix="$exec_prefix"
exec_prefix="$acl_final_exec_prefix"
eval x=\"$x\"
exec_prefix="$acl_save_exec_prefix"
prefix="$acl_save_prefix"
if test "X$x" = "X-L$additional_libdir"; then
haveit=yes
break
fi
done
if test -z "$haveit"; then
if test -d "$additional_libdir"; then
LTLIBICONV="${LTLIBICONV}${LTLIBICONV:+ }-L$additional_libdir"
fi
fi
fi
fi
;;
-R*)
dir=`echo "X$dep" | sed -e 's/^X-R//'`
if test "$enable_rpath" != no; then
haveit=
for x in $rpathdirs; do
if test "X$x" = "X$dir"; then
haveit=yes
break
fi
done
if test -z "$haveit"; then
rpathdirs="$rpathdirs $dir"
fi
haveit=
for x in $ltrpathdirs; do
if test "X$x" = "X$dir"; then
haveit=yes
break
fi
done
if test -z "$haveit"; then
ltrpathdirs="$ltrpathdirs $dir"
fi
fi
;;
-l*)
names_next_round="$names_next_round "`echo "X$dep" | sed -e 's/^X-l//'`
;;
*.la)
names_next_round="$names_next_round "`echo "X$dep" | sed -e 's,^X.*/,,' -e 's,^lib,,' -e 's,\.la$,,'`
;;
*)
LIBICONV="${LIBICONV}${LIBICONV:+ }$dep"
LTLIBICONV="${LTLIBICONV}${LTLIBICONV:+ }$dep"
;;
esac
done
fi
else
LIBICONV="${LIBICONV}${LIBICONV:+ }-l$name"
LTLIBICONV="${LTLIBICONV}${LTLIBICONV:+ }-l$name"
fi
fi
fi
done
done
if test "X$rpathdirs" != "X"; then
if test -n "$acl_hardcode_libdir_separator"; then
alldirs=
for found_dir in $rpathdirs; do
alldirs="${alldirs}${alldirs:+$acl_hardcode_libdir_separator}$found_dir"
done
acl_save_libdir="$libdir"
libdir="$alldirs"
eval flag=\"$acl_hardcode_libdir_flag_spec\"
libdir="$acl_save_libdir"
LIBICONV="${LIBICONV}${LIBICONV:+ }$flag"
else
for found_dir in $rpathdirs; do
acl_save_libdir="$libdir"
libdir="$found_dir"
eval flag=\"$acl_hardcode_libdir_flag_spec\"
libdir="$acl_save_libdir"
LIBICONV="${LIBICONV}${LIBICONV:+ }$flag"
done
fi
fi
if test "X$ltrpathdirs" != "X"; then
for found_dir in $ltrpathdirs; do
LTLIBICONV="${LTLIBICONV}${LTLIBICONV:+ }-R$found_dir"
done
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for CFPreferencesCopyAppValue" >&5
$as_echo_n "checking for CFPreferencesCopyAppValue... " >&6; }
if ${gt_cv_func_CFPreferencesCopyAppValue+:} false; then :
$as_echo_n "(cached) " >&6
else
gt_save_LIBS="$LIBS"
LIBS="$LIBS -Wl,-framework -Wl,CoreFoundation"
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h. */
#include
int
main ()
{
CFPreferencesCopyAppValue(NULL, NULL)
;
return 0;
}
_ACEOF
if ac_fn_c_try_link "$LINENO"; then :
gt_cv_func_CFPreferencesCopyAppValue=yes
else
gt_cv_func_CFPreferencesCopyAppValue=no
fi
rm -f core conftest.err conftest.$ac_objext \
conftest$ac_exeext conftest.$ac_ext
LIBS="$gt_save_LIBS"
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $gt_cv_func_CFPreferencesCopyAppValue" >&5
$as_echo "$gt_cv_func_CFPreferencesCopyAppValue" >&6; }
if test $gt_cv_func_CFPreferencesCopyAppValue = yes; then
$as_echo "#define HAVE_CFPREFERENCESCOPYAPPVALUE 1" >>confdefs.h
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for CFLocaleCopyCurrent" >&5
$as_echo_n "checking for CFLocaleCopyCurrent... " >&6; }
if ${gt_cv_func_CFLocaleCopyCurrent+:} false; then :
$as_echo_n "(cached) " >&6
else
gt_save_LIBS="$LIBS"
LIBS="$LIBS -Wl,-framework -Wl,CoreFoundation"
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h. */
#include
int
main ()
{
CFLocaleCopyCurrent();
;
return 0;
}
_ACEOF
if ac_fn_c_try_link "$LINENO"; then :
gt_cv_func_CFLocaleCopyCurrent=yes
else
gt_cv_func_CFLocaleCopyCurrent=no
fi
rm -f core conftest.err conftest.$ac_objext \
conftest$ac_exeext conftest.$ac_ext
LIBS="$gt_save_LIBS"
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $gt_cv_func_CFLocaleCopyCurrent" >&5
$as_echo "$gt_cv_func_CFLocaleCopyCurrent" >&6; }
if test $gt_cv_func_CFLocaleCopyCurrent = yes; then
$as_echo "#define HAVE_CFLOCALECOPYCURRENT 1" >>confdefs.h
fi
INTL_MACOSX_LIBS=
if test $gt_cv_func_CFPreferencesCopyAppValue = yes || test $gt_cv_func_CFLocaleCopyCurrent = yes; then
INTL_MACOSX_LIBS="-Wl,-framework -Wl,CoreFoundation"
fi
LIBINTL=
LTLIBINTL=
POSUB=
case " $gt_needs " in
*" need-formatstring-macros "*) gt_api_version=3 ;;
*" need-ngettext "*) gt_api_version=2 ;;
*) gt_api_version=1 ;;
esac
gt_func_gnugettext_libc="gt_cv_func_gnugettext${gt_api_version}_libc"
gt_func_gnugettext_libintl="gt_cv_func_gnugettext${gt_api_version}_libintl"
if test "$USE_NLS" = "yes"; then
gt_use_preinstalled_gnugettext=no
if test $gt_api_version -ge 3; then
gt_revision_test_code='
#ifndef __GNU_GETTEXT_SUPPORTED_REVISION
#define __GNU_GETTEXT_SUPPORTED_REVISION(major) ((major) == 0 ? 0 : -1)
#endif
typedef int array [2 * (__GNU_GETTEXT_SUPPORTED_REVISION(0) >= 1) - 1];
'
else
gt_revision_test_code=
fi
if test $gt_api_version -ge 2; then
gt_expression_test_code=' + * ngettext ("", "", 0)'
else
gt_expression_test_code=
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for GNU gettext in libc" >&5
$as_echo_n "checking for GNU gettext in libc... " >&6; }
if eval \${$gt_func_gnugettext_libc+:} false; then :
$as_echo_n "(cached) " >&6
else
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h. */
#include
$gt_revision_test_code
extern int _nl_msg_cat_cntr;
extern int *_nl_domain_bindings;
int
main ()
{
bindtextdomain ("", "");
return * gettext ("")$gt_expression_test_code + _nl_msg_cat_cntr + *_nl_domain_bindings
;
return 0;
}
_ACEOF
if ac_fn_c_try_link "$LINENO"; then :
eval "$gt_func_gnugettext_libc=yes"
else
eval "$gt_func_gnugettext_libc=no"
fi
rm -f core conftest.err conftest.$ac_objext \
conftest$ac_exeext conftest.$ac_ext
fi
eval ac_res=\$$gt_func_gnugettext_libc
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_res" >&5
$as_echo "$ac_res" >&6; }
if { eval "gt_val=\$$gt_func_gnugettext_libc"; test "$gt_val" != "yes"; }; then
am_save_CPPFLAGS="$CPPFLAGS"
for element in $INCICONV; do
haveit=
for x in $CPPFLAGS; do
acl_save_prefix="$prefix"
prefix="$acl_final_prefix"
acl_save_exec_prefix="$exec_prefix"
exec_prefix="$acl_final_exec_prefix"
eval x=\"$x\"
exec_prefix="$acl_save_exec_prefix"
prefix="$acl_save_prefix"
if test "X$x" = "X$element"; then
haveit=yes
break
fi
done
if test -z "$haveit"; then
CPPFLAGS="${CPPFLAGS}${CPPFLAGS:+ }$element"
fi
done
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for iconv" >&5
$as_echo_n "checking for iconv... " >&6; }
if ${am_cv_func_iconv+:} false; then :
$as_echo_n "(cached) " >&6
else
am_cv_func_iconv="no, consider installing GNU libiconv"
am_cv_lib_iconv=no
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h. */
#include
#include
int
main ()
{
iconv_t cd = iconv_open("","");
iconv(cd,NULL,NULL,NULL,NULL);
iconv_close(cd);
;
return 0;
}
_ACEOF
if ac_fn_c_try_link "$LINENO"; then :
am_cv_func_iconv=yes
fi
rm -f core conftest.err conftest.$ac_objext \
conftest$ac_exeext conftest.$ac_ext
if test "$am_cv_func_iconv" != yes; then
am_save_LIBS="$LIBS"
LIBS="$LIBS $LIBICONV"
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h. */
#include
#include
int
main ()
{
iconv_t cd = iconv_open("","");
iconv(cd,NULL,NULL,NULL,NULL);
iconv_close(cd);
;
return 0;
}
_ACEOF
if ac_fn_c_try_link "$LINENO"; then :
am_cv_lib_iconv=yes
am_cv_func_iconv=yes
fi
rm -f core conftest.err conftest.$ac_objext \
conftest$ac_exeext conftest.$ac_ext
LIBS="$am_save_LIBS"
fi
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $am_cv_func_iconv" >&5
$as_echo "$am_cv_func_iconv" >&6; }
if test "$am_cv_func_iconv" = yes; then
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for working iconv" >&5
$as_echo_n "checking for working iconv... " >&6; }
if ${am_cv_func_iconv_works+:} false; then :
$as_echo_n "(cached) " >&6
else
am_save_LIBS="$LIBS"
if test $am_cv_lib_iconv = yes; then
LIBS="$LIBS $LIBICONV"
fi
if test "$cross_compiling" = yes; then :
case "$host_os" in
aix* | hpux*) am_cv_func_iconv_works="guessing no" ;;
*) am_cv_func_iconv_works="guessing yes" ;;
esac
else
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h. */
#include
#include
int main ()
{
/* Test against AIX 5.1 bug: Failures are not distinguishable from successful
returns. */
{
iconv_t cd_utf8_to_88591 = iconv_open ("ISO8859-1", "UTF-8");
if (cd_utf8_to_88591 != (iconv_t)(-1))
{
static const char input[] = "\342\202\254"; /* EURO SIGN */
char buf[10];
const char *inptr = input;
size_t inbytesleft = strlen (input);
char *outptr = buf;
size_t outbytesleft = sizeof (buf);
size_t res = iconv (cd_utf8_to_88591,
(char **) &inptr, &inbytesleft,
&outptr, &outbytesleft);
if (res == 0)
return 1;
}
}
#if 0 /* This bug could be worked around by the caller. */
/* Test against HP-UX 11.11 bug: Positive return value instead of 0. */
{
iconv_t cd_88591_to_utf8 = iconv_open ("utf8", "iso88591");
if (cd_88591_to_utf8 != (iconv_t)(-1))
{
static const char input[] = "\304rger mit b\366sen B\374bchen ohne Augenma\337";
char buf[50];
const char *inptr = input;
size_t inbytesleft = strlen (input);
char *outptr = buf;
size_t outbytesleft = sizeof (buf);
size_t res = iconv (cd_88591_to_utf8,
(char **) &inptr, &inbytesleft,
&outptr, &outbytesleft);
if ((int)res > 0)
return 1;
}
}
#endif
/* Test against HP-UX 11.11 bug: No converter from EUC-JP to UTF-8 is
provided. */
if (/* Try standardized names. */
iconv_open ("UTF-8", "EUC-JP") == (iconv_t)(-1)
/* Try IRIX, OSF/1 names. */
&& iconv_open ("UTF-8", "eucJP") == (iconv_t)(-1)
/* Try AIX names. */
&& iconv_open ("UTF-8", "IBM-eucJP") == (iconv_t)(-1)
/* Try HP-UX names. */
&& iconv_open ("utf8", "eucJP") == (iconv_t)(-1))
return 1;
return 0;
}
_ACEOF
if ac_fn_c_try_run "$LINENO"; then :
am_cv_func_iconv_works=yes
else
am_cv_func_iconv_works=no
fi
rm -f core *.core core.conftest.* gmon.out bb.out conftest$ac_exeext \
conftest.$ac_objext conftest.beam conftest.$ac_ext
fi
LIBS="$am_save_LIBS"
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $am_cv_func_iconv_works" >&5
$as_echo "$am_cv_func_iconv_works" >&6; }
case "$am_cv_func_iconv_works" in
*no) am_func_iconv=no am_cv_lib_iconv=no ;;
*) am_func_iconv=yes ;;
esac
else
am_func_iconv=no am_cv_lib_iconv=no
fi
if test "$am_func_iconv" = yes; then
$as_echo "#define HAVE_ICONV 1" >>confdefs.h
fi
if test "$am_cv_lib_iconv" = yes; then
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking how to link with libiconv" >&5
$as_echo_n "checking how to link with libiconv... " >&6; }
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $LIBICONV" >&5
$as_echo "$LIBICONV" >&6; }
else
CPPFLAGS="$am_save_CPPFLAGS"
LIBICONV=
LTLIBICONV=
fi
use_additional=yes
acl_save_prefix="$prefix"
prefix="$acl_final_prefix"
acl_save_exec_prefix="$exec_prefix"
exec_prefix="$acl_final_exec_prefix"
eval additional_includedir=\"$includedir\"
eval additional_libdir=\"$libdir\"
exec_prefix="$acl_save_exec_prefix"
prefix="$acl_save_prefix"
# Check whether --with-libintl-prefix was given.
if test "${with_libintl_prefix+set}" = set; then :
withval=$with_libintl_prefix;
if test "X$withval" = "Xno"; then
use_additional=no
else
if test "X$withval" = "X"; then
acl_save_prefix="$prefix"
prefix="$acl_final_prefix"
acl_save_exec_prefix="$exec_prefix"
exec_prefix="$acl_final_exec_prefix"
eval additional_includedir=\"$includedir\"
eval additional_libdir=\"$libdir\"
exec_prefix="$acl_save_exec_prefix"
prefix="$acl_save_prefix"
else
additional_includedir="$withval/include"
additional_libdir="$withval/$acl_libdirstem"
fi
fi
fi
LIBINTL=
LTLIBINTL=
INCINTL=
LIBINTL_PREFIX=
rpathdirs=
ltrpathdirs=
names_already_handled=
names_next_round='intl '
while test -n "$names_next_round"; do
names_this_round="$names_next_round"
names_next_round=
for name in $names_this_round; do
already_handled=
for n in $names_already_handled; do
if test "$n" = "$name"; then
already_handled=yes
break
fi
done
if test -z "$already_handled"; then
names_already_handled="$names_already_handled $name"
uppername=`echo "$name" | sed -e 'y|abcdefghijklmnopqrstuvwxyz./-|ABCDEFGHIJKLMNOPQRSTUVWXYZ___|'`
eval value=\"\$HAVE_LIB$uppername\"
if test -n "$value"; then
if test "$value" = yes; then
eval value=\"\$LIB$uppername\"
test -z "$value" || LIBINTL="${LIBINTL}${LIBINTL:+ }$value"
eval value=\"\$LTLIB$uppername\"
test -z "$value" || LTLIBINTL="${LTLIBINTL}${LTLIBINTL:+ }$value"
else
:
fi
else
found_dir=
found_la=
found_so=
found_a=
eval libname=\"$acl_libname_spec\" # typically: libname=lib$name
if test -n "$acl_shlibext"; then
shrext=".$acl_shlibext" # typically: shrext=.so
else
shrext=
fi
if test $use_additional = yes; then
dir="$additional_libdir"
if test -n "$acl_shlibext"; then
if test -f "$dir/$libname$shrext"; then
found_dir="$dir"
found_so="$dir/$libname$shrext"
else
if test "$acl_library_names_spec" = '$libname$shrext$versuffix'; then
ver=`(cd "$dir" && \
for f in "$libname$shrext".*; do echo "$f"; done \
| sed -e "s,^$libname$shrext\\\\.,," \
| sort -t '.' -n -r -k1,1 -k2,2 -k3,3 -k4,4 -k5,5 \
| sed 1q ) 2>/dev/null`
if test -n "$ver" && test -f "$dir/$libname$shrext.$ver"; then
found_dir="$dir"
found_so="$dir/$libname$shrext.$ver"
fi
else
eval library_names=\"$acl_library_names_spec\"
for f in $library_names; do
if test -f "$dir/$f"; then
found_dir="$dir"
found_so="$dir/$f"
break
fi
done
fi
fi
fi
if test "X$found_dir" = "X"; then
if test -f "$dir/$libname.$acl_libext"; then
found_dir="$dir"
found_a="$dir/$libname.$acl_libext"
fi
fi
if test "X$found_dir" != "X"; then
if test -f "$dir/$libname.la"; then
found_la="$dir/$libname.la"
fi
fi
fi
if test "X$found_dir" = "X"; then
for x in $LDFLAGS $LTLIBINTL; do
acl_save_prefix="$prefix"
prefix="$acl_final_prefix"
acl_save_exec_prefix="$exec_prefix"
exec_prefix="$acl_final_exec_prefix"
eval x=\"$x\"
exec_prefix="$acl_save_exec_prefix"
prefix="$acl_save_prefix"
case "$x" in
-L*)
dir=`echo "X$x" | sed -e 's/^X-L//'`
if test -n "$acl_shlibext"; then
if test -f "$dir/$libname$shrext"; then
found_dir="$dir"
found_so="$dir/$libname$shrext"
else
if test "$acl_library_names_spec" = '$libname$shrext$versuffix'; then
ver=`(cd "$dir" && \
for f in "$libname$shrext".*; do echo "$f"; done \
| sed -e "s,^$libname$shrext\\\\.,," \
| sort -t '.' -n -r -k1,1 -k2,2 -k3,3 -k4,4 -k5,5 \
| sed 1q ) 2>/dev/null`
if test -n "$ver" && test -f "$dir/$libname$shrext.$ver"; then
found_dir="$dir"
found_so="$dir/$libname$shrext.$ver"
fi
else
eval library_names=\"$acl_library_names_spec\"
for f in $library_names; do
if test -f "$dir/$f"; then
found_dir="$dir"
found_so="$dir/$f"
break
fi
done
fi
fi
fi
if test "X$found_dir" = "X"; then
if test -f "$dir/$libname.$acl_libext"; then
found_dir="$dir"
found_a="$dir/$libname.$acl_libext"
fi
fi
if test "X$found_dir" != "X"; then
if test -f "$dir/$libname.la"; then
found_la="$dir/$libname.la"
fi
fi
;;
esac
if test "X$found_dir" != "X"; then
break
fi
done
fi
if test "X$found_dir" != "X"; then
LTLIBINTL="${LTLIBINTL}${LTLIBINTL:+ }-L$found_dir -l$name"
if test "X$found_so" != "X"; then
if test "$enable_rpath" = no || test "X$found_dir" = "X/usr/$acl_libdirstem"; then
LIBINTL="${LIBINTL}${LIBINTL:+ }$found_so"
else
haveit=
for x in $ltrpathdirs; do
if test "X$x" = "X$found_dir"; then
haveit=yes
break
fi
done
if test -z "$haveit"; then
ltrpathdirs="$ltrpathdirs $found_dir"
fi
if test "$acl_hardcode_direct" = yes; then
LIBINTL="${LIBINTL}${LIBINTL:+ }$found_so"
else
if test -n "$acl_hardcode_libdir_flag_spec" && test "$acl_hardcode_minus_L" = no; then
LIBINTL="${LIBINTL}${LIBINTL:+ }$found_so"
haveit=
for x in $rpathdirs; do
if test "X$x" = "X$found_dir"; then
haveit=yes
break
fi
done
if test -z "$haveit"; then
rpathdirs="$rpathdirs $found_dir"
fi
else
haveit=
for x in $LDFLAGS $LIBINTL; do
acl_save_prefix="$prefix"
prefix="$acl_final_prefix"
acl_save_exec_prefix="$exec_prefix"
exec_prefix="$acl_final_exec_prefix"
eval x=\"$x\"
exec_prefix="$acl_save_exec_prefix"
prefix="$acl_save_prefix"
if test "X$x" = "X-L$found_dir"; then
haveit=yes
break
fi
done
if test -z "$haveit"; then
LIBINTL="${LIBINTL}${LIBINTL:+ }-L$found_dir"
fi
if test "$acl_hardcode_minus_L" != no; then
LIBINTL="${LIBINTL}${LIBINTL:+ }$found_so"
else
LIBINTL="${LIBINTL}${LIBINTL:+ }-l$name"
fi
fi
fi
fi
else
if test "X$found_a" != "X"; then
LIBINTL="${LIBINTL}${LIBINTL:+ }$found_a"
else
LIBINTL="${LIBINTL}${LIBINTL:+ }-L$found_dir -l$name"
fi
fi
additional_includedir=
case "$found_dir" in
*/$acl_libdirstem | */$acl_libdirstem/)
basedir=`echo "X$found_dir" | sed -e 's,^X,,' -e "s,/$acl_libdirstem/"'*$,,'`
LIBINTL_PREFIX="$basedir"
additional_includedir="$basedir/include"
;;
esac
if test "X$additional_includedir" != "X"; then
if test "X$additional_includedir" != "X/usr/include"; then
haveit=
if test "X$additional_includedir" = "X/usr/local/include"; then
if test -n "$GCC"; then
case $host_os in
linux* | gnu* | k*bsd*-gnu) haveit=yes;;
esac
fi
fi
if test -z "$haveit"; then
for x in $CPPFLAGS $INCINTL; do
acl_save_prefix="$prefix"
prefix="$acl_final_prefix"
acl_save_exec_prefix="$exec_prefix"
exec_prefix="$acl_final_exec_prefix"
eval x=\"$x\"
exec_prefix="$acl_save_exec_prefix"
prefix="$acl_save_prefix"
if test "X$x" = "X-I$additional_includedir"; then
haveit=yes
break
fi
done
if test -z "$haveit"; then
if test -d "$additional_includedir"; then
INCINTL="${INCINTL}${INCINTL:+ }-I$additional_includedir"
fi
fi
fi
fi
fi
if test -n "$found_la"; then
save_libdir="$libdir"
case "$found_la" in
*/* | *\\*) . "$found_la" ;;
*) . "./$found_la" ;;
esac
libdir="$save_libdir"
for dep in $dependency_libs; do
case "$dep" in
-L*)
additional_libdir=`echo "X$dep" | sed -e 's/^X-L//'`
if test "X$additional_libdir" != "X/usr/$acl_libdirstem"; then
haveit=
if test "X$additional_libdir" = "X/usr/local/$acl_libdirstem"; then
if test -n "$GCC"; then
case $host_os in
linux* | gnu* | k*bsd*-gnu) haveit=yes;;
esac
fi
fi
if test -z "$haveit"; then
haveit=
for x in $LDFLAGS $LIBINTL; do
acl_save_prefix="$prefix"
prefix="$acl_final_prefix"
acl_save_exec_prefix="$exec_prefix"
exec_prefix="$acl_final_exec_prefix"
eval x=\"$x\"
exec_prefix="$acl_save_exec_prefix"
prefix="$acl_save_prefix"
if test "X$x" = "X-L$additional_libdir"; then
haveit=yes
break
fi
done
if test -z "$haveit"; then
if test -d "$additional_libdir"; then
LIBINTL="${LIBINTL}${LIBINTL:+ }-L$additional_libdir"
fi
fi
haveit=
for x in $LDFLAGS $LTLIBINTL; do
acl_save_prefix="$prefix"
prefix="$acl_final_prefix"
acl_save_exec_prefix="$exec_prefix"
exec_prefix="$acl_final_exec_prefix"
eval x=\"$x\"
exec_prefix="$acl_save_exec_prefix"
prefix="$acl_save_prefix"
if test "X$x" = "X-L$additional_libdir"; then
haveit=yes
break
fi
done
if test -z "$haveit"; then
if test -d "$additional_libdir"; then
LTLIBINTL="${LTLIBINTL}${LTLIBINTL:+ }-L$additional_libdir"
fi
fi
fi
fi
;;
-R*)
dir=`echo "X$dep" | sed -e 's/^X-R//'`
if test "$enable_rpath" != no; then
haveit=
for x in $rpathdirs; do
if test "X$x" = "X$dir"; then
haveit=yes
break
fi
done
if test -z "$haveit"; then
rpathdirs="$rpathdirs $dir"
fi
haveit=
for x in $ltrpathdirs; do
if test "X$x" = "X$dir"; then
haveit=yes
break
fi
done
if test -z "$haveit"; then
ltrpathdirs="$ltrpathdirs $dir"
fi
fi
;;
-l*)
names_next_round="$names_next_round "`echo "X$dep" | sed -e 's/^X-l//'`
;;
*.la)
names_next_round="$names_next_round "`echo "X$dep" | sed -e 's,^X.*/,,' -e 's,^lib,,' -e 's,\.la$,,'`
;;
*)
LIBINTL="${LIBINTL}${LIBINTL:+ }$dep"
LTLIBINTL="${LTLIBINTL}${LTLIBINTL:+ }$dep"
;;
esac
done
fi
else
LIBINTL="${LIBINTL}${LIBINTL:+ }-l$name"
LTLIBINTL="${LTLIBINTL}${LTLIBINTL:+ }-l$name"
fi
fi
fi
done
done
if test "X$rpathdirs" != "X"; then
if test -n "$acl_hardcode_libdir_separator"; then
alldirs=
for found_dir in $rpathdirs; do
alldirs="${alldirs}${alldirs:+$acl_hardcode_libdir_separator}$found_dir"
done
acl_save_libdir="$libdir"
libdir="$alldirs"
eval flag=\"$acl_hardcode_libdir_flag_spec\"
libdir="$acl_save_libdir"
LIBINTL="${LIBINTL}${LIBINTL:+ }$flag"
else
for found_dir in $rpathdirs; do
acl_save_libdir="$libdir"
libdir="$found_dir"
eval flag=\"$acl_hardcode_libdir_flag_spec\"
libdir="$acl_save_libdir"
LIBINTL="${LIBINTL}${LIBINTL:+ }$flag"
done
fi
fi
if test "X$ltrpathdirs" != "X"; then
for found_dir in $ltrpathdirs; do
LTLIBINTL="${LTLIBINTL}${LTLIBINTL:+ }-R$found_dir"
done
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for GNU gettext in libintl" >&5
$as_echo_n "checking for GNU gettext in libintl... " >&6; }
if eval \${$gt_func_gnugettext_libintl+:} false; then :
$as_echo_n "(cached) " >&6
else
gt_save_CPPFLAGS="$CPPFLAGS"
CPPFLAGS="$CPPFLAGS $INCINTL"
gt_save_LIBS="$LIBS"
LIBS="$LIBS $LIBINTL"
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h. */
#include
$gt_revision_test_code
extern int _nl_msg_cat_cntr;
extern
#ifdef __cplusplus
"C"
#endif
const char *_nl_expand_alias (const char *);
int
main ()
{
bindtextdomain ("", "");
return * gettext ("")$gt_expression_test_code + _nl_msg_cat_cntr + *_nl_expand_alias ("")
;
return 0;
}
_ACEOF
if ac_fn_c_try_link "$LINENO"; then :
eval "$gt_func_gnugettext_libintl=yes"
else
eval "$gt_func_gnugettext_libintl=no"
fi
rm -f core conftest.err conftest.$ac_objext \
conftest$ac_exeext conftest.$ac_ext
if { eval "gt_val=\$$gt_func_gnugettext_libintl"; test "$gt_val" != yes; } && test -n "$LIBICONV"; then
LIBS="$LIBS $LIBICONV"
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h. */
#include
$gt_revision_test_code
extern int _nl_msg_cat_cntr;
extern
#ifdef __cplusplus
"C"
#endif
const char *_nl_expand_alias (const char *);
int
main ()
{
bindtextdomain ("", "");
return * gettext ("")$gt_expression_test_code + _nl_msg_cat_cntr + *_nl_expand_alias ("")
;
return 0;
}
_ACEOF
if ac_fn_c_try_link "$LINENO"; then :
LIBINTL="$LIBINTL $LIBICONV"
LTLIBINTL="$LTLIBINTL $LTLIBICONV"
eval "$gt_func_gnugettext_libintl=yes"
fi
rm -f core conftest.err conftest.$ac_objext \
conftest$ac_exeext conftest.$ac_ext
fi
CPPFLAGS="$gt_save_CPPFLAGS"
LIBS="$gt_save_LIBS"
fi
eval ac_res=\$$gt_func_gnugettext_libintl
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_res" >&5
$as_echo "$ac_res" >&6; }
fi
if { eval "gt_val=\$$gt_func_gnugettext_libc"; test "$gt_val" = "yes"; } \
|| { { eval "gt_val=\$$gt_func_gnugettext_libintl"; test "$gt_val" = "yes"; } \
&& test "$PACKAGE" != gettext-runtime \
&& test "$PACKAGE" != gettext-tools; }; then
gt_use_preinstalled_gnugettext=yes
else
LIBINTL=
LTLIBINTL=
INCINTL=
fi
if test -n "$INTL_MACOSX_LIBS"; then
if test "$gt_use_preinstalled_gnugettext" = "yes" \
|| test "$nls_cv_use_gnu_gettext" = "yes"; then
LIBINTL="$LIBINTL $INTL_MACOSX_LIBS"
LTLIBINTL="$LTLIBINTL $INTL_MACOSX_LIBS"
fi
fi
if test "$gt_use_preinstalled_gnugettext" = "yes" \
|| test "$nls_cv_use_gnu_gettext" = "yes"; then
$as_echo "#define ENABLE_NLS 1" >>confdefs.h
else
USE_NLS=no
fi
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether to use NLS" >&5
$as_echo_n "checking whether to use NLS... " >&6; }
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $USE_NLS" >&5
$as_echo "$USE_NLS" >&6; }
if test "$USE_NLS" = "yes"; then
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking where the gettext function comes from" >&5
$as_echo_n "checking where the gettext function comes from... " >&6; }
if test "$gt_use_preinstalled_gnugettext" = "yes"; then
if { eval "gt_val=\$$gt_func_gnugettext_libintl"; test "$gt_val" = "yes"; }; then
gt_source="external libintl"
else
gt_source="libc"
fi
else
gt_source="included intl directory"
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $gt_source" >&5
$as_echo "$gt_source" >&6; }
fi
if test "$USE_NLS" = "yes"; then
if test "$gt_use_preinstalled_gnugettext" = "yes"; then
if { eval "gt_val=\$$gt_func_gnugettext_libintl"; test "$gt_val" = "yes"; }; then
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking how to link with libintl" >&5
$as_echo_n "checking how to link with libintl... " >&6; }
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $LIBINTL" >&5
$as_echo "$LIBINTL" >&6; }
for element in $INCINTL; do
haveit=
for x in $CPPFLAGS; do
acl_save_prefix="$prefix"
prefix="$acl_final_prefix"
acl_save_exec_prefix="$exec_prefix"
exec_prefix="$acl_final_exec_prefix"
eval x=\"$x\"
exec_prefix="$acl_save_exec_prefix"
prefix="$acl_save_prefix"
if test "X$x" = "X$element"; then
haveit=yes
break
fi
done
if test -z "$haveit"; then
CPPFLAGS="${CPPFLAGS}${CPPFLAGS:+ }$element"
fi
done
fi
$as_echo "#define HAVE_GETTEXT 1" >>confdefs.h
$as_echo "#define HAVE_DCGETTEXT 1" >>confdefs.h
fi
POSUB=po
fi
INTLLIBS="$LIBINTL"
GETTEXT_PACKAGE=jhbuild
cat >>confdefs.h <<_ACEOF
#define GETTEXT_PACKAGE "$GETTEXT_PACKAGE"
_ACEOF
# Documentation
# Check whether --enable-doc_installation was given.
if test "${enable_doc_installation+set}" = set; then :
enableval=$enable_doc_installation; enable_doc_installation=$enableval
else
enable_doc_installation=no
fi
if test "x$enable_doc_installation" = "xyes"; then
DOC_INSTALLATION_ENABLED_TRUE=
DOC_INSTALLATION_ENABLED_FALSE='#'
else
DOC_INSTALLATION_ENABLED_TRUE='#'
DOC_INSTALLATION_ENABLED_FALSE=
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether ln -s works" >&5
$as_echo_n "checking whether ln -s works... " >&6; }
LN_S=$as_ln_s
if test "$LN_S" = "ln -s"; then
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: yes" >&5
$as_echo "yes" >&6; }
else
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no, using $LN_S" >&5
$as_echo "no, using $LN_S" >&6; }
fi
# Check whether --with-help-dir was given.
if test "${with_help_dir+set}" = set; then :
withval=$with_help_dir;
else
with_help_dir='${datadir}/help'
fi
HELP_DIR="$with_help_dir"
# Extract the first word of "itstool", so it can be a program name with args.
set dummy itstool; ac_word=$2
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5
$as_echo_n "checking for $ac_word... " >&6; }
if ${ac_cv_prog_ITSTOOL+:} false; then :
$as_echo_n "(cached) " >&6
else
if test -n "$ITSTOOL"; then
ac_cv_prog_ITSTOOL="$ITSTOOL" # Let the user override the test.
else
as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
for as_dir in $PATH
do
IFS=$as_save_IFS
test -z "$as_dir" && as_dir=.
for ac_exec_ext in '' $ac_executable_extensions; do
if as_fn_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
ac_cv_prog_ITSTOOL="itstool"
$as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5
break 2
fi
done
done
IFS=$as_save_IFS
fi
fi
ITSTOOL=$ac_cv_prog_ITSTOOL
if test -n "$ITSTOOL"; then
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ITSTOOL" >&5
$as_echo "$ITSTOOL" >&6; }
else
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
fi
if test x"$ITSTOOL" = x; then
as_fn_error $? "itstool not found" "$LINENO" 5
fi
# Extract the first word of "xmllint", so it can be a program name with args.
set dummy xmllint; ac_word=$2
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5
$as_echo_n "checking for $ac_word... " >&6; }
if ${ac_cv_prog_XMLLINT+:} false; then :
$as_echo_n "(cached) " >&6
else
if test -n "$XMLLINT"; then
ac_cv_prog_XMLLINT="$XMLLINT" # Let the user override the test.
else
as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
for as_dir in $PATH
do
IFS=$as_save_IFS
test -z "$as_dir" && as_dir=.
for ac_exec_ext in '' $ac_executable_extensions; do
if as_fn_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
ac_cv_prog_XMLLINT="xmllint"
$as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5
break 2
fi
done
done
IFS=$as_save_IFS
fi
fi
XMLLINT=$ac_cv_prog_XMLLINT
if test -n "$XMLLINT"; then
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $XMLLINT" >&5
$as_echo "$XMLLINT" >&6; }
else
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
fi
if test x"$XMLLINT" = x; then
as_fn_error $? "xmllint not found" "$LINENO" 5
fi
YELP_HELP_RULES='
HELP_ID ?=
HELP_POT ?=
HELP_FILES ?=
HELP_EXTRA ?=
HELP_MEDIA ?=
HELP_LINGUAS ?=
_HELP_LINGUAS = $(if $(filter environment,$(origin LINGUAS)),$(filter $(LINGUAS),$(HELP_LINGUAS)),$(HELP_LINGUAS))
_HELP_POTFILE = $(if $(HELP_POT),$(HELP_POT),$(if $(HELP_ID),$(HELP_ID).pot))
_HELP_POFILES = $(if $(HELP_ID),$(foreach lc,$(_HELP_LINGUAS),$(lc)/$(lc).po))
_HELP_MOFILES = $(patsubst %.po,%.mo,$(_HELP_POFILES))
_HELP_C_FILES = $(foreach f,$(HELP_FILES),C/$(f))
_HELP_C_EXTRA = $(foreach f,$(HELP_EXTRA),C/$(f))
_HELP_C_MEDIA = $(foreach f,$(HELP_MEDIA),C/$(f))
_HELP_LC_FILES = $(foreach lc,$(_HELP_LINGUAS),$(foreach f,$(HELP_FILES),$(lc)/$(f)))
_HELP_LC_STAMPS = $(foreach lc,$(_HELP_LINGUAS),$(lc)/$(lc).stamp)
_HELP_DEFAULT_V = $(if $(AM_DEFAULT_VERBOSITY),$(AM_DEFAULT_VERBOSITY),1)
_HELP_V = $(if $(V),$(V),$(_HELP_DEFAULT_V))
_HELP_LC_VERBOSE = $(_HELP_LC_VERBOSE_$(_HELP_V))
_HELP_LC_VERBOSE_ = $(_HELP_LC_VERBOSE_$(_HELP_DEFAULT_V))
_HELP_LC_VERBOSE_0 = @echo " GEN "$(dir $@);
all: $(_HELP_C_FILES) $(_HELP_C_EXTRA) $(_HELP_C_MEDIA) $(_HELP_LC_FILES) $(_HELP_POFILES)
.PHONY: pot
pot: $(_HELP_POTFILE)
$(_HELP_POTFILE): $(_HELP_C_FILES) $(_HELP_C_EXTRA) $(_HELP_C_MEDIA)
$(AM_V_GEN)$(ITSTOOL) -o "$@" $(_HELP_C_FILES)
.PHONY: repo
repo: $(_HELP_POTFILE)
$(AM_V_at)for po in $(_HELP_POFILES); do \
if test "x$(_HELP_V)" = "x0"; then echo " GEN $${po}"; fi; \
msgmerge -q -o "$${po}" "$${po}" "$(_HELP_POTFILE)"; \
done
$(_HELP_POFILES):
$(AM_V_at)if ! test -d "$(dir $@)"; then mkdir "$(dir $@)"; fi
$(AM_V_at)if test ! -f "$@" -a -f "$(srcdir)/$@"; then cp "$(srcdir)/$@" "$@"; fi
$(AM_V_GEN)if ! test -f "$@"; then \
(cd "$(dir $@)" && \
$(ITSTOOL) -o "$(notdir $@).tmp" $(_HELP_C_FILES) && \
mv "$(notdir $@).tmp" "$(notdir $@)"); \
else \
(cd "$(dir $@)" && \
$(ITSTOOL) -o "$(notdir $@).tmp" $(_HELP_C_FILES) && \
msgmerge -o "$(notdir $@)" "$(notdir $@)" "$(notdir $@).tmp" && \
rm "$(notdir $@).tmp"); \
fi
$(_HELP_MOFILES): %.mo: %.po
$(AM_V_at)if ! test -d "$(dir $@)"; then mkdir "$(dir $@)"; fi
$(AM_V_GEN)msgfmt -o "$@" "$<"
$(_HELP_LC_FILES): $(_HELP_LINGUAS)
$(_HELP_LINGUAS): $(_HELP_LC_STAMPS)
$(_HELP_LC_STAMPS): %.stamp: %.mo
$(_HELP_LC_STAMPS): $(_HELP_C_FILES) $(_HELP_C_EXTRA)
$(AM_V_at)if ! test -d "$(dir $@)"; then mkdir "$(dir $@)"; fi
$(_HELP_LC_VERBOSE)if test -d "C"; then d="../"; else d="$(abs_srcdir)/"; fi; \
mo="$(dir $@)$(patsubst %/$(notdir $@),%,$@).mo"; \
if test -f "$${mo}"; then mo="../$${mo}"; else mo="$(abs_srcdir)/$${mo}"; fi; \
(cd "$(dir $@)" && $(ITSTOOL) -m "$${mo}" $(foreach f,$(_HELP_C_FILES),$${d}/$(f))) && \
touch "$@"
.PHONY: clean-help
mostlyclean-am: $(if $(HELP_ID),clean-help)
clean-help:
rm -f $(_HELP_LC_FILES) $(_HELP_LC_STAMPS) $(_HELP_MOFILES)
EXTRA_DIST ?=
EXTRA_DIST += $(_HELP_C_EXTRA) $(_HELP_C_MEDIA)
EXTRA_DIST += $(foreach lc,$(HELP_LINGUAS),$(lc)/$(lc).stamp)
EXTRA_DIST += $(foreach lc,$(HELP_LINGUAS),$(lc)/$(lc).po)
EXTRA_DIST += $(foreach f,$(HELP_MEDIA),$(foreach lc,$(HELP_LINGUAS),$(wildcard $(lc)/$(f))))
distdir: distdir-help-files
distdir-help-files:
@for lc in C $(HELP_LINGUAS); do \
$(MKDIR_P) "$(distdir)/$$lc"; \
for file in $(HELP_FILES); do \
if test -f "$$lc/$$file"; then d=./; else d=$(srcdir)/; fi; \
cp -p "$$d$$lc/$$file" "$(distdir)/$$lc/" || exit 1; \
done; \
done; \
.PHONY: check-help
check: check-help
check-help:
for lc in C $(_HELP_LINGUAS); do \
if test -d "$$lc"; \
then d=; \
xmlpath="$$lc"; \
else \
d="$(srcdir)/"; \
xmlpath="$$lc:$(srcdir)/$$lc"; \
fi; \
for page in $(HELP_FILES); do \
echo "$(XMLLINT) --noout --noent --path $$xmlpath --xinclude $$d$$lc/$$page"; \
$(XMLLINT) --noout --noent --path "$$xmlpath" --xinclude "$$d$$lc/$$page"; \
done; \
done
.PHONY: install-help
install-data-am: $(if $(HELP_ID),install-help)
install-help:
@for lc in C $(_HELP_LINGUAS); do \
$(mkinstalldirs) "$(DESTDIR)$(HELP_DIR)/$$lc/$(HELP_ID)" || exit 1; \
done
@for lc in C $(_HELP_LINGUAS); do for f in $(HELP_FILES); do \
if test -f "$$lc/$$f"; then d=; else d="$(srcdir)/"; fi; \
helpdir="$(DESTDIR)$(HELP_DIR)/$$lc/$(HELP_ID)/"; \
if ! test -d "$$helpdir"; then $(mkinstalldirs) "$$helpdir"; fi; \
echo "$(INSTALL_DATA) $$d$$lc/$$f $$helpdir`basename $$f`"; \
$(INSTALL_DATA) "$$d$$lc/$$f" "$$helpdir`basename $$f`" || exit 1; \
done; done
@for f in $(_HELP_C_EXTRA); do \
lc=`dirname "$$f"`; lc=`basename "$$lc"`; \
if test -f "$$f"; then d=; else d="$(srcdir)/"; fi; \
helpdir="$(DESTDIR)$(HELP_DIR)/$$lc/$(HELP_ID)/"; \
if ! test -d "$$helpdir"; then $(mkinstalldirs) "$$helpdir"; fi; \
echo "$(INSTALL_DATA) $$d$$f $$helpdir`basename $$f`"; \
$(INSTALL_DATA) "$$d$$f" "$$helpdir`basename $$f`" || exit 1; \
done
@for f in $(HELP_MEDIA); do \
for lc in C $(_HELP_LINGUAS); do \
if test -f "$$lc$$f"; then d=; else d="$(srcdir)/"; fi; \
helpdir="$(DESTDIR)$(HELP_DIR)/$$lc/$(HELP_ID)/"; \
mdir=`dirname "$$f"`; \
if test "x$mdir" = "x."; then mdir=""; fi; \
if ! test -d "$$helpdir$$mdir"; then $(mkinstalldirs) "$$helpdir$$mdir"; fi; \
if test -f "$$d$$lc/$$f"; then \
echo "$(INSTALL_DATA) $$d$$lc/$$f $$helpdir$$f"; \
$(INSTALL_DATA) "$$d$$lc/$$f" "$$helpdir$$f" || exit 1; \
elif test "x$$lc" != "xC"; then \
echo "$(LN_S) -f $(HELP_DIR)/C/$(HELP_ID)/$$f $$helpdir$$f"; \
$(LN_S) -f "$(HELP_DIR)/C/$(HELP_ID)/$$f" "$$helpdir$$f" || exit 1; \
fi; \
done; \
done
.PHONY: uninstall-help
uninstall-am: $(if $(HELP_ID),uninstall-help)
uninstall-help:
for lc in C $(_HELP_LINGUAS); do for f in $(HELP_FILES); do \
helpdir="$(DESTDIR)$(HELP_DIR)/$$lc/$(HELP_ID)/"; \
echo "rm -f $$helpdir`basename $$f`"; \
rm -f "$$helpdir`basename $$f`"; \
done; done
@for f in $(_HELP_C_EXTRA); do \
lc=`dirname "$$f"`; lc=`basename "$$lc"`; \
helpdir="$(DESTDIR)$(HELP_DIR)/$$lc/$(HELP_ID)/"; \
echo "rm -f $$helpdir`basename $$f`"; \
rm -f "$$helpdir`basename $$f`"; \
done
@for f in $(HELP_MEDIA); do \
for lc in C $(_HELP_LINGUAS); do \
helpdir="$(DESTDIR)$(HELP_DIR)/$$lc/$(HELP_ID)/"; \
echo "rm -f $$helpdir$$f"; \
rm -f "$$helpdir$$f"; \
done; \
done;
'
ac_config_files="$ac_config_files Makefile doc/Makefile po/Makefile.in examples/Makefile scripts/Makefile triggers/Makefile jhbuild.desktop.in jhbuild/Makefile jhbuild/buildbot/Makefile jhbuild/buildbot/status/web/Makefile jhbuild/buildbot/status/Makefile jhbuild/commands/Makefile jhbuild/cut_n_paste/Makefile jhbuild/frontends/Makefile jhbuild/modtypes/Makefile jhbuild/utils/Makefile jhbuild/versioncontrol/Makefile buildbot/Makefile"
cat >confcache <<\_ACEOF
# This file is a shell script that caches the results of configure
# tests run on this system so they can be shared between configure
# scripts and configure runs, see configure's option --config-cache.
# It is not useful on other systems. If it contains results you don't
# want to keep, you may remove or edit it.
#
# config.status only pays attention to the cache file if you give it
# the --recheck option to rerun configure.
#
# `ac_cv_env_foo' variables (set or unset) will be overridden when
# loading this file, other *unset* `ac_cv_foo' will be assigned the
# following values.
_ACEOF
# The following way of writing the cache mishandles newlines in values,
# but we know of no workaround that is simple, portable, and efficient.
# So, we kill variables containing newlines.
# Ultrix sh set writes to stderr and can't be redirected directly,
# and sets the high bit in the cache file unless we assign to the vars.
(
for ac_var in `(set) 2>&1 | sed -n 's/^\([a-zA-Z_][a-zA-Z0-9_]*\)=.*/\1/p'`; do
eval ac_val=\$$ac_var
case $ac_val in #(
*${as_nl}*)
case $ac_var in #(
*_cv_*) { $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: cache variable $ac_var contains a newline" >&5
$as_echo "$as_me: WARNING: cache variable $ac_var contains a newline" >&2;} ;;
esac
case $ac_var in #(
_ | IFS | as_nl) ;; #(
BASH_ARGV | BASH_SOURCE) eval $ac_var= ;; #(
*) { eval $ac_var=; unset $ac_var;} ;;
esac ;;
esac
done
(set) 2>&1 |
case $as_nl`(ac_space=' '; set) 2>&1` in #(
*${as_nl}ac_space=\ *)
# `set' does not quote correctly, so add quotes: double-quote
# substitution turns \\\\ into \\, and sed turns \\ into \.
sed -n \
"s/'/'\\\\''/g;
s/^\\([_$as_cr_alnum]*_cv_[_$as_cr_alnum]*\\)=\\(.*\\)/\\1='\\2'/p"
;; #(
*)
# `set' quotes correctly as required by POSIX, so do not add quotes.
sed -n "/^[_$as_cr_alnum]*_cv_[_$as_cr_alnum]*=/p"
;;
esac |
sort
) |
sed '
/^ac_cv_env_/b end
t clear
:clear
s/^\([^=]*\)=\(.*[{}].*\)$/test "${\1+set}" = set || &/
t end
s/^\([^=]*\)=\(.*\)$/\1=${\1=\2}/
:end' >>confcache
if diff "$cache_file" confcache >/dev/null 2>&1; then :; else
if test -w "$cache_file"; then
if test "x$cache_file" != "x/dev/null"; then
{ $as_echo "$as_me:${as_lineno-$LINENO}: updating cache $cache_file" >&5
$as_echo "$as_me: updating cache $cache_file" >&6;}
if test ! -f "$cache_file" || test -h "$cache_file"; then
cat confcache >"$cache_file"
else
case $cache_file in #(
*/* | ?:*)
mv -f confcache "$cache_file"$$ &&
mv -f "$cache_file"$$ "$cache_file" ;; #(
*)
mv -f confcache "$cache_file" ;;
esac
fi
fi
else
{ $as_echo "$as_me:${as_lineno-$LINENO}: not updating unwritable cache $cache_file" >&5
$as_echo "$as_me: not updating unwritable cache $cache_file" >&6;}
fi
fi
rm -f confcache
test "x$prefix" = xNONE && prefix=$ac_default_prefix
# Let make expand exec_prefix.
test "x$exec_prefix" = xNONE && exec_prefix='${prefix}'
# Transform confdefs.h into DEFS.
# Protect against shell expansion while executing Makefile rules.
# Protect against Makefile macro expansion.
#
# If the first sed substitution is executed (which looks for macros that
# take arguments), then branch to the quote section. Otherwise,
# look for a macro that doesn't take arguments.
ac_script='
:mline
/\\$/{
N
s,\\\n,,
b mline
}
t clear
:clear
s/^[ ]*#[ ]*define[ ][ ]*\([^ (][^ (]*([^)]*)\)[ ]*\(.*\)/-D\1=\2/g
t quote
s/^[ ]*#[ ]*define[ ][ ]*\([^ ][^ ]*\)[ ]*\(.*\)/-D\1=\2/g
t quote
b any
:quote
s/[ `~#$^&*(){}\\|;'\''"<>?]/\\&/g
s/\[/\\&/g
s/\]/\\&/g
s/\$/$$/g
H
:any
${
g
s/^\n//
s/\n/ /g
p
}
'
DEFS=`sed -n "$ac_script" confdefs.h`
ac_libobjs=
ac_ltlibobjs=
U=
for ac_i in : $LIBOBJS; do test "x$ac_i" = x: && continue
# 1. Remove the extension, and $U if already installed.
ac_script='s/\$U\././;s/\.o$//;s/\.obj$//'
ac_i=`$as_echo "$ac_i" | sed "$ac_script"`
# 2. Prepend LIBOBJDIR. When used with automake>=1.10 LIBOBJDIR
# will be set to the directory where LIBOBJS objects are built.
as_fn_append ac_libobjs " \${LIBOBJDIR}$ac_i\$U.$ac_objext"
as_fn_append ac_ltlibobjs " \${LIBOBJDIR}$ac_i"'$U.lo'
done
LIBOBJS=$ac_libobjs
LTLIBOBJS=$ac_ltlibobjs
if test -n "$EXEEXT"; then
am__EXEEXT_TRUE=
am__EXEEXT_FALSE='#'
else
am__EXEEXT_TRUE='#'
am__EXEEXT_FALSE=
fi
if test -z "${MAINTAINER_MODE_TRUE}" && test -z "${MAINTAINER_MODE_FALSE}"; then
as_fn_error $? "conditional \"MAINTAINER_MODE\" was never defined.
Usually this means the macro was only invoked conditionally." "$LINENO" 5
fi
if test -z "${AMDEP_TRUE}" && test -z "${AMDEP_FALSE}"; then
as_fn_error $? "conditional \"AMDEP\" was never defined.
Usually this means the macro was only invoked conditionally." "$LINENO" 5
fi
if test -z "${am__fastdepCC_TRUE}" && test -z "${am__fastdepCC_FALSE}"; then
as_fn_error $? "conditional \"am__fastdepCC\" was never defined.
Usually this means the macro was only invoked conditionally." "$LINENO" 5
fi
ac_config_commands="$ac_config_commands po/stamp-it"
if test -z "${DOC_INSTALLATION_ENABLED_TRUE}" && test -z "${DOC_INSTALLATION_ENABLED_FALSE}"; then
as_fn_error $? "conditional \"DOC_INSTALLATION_ENABLED\" was never defined.
Usually this means the macro was only invoked conditionally." "$LINENO" 5
fi
: "${CONFIG_STATUS=./config.status}"
ac_write_fail=0
ac_clean_files_save=$ac_clean_files
ac_clean_files="$ac_clean_files $CONFIG_STATUS"
{ $as_echo "$as_me:${as_lineno-$LINENO}: creating $CONFIG_STATUS" >&5
$as_echo "$as_me: creating $CONFIG_STATUS" >&6;}
as_write_fail=0
cat >$CONFIG_STATUS <<_ASEOF || as_write_fail=1
#! $SHELL
# Generated by $as_me.
# Run this file to recreate the current configuration.
# Compiler output produced by configure, useful for debugging
# configure, is in config.log if it exists.
debug=false
ac_cs_recheck=false
ac_cs_silent=false
SHELL=\${CONFIG_SHELL-$SHELL}
export SHELL
_ASEOF
cat >>$CONFIG_STATUS <<\_ASEOF || as_write_fail=1
## -------------------- ##
## M4sh Initialization. ##
## -------------------- ##
# Be more Bourne compatible
DUALCASE=1; export DUALCASE # for MKS sh
if test -n "${ZSH_VERSION+set}" && (emulate sh) >/dev/null 2>&1; then :
emulate sh
NULLCMD=:
# Pre-4.2 versions of Zsh do word splitting on ${1+"$@"}, which
# is contrary to our usage. Disable this feature.
alias -g '${1+"$@"}'='"$@"'
setopt NO_GLOB_SUBST
else
case `(set -o) 2>/dev/null` in #(
*posix*) :
set -o posix ;; #(
*) :
;;
esac
fi
as_nl='
'
export as_nl
# Printing a long string crashes Solaris 7 /usr/bin/printf.
as_echo='\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\'
as_echo=$as_echo$as_echo$as_echo$as_echo$as_echo
as_echo=$as_echo$as_echo$as_echo$as_echo$as_echo$as_echo
# Prefer a ksh shell builtin over an external printf program on Solaris,
# but without wasting forks for bash or zsh.
if test -z "$BASH_VERSION$ZSH_VERSION" \
&& (test "X`print -r -- $as_echo`" = "X$as_echo") 2>/dev/null; then
as_echo='print -r --'
as_echo_n='print -rn --'
elif (test "X`printf %s $as_echo`" = "X$as_echo") 2>/dev/null; then
as_echo='printf %s\n'
as_echo_n='printf %s'
else
if test "X`(/usr/ucb/echo -n -n $as_echo) 2>/dev/null`" = "X-n $as_echo"; then
as_echo_body='eval /usr/ucb/echo -n "$1$as_nl"'
as_echo_n='/usr/ucb/echo -n'
else
as_echo_body='eval expr "X$1" : "X\\(.*\\)"'
as_echo_n_body='eval
arg=$1;
case $arg in #(
*"$as_nl"*)
expr "X$arg" : "X\\(.*\\)$as_nl";
arg=`expr "X$arg" : ".*$as_nl\\(.*\\)"`;;
esac;
expr "X$arg" : "X\\(.*\\)" | tr -d "$as_nl"
'
export as_echo_n_body
as_echo_n='sh -c $as_echo_n_body as_echo'
fi
export as_echo_body
as_echo='sh -c $as_echo_body as_echo'
fi
# The user is always right.
if test "${PATH_SEPARATOR+set}" != set; then
PATH_SEPARATOR=:
(PATH='/bin;/bin'; FPATH=$PATH; sh -c :) >/dev/null 2>&1 && {
(PATH='/bin:/bin'; FPATH=$PATH; sh -c :) >/dev/null 2>&1 ||
PATH_SEPARATOR=';'
}
fi
# IFS
# We need space, tab and new line, in precisely that order. Quoting is
# there to prevent editors from complaining about space-tab.
# (If _AS_PATH_WALK were called with IFS unset, it would disable word
# splitting by setting IFS to empty value.)
IFS=" "" $as_nl"
# Find who we are. Look in the path if we contain no directory separator.
as_myself=
case $0 in #((
*[\\/]* ) as_myself=$0 ;;
*) as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
for as_dir in $PATH
do
IFS=$as_save_IFS
test -z "$as_dir" && as_dir=.
test -r "$as_dir/$0" && as_myself=$as_dir/$0 && break
done
IFS=$as_save_IFS
;;
esac
# We did not find ourselves, most probably we were run as `sh COMMAND'
# in which case we are not to be found in the path.
if test "x$as_myself" = x; then
as_myself=$0
fi
if test ! -f "$as_myself"; then
$as_echo "$as_myself: error: cannot find myself; rerun with an absolute file name" >&2
exit 1
fi
# Unset variables that we do not need and which cause bugs (e.g. in
# pre-3.0 UWIN ksh). But do not cause bugs in bash 2.01; the "|| exit 1"
# suppresses any "Segmentation fault" message there. '((' could
# trigger a bug in pdksh 5.2.14.
for as_var in BASH_ENV ENV MAIL MAILPATH
do eval test x\${$as_var+set} = xset \
&& ( (unset $as_var) || exit 1) >/dev/null 2>&1 && unset $as_var || :
done
PS1='$ '
PS2='> '
PS4='+ '
# NLS nuisances.
LC_ALL=C
export LC_ALL
LANGUAGE=C
export LANGUAGE
# CDPATH.
(unset CDPATH) >/dev/null 2>&1 && unset CDPATH
# as_fn_error STATUS ERROR [LINENO LOG_FD]
# ----------------------------------------
# Output "`basename $0`: error: ERROR" to stderr. If LINENO and LOG_FD are
# provided, also output the error to LOG_FD, referencing LINENO. Then exit the
# script with STATUS, using 1 if that was 0.
as_fn_error ()
{
as_status=$1; test $as_status -eq 0 && as_status=1
if test "$4"; then
as_lineno=${as_lineno-"$3"} as_lineno_stack=as_lineno_stack=$as_lineno_stack
$as_echo "$as_me:${as_lineno-$LINENO}: error: $2" >&$4
fi
$as_echo "$as_me: error: $2" >&2
as_fn_exit $as_status
} # as_fn_error
# as_fn_set_status STATUS
# -----------------------
# Set $? to STATUS, without forking.
as_fn_set_status ()
{
return $1
} # as_fn_set_status
# as_fn_exit STATUS
# -----------------
# Exit the shell with STATUS, even in a "trap 0" or "set -e" context.
as_fn_exit ()
{
set +e
as_fn_set_status $1
exit $1
} # as_fn_exit
# as_fn_unset VAR
# ---------------
# Portably unset VAR.
as_fn_unset ()
{
{ eval $1=; unset $1;}
}
as_unset=as_fn_unset
# as_fn_append VAR VALUE
# ----------------------
# Append the text in VALUE to the end of the definition contained in VAR. Take
# advantage of any shell optimizations that allow amortized linear growth over
# repeated appends, instead of the typical quadratic growth present in naive
# implementations.
if (eval "as_var=1; as_var+=2; test x\$as_var = x12") 2>/dev/null; then :
eval 'as_fn_append ()
{
eval $1+=\$2
}'
else
as_fn_append ()
{
eval $1=\$$1\$2
}
fi # as_fn_append
# as_fn_arith ARG...
# ------------------
# Perform arithmetic evaluation on the ARGs, and store the result in the
# global $as_val. Take advantage of shells that can avoid forks. The arguments
# must be portable across $(()) and expr.
if (eval "test \$(( 1 + 1 )) = 2") 2>/dev/null; then :
eval 'as_fn_arith ()
{
as_val=$(( $* ))
}'
else
as_fn_arith ()
{
as_val=`expr "$@" || test $? -eq 1`
}
fi # as_fn_arith
if expr a : '\(a\)' >/dev/null 2>&1 &&
test "X`expr 00001 : '.*\(...\)'`" = X001; then
as_expr=expr
else
as_expr=false
fi
if (basename -- /) >/dev/null 2>&1 && test "X`basename -- / 2>&1`" = "X/"; then
as_basename=basename
else
as_basename=false
fi
if (as_dir=`dirname -- /` && test "X$as_dir" = X/) >/dev/null 2>&1; then
as_dirname=dirname
else
as_dirname=false
fi
as_me=`$as_basename -- "$0" ||
$as_expr X/"$0" : '.*/\([^/][^/]*\)/*$' \| \
X"$0" : 'X\(//\)$' \| \
X"$0" : 'X\(/\)' \| . 2>/dev/null ||
$as_echo X/"$0" |
sed '/^.*\/\([^/][^/]*\)\/*$/{
s//\1/
q
}
/^X\/\(\/\/\)$/{
s//\1/
q
}
/^X\/\(\/\).*/{
s//\1/
q
}
s/.*/./; q'`
# Avoid depending upon Character Ranges.
as_cr_letters='abcdefghijklmnopqrstuvwxyz'
as_cr_LETTERS='ABCDEFGHIJKLMNOPQRSTUVWXYZ'
as_cr_Letters=$as_cr_letters$as_cr_LETTERS
as_cr_digits='0123456789'
as_cr_alnum=$as_cr_Letters$as_cr_digits
ECHO_C= ECHO_N= ECHO_T=
case `echo -n x` in #(((((
-n*)
case `echo 'xy\c'` in
*c*) ECHO_T=' ';; # ECHO_T is single tab character.
xy) ECHO_C='\c';;
*) echo `echo ksh88 bug on AIX 6.1` > /dev/null
ECHO_T=' ';;
esac;;
*)
ECHO_N='-n';;
esac
rm -f conf$$ conf$$.exe conf$$.file
if test -d conf$$.dir; then
rm -f conf$$.dir/conf$$.file
else
rm -f conf$$.dir
mkdir conf$$.dir 2>/dev/null
fi
if (echo >conf$$.file) 2>/dev/null; then
if ln -s conf$$.file conf$$ 2>/dev/null; then
as_ln_s='ln -s'
# ... but there are two gotchas:
# 1) On MSYS, both `ln -s file dir' and `ln file dir' fail.
# 2) DJGPP < 2.04 has no symlinks; `ln -s' creates a wrapper executable.
# In both cases, we have to default to `cp -pR'.
ln -s conf$$.file conf$$.dir 2>/dev/null && test ! -f conf$$.exe ||
as_ln_s='cp -pR'
elif ln conf$$.file conf$$ 2>/dev/null; then
as_ln_s=ln
else
as_ln_s='cp -pR'
fi
else
as_ln_s='cp -pR'
fi
rm -f conf$$ conf$$.exe conf$$.dir/conf$$.file conf$$.file
rmdir conf$$.dir 2>/dev/null
# as_fn_mkdir_p
# -------------
# Create "$as_dir" as a directory, including parents if necessary.
as_fn_mkdir_p ()
{
case $as_dir in #(
-*) as_dir=./$as_dir;;
esac
test -d "$as_dir" || eval $as_mkdir_p || {
as_dirs=
while :; do
case $as_dir in #(
*\'*) as_qdir=`$as_echo "$as_dir" | sed "s/'/'\\\\\\\\''/g"`;; #'(
*) as_qdir=$as_dir;;
esac
as_dirs="'$as_qdir' $as_dirs"
as_dir=`$as_dirname -- "$as_dir" ||
$as_expr X"$as_dir" : 'X\(.*[^/]\)//*[^/][^/]*/*$' \| \
X"$as_dir" : 'X\(//\)[^/]' \| \
X"$as_dir" : 'X\(//\)$' \| \
X"$as_dir" : 'X\(/\)' \| . 2>/dev/null ||
$as_echo X"$as_dir" |
sed '/^X\(.*[^/]\)\/\/*[^/][^/]*\/*$/{
s//\1/
q
}
/^X\(\/\/\)[^/].*/{
s//\1/
q
}
/^X\(\/\/\)$/{
s//\1/
q
}
/^X\(\/\).*/{
s//\1/
q
}
s/.*/./; q'`
test -d "$as_dir" && break
done
test -z "$as_dirs" || eval "mkdir $as_dirs"
} || test -d "$as_dir" || as_fn_error $? "cannot create directory $as_dir"
} # as_fn_mkdir_p
if mkdir -p . 2>/dev/null; then
as_mkdir_p='mkdir -p "$as_dir"'
else
test -d ./-p && rmdir ./-p
as_mkdir_p=false
fi
# as_fn_executable_p FILE
# -----------------------
# Test if FILE is an executable regular file.
as_fn_executable_p ()
{
test -f "$1" && test -x "$1"
} # as_fn_executable_p
as_test_x='test -x'
as_executable_p=as_fn_executable_p
# Sed expression to map a string onto a valid CPP name.
as_tr_cpp="eval sed 'y%*$as_cr_letters%P$as_cr_LETTERS%;s%[^_$as_cr_alnum]%_%g'"
# Sed expression to map a string onto a valid variable name.
as_tr_sh="eval sed 'y%*+%pp%;s%[^_$as_cr_alnum]%_%g'"
exec 6>&1
## ----------------------------------- ##
## Main body of $CONFIG_STATUS script. ##
## ----------------------------------- ##
_ASEOF
test $as_write_fail = 0 && chmod +x $CONFIG_STATUS || ac_write_fail=1
cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1
# Save the log message, to keep $0 and so on meaningful, and to
# report actual input values of CONFIG_FILES etc. instead of their
# values after options handling.
ac_log="
This file was extended by jhbuild $as_me 3.5.91, which was
generated by GNU Autoconf 2.69. Invocation command line was
CONFIG_FILES = $CONFIG_FILES
CONFIG_HEADERS = $CONFIG_HEADERS
CONFIG_LINKS = $CONFIG_LINKS
CONFIG_COMMANDS = $CONFIG_COMMANDS
$ $0 $@
on `(hostname || uname -n) 2>/dev/null | sed 1q`
"
_ACEOF
case $ac_config_files in *"
"*) set x $ac_config_files; shift; ac_config_files=$*;;
esac
cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1
# Files that config.status was made for.
config_files="$ac_config_files"
config_commands="$ac_config_commands"
_ACEOF
cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1
ac_cs_usage="\
\`$as_me' instantiates files and other configuration actions
from templates according to the current configuration. Unless the files
and actions are specified as TAGs, all are instantiated by default.
Usage: $0 [OPTION]... [TAG]...
-h, --help print this help, then exit
-V, --version print version number and configuration settings, then exit
--config print configuration, then exit
-q, --quiet, --silent
do not print progress messages
-d, --debug don't remove temporary files
--recheck update $as_me by reconfiguring in the same conditions
--file=FILE[:TEMPLATE]
instantiate the configuration file FILE
Configuration files:
$config_files
Configuration commands:
$config_commands
Report bugs to ."
_ACEOF
cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1
ac_cs_config="`$as_echo "$ac_configure_args" | sed 's/^ //; s/[\\""\`\$]/\\\\&/g'`"
ac_cs_version="\\
jhbuild config.status 3.5.91
configured by $0, generated by GNU Autoconf 2.69,
with options \\"\$ac_cs_config\\"
Copyright (C) 2012 Free Software Foundation, Inc.
This config.status script is free software; the Free Software Foundation
gives unlimited permission to copy, distribute and modify it."
ac_pwd='$ac_pwd'
srcdir='$srcdir'
INSTALL='$INSTALL'
MKDIR_P='$MKDIR_P'
AWK='$AWK'
test -n "\$AWK" || AWK=awk
_ACEOF
cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1
# The default lists apply if the user does not specify any file.
ac_need_defaults=:
while test $# != 0
do
case $1 in
--*=?*)
ac_option=`expr "X$1" : 'X\([^=]*\)='`
ac_optarg=`expr "X$1" : 'X[^=]*=\(.*\)'`
ac_shift=:
;;
--*=)
ac_option=`expr "X$1" : 'X\([^=]*\)='`
ac_optarg=
ac_shift=:
;;
*)
ac_option=$1
ac_optarg=$2
ac_shift=shift
;;
esac
case $ac_option in
# Handling of the options.
-recheck | --recheck | --rechec | --reche | --rech | --rec | --re | --r)
ac_cs_recheck=: ;;
--version | --versio | --versi | --vers | --ver | --ve | --v | -V )
$as_echo "$ac_cs_version"; exit ;;
--config | --confi | --conf | --con | --co | --c )
$as_echo "$ac_cs_config"; exit ;;
--debug | --debu | --deb | --de | --d | -d )
debug=: ;;
--file | --fil | --fi | --f )
$ac_shift
case $ac_optarg in
*\'*) ac_optarg=`$as_echo "$ac_optarg" | sed "s/'/'\\\\\\\\''/g"` ;;
'') as_fn_error $? "missing file argument" ;;
esac
as_fn_append CONFIG_FILES " '$ac_optarg'"
ac_need_defaults=false;;
--he | --h | --help | --hel | -h )
$as_echo "$ac_cs_usage"; exit ;;
-q | -quiet | --quiet | --quie | --qui | --qu | --q \
| -silent | --silent | --silen | --sile | --sil | --si | --s)
ac_cs_silent=: ;;
# This is an error.
-*) as_fn_error $? "unrecognized option: \`$1'
Try \`$0 --help' for more information." ;;
*) as_fn_append ac_config_targets " $1"
ac_need_defaults=false ;;
esac
shift
done
ac_configure_extra_args=
if $ac_cs_silent; then
exec 6>/dev/null
ac_configure_extra_args="$ac_configure_extra_args --silent"
fi
_ACEOF
cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1
if \$ac_cs_recheck; then
set X $SHELL '$0' $ac_configure_args \$ac_configure_extra_args --no-create --no-recursion
shift
\$as_echo "running CONFIG_SHELL=$SHELL \$*" >&6
CONFIG_SHELL='$SHELL'
export CONFIG_SHELL
exec "\$@"
fi
_ACEOF
cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1
exec 5>>config.log
{
echo
sed 'h;s/./-/g;s/^.../## /;s/...$/ ##/;p;x;p;x' <<_ASBOX
## Running $as_me. ##
_ASBOX
$as_echo "$ac_log"
} >&5
_ACEOF
cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1
#
# INIT-COMMANDS
#
AMDEP_TRUE="$AMDEP_TRUE" ac_aux_dir="$ac_aux_dir"
# Capture the value of obsolete ALL_LINGUAS because we need it to compute
# POFILES, UPDATEPOFILES, DUMMYPOFILES, GMOFILES, CATALOGS. But hide it
# from automake < 1.5.
eval 'OBSOLETE_ALL_LINGUAS''="$ALL_LINGUAS"'
# Capture the value of LINGUAS because we need it to compute CATALOGS.
LINGUAS="${LINGUAS-%UNSET%}"
_ACEOF
cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1
# Handling of arguments.
for ac_config_target in $ac_config_targets
do
case $ac_config_target in
"depfiles") CONFIG_COMMANDS="$CONFIG_COMMANDS depfiles" ;;
"po-directories") CONFIG_COMMANDS="$CONFIG_COMMANDS po-directories" ;;
"Makefile") CONFIG_FILES="$CONFIG_FILES Makefile" ;;
"doc/Makefile") CONFIG_FILES="$CONFIG_FILES doc/Makefile" ;;
"po/Makefile.in") CONFIG_FILES="$CONFIG_FILES po/Makefile.in" ;;
"examples/Makefile") CONFIG_FILES="$CONFIG_FILES examples/Makefile" ;;
"scripts/Makefile") CONFIG_FILES="$CONFIG_FILES scripts/Makefile" ;;
"triggers/Makefile") CONFIG_FILES="$CONFIG_FILES triggers/Makefile" ;;
"jhbuild.desktop.in") CONFIG_FILES="$CONFIG_FILES jhbuild.desktop.in" ;;
"jhbuild/Makefile") CONFIG_FILES="$CONFIG_FILES jhbuild/Makefile" ;;
"jhbuild/buildbot/Makefile") CONFIG_FILES="$CONFIG_FILES jhbuild/buildbot/Makefile" ;;
"jhbuild/buildbot/status/web/Makefile") CONFIG_FILES="$CONFIG_FILES jhbuild/buildbot/status/web/Makefile" ;;
"jhbuild/buildbot/status/Makefile") CONFIG_FILES="$CONFIG_FILES jhbuild/buildbot/status/Makefile" ;;
"jhbuild/commands/Makefile") CONFIG_FILES="$CONFIG_FILES jhbuild/commands/Makefile" ;;
"jhbuild/cut_n_paste/Makefile") CONFIG_FILES="$CONFIG_FILES jhbuild/cut_n_paste/Makefile" ;;
"jhbuild/frontends/Makefile") CONFIG_FILES="$CONFIG_FILES jhbuild/frontends/Makefile" ;;
"jhbuild/modtypes/Makefile") CONFIG_FILES="$CONFIG_FILES jhbuild/modtypes/Makefile" ;;
"jhbuild/utils/Makefile") CONFIG_FILES="$CONFIG_FILES jhbuild/utils/Makefile" ;;
"jhbuild/versioncontrol/Makefile") CONFIG_FILES="$CONFIG_FILES jhbuild/versioncontrol/Makefile" ;;
"buildbot/Makefile") CONFIG_FILES="$CONFIG_FILES buildbot/Makefile" ;;
"po/stamp-it") CONFIG_COMMANDS="$CONFIG_COMMANDS po/stamp-it" ;;
*) as_fn_error $? "invalid argument: \`$ac_config_target'" "$LINENO" 5;;
esac
done
# If the user did not use the arguments to specify the items to instantiate,
# then the envvar interface is used. Set only those that are not.
# We use the long form for the default assignment because of an extremely
# bizarre bug on SunOS 4.1.3.
if $ac_need_defaults; then
test "${CONFIG_FILES+set}" = set || CONFIG_FILES=$config_files
test "${CONFIG_COMMANDS+set}" = set || CONFIG_COMMANDS=$config_commands
fi
# Have a temporary directory for convenience. Make it in the build tree
# simply because there is no reason against having it here, and in addition,
# creating and moving files from /tmp can sometimes cause problems.
# Hook for its removal unless debugging.
# Note that there is a small window in which the directory will not be cleaned:
# after its creation but before its name has been assigned to `$tmp'.
$debug ||
{
tmp= ac_tmp=
trap 'exit_status=$?
: "${ac_tmp:=$tmp}"
{ test ! -d "$ac_tmp" || rm -fr "$ac_tmp"; } && exit $exit_status
' 0
trap 'as_fn_exit 1' 1 2 13 15
}
# Create a (secure) tmp directory for tmp files.
{
tmp=`(umask 077 && mktemp -d "./confXXXXXX") 2>/dev/null` &&
test -d "$tmp"
} ||
{
tmp=./conf$$-$RANDOM
(umask 077 && mkdir "$tmp")
} || as_fn_error $? "cannot create a temporary directory in ." "$LINENO" 5
ac_tmp=$tmp
# Set up the scripts for CONFIG_FILES section.
# No need to generate them if there are no CONFIG_FILES.
# This happens for instance with `./config.status config.h'.
if test -n "$CONFIG_FILES"; then
ac_cr=`echo X | tr X '\015'`
# On cygwin, bash can eat \r inside `` if the user requested igncr.
# But we know of no other shell where ac_cr would be empty at this
# point, so we can use a bashism as a fallback.
if test "x$ac_cr" = x; then
eval ac_cr=\$\'\\r\'
fi
ac_cs_awk_cr=`$AWK 'BEGIN { print "a\rb" }' /dev/null`
if test "$ac_cs_awk_cr" = "a${ac_cr}b"; then
ac_cs_awk_cr='\\r'
else
ac_cs_awk_cr=$ac_cr
fi
echo 'BEGIN {' >"$ac_tmp/subs1.awk" &&
_ACEOF
{
echo "cat >conf$$subs.awk <<_ACEOF" &&
echo "$ac_subst_vars" | sed 's/.*/&!$&$ac_delim/' &&
echo "_ACEOF"
} >conf$$subs.sh ||
as_fn_error $? "could not make $CONFIG_STATUS" "$LINENO" 5
ac_delim_num=`echo "$ac_subst_vars" | grep -c '^'`
ac_delim='%!_!# '
for ac_last_try in false false false false false :; do
. ./conf$$subs.sh ||
as_fn_error $? "could not make $CONFIG_STATUS" "$LINENO" 5
ac_delim_n=`sed -n "s/.*$ac_delim\$/X/p" conf$$subs.awk | grep -c X`
if test $ac_delim_n = $ac_delim_num; then
break
elif $ac_last_try; then
as_fn_error $? "could not make $CONFIG_STATUS" "$LINENO" 5
else
ac_delim="$ac_delim!$ac_delim _$ac_delim!! "
fi
done
rm -f conf$$subs.sh
cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1
cat >>"\$ac_tmp/subs1.awk" <<\\_ACAWK &&
_ACEOF
sed -n '
h
s/^/S["/; s/!.*/"]=/
p
g
s/^[^!]*!//
:repl
t repl
s/'"$ac_delim"'$//
t delim
:nl
h
s/\(.\{148\}\)..*/\1/
t more1
s/["\\]/\\&/g; s/^/"/; s/$/\\n"\\/
p
n
b repl
:more1
s/["\\]/\\&/g; s/^/"/; s/$/"\\/
p
g
s/.\{148\}//
t nl
:delim
h
s/\(.\{148\}\)..*/\1/
t more2
s/["\\]/\\&/g; s/^/"/; s/$/"/
p
b
:more2
s/["\\]/\\&/g; s/^/"/; s/$/"\\/
p
g
s/.\{148\}//
t delim
' >$CONFIG_STATUS || ac_write_fail=1
rm -f conf$$subs.awk
cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1
_ACAWK
cat >>"\$ac_tmp/subs1.awk" <<_ACAWK &&
for (key in S) S_is_set[key] = 1
FS = ""
}
{
line = $ 0
nfields = split(line, field, "@")
substed = 0
len = length(field[1])
for (i = 2; i < nfields; i++) {
key = field[i]
keylen = length(key)
if (S_is_set[key]) {
value = S[key]
line = substr(line, 1, len) "" value "" substr(line, len + keylen + 3)
len += length(value) + length(field[++i])
substed = 1
} else
len += 1 + keylen
}
print line
}
_ACAWK
_ACEOF
cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1
if sed "s/$ac_cr//" < /dev/null > /dev/null 2>&1; then
sed "s/$ac_cr\$//; s/$ac_cr/$ac_cs_awk_cr/g"
else
cat
fi < "$ac_tmp/subs1.awk" > "$ac_tmp/subs.awk" \
|| as_fn_error $? "could not setup config files machinery" "$LINENO" 5
_ACEOF
# VPATH may cause trouble with some makes, so we remove sole $(srcdir),
# ${srcdir} and @srcdir@ entries from VPATH if srcdir is ".", strip leading and
# trailing colons and then remove the whole line if VPATH becomes empty
# (actually we leave an empty line to preserve line numbers).
if test "x$srcdir" = x.; then
ac_vpsub='/^[ ]*VPATH[ ]*=[ ]*/{
h
s///
s/^/:/
s/[ ]*$/:/
s/:\$(srcdir):/:/g
s/:\${srcdir}:/:/g
s/:@srcdir@:/:/g
s/^:*//
s/:*$//
x
s/\(=[ ]*\).*/\1/
G
s/\n//
s/^[^=]*=[ ]*$//
}'
fi
cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1
fi # test -n "$CONFIG_FILES"
eval set X " :F $CONFIG_FILES :C $CONFIG_COMMANDS"
shift
for ac_tag
do
case $ac_tag in
:[FHLC]) ac_mode=$ac_tag; continue;;
esac
case $ac_mode$ac_tag in
:[FHL]*:*);;
:L* | :C*:*) as_fn_error $? "invalid tag \`$ac_tag'" "$LINENO" 5;;
:[FH]-) ac_tag=-:-;;
:[FH]*) ac_tag=$ac_tag:$ac_tag.in;;
esac
ac_save_IFS=$IFS
IFS=:
set x $ac_tag
IFS=$ac_save_IFS
shift
ac_file=$1
shift
case $ac_mode in
:L) ac_source=$1;;
:[FH])
ac_file_inputs=
for ac_f
do
case $ac_f in
-) ac_f="$ac_tmp/stdin";;
*) # Look for the file first in the build tree, then in the source tree
# (if the path is not absolute). The absolute path cannot be DOS-style,
# because $ac_f cannot contain `:'.
test -f "$ac_f" ||
case $ac_f in
[\\/$]*) false;;
*) test -f "$srcdir/$ac_f" && ac_f="$srcdir/$ac_f";;
esac ||
as_fn_error 1 "cannot find input file: \`$ac_f'" "$LINENO" 5;;
esac
case $ac_f in *\'*) ac_f=`$as_echo "$ac_f" | sed "s/'/'\\\\\\\\''/g"`;; esac
as_fn_append ac_file_inputs " '$ac_f'"
done
# Let's still pretend it is `configure' which instantiates (i.e., don't
# use $as_me), people would be surprised to read:
# /* config.h. Generated by config.status. */
configure_input='Generated from '`
$as_echo "$*" | sed 's|^[^:]*/||;s|:[^:]*/|, |g'
`' by configure.'
if test x"$ac_file" != x-; then
configure_input="$ac_file. $configure_input"
{ $as_echo "$as_me:${as_lineno-$LINENO}: creating $ac_file" >&5
$as_echo "$as_me: creating $ac_file" >&6;}
fi
# Neutralize special characters interpreted by sed in replacement strings.
case $configure_input in #(
*\&* | *\|* | *\\* )
ac_sed_conf_input=`$as_echo "$configure_input" |
sed 's/[\\\\&|]/\\\\&/g'`;; #(
*) ac_sed_conf_input=$configure_input;;
esac
case $ac_tag in
*:-:* | *:-) cat >"$ac_tmp/stdin" \
|| as_fn_error $? "could not create $ac_file" "$LINENO" 5 ;;
esac
;;
esac
ac_dir=`$as_dirname -- "$ac_file" ||
$as_expr X"$ac_file" : 'X\(.*[^/]\)//*[^/][^/]*/*$' \| \
X"$ac_file" : 'X\(//\)[^/]' \| \
X"$ac_file" : 'X\(//\)$' \| \
X"$ac_file" : 'X\(/\)' \| . 2>/dev/null ||
$as_echo X"$ac_file" |
sed '/^X\(.*[^/]\)\/\/*[^/][^/]*\/*$/{
s//\1/
q
}
/^X\(\/\/\)[^/].*/{
s//\1/
q
}
/^X\(\/\/\)$/{
s//\1/
q
}
/^X\(\/\).*/{
s//\1/
q
}
s/.*/./; q'`
as_dir="$ac_dir"; as_fn_mkdir_p
ac_builddir=.
case "$ac_dir" in
.) ac_dir_suffix= ac_top_builddir_sub=. ac_top_build_prefix= ;;
*)
ac_dir_suffix=/`$as_echo "$ac_dir" | sed 's|^\.[\\/]||'`
# A ".." for each directory in $ac_dir_suffix.
ac_top_builddir_sub=`$as_echo "$ac_dir_suffix" | sed 's|/[^\\/]*|/..|g;s|/||'`
case $ac_top_builddir_sub in
"") ac_top_builddir_sub=. ac_top_build_prefix= ;;
*) ac_top_build_prefix=$ac_top_builddir_sub/ ;;
esac ;;
esac
ac_abs_top_builddir=$ac_pwd
ac_abs_builddir=$ac_pwd$ac_dir_suffix
# for backward compatibility:
ac_top_builddir=$ac_top_build_prefix
case $srcdir in
.) # We are building in place.
ac_srcdir=.
ac_top_srcdir=$ac_top_builddir_sub
ac_abs_top_srcdir=$ac_pwd ;;
[\\/]* | ?:[\\/]* ) # Absolute name.
ac_srcdir=$srcdir$ac_dir_suffix;
ac_top_srcdir=$srcdir
ac_abs_top_srcdir=$srcdir ;;
*) # Relative name.
ac_srcdir=$ac_top_build_prefix$srcdir$ac_dir_suffix
ac_top_srcdir=$ac_top_build_prefix$srcdir
ac_abs_top_srcdir=$ac_pwd/$srcdir ;;
esac
ac_abs_srcdir=$ac_abs_top_srcdir$ac_dir_suffix
case $ac_mode in
:F)
#
# CONFIG_FILE
#
case $INSTALL in
[\\/$]* | ?:[\\/]* ) ac_INSTALL=$INSTALL ;;
*) ac_INSTALL=$ac_top_build_prefix$INSTALL ;;
esac
ac_MKDIR_P=$MKDIR_P
case $MKDIR_P in
[\\/$]* | ?:[\\/]* ) ;;
*/*) ac_MKDIR_P=$ac_top_build_prefix$MKDIR_P ;;
esac
_ACEOF
cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1
# If the template does not know about datarootdir, expand it.
# FIXME: This hack should be removed a few years after 2.60.
ac_datarootdir_hack=; ac_datarootdir_seen=
ac_sed_dataroot='
/datarootdir/ {
p
q
}
/@datadir@/p
/@docdir@/p
/@infodir@/p
/@localedir@/p
/@mandir@/p'
case `eval "sed -n \"\$ac_sed_dataroot\" $ac_file_inputs"` in
*datarootdir*) ac_datarootdir_seen=yes;;
*@datadir@*|*@docdir@*|*@infodir@*|*@localedir@*|*@mandir@*)
{ $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: $ac_file_inputs seems to ignore the --datarootdir setting" >&5
$as_echo "$as_me: WARNING: $ac_file_inputs seems to ignore the --datarootdir setting" >&2;}
_ACEOF
cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1
ac_datarootdir_hack='
s&@datadir@&$datadir&g
s&@docdir@&$docdir&g
s&@infodir@&$infodir&g
s&@localedir@&$localedir&g
s&@mandir@&$mandir&g
s&\\\${datarootdir}&$datarootdir&g' ;;
esac
_ACEOF
# Neutralize VPATH when `$srcdir' = `.'.
# Shell code in configure.ac might set extrasub.
# FIXME: do we really want to maintain this feature?
cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1
ac_sed_extra="$ac_vpsub
$extrasub
_ACEOF
cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1
:t
/@[a-zA-Z_][a-zA-Z_0-9]*@/!b
s|@configure_input@|$ac_sed_conf_input|;t t
s&@top_builddir@&$ac_top_builddir_sub&;t t
s&@top_build_prefix@&$ac_top_build_prefix&;t t
s&@srcdir@&$ac_srcdir&;t t
s&@abs_srcdir@&$ac_abs_srcdir&;t t
s&@top_srcdir@&$ac_top_srcdir&;t t
s&@abs_top_srcdir@&$ac_abs_top_srcdir&;t t
s&@builddir@&$ac_builddir&;t t
s&@abs_builddir@&$ac_abs_builddir&;t t
s&@abs_top_builddir@&$ac_abs_top_builddir&;t t
s&@INSTALL@&$ac_INSTALL&;t t
s&@MKDIR_P@&$ac_MKDIR_P&;t t
$ac_datarootdir_hack
"
eval sed \"\$ac_sed_extra\" "$ac_file_inputs" | $AWK -f "$ac_tmp/subs.awk" \
>$ac_tmp/out || as_fn_error $? "could not create $ac_file" "$LINENO" 5
test -z "$ac_datarootdir_hack$ac_datarootdir_seen" &&
{ ac_out=`sed -n '/\${datarootdir}/p' "$ac_tmp/out"`; test -n "$ac_out"; } &&
{ ac_out=`sed -n '/^[ ]*datarootdir[ ]*:*=/p' \
"$ac_tmp/out"`; test -z "$ac_out"; } &&
{ $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: $ac_file contains a reference to the variable \`datarootdir'
which seems to be undefined. Please make sure it is defined" >&5
$as_echo "$as_me: WARNING: $ac_file contains a reference to the variable \`datarootdir'
which seems to be undefined. Please make sure it is defined" >&2;}
rm -f "$ac_tmp/stdin"
case $ac_file in
-) cat "$ac_tmp/out" && rm -f "$ac_tmp/out";;
*) rm -f "$ac_file" && mv "$ac_tmp/out" "$ac_file";;
esac \
|| as_fn_error $? "could not create $ac_file" "$LINENO" 5
;;
:C) { $as_echo "$as_me:${as_lineno-$LINENO}: executing $ac_file commands" >&5
$as_echo "$as_me: executing $ac_file commands" >&6;}
;;
esac
case $ac_file$ac_mode in
"depfiles":C) test x"$AMDEP_TRUE" != x"" || {
# Autoconf 2.62 quotes --file arguments for eval, but not when files
# are listed without --file. Let's play safe and only enable the eval
# if we detect the quoting.
case $CONFIG_FILES in
*\'*) eval set x "$CONFIG_FILES" ;;
*) set x $CONFIG_FILES ;;
esac
shift
for mf
do
# Strip MF so we end up with the name of the file.
mf=`echo "$mf" | sed -e 's/:.*$//'`
# Check whether this is an Automake generated Makefile or not.
# We used to match only the files named `Makefile.in', but
# some people rename them; so instead we look at the file content.
# Grep'ing the first line is not enough: some people post-process
# each Makefile.in and add a new line on top of each file to say so.
# Grep'ing the whole file is not good either: AIX grep has a line
# limit of 2048, but all sed's we know have understand at least 4000.
if sed -n 's,^#.*generated by automake.*,X,p' "$mf" | grep X >/dev/null 2>&1; then
dirpart=`$as_dirname -- "$mf" ||
$as_expr X"$mf" : 'X\(.*[^/]\)//*[^/][^/]*/*$' \| \
X"$mf" : 'X\(//\)[^/]' \| \
X"$mf" : 'X\(//\)$' \| \
X"$mf" : 'X\(/\)' \| . 2>/dev/null ||
$as_echo X"$mf" |
sed '/^X\(.*[^/]\)\/\/*[^/][^/]*\/*$/{
s//\1/
q
}
/^X\(\/\/\)[^/].*/{
s//\1/
q
}
/^X\(\/\/\)$/{
s//\1/
q
}
/^X\(\/\).*/{
s//\1/
q
}
s/.*/./; q'`
else
continue
fi
# Extract the definition of DEPDIR, am__include, and am__quote
# from the Makefile without running `make'.
DEPDIR=`sed -n 's/^DEPDIR = //p' < "$mf"`
test -z "$DEPDIR" && continue
am__include=`sed -n 's/^am__include = //p' < "$mf"`
test -z "am__include" && continue
am__quote=`sed -n 's/^am__quote = //p' < "$mf"`
# When using ansi2knr, U may be empty or an underscore; expand it
U=`sed -n 's/^U = //p' < "$mf"`
# Find all dependency output files, they are included files with
# $(DEPDIR) in their names. We invoke sed twice because it is the
# simplest approach to changing $(DEPDIR) to its actual value in the
# expansion.
for file in `sed -n "
s/^$am__include $am__quote\(.*(DEPDIR).*\)$am__quote"'$/\1/p' <"$mf" | \
sed -e 's/\$(DEPDIR)/'"$DEPDIR"'/g' -e 's/\$U/'"$U"'/g'`; do
# Make sure the directory exists.
test -f "$dirpart/$file" && continue
fdir=`$as_dirname -- "$file" ||
$as_expr X"$file" : 'X\(.*[^/]\)//*[^/][^/]*/*$' \| \
X"$file" : 'X\(//\)[^/]' \| \
X"$file" : 'X\(//\)$' \| \
X"$file" : 'X\(/\)' \| . 2>/dev/null ||
$as_echo X"$file" |
sed '/^X\(.*[^/]\)\/\/*[^/][^/]*\/*$/{
s//\1/
q
}
/^X\(\/\/\)[^/].*/{
s//\1/
q
}
/^X\(\/\/\)$/{
s//\1/
q
}
/^X\(\/\).*/{
s//\1/
q
}
s/.*/./; q'`
as_dir=$dirpart/$fdir; as_fn_mkdir_p
# echo "creating $dirpart/$file"
echo '# dummy' > "$dirpart/$file"
done
done
}
;;
"po-directories":C)
for ac_file in $CONFIG_FILES; do
# Support "outfile[:infile[:infile...]]"
case "$ac_file" in
*:*) ac_file=`echo "$ac_file"|sed 's%:.*%%'` ;;
esac
# PO directories have a Makefile.in generated from Makefile.in.in.
case "$ac_file" in */Makefile.in)
# Adjust a relative srcdir.
ac_dir=`echo "$ac_file"|sed 's%/[^/][^/]*$%%'`
ac_dir_suffix="/`echo "$ac_dir"|sed 's%^\./%%'`"
ac_dots=`echo "$ac_dir_suffix"|sed 's%/[^/]*%../%g'`
# In autoconf-2.13 it is called $ac_given_srcdir.
# In autoconf-2.50 it is called $srcdir.
test -n "$ac_given_srcdir" || ac_given_srcdir="$srcdir"
case "$ac_given_srcdir" in
.) top_srcdir=`echo $ac_dots|sed 's%/$%%'` ;;
/*) top_srcdir="$ac_given_srcdir" ;;
*) top_srcdir="$ac_dots$ac_given_srcdir" ;;
esac
# Treat a directory as a PO directory if and only if it has a
# POTFILES.in file. This allows packages to have multiple PO
# directories under different names or in different locations.
if test -f "$ac_given_srcdir/$ac_dir/POTFILES.in"; then
rm -f "$ac_dir/POTFILES"
test -n "$as_me" && echo "$as_me: creating $ac_dir/POTFILES" || echo "creating $ac_dir/POTFILES"
cat "$ac_given_srcdir/$ac_dir/POTFILES.in" | sed -e "/^#/d" -e "/^[ ]*\$/d" -e "s,.*, $top_srcdir/& \\\\," | sed -e "\$s/\(.*\) \\\\/\1/" > "$ac_dir/POTFILES"
POMAKEFILEDEPS="POTFILES.in"
# ALL_LINGUAS, POFILES, UPDATEPOFILES, DUMMYPOFILES, GMOFILES depend
# on $ac_dir but don't depend on user-specified configuration
# parameters.
if test -f "$ac_given_srcdir/$ac_dir/LINGUAS"; then
# The LINGUAS file contains the set of available languages.
if test -n "$OBSOLETE_ALL_LINGUAS"; then
test -n "$as_me" && echo "$as_me: setting ALL_LINGUAS in configure.in is obsolete" || echo "setting ALL_LINGUAS in configure.in is obsolete"
fi
ALL_LINGUAS_=`sed -e "/^#/d" -e "s/#.*//" "$ac_given_srcdir/$ac_dir/LINGUAS"`
# Hide the ALL_LINGUAS assigment from automake < 1.5.
eval 'ALL_LINGUAS''=$ALL_LINGUAS_'
POMAKEFILEDEPS="$POMAKEFILEDEPS LINGUAS"
else
# The set of available languages was given in configure.in.
# Hide the ALL_LINGUAS assigment from automake < 1.5.
eval 'ALL_LINGUAS''=$OBSOLETE_ALL_LINGUAS'
fi
# Compute POFILES
# as $(foreach lang, $(ALL_LINGUAS), $(srcdir)/$(lang).po)
# Compute UPDATEPOFILES
# as $(foreach lang, $(ALL_LINGUAS), $(lang).po-update)
# Compute DUMMYPOFILES
# as $(foreach lang, $(ALL_LINGUAS), $(lang).nop)
# Compute GMOFILES
# as $(foreach lang, $(ALL_LINGUAS), $(srcdir)/$(lang).gmo)
case "$ac_given_srcdir" in
.) srcdirpre= ;;
*) srcdirpre='$(srcdir)/' ;;
esac
POFILES=
UPDATEPOFILES=
DUMMYPOFILES=
GMOFILES=
for lang in $ALL_LINGUAS; do
POFILES="$POFILES $srcdirpre$lang.po"
UPDATEPOFILES="$UPDATEPOFILES $lang.po-update"
DUMMYPOFILES="$DUMMYPOFILES $lang.nop"
GMOFILES="$GMOFILES $srcdirpre$lang.gmo"
done
# CATALOGS depends on both $ac_dir and the user's LINGUAS
# environment variable.
INST_LINGUAS=
if test -n "$ALL_LINGUAS"; then
for presentlang in $ALL_LINGUAS; do
useit=no
if test "%UNSET%" != "$LINGUAS"; then
desiredlanguages="$LINGUAS"
else
desiredlanguages="$ALL_LINGUAS"
fi
for desiredlang in $desiredlanguages; do
# Use the presentlang catalog if desiredlang is
# a. equal to presentlang, or
# b. a variant of presentlang (because in this case,
# presentlang can be used as a fallback for messages
# which are not translated in the desiredlang catalog).
case "$desiredlang" in
"$presentlang"*) useit=yes;;
esac
done
if test $useit = yes; then
INST_LINGUAS="$INST_LINGUAS $presentlang"
fi
done
fi
CATALOGS=
if test -n "$INST_LINGUAS"; then
for lang in $INST_LINGUAS; do
CATALOGS="$CATALOGS $lang.gmo"
done
fi
test -n "$as_me" && echo "$as_me: creating $ac_dir/Makefile" || echo "creating $ac_dir/Makefile"
sed -e "/^POTFILES =/r $ac_dir/POTFILES" -e "/^# Makevars/r $ac_given_srcdir/$ac_dir/Makevars" -e "s|@POFILES@|$POFILES|g" -e "s|@UPDATEPOFILES@|$UPDATEPOFILES|g" -e "s|@DUMMYPOFILES@|$DUMMYPOFILES|g" -e "s|@GMOFILES@|$GMOFILES|g" -e "s|@CATALOGS@|$CATALOGS|g" -e "s|@POMAKEFILEDEPS@|$POMAKEFILEDEPS|g" "$ac_dir/Makefile.in" > "$ac_dir/Makefile"
for f in "$ac_given_srcdir/$ac_dir"/Rules-*; do
if test -f "$f"; then
case "$f" in
*.orig | *.bak | *~) ;;
*) cat "$f" >> "$ac_dir/Makefile" ;;
esac
fi
done
fi
;;
esac
done ;;
"po/stamp-it":C)
if ! grep "^# INTLTOOL_MAKEFILE$" "po/Makefile.in" > /dev/null ; then
as_fn_error $? "po/Makefile.in.in was not created by intltoolize." "$LINENO" 5
fi
rm -f "po/stamp-it" "po/stamp-it.tmp" "po/POTFILES" "po/Makefile.tmp"
>"po/stamp-it.tmp"
sed '/^#/d
s/^[[].*] *//
/^[ ]*$/d
'"s|^| $ac_top_srcdir/|" \
"$srcdir/po/POTFILES.in" | sed '$!s/$/ \\/' >"po/POTFILES"
sed '/^POTFILES =/,/[^\\]$/ {
/^POTFILES =/!d
r po/POTFILES
}
' "po/Makefile.in" >"po/Makefile"
rm -f "po/Makefile.tmp"
mv "po/stamp-it.tmp" "po/stamp-it"
;;
esac
done # for ac_tag
as_fn_exit 0
_ACEOF
ac_clean_files=$ac_clean_files_save
test $ac_write_fail = 0 ||
as_fn_error $? "write failure creating $CONFIG_STATUS" "$LINENO" 5
# configure is writing to config.log, and then calls config.status.
# config.status does its own redirection, appending to config.log.
# Unfortunately, on DOS this fails, as config.log is still kept open
# by configure, so config.status won't be able to write to it; its
# output is simply discarded. So we exec the FD to /dev/null,
# effectively closing config.log, so it can be properly (re)opened and
# appended to by config.status. When coming back to configure, we
# need to make the FD available again.
if test "$no_create" != yes; then
ac_cs_success=:
ac_config_status_args=
test "$silent" = yes &&
ac_config_status_args="$ac_config_status_args --quiet"
exec 5>/dev/null
$SHELL $CONFIG_STATUS $ac_config_status_args || ac_cs_success=false
exec 5>>config.log
# Use ||, not &&, to avoid exiting from the if with $? = 1, which
# would make configure fail if this is the last instruction.
$ac_cs_success || as_fn_exit 1
fi
if test -n "$ac_unrecognized_opts" && test "$enable_option_checking" != no; then
{ $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: unrecognized options: $ac_unrecognized_opts" >&5
$as_echo "$as_me: WARNING: unrecognized options: $ac_unrecognized_opts" >&2;}
fi
jhbuild-3.5.91/doc/ 0000755 0001750 0001750 00000000000 12021725614 013721 5 ustar 00fred fred 0000000 0000000 jhbuild-3.5.91/doc/sv/ 0000755 0001750 0001750 00000000000 12021725615 014352 5 ustar 00fred fred 0000000 0000000 jhbuild-3.5.91/doc/sv/index.docbook 0000644 0001750 0001750 00000363125 11743103647 017042 0 ustar 00fred fred 0000000 0000000
Handbok för JHBuild
James
Henstridge
C.J.
Adams-Collier
Frederic
Peters
David
Turner
2004, 2008
James Henstridge
JHBuild Manual v0.5
January 2008
JHBuild Manual v0.1
August 2007
JHBuild is a tool used to build the whole GNOME desktop from the
version control system. JHBuild can also be customized to build other
projects too.
Introduktion
JHBuild is a tool designed to ease building collections of source
packages, called modules
. JHBuild uses module
set
files to describe the modules available to build. The
module set
files include dependency information that allows
JHBuild to discover what modules need to be built and in what order.
JHBuild was originally written for building
GNOME , but has since been
extended to be usable with other projects. A module set
file can be hosted on a web server, allowing for build rules independent
of the JHBuild project.
JHBuild can build modules from a variety of sources, including
CVS ,
Subversion ,
Bazaar ,
Darcs ,
Git and
Mercurial
repositories, as well as Tar and Zip archives hosted on web or FTP sites.
JHBuild can build modules using a variety of build systems, including
Autotools, CMake, WAF, Python Distutils and Perl Makefiles.
JHBuild is not intended as a replacement for the distribution's
package management system. Instead, it makes it easy to build software
into a separate install prefix without interfering with the rest of the
system.
Komma igång
JHBuild requires a few set up steps to be run before building
software. JHBuild requires some prerequisite software, and it is necessary
to install prerequisite tools needed to obtain and build the software
modules.
Installera JHBuild
JHBuild requires a Python runtime. Verify Python >= 2.3 is
installed.
The recommended way to download JHBuild is via the version control
system, git . This can be achieved with the following
command. It is recommended to run the command from a new directory where
all source code will be installed, for example,
~/checkout/gnome .
$ git clone git://git.gnome.org/jhbuild
...
$ This will download JHBuild into a new folder named
jhbuild under the current directory. Now to build
and install JHBuild:
$ cd jhbuild
$ ./autogen.sh
...
$ make
...
$ make install
...
$ If gnome-common ,
yelp-tools and
autotools are available,
autogen.sh will configure JHBuild to install via
autotools . If
gnome-common ,
yelp-tools and
autotools are not available,
autogen.sh will configure JHBuild to install via a
plain Makefile. To always use the plain Makefile method pass
--simple-install to autogen.sh .
If the above steps complete successfully, a small shell script
will be installed in ~/.local/bin to start JHBuild.
Add ~/.local/bin to the PATH :
$ PATH=$PATH:~/.local/bin
$ To permanently add ~/.local/bin to the
PATH variable, run the following command:
$ echo PATH=$PATH:~/.local/bin >> ~/.bashrc
$
Before running JHBuild, it is necessary to set up a configuration
file located at ~/.jhbuildrc .
Build Prerequisites
Before any modules can be built, it is necessary to have certain
build tools installed. Common build tools include the GNU Autotools
(autoconf ,
automake , libtool
and gettext ), The GNU Toolchain
(binutils , gcc ,
g++ ), make, pkg-config and Python, depending
on which modules will be built.
JHBuild can check the tools are installed using the
sanitycheck command:
$ jhbuild sanitycheck If this command displays any messages, the errors can be fixed in
one of two ways:
Install the required package from your distribution's
repository. A list of
package
names for different distributions is maintained on the GNOME
wiki. Run the sanitycheck command again after
installing the distribution's packages to ensure the required tools
are present.
Run the bootstrap command to download,
build and install the build prerequisites:
$ jhbuild bootstrap When complete, run the sanitycheck command
to verify the required tools are present.
The bootstrap command does not build all
the package dependencies required by the build tools. If your
distribution does not provide the required packages, they will
need to be built outside of the JHBuild environment.
The build tools dependencies include
m4 , perl and
a C compiler (for example, gcc ).
Using JHBuild
After set up is complete, JHBuild can be used to build software.
To build all the modules selected in the
~/.jhbuildrc file, run the following command:
$ jhbuild build JHBuild will download, configure, compile and install each of the
modules. If an error occurs at any stage, JHBuild will present a menu
asking what to do. The choices include dropping to a shell to fix the
error, rerunning the build from various stages, giving up on the module,
or ignore the error and continue.
Giving up on a module will cause any modules depending on the
module to fail.
Below is an example of the menu displayed:
[1] Rerun phase build
[2] Ignore error and continue to install
[3] Give up on module
[4] Start shell
[5] Reload configuration
[6] Go to phase "wipe directory and start over"
[7] Go to phase "configure"
[8] Go to phase "clean"
[9] Go to phase "distclean"
choice:
It is also possible to build a different set of modules and their
dependencies by passing the module names as arguments to the
build command. For example, to build gtk+:
$ jhbuild build gtk+ If JHBuild is cancelled part way through a build, it is possible
to resume the build at a particular module using the
--start-at option:
$ jhbuild build --start-at=pango To build one or more modules, ignoring their dependencies, JHBuild
provides the buildone command. For the
buildone command to complete successfully, all
dependencies must be previously built and installed or provided by
distribution packages.
$ jhbuild buildone gtk+ When actively developing a module, you are likely in a source
working directory. The make will invoke the build
system and install the module. This will be a key part of your
edit-compile-install-test cycle.
$ jhbuild make If JHBuild is cancelled part way through a build, it is possible
to resume the build at a particular module using the
--start-at option:
To get a list of the modules and dependencies JHBuild will build,
and the order they will be built, use the list
command:
$ jhbuild list To get information about a particular module, use the
info command:
$ jhbuild info gtk+ To download or update all the software sources without building,
use the update command. The update
command provides an opportunity to modify the sources before building
and can be useful if internet bandwidth varies.
$ jhbuild update Later, JHBuild can build everything without downloading or
updating the sources:
$ jhbuild build --no-network To run a particular command with the same environment used by
JHBuild, use the run command:
$ jhbuild run program To start a shell with the same environment used by JHBuild, use
the shell command:
$ jhbuild shell
JHBuild and GNOME
This section provides guidance on building, installing and running
GNOME.
Building GNOME
To build GNOME some development packages are required. This
includes:
DocBook XML DTD and XSLT stylesheets. These need to be
registered in the XML catalog
(/etc/xml/catalog ).
X libraries
libsmbclient from Samba (used for
browsing Windows networks).
libbz2 from bzip2.
libpng , libjpeg
and libtiff (used for image loading).
If installing distribution packages, and if applicable for your
distribution, install the corresponding dev
or
devel
packages. A list of
package
names for different distributions is maintained on the GNOME
wiki.
Running a Single GNOME Application
This section details how to run a single GNOME application. The
application will run within the current desktop environment. To run the
application within the complete JHBuild GNOME see
Launch a JHBuild shell. The JHBuild shell has all the necessary
environment variables set.
$ jhbuild shell Verify the correct application will be run. For example:
$ which gedit
/opt/gnome/bin/geditRun the application:
$ gedit & Alternatively, run the application using the
run command:
$ jhbuild run gedit
Running the GNOME Desktop Environment
Create a new user account to run the JHBuild GNOME. Running
JHBuild GNOME using different user account is recommended to avoid
problems caused by user settings stored in the home directory. This
manual refers to the new account as
gnomedev .
Setup JHBuild on the new
gnomedev account. Copy or
soft-link ~/.jhbuildrc and
~/.local/bin/jhbuild to
gnomedev home directory.
Open a terminal as the user
gnomedev . Permanently add
~/.local/bin to the PATH variable,
run the following command:
$ echo PATH=$PATH:~/.local/bin >> ~/.bashrc Test JHBuild works:
$ jhbuild run pkg-config gtk+-2.0 --modversion
2.20.1
Setup GNOME to run from the display manager
Build and install JHBuild GNOME.
Enable system services. JHBuild GNOME will use the
/usr/bin system D-Bus
daemon and the system services within
/usr/share/dbus-1/system-services/ . JHBuild GNOME
will use the JHBuild session D-Bus daemon
and the services within
/opt/gnome /share/dbus-1/services//opt/gnome with GNOME install
prefix in the command below:
$ rm -rf /opt/gnome /var/run/dbus
$ ln -s /var/run/dbus /opt/gnome /var/run/dbus
$ rm -rf /opt/gnome /var/lib/dbus/machine-id
$ ln -s /var/lib/dbus/machine-id /opt/gnome /var/lib/dbus/machine-id Create a GNOME startup script at
/usr/bin/gnome-jhbuild-session with the
following, replacing /opt/gnome with GNOME
install prefix :
#!/bin/sh
GNOME=/opt/gnome
GDK_USE_XFT=1
XDG_DATA_DIRS=$XDG_DATA_DIRS:$GNOME/share
XDG_CONFIG_DIRS=$XDG_CONFIG_DIRS:$GNOME/etc/xdg
jhbuild run gnome-session
Make the file
/usr/bin/gnome-jhbuild-session executable:
$ chmod a+x /usr/bin/gnome-jhbuild-session To add a new session entry in the display manager, create
/usr/share/xsessions/gnome-jhbuild.desktop and
enter:
[Desktop Entry]
Name=GNOME (JHBuild)
Comment=This session logs you into GNOME testing session
TryExec=/usr/bin/gnome-jhbuild-session
Exec=/usr/bin/gnome-jhbuild-session
Icon=
Type=Application
Restart gdm .
Running GNOME from the display manager
To run the JHBuild GNOME, select the GNOME (JHBuild) session at
the display manager before entering
gnomedev login credentials.
If successful, JHBuild GNOME will be displayed. If unsuccessful, check
the log within the ~gnomedev/.xsession-errors
file.
Buildbot Integration
Coupled with the Buildbot
project, JHBuild can also function as a continuous integration tool. The
Buildbot configuration is used by the GNOME project at
build.gnome.org .
Configuring a Buildbot Slave
A Buildbot slave is a variation of a normal JHBuild installation
that serves the requests of a Buildbot master. It is recommended to set
up JHBuild and complete a build with most modules building successfully
before adding the Buildbot customizations.
Buildbot commands are options to the bot
command. To download and install the extra required software, run the
following command:
$ jhbuild bot --setup Once this step has completed successfully, three new configuration
variables are required in ~/.jhbuildrc .
It is not possible to use an alternate configuration file, the
--file will not
get desired effects.
jhbuildbot_master = 'build.gnome.org:9070'
jhbuildbot_slavename = 'slavename'
jhbuildbot_password = 'password'
jhbuildbot_master is a string specifying the
Buildbot master server; it defaults to
'build.gnome.org:9070' .
jhbuildbot_slavename and
jhbuildbot_password identify the slave on the master
server. Contact the Buildbot master administrators to obtain the slave
name and password.
The administrators of
build.gnome.org can be
reached on the Build
Brigade mailing list .
Kommandoreferens
JHBuild uses a command line syntax similar to tools like CVS:
jhbuild
global-options command command-arguments The global JHBuild options are:
-f , --file
config
Use an alternative configuration file instead of the
default ~/.jhbuildrc .
-m , --moduleset
moduleset
Use a module set other than the module set listed in the
configuration file. This option can be a relative path if the module
set is located in the JHBuild moduleset folder, or an absolute path
if located elsewhere.
--no-interact
Do not prompt the user for any input. This option is useful
if leaving a build unattended, in order to ensure the build is not
interrupted.
Command specific options are listed below.
autobuild
The autobuild command automatically builds the
modules as specified in the configuration file, and then upload the
results to JhAutobuild.
jhbuild autobuild
--autogen
--clean
--distcheck
--skip=module
--start-at=module
--report-url=reporturl
--verbose
The --autogen , --clean ,
--distcheck , --skip and
--start-at options are processed as per the
build
command.
--report-url=reporturl ,
-r reporturl
This option specifies the JhAutobuild URL to report to.
--verbose , -v
If specified, JHBuild's output will be more verbose.
bootstrap
The bootstrap command installs a set of build
utilities required to build most modules (e.g.
autoconf ,
automake , etc).
jhbuild bootstrap
The bootstrap command builds modules using the
same method as the build command, but uses the
bootstrap.modules moduleset.
See the
build
command documentation for available options.
build
The build command builds one or more packages,
including their dependencies.
jhbuild build
--autogen
--clean
--check
--dist
--distcheck
--ignore-suggests
--no-network
--skip=module
--start-at=module
--tags=tags
-D date
--no-xvfb
--try-checkout
--no-poison
--force
--build-optional-modules
--min-age=time
module
If no module names are provided on the command line, the
-c , --clean
Run make clean before building
modules.
--check
Run make check after building modules.
-d , --dist
Run make dist after building modules.
--distcheck
Run make distcheck after building
modules.
--ignore-suggests
Do not build soft dependencies.
-n , --no-network
Do not access the network when building modules. This
will skip download or update stages in a build. If a module can't
be built without network access, the module build will fail.
-s ,
--skip =module,...
Do not build the listed modules. Used to skip the
building of specified dependencies.
--tags =tag,...
Ignore modules that do not match
tag . Modules are automatically
attributed a tag matching the name of the module's module set.
-t ,
--start-at =module
Start at the named module rather than at the beginning of
the list. This option is useful if the build was interrupted.
-D date
If supported by the underlying version control system,
update the source tree to the specified date before building. An
ISO date format is required, e.g. "2009-09-18
02:32Z" .
-x , --no-xvfb
Run graphical tests on the actual X server rather than in
a simulated Xvfb.
-C , --try-checkout
If the build fails, and if supported by the version
control system, force a checkout and run
autogen.sh before retrying the build.
-N , --no-poison
If one or more of a module's dependencies failed, this
option forces JHBuild to try to build the module anyway.
-f , --force
Build the modules even if policy states it is not
required.
--build-optional-modules
Modules listed as optional dependencies, may not be
required to build the module. This option forces JHBuild to build
optional dependencies.
--min-age =time
Skip modules installed more recently than the specified
relative time. The time string format
is a number followed by a unit. The following units are supported:
seconds (s), minutes (m), hours (h) and days (d). For example,
--min-age=2h will skip modules built less than
two hours ago.
make
The make command is for actively developing on
a particular module. It requires the current directory be a source
checkout, and does the equivalent of buildone -nf $(basename
$(pwd)) .
jhbuild make
--clean
--check
--distcheck
--quiet
The options are the same as those available for the
buildone
command.
buildone
The buildone command is similar to
build , but it does not build the dependent modules.
It is useful for rebuilding one or more modules.
jhbuild buildone
--clean
--check
--distcheck
--no-network
-D date
--no-xvfb
--force
--min-age=time
module
The --check , --clean ,
-d , --distcheck ,
--no-network , -D and
-x options are processed as per the
build
command.
At least one module must be listed on the command line.
checkbranches
The checkbranches checks the module's branches
are defined correctly within the version control system and the branches
are consistent with the module set.
jhbuild checkbranches
--branch=branch
--branch =branch ,
-b branch
The branch to check.
$ jhbuild -m gnome-2.20 checkbranches
libgnomecanvas is missing branch definition for gnome-2-20
$
clean
The clean command cleans the build directories
of one or more modules.
jhbuild clean
--skip=module
--start-at=module
If no module names are provided on the command line, the
See the
build
command documentation for a description of available options.
dot
The dot command generates a file describing the
directed graph formed by the dependencies between a set of modules. This
file can then be processed using the
GraphViz software to
produce a diagram.
jhbuild dot
--soft-deps
--clusters
module
If no module names are provided on the command line, the
The --soft-deps option adds dotted lines from the
modules to the soft dependencies. The --clusters option
groups modules from
The output of the dot command can be piped to the dot utility to
generate a PostScript file:
$ jhbuild dot modules | dot -Tps > dependencies.ps Or a PNG image:
$ jhbuild dot modules | dot -Tpng > dependencies.png
Sample JHBuild dot output
gui
The gui command starts a graphical interface to
JHBuild which can be used to select modules to build and change some
options.
jhbuild gui
The graphical interface is rendered using GTK, so extra support
libraries are required.
info
The info command displays information about one
or more modules.
jhbuild info
module
The command displays the module name, type, dependencies,
dependent packages, the source directory, and the time it was last
installed with JHBuild. If available, information specific to the module
type such as the CVS repository or download URL will also be displayed.
If there is no module specified the command will display
information about all the modules defined in the module set.
list
The list command displays the expanded list of
modules the build command would build.
jhbuild list
-a
-r
-s
--start-at=module
--tags=tags
--ignore-suggests
--list-optional-modules
module
If no module names are provided on the command line, the
The --skip , --start-at ,
--tags , and --ignore-suggests options
are processed as per the
build
command.
-a , --all-modules
List all the modules from the module set regardless of
the build dependencies.
-r , --show-revision
If a module is set to a branch, show the branch name with
the module name.
--list-optional-modules
This option forces JHBuild to list optional dependencies.
rdepends
The rdepends command displays the reverse
dependencies of a module.
jhbuild rdepends
module
--dependencies
Show dependency path next to modules.
--direct
Limit display to modules directly depending on specified
module.
run
The run command runs the specified command
using the same environment that JHBuild uses when building modules.
jhbuild run
--in-builddir
--in-checkoutdir
program argument If using JHBuild to build GNOME, this command can be useful in X
startup scripts.
--in-builddir =module
Run the command in the build directory of the specified
module.
--in-checkoutdir =module
Run the command in the source directory of the specified
module.
sanitycheck
The sanitycheck command performs a number of
checks to verify the build environment is okay.
jhbuild sanitycheck
Some of the checks include:
The checkout and install prefixes are writable.
The required build tools are installed.
Some commonly used macros are available in the search paths
of the aclocal commands associated with the
various versions of automake .
The XML catalog contains the DocBook DTD and stylesheets.
shell
The shell command starts the user's shell with
the same environment as JHBuild uses when building modules.
jhbuild shell
This command is equivalent to the following:
$ jhbuild run $SHELL The UNDER_JHBUILD environment variable will be set
to "true" when this shell is active. You can use the presence of that
variable to customize your shell's prompt to indicate that you indeed
are under a jhbuild-controlled shell. For example, you may want to put
this in your .bashrc :
if [ -n "$UNDER_JHBUILD" ]; then
PS1="[jhbuild] $PS1"
fi
This will make your bash shell display
[jhbuild] before your normal prompt, making it easier
to see which shells are under a jhbuild environment.
sysdeps
The sysdeps command displays a list of
dependency modules that are provided by installed system packages.
JHBuild will not build the modules from source if the configuration
variable
partial_build
is True .
The sysdeps command also displays a list of
dependency modules where the installed system packages are too old.
JHBuild will build newer modules from source.
The sysdeps command also displays a list of
dependency modules with no matching system package installed.
jhbuild sysdeps
--install
--install
This option installs system packages which are
dependencies of the moduleset. The system packages are installed
using PackageKit .
<command>sysdeps</command> example
$ jhbuild sysdeps
System installed packages which are new enough:
speex (required=1.2rc1, installed=1.2rc1)
libdiscid (required=0.2.2, installed=0.2.2)
telepathy-farsight (required=0.0.14, installed=0.0.16)
lcms2 (required=2.2, installed=2.2)
...
System installed packages which are too old:
webkitgtk-3.0 (required=1.5.1, installed=1.4.0)
...
No matching system package installed:
libvala-0.14 (required=0.13.1)
...
tinderbox
The tinderbox command is similar to
build , but writes all terminal output to HTML files
suitable for publishing on a website. It can be used to set up systems
similar to Mozilla's Tinderbox, or Debian's Buildd.
jhbuild tinderbox
--clean
--no-network
--output=directory
--skip=module
--start-at=module
-D date
-C
-N
-f
module
The --clean , --no-network ,
--skip , --start-at ,
-D , -C , -N and
-f options are processed as per the
build
command.
-o ,
--output =directory
The directory to write the HTML files.
uninstall
The uninstall command uninstalls one or more
modules.
jhbuild uninstall
module
update
The update command is similar to
build , but only performs the download or update stage
for modules without building them.
jhbuild update
--skip=module
--start-at=module
--tags=tags
--ignore-suggests
-D date
module
The --skip , --start-at ,
--tags , --ignore-suggests and
-D options are processed as per the
build
command.
updateone
The updateone command is similar to
update , but it does not update the dependent modules.
It is useful for updating one or more modules.
jhbuild updateone
-D date
module
The -D option is processed as per the
build
command.
At least one module must be listed on the command line.
Configuration File Reference
The ~/.jhbuildrc file uses standard Python
syntax. The file is run, and the resulting variables defined in the
namespace are used to control how JHBuild acts. A set of default values
are inserted into the namespace before running the user's configuration
file.
Boolean configuration variables are set using syntax as demonstrated
in the following example:
use_local_modulesets = True
String configuration variables are set using syntax as demonstrated
in the following example:
autogenargs = '--disable-static --disable-gtk-doc'
List configuration variables are set using syntax as demonstrated in
the following example:
skip = ['mozilla', 'pulseaudio']
Dictionary configuration variables are set using syntax as
demonstrated in the following example:
repos['git.gnome.org'] = 'ssh://username@git.gnome.org/git/'
Configuration Variables
autogenargs
A string containing arguments passed to the
autogen.sh script of all modules. Can be
overridden for particular modules using the
module_autogenargs dictionary.
branches
A dictionary specifying which branch to use for specific
modules. This is useful if you are making some changes on a branch
of a module and want JHBuild to build that branch instead of the
one listed in the module set.
The definition of branches depends on the module VCS:
CVS: revision. E.g.
'BRANCH-PROJECT-0_8'
Bazaar: URI of module branch. E.g.
'http://bzr.example.net/project/gnome-2-28'
Git: tuple, with first part being an optional
repository (or the None value) and the second part the name of
the branch. E.g. ('git://git.example.net/project',
'gnome-2-28')
Simple example
branches['modulename'] = (None, 'branchname')
Subversion: URI of module branch E.g.
'svn://svn.example.net/project/gnome-2-28'
builddir_pattern
A printf style formatting pattern
used to generate build directory names. This is only used when
using separate source and build trees. The %s
in the format string will be replaced with
checkoutdir . Defaults to
'%s' .
buildroot
A string specifying the parent directory to place build
trees. Defaults to None , which causes builds
to be performed within the source trees.
buildscript
A string specifying which buildscript to use. The
recommended setting is the default, terminal .
In particular, do not set to gtk .
build_policy
A string specifying which modules to build. The three
possible options are all , to build all modules
requested, updated to build only modules which
have changed, or updated-deps to build modules
which have changed or which have dependencies which have changed.
Defaults to updated-deps .
checkoutroot
A string specifying the directory to unpack source trees
to. Unless buildroot is set, builds will occur
in this directory too. Defaults to
~/checkout/gnome .
checkout_mode
A string specifying how the checkout is performed for
directories in version control. Defaults to
update . This can be set per module using
module_checkout_mode . Possible values are
update (update checkout directory),
clobber (wipe out directory before checking out
the sources), export (wipe out directory then
create an unversioned copy of the sources) and
copy (checkout in a directory different from
the one it will build).
copy_dir
A string specifying the directory to copy to, if the copy
checkout_mode is in use. Defaults to the
checkout directory.
cvs_program
A string specifying which program to use for CVS support.
This can be git-cvsimport , or
cvs . Defaults to cvs .
dvcs_mirror_dir
A string specifying a local mirror directory. JHBuild
will create local mirrors of repositories at the specified
directory. The mirrors can be shared by multiple repository
groups, saving space and time because hard-links will be used for
local clones. The commands update and
updateone will create the mirrors and fetch new
commits from the online repositories. This option is only
supported by Git and Bazaar repositories.
installprog
A string specifying a program to use as replacement for
/usr/bin/install . If available, defaults to the
install-check wrapper provided by JHBuild. The
install-check wrapper optimizes header
installation to reduce the time taken for rebuilds.
ignore_suggests
A boolean value specifying whether to ignore soft
dependencies when calculating the dependency tree. Defaults to
False .
interact
A boolean value specifying whether to interact with the
user. Setting this value to False is
equivalent to passing the --no-interact option.
Defaults to True .
makeargs
A string listing additional arguments to be passed to
make . Defaults to '' .
makecheck
A boolean value specifying whether to run make
check after make . Defaults to
False .
makecheck_advisory
A boolean value specifying whether failures when running
make check should be advisory only and not
cause a build failure. Defaults to False .
makeclean
A boolean value specifying whether to run make
clean before make . Defaults to
False .
makedist
A boolean value specifying whether to run make
dist after make . Defaults to
False . This setting is equivalent to passing
the --dist option.
makedistcheck
A boolean value specifying whether to run make
distcheck after make . Defaults to
False . This setting is equivalent to passing
the --distcheck option.
module_autogenargs
A dictionary mapping module names to strings specifying
the arguments to be passed to autogen.sh . The
setting in module_autogenargs is used instead
of the global autogenargs setting. If a
particular module isn't listed in the dictionary, the global
autogenargs will be used.
module_checkout_mode
A dictionary specifying which checkout mode to use for
modules. This overrides the global
checkout_mode setting.
module_makeargs
A dictionary mapping module names to strings specifying
the arguments to pass to make . The setting in
module_makeargs replaces the value of
makeargs . If a particular module isn't listed
in the dictionary, the global makeargs will be
used.
module_makecheck
A dictionary mapping module names to boolean values
specifying whether to run make check after
make . The setting in
module_makecheck replaces the value of
makecheck . If a particular module isn't listed
in the dictionary, the global makecheck will be
used.
module_nopoison
A dictionary mapping module names to boolean values. If a
module is set to True , JHBuild will attempt
to build dependent modules even if the specified module failed.
The setting in module_nopoison replaces the
value of nopoison . If a particular module isn't
listed in the dictionary, the global nopoison
will be used.
A dictionary mapping module names to dictionaries with
extra environment variables to pass when executing commands for
the module.
modules
A list of strings specifying the modules to build. The
list of modules actually built will be recursively expanded to
include all the dependencies unless the
buildone command is used. Defaults to
['meta-gnome-desktop'] .
moduleset
A string or list of strings specifying the name(s) of the
module set(s) to use. This can either be the filename of a
moduleset included with JHBuild (excluding the path and
extension), or a full HTTP URL to an externally managed moduleset.
HTTP URL modulesets are cached locally. If a module with the same
name is present in more than one moduleset, the last set listed
takes priority. Modulesets provided with JHBuild are updated to
match the current GNOME development release.
modulesets_dir
A string specifying the directory containing the
modulesets to use. Defaults to the
modulesets/ directory in JHBuild sources.
nice_build
Run builds under the SCHED_IDLE
priority on Linux, nice on other Unix. This can
dramatically improve desktop interactivity for parallel builds
while having only a negligible impact on build throughput.
nobuild
A boolean value, if set to True
JHBuild will not build modules, but just download and unpack the
sources. The default vale is False .
nonetwork
A boolean value specifying whether to access the network.
This affects checking out or updating CVS modules, downloading
tarballs and updating module sets. Setting this to
True is equivalent to passing the
--no-network option. Defaults to
False .
nonotify
A boolean value specifying whether to emit notifications
using the notification daemon. If set to
False , notifications are emitted. Defaults to
True .
nopoison
A boolean value, if set to True
JHBuild attempts to build modules even if one or more of the
module's dependencies failed to build. This option is equivalent
to the --no-poison argument. The default value is
False .
notrayicon
A boolean value specifying whether to show an icon in the
system tray using Zenity. If set to False ,
notifications are emitted. Defaults to True .
noxvfb
A boolean value, if set to True
JHBuild will run any graphical tests on the real X server, rather
than using Xvfb . This option is equivalent to
passing --no-xvfb . The default value is
False
partial_build
A boolean value, if set to True
JHBuild will not build dependency modules if corresponding system
packages are installed and sufficient version. Defaults to
True .
prefix
A string specifying the prefix to install modules to.
prefix must be an absolute path. This directory
must be writable. Defaults to '/opt/gnome' .
pretty_print
A boolean value specifying whether to pretty format the
subprocess output. Only CVS output supports pretty printing.
Disable if the pretty printing causes problems. Defaults to
True .
print_command_pattern
A string displayed before JHBuild executes a command.
%(command)s in the string will be replaced with
the command about to be executed. %(cwd)s in
the string will be replaced with the current working directory.
Defaults to '%(command)s' .
progress_bar
A boolean value specifying whether to display a progress
bar during True .
quiet_mode
A boolean value, if set to True
disables the output of running commands. Defaults to
False .
repos
A dictionary specifying an alternative repository
location for a particular repository. This configuration variable
is useful to a module developer. By default, JHBuild will check
out code from repositories using an anonymous repository location.
The dictionary keys are short repository names and the values are
the alternative repository location strings. For example:
repos['git.gnome.org'] = 'ssh://username@git.gnome.org/git/'
skip
A list of modules to skip. This --skip
command line option extends the list. This list is empty by
default.
sticky_date
A string if set, and if supported by the underlying
version control system, JHBuild will update the source tree to the
specified date before building. An ISO date format is required,
e.g.
'yyyy -mm -dd ' .
Defaults to None .
svn_program
A string specifying which program to use for subversion
support. This can be svn ,
git-svn or bzr . Defaults to
svn .
tarballdir
A string if set, tarballs will be downloaded to the
specified directory instead of checkoutroot .
This is useful if you have multiple JHBuild environments or
regularly clear out checkoutroot and want to
reduce bandwidth usage.
tinderbox_outputdir
A string specifying the directory to store
jhbuild tinderbox output. This string can be
overridden by the --output option. Defaults to
None , so either the command line option must
be used or this variable must be set in the configuration file.
trycheckout
A boolean value, if set to True
JHBuild will automatically try to solve failures by 1) running
autogen.sh again, and 2) checking out a newer
version of a module from version control. This setting is
equivalent to passing the --try-checkout option.
use_lib64
A boolean value that specifies whether to install
libraries to lib64 directories. If set,
--libdir=\${exec_prefix}/lib64 will be passed
to configure. Defaults to True if running on
x86_64 , ppc64 or
s390x Linux, and False on
other systems.
use_local_modulesets
A boolean value that specifies to use modulesets that
were checked out along the JHBuild source code; instead of
downloading them on-the-fly from GNOME version control system.
Defaults to False .
xvfbargs
A string listing arguments to pass to
Xvfb if running graphical tests.
Other Configuration File Structures
In addition to the above variables, there are other settings that
can be set in the configuration file:
os.environ
A dictionary representing the environment. This environment
is passed to processes that JHBuild spawns.
Some influential environment variables include
CPPFLAGS , CFLAGS ,
INSTALL and LDFLAGS . For example:
os.environ['CFLAGS'] = '-O0 -g'
addpath (envvar ,
pathname )
This will add a directory to the PATH
environment variable. addpath will correctly
handle the case when the environment variable is initially empty
(having a stray colon at the beginning or end of an environment
variable can have unexpected consequences).
addpath has special handling for the
ACLOCAL_FLAGS environment variable, which expects
paths to be listed in the form -I
pathname .
prependpath (envvar ,
pathname )
After processing the configuration file, JHBuild will alter
some paths based on variables such as prefix
(e.g. adding $prefix/bin to the start of
PATH ).
The prependpath function works like
addpath , except that the environment variable
is modified after JHBuild has made its changes to the environment.
Module Set File Syntax
JHBuild uses XML files to describe the dependencies between modules.
A RELAX-NG schema and Document Type Definition are included with JHBuild
in the modulesets/ directory. The RELAX-NG schema can
be used to edit module set files using nxml-mode in
Emacs.
The top-level element in a module set file is
moduleset element. No XML namespace is
used. The elements below the top-level come in three types: module
sources, include statements and module definitions.
Module Sources
Rather than listing the full location of every module, a number of
"module sources" are listed in the module set, and then referenced by
name in the module definitions. As well as reducing the amount of
redundant information in the module set, it makes it easy for a user to
specify an alternative source for those modules (for CVS and Subversion,
it is common for developers and users to use different repository access
methods).
The repository element is used
to describe all types of repository. The
branch element is used inside module
definition to specify additional settings.
<repository name="name "
type="type "
[ default="default " ]
[ password="password " ]
[ cvsroot="cvsroot " ]
[ archive="archive " ]
[ href="href " ]
[ server="server " ]
[ database="database " ]
[ defbranch="defbranch " ]
[ trunk-template="trunk-template " ]
[ branches-template="branches-template " ]
[ tags-template="tags-template " ]
[ developer-href-example="developer-href-example " ] />
The name attribute is a
unique identifier for the repository.
The default attribute
specifies whether this repository is the default source for this module
set.
The type attribute specifies
the type of repository. It can be one of: bzr ,
cvs , darcs ,
fossil , git ,
hg , mnt , svn ,
tarball . Other attributes depend on the
type , as well as the
branch used inside module
definitions. Those are described below in the repository type
sub-sections.
The developer-href-example
attribute is used to specify the format of the URL for the repository
used by developers. This is informational only.
The branch element is used
inside module definitions.
<branch
[ repo="repository " ]
[ module="module name " ]
[ checkoutdir="checkoutdir " ]
[ revision="revision " ]
[ tag="tag " ]
[ update-new-dirs="update-new-dirs " ]
[ override-checkoutdir="override-checkoutdir " ]
[ subdir="subdir " ]
[ branch="branch " ]
[ version="version " ]
[ size="size " ]
[ source-subdir="source-subdir " ]
[ hash="hash " ]/>
All atributes have sensible defaults and depend on the module and
repository definitions. Common attributes are described here.
The repo attribute is used to
specify non-default repository name.
The module attribute is used
to specify module name to checkout from the repository. Defaults to
module id.
The checkoutdir attribute is
used to specify the checkout directory name. Defaults to module id.
Other attributes are described below
Bazaar
This repository type is used to define a Bazaar repository. It
is recommended to have Bazaar 1.16 or higher.
<repository type="bzr" name="launchpad.net"
href="lp:"/>
Additional attributes are:
trunk-template (defaults to
"%(module)s" ) and
branches-template (defaults to
"%(module)s/%(branch)s "). These attributes are used
to specify templates for constructing URL. A
branch element in the module
definitions can specify branch
and user attributes. These values
will be substitued in the templates. If either of those are defined
branches-template is used,
otherwise trunk-template is used.
This way you can ovveride repository to build modules from your
personal branch or build many modules fron a repository with
non-standard layout.
An addition branch element
accepts revspec attibute to
anchor on a particular revision. Any valid bzr
revspec is accepted, for example date:yesterday,
-5, tag:0.1 to get first revision since yesterday, 5 commits
behind the tip or tag "0.1". See bzr help
revisionspec for all possible values.
For example repository with
template attributes defined:
<repository type="bzr" name="launchpad.net"
href="lp:"
trunk-template="~bzr-pqm/%(module)s/bzr.dev"
branches-template="~bzr-pqm/%(module)s/%(branch)s"/>
Example branch elements for
the above repository:
<branch repo="launchpad.net"
module="bzr"
checkoutdir="bzr-next"/>
<branch repo="launchpad.net"
module="bzr"
branch="2.2"
checkoutdir="bzr-beta"/>
CVS
This repository type is used to define a CVS repository.
The password attribute is
used to specify the password to the repository.
The cvsroot attribute is
used to specify the root of the repository.
<repository type="cvs" name="tango.freedesktop.org"
cvsroot=":pserver:anoncvs@anoncvs.freedesktop.org:/cvs/tango"
password=""/>
Additional attributes are:
revision ,
update-new-dirs and
override-checkoutdir .
Darcs
This repository type is used to define a Darcs repository.
<repository type="darcs" name="telepathy.freedesktop.org"
href="http://projects.collabora.co.uk/darcs/telepathy/"/>
Git
This repository type is used to define a Git repository.
<repository type="git" name="git.freedesktop.org"
href="git://anongit.freedesktop.org/git/"/>
It allows the following attributes on the
branch element:
The revision attribute is
used to specify a local or remote-tracking branch to switch to in the
update phase. It defaults to 'master'. It is possible to override this
attribute with the branches configuration variable.
The switch will only be performed, if the current branch is tracking a
remote branch, to not disturb your own work.
The tag attribute is used
to specify a revision to unconditionally check out in the update
phase. It overrides the revision
attribute.
<branch repo="git.freedesktop.org" module="swfdec/swfdec"
checkoutdir="swfdec"
revision="local-or-remote-branch "
tag="tree-ish "/>
Mercurial
This repository type is used to define a Mercurial repository.
<repository type="hg" name="hg.gtk-vnc"
href="http://gtk-vnc.codemonkey.ws/hg/" />
<branch repo="hg.gtk-vnc" module="outgoing.hg" checkoutdir="gtk-vnc"/>
Monotone
This repository type is used to define a Monotone repository.
The server attribute is
used to specify the repository server.
The database attribute is
used to specify the database to use for the repository.
The defbranch attribute is
used specify the branch of the repository to use.
<repository type="mtn" name="pidgin.im"
server="pidgin.im" database="pidgin.im.mtn"
defbranch="im.pidgin.pidgin"/>
Subversion
This repository type is used to define a Subversion repository.
<repository type="svn" name="svn.gnome.org" default="yes"
href="http://svn.gnome.org/svn/"/>
It allows a revision on the
branch element. This attribute
defines the branch to checkout or, if it is a number, a specific
revision to checkout.
<branch revision="gnome-2-20"/>
It is possible to specify custom svn layout
using trunk-template (defaults to
"%(module)s/trunk"),
branches-template (defaults to
"%(module)s/branches/%(branch)s") and
tags-template (defaults to
"%(module)s/tags/%(tag)s")
Tarballs
This repository type is used to define a tarball repository.
<repository type="tarball" name="dbus/dbus-python"
href="http://dbus.freedesktop.org/releases/dbus-python/"/>
It allows the following attributes on the
branch element:
The module attribute
specifies the file to download and compile, the
version attribute specifies the
module version.
The size and
hash , as well as the obsolete
md5sum , attributes are optional.
If these attributes are present, they are used to check that the
source package was downloaded correctly.
Any number of patch elements
may be nested inside the branch
element. These patches are applied, in order, to the source tree after
unpacking. The file attribute
gives the patch filename, and the
strip attribute says how many
levels of directories to prune when applying the patch.
For module sets shipped with JHBuild, the patch files are looked
up in the jhbuild/patches/ directory; for module
sets referred by URI, the patch files are looked for in the same
directory as the moduleset file, or in its
patches/ subdirectory. It is also possible for
the file attribute to specify a
URI, in which case it will be downloaded from that location.
<branch module="dbus-python-0.80.2.tar.gz" version="0.80.2"
repo="dbus/dbus-python"
hash="md5:2807bc85215c995bd595e01edd9d2077" size="453499">
<patch file="dbus-glib-build.patch" strip="1" />
</branch>
A tarball branch element may
also contain quilt elements which
specify nested branch to import.
Including Other Module Sets
JHBuild allows one module set to include the contents of another
by reference using the include
element.
<include href="uri "/>
The href is a URI reference
to the module set to be included, relative to the file containing the
include element.
Only module definitions are imported from the referenced module
set - module sources are not. Multiple levels of includes are allowed,
but include loops are not (there isn't any code to handle loops at the
moment).
Module Definitions
There are various types of module definitions that can be used in
a module set file, and the list can easily be extended. Only the most
common ones will be mentioned here.
They are all basically composed of a
branch element describing how to get
the module and dependencies ,
suggests and
after elements to declare the
dependencies of the module.
Any modules listed in the
dependencies element will be added to
the module list for jhbuild build if it isn't already
included, and make sure the dependent modules are built first.
After generating the modules list, the modules listed in the
suggests element will be used to
further sort the modules list (although it will not pull any additional
modules). This is intended for cases where a module has an optional
dependency on another module.
cmake
The cmake element is used to
define a module which is built using the CMake build system.
<cmake id="modulename ">
<branch [ ... ] >
[...]
</branch>
<dependencies>
<dep package="modulename "/>
...
</dependencies>
<after>
<dep package="modulename "/>
...
</after>
</cmake>
distutils
The distutils element is used
to define a module which is built using python's distutils
<distutils id="modulename "
[ supports-non-srcdir-builds="yes|no " ]>
<branch [ ... ] >
[...]
</branch>
<dependencies>
<dep package="modulename "/>
...
</dependencies>
<after>
<dep package="modulename "/>
...
</after>
</distutils>
linux
The linux element defines a
module used to build a linux kernel. In addition, a separate kernel
configuration can be chosen using the
kconfig subelement.
<linux id="id "
[ makeargs="makeargs " ]>
<branch [ ... ] >
[...]
</branch>
<dependencies>
<dep package="modulename "/>
...
</dependencies>
<after>
<dep package="modulename "/>
...
</after>
<kconfig [ repo="repo " ]
version="version "
[ module="module " ]
[ config="config " ] />
</linux>
perl
The perl element is used to
build perl modules.
The makeargs attribute is
used to specify additional arguments to pass to
make .
<perl id="modulename "
[ makeargs="makeargs " ]>
<branch [ ... ] >
[...]
</branch>
<dependencies>
<dep package="modulename "/>
...
</dependencies>
<after>
<dep package="modulename "/>
...
</after>
</perl>
waf
The waf element is used to
define a module which is built using the Waf build system.
The waf-command attribute
is used to specify the waf command script to use; it defaults to
waf .
<waf id="modulename ">
[ waf-command="waf-command " ]>
<branch [ ... ] >
[...]
</branch>
<dependencies>
<dep package="modulename "/>
...
</dependencies>
<after>
<dep package="modulename "/>
...
</after>
</waf>
testmodule
The testmodule element is
used to create a module which runs a suite of tests using LDTP or
Dogtail.
<testmodule id="id "
type="type ">
<branch [ ... ] >
[...]
</branch>
<dependencies>
<dep package="modulename "/>
...
</dependencies>
<after>
<dep package="modulename "/>
...
</after>
<testedmodules>
<tested package="package " />
</testedmodules>
</testmodule>
The type attribute gives
the type of tests to be run in the module. 'dogtail' uses python to
invoke all .py files. 'ldtp' invokes 'ldtprunner run.xml'.
Unless the noxvfb configuration option is set, an Xvfb server is
started to run the tests in
Deprecated Elements
Module Sources
cvsroot
The cvsroot element is now
deprecated - the repository
element should be used instead.
The cvsroot element is used
to describe a CVS repository.
<cvsroot name="rootname "
[ default="yes|no " ]
root="anon-cvsroot "
password="anon-password "/>
The name attribute should
be a unique identifier for the CVS repository.
The default attribute
says whether this is the default module source for this module set
file.
The root attribute lists
the CVS root used for anonymous access to this repository, and the
password attribute gives the
password used for anonymous access.
svnroot
The svnroot element is now
deprecated - the repository
element should be used instead.
The svnroot element is used
to describe a Subversion repository.
<svnroot name="rootname "
[ default="yes|no " ]
href="anon-svnroot "/>
The name attribute should
be a unique identifier for the Subversion repository.
If default attribute says
whether this is the default module source for this module set file.
The href attribute lists
the base URL for the repository. This will probably be either a
http , https or
svn URL.
Deprecated Module Types
This section describes deprecated elements, they may still be
used in existing module sets but it is advised not to use them
anymore.
tarball
This deprecated element is just a thin wrapper around both
autotools module type and
tarball repository type.
The tarball element is used
to define a module that is to be built from a tarball.
<tarball id="modulename "
[ version="version " ]
[ checkourdir="checkoutdir " ]
[ autogenargs="autogenargs " ]
[ makeargs="makeargs " ]
[ autogen-sh="autogen-sh " ]
[ supports-non-srcdir-builds="yes|no " ]>
<source href="source-url "
[ size="source-size " ]
[ hash="source-algo:source-hash " ]
[ md5sum="source-md5sum " ]/>
<patches>
<patch file="filename " strip="level "/>
...
</patches>
<dependencies>
<dep package="modulename "/>
...
</dependencies>
<suggests>
<dep package="modulename "/>
...
</suggests>
</tarball>
The id and
version attributes are used to
identify the module.
The source element
specifies the file to download and compile. The
href attribute is mandatory,
while the size and
hash , as well as the obsolete
md5sum , attributes are
optional. If these last two attributes are present, they are used to
check that the source package was downloaded correctly.
The patches element is used
to specify one or more patches to apply to the source tree after
unpacking, the file attribute
gives the patch filename, and the
strip attribute says how many
levels of directories to prune when applying the patch.
For module sets shipped with JHBuild, the patch files are
looked up in the jhbuild/patches/ directory;
for module sets referred by URI, the patch files are looked for in
the same directory as the moduleset file, or in its
patches/ subdirectory. It is also possible for
the file attribute to specify a
URI, in which case it will be downloaded from that location.
The other attributes and the
dependencies ,
suggests and
after elements are processed as
for
jhbuild-3.5.91/doc/sv/sv.po 0000644 0001750 0001750 00000310132 11243013407 015334 0 ustar 00fred fred 0000000 0000000 msgid ""
msgstr ""
"Project-Id-Version: jhbuild doc\n"
"POT-Creation-Date: 2008-07-26 14:28+0000\n"
"PO-Revision-Date: 2008-07-27 01:09+0100\n"
"Last-Translator: Daniel Nylander \n"
"Language-Team: Swedish \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. When image changes, this message will be marked fuzzy or untranslated for you.
#. It doesn't matter what you translate it to: it's not used at all.
#: C/jhbuild.xml:806(None)
msgid "@@image: 'figures/jhbuild_sample_dot_output.png'; md5=af9fe7edb29fcaefeadfb2f5987aa6e4"
msgstr ""
#: C/jhbuild.xml:7(title)
msgid "JHBuild Manual"
msgstr "Handbok för JHBuild"
#: C/jhbuild.xml:10(firstname)
msgid "James"
msgstr "James"
#: C/jhbuild.xml:11(surname)
msgid "Henstridge"
msgstr "Henstridge"
#: C/jhbuild.xml:14(firstname)
msgid "C.J."
msgstr "C.J."
#: C/jhbuild.xml:15(surname)
msgid "Adams-Collier"
msgstr "Adams-Collier"
#: C/jhbuild.xml:18(firstname)
msgid "Frederic"
msgstr "Frederic"
#: C/jhbuild.xml:19(surname)
msgid "Peters"
msgstr "Peters"
#: C/jhbuild.xml:22(firstname)
msgid "David"
msgstr "David"
#: C/jhbuild.xml:23(surname)
msgid "Turner"
msgstr "Turner"
#: C/jhbuild.xml:27(year)
msgid "2004, 2008"
msgstr "2004, 2008"
#: C/jhbuild.xml:28(holder)
msgid "James Henstridge"
msgstr "James Henstridge"
#: C/jhbuild.xml:33(revnumber)
msgid "JHBuild Manual v0.5"
msgstr "Handbok för JHBuild v0.5"
#: C/jhbuild.xml:34(date)
msgid "January 2008"
msgstr "Januari 2008"
#: C/jhbuild.xml:37(revnumber)
msgid "JHBuild Manual v0.1"
msgstr "Handbok för JHBuild v0.1"
#: C/jhbuild.xml:38(date)
msgid "August 2007"
msgstr "Augusti 2007"
#: C/jhbuild.xml:43(para)
msgid "JHBuild is a tool used to build the whole GNOME desktop from the SVN source, however, it can be used to build other projects by creating a moduleset for it."
msgstr ""
#: C/jhbuild.xml:50(title)
msgid "Introduction"
msgstr "Introduktion"
#: C/jhbuild.xml:52(para)
msgid "JHBuild is a tool designed to ease building collections of source packages (also known as modules). It uses module set
files to describe the modules available to build. These files include dependency information that allows JHBuild to work out what modules need to be built and in what order to build what the user requested."
msgstr ""
#: C/jhbuild.xml:59(para)
msgid "JHBuild was originally written for building GNOME , but has since been extended to make it usable with other projects. A module set
file can be hosted on a web server, allowing people to provide build rules independent of JHBuild."
msgstr ""
#: C/jhbuild.xml:65(para)
msgid "JHBuild can build modules from a variety of sources, including CVS , Subversion Arch , Bazaar , Darcs , Git and Mercurial repositories, as well as Tar archives hosted on web or FTP sites; and using a variety of build systems, including Autotools, CMake, WAF, Ant, Python Distutils and Perl Makefiles."
msgstr ""
#: C/jhbuild.xml:79(para)
msgid "JHBuild is not intended as a replacement for the distribution's package management system. Instead, it makes it easy to build everything into a separate install prefix so that it doesn't interfere with the rest of the system."
msgstr ""
#: C/jhbuild.xml:87(title)
msgid "Getting Started"
msgstr "Komma igång"
#: C/jhbuild.xml:89(para)
msgid "JHBuild takes a bit of work to set up on a system. As well as installing JHBuild's prerequisites, it is necessary to install the prerequisite tools needed to obtain and build the software sources."
msgstr ""
#: C/jhbuild.xml:95(title)
msgid "Installing JHBuild"
msgstr "Installera JHBuild"
#: C/jhbuild.xml:97(para)
msgid "Before downloading JHBuild, you should make sure you have a copy of Python >= 2.0 installed on your system. It is also essential that the Expat XML parser extension is installed. This will be the case if you are using Python >= 2.3, or had expat installed when building Python. You can check whether this is the case by running the following simple command from the Python interpreter:"
msgstr ""
#: C/jhbuild.xml:105(prompt)
#: C/jhbuild.xml:106(prompt)
msgid ">>>"
msgstr ">>>"
#: C/jhbuild.xml:105(userinput)
#, no-wrap
msgid "import xml.parsers.expat"
msgstr "import xml.parsers.expat"
#: C/jhbuild.xml:108(para)
msgid "If this completes without an exception, then it is installed correctly."
msgstr ""
#: C/jhbuild.xml:111(para)
msgid "At the moment, the only way to download JHBuild is via Subversion. This can be achieved with the following commands. They should be run in the directory where JHBuild will be installed (for example, ~/checkout/gnome2 )."
msgstr ""
#: C/jhbuild.xml:116(prompt)
#: C/jhbuild.xml:118(prompt)
#: C/jhbuild.xml:124(prompt)
#: C/jhbuild.xml:125(prompt)
#: C/jhbuild.xml:127(prompt)
#: C/jhbuild.xml:129(prompt)
#: C/jhbuild.xml:131(prompt)
#: C/jhbuild.xml:137(prompt)
#: C/jhbuild.xml:138(prompt)
#: C/jhbuild.xml:140(prompt)
#: C/jhbuild.xml:142(prompt)
#: C/jhbuild.xml:149(prompt)
#: C/jhbuild.xml:150(prompt)
#: C/jhbuild.xml:158(prompt)
#: C/jhbuild.xml:159(prompt)
#: C/jhbuild.xml:299(prompt)
#: C/jhbuild.xml:323(prompt)
#: C/jhbuild.xml:349(prompt)
#: C/jhbuild.xml:363(prompt)
#: C/jhbuild.xml:369(prompt)
#: C/jhbuild.xml:376(prompt)
#: C/jhbuild.xml:382(prompt)
#: C/jhbuild.xml:387(prompt)
#: C/jhbuild.xml:393(prompt)
#: C/jhbuild.xml:398(prompt)
#: C/jhbuild.xml:404(prompt)
#: C/jhbuild.xml:409(prompt)
#: C/jhbuild.xml:760(prompt)
#: C/jhbuild.xml:762(prompt)
#: C/jhbuild.xml:795(prompt)
#: C/jhbuild.xml:799(prompt)
#: C/jhbuild.xml:1035(prompt)
msgid "$"
msgstr "$"
#: C/jhbuild.xml:116(userinput)
#, no-wrap
msgid "svn co http://svn.gnome.org/svn/jhbuild/trunk jhbuild"
msgstr "svn co http://svn.gnome.org/svn/jhbuild/trunk jhbuild"
#: C/jhbuild.xml:117(computeroutput)
#: C/jhbuild.xml:126(computeroutput)
#: C/jhbuild.xml:128(computeroutput)
#: C/jhbuild.xml:130(computeroutput)
#: C/jhbuild.xml:139(computeroutput)
#: C/jhbuild.xml:141(computeroutput)
#, no-wrap
msgid "..."
msgstr "..."
#: C/jhbuild.xml:120(para)
msgid "This will download JHBuild into a new folder named jhbuild under the current directory. Now to build and install it:"
msgstr ""
#: C/jhbuild.xml:124(userinput)
#: C/jhbuild.xml:137(userinput)
#, no-wrap
msgid "cd jhbuild"
msgstr "cd jhbuild"
#: C/jhbuild.xml:125(userinput)
#, no-wrap
msgid "./autogen.sh"
msgstr "./autogen.sh"
#: C/jhbuild.xml:127(userinput)
#, no-wrap
msgid "make"
msgstr "make"
#: C/jhbuild.xml:129(userinput)
#, no-wrap
msgid "make install"
msgstr "make install"
#: C/jhbuild.xml:133(para)
msgid "Alternatively, if your work environment doesn't have autotools or gnome-doc-utils installed you can also build and install JHBuild that way:"
msgstr ""
#: C/jhbuild.xml:138(userinput)
#, no-wrap
msgid "make -f Makefile.plain"
msgstr "make -f Makefile.plain"
#: C/jhbuild.xml:140(userinput)
#, no-wrap
msgid "make -f Makefile.plain install"
msgstr "make -f Makefile.plain install"
#: C/jhbuild.xml:144(para)
msgid "If these steps complete successfully, a small shell script should be installed in ~/bin to start JHBuild. If this directory is not in the PATH , it will need to be added. This can be done with the command:"
msgstr ""
#: C/jhbuild.xml:149(userinput)
#, no-wrap
msgid "PATH=$PATH:~/bin"
msgstr "PATH=$PATH:~/bin"
#: C/jhbuild.xml:152(para)
msgid "This command will need to be run every time you login and want to use JHBuild. In order to permanently add ~/bin to your PATH variable, run the following command:"
msgstr ""
#: C/jhbuild.xml:158(userinput)
#, no-wrap
msgid "echo PATH=$PATH:~/bin >> ~/.bashrc"
msgstr "echo PATH=$PATH:~/bin >> ~/.bashrc"
#: C/jhbuild.xml:161(para)
msgid "Before JHBuild can be run, it is necessary to set up a configuration file, located at ~/.jhbuildrc . This file specifies JHBuild will behave."
msgstr ""
#: C/jhbuild.xml:168(title)
msgid "Configuring JHBuild"
msgstr "Konfigurera JHBuild"
#: C/jhbuild.xml:170(para)
msgid "The ~/.jhbuildrc file uses Python syntax to set a number of configuration variables for JHBuild. A minimal configuration file might look something like this:"
msgstr ""
#: C/jhbuild.xml:175(programlisting)
#, no-wrap
msgid ""
"\n"
"moduleset = 'gnome-2.22'\n"
"modules = [ 'meta-gnome-desktop' ]\n"
"checkoutroot = os.path.join(os.environ['HOME'], 'checkout', 'gnome2')\n"
"prefix = os.path.join(os.environ['HOME'], 'prefix')\n"
"os.environ['INSTALL'] = os.path.join(os.environ['HOME'],\n"
" 'bin', 'install-check')\n"
msgstr ""
#: C/jhbuild.xml:184(para)
msgid "This will make JHBuild build the meta-gnome-desktop module and its dependencies from the gnome-2.22 module set. It will unpack source trees to ~/checkout/gnome2 and install all files to subdirectories of ~/prefix . It also sets the INSTALL environment variable, so modules use a different install program which handles installation of headers differently, in order to reduce the time taken for rebuilds."
msgstr ""
#: C/jhbuild.xml:194(para)
msgid "Some of configuration variables available include:"
msgstr ""
#: C/jhbuild.xml:199(varname)
#: C/jhbuild.xml:1372(varname)
msgid "moduleset"
msgstr ""
#: C/jhbuild.xml:201(simpara)
msgid "A string or list of strings specifying the name(s) of the module set(s) to use. If a module set name is a fully qualified URL, then the module set will be cached locally and regularly updated. If a module with the same name is present in more than one module set, the last set listed takes priority."
msgstr ""
#: C/jhbuild.xml:210(varname)
#: C/jhbuild.xml:795(replaceable)
#: C/jhbuild.xml:799(replaceable)
#: C/jhbuild.xml:1363(varname)
msgid "modules"
msgstr ""
#: C/jhbuild.xml:212(simpara)
msgid "A list of strings giving the modules you want to build. The list of modules actually built will be recursively expanded to include all the dependencies unless the buildone is used."
msgstr ""
#: C/jhbuild.xml:219(varname)
#: C/jhbuild.xml:1212(varname)
msgid "checkoutroot"
msgstr ""
#: C/jhbuild.xml:221(simpara)
msgid "The base directory where all source modules are unpacked or checked out of revision control."
msgstr ""
#: C/jhbuild.xml:226(varname)
#: C/jhbuild.xml:1436(varname)
msgid "prefix"
msgstr ""
#: C/jhbuild.xml:228(simpara)
msgid "The directory prefix to install modules to. You must have write permissions to this directory, or JHBuild will be unable to install files."
msgstr ""
#: C/jhbuild.xml:234(varname)
#: C/jhbuild.xml:1584(varname)
msgid "os.environ"
msgstr ""
#: C/jhbuild.xml:236(simpara)
msgid "A dictionary representing the environment. This can be used to set or get environment variable values as shown in the example configuration above."
msgstr ""
#: C/jhbuild.xml:242(varname)
#: C/jhbuild.xml:1483(varname)
msgid "skip"
msgstr ""
#: C/jhbuild.xml:244(simpara)
msgid "A list of module names that to not include when deciding what to build. One use of this variable is to use the version of a package included with the distribution instead of building it."
msgstr ""
#: C/jhbuild.xml:251(varname)
#: C/jhbuild.xml:1151(varname)
msgid "autogenargs"
msgstr ""
#: C/jhbuild.xml:253(simpara)
msgid "A string listing additional arguments to pass to the autogen.sh or configure scripts for modules."
msgstr ""
#: C/jhbuild.xml:259(varname)
#: C/jhbuild.xml:1267(varname)
msgid "makeargs"
msgstr ""
#: C/jhbuild.xml:261(simpara)
msgid "A string listing arguments to be pass to the make command."
msgstr ""
#: C/jhbuild.xml:266(varname)
#: C/jhbuild.xml:1469(varname)
msgid "repos"
msgstr ""
#: C/jhbuild.xml:268(simpara)
#: C/jhbuild.xml:1471(simpara)
msgid "By default, JHBuild will check out code from repositories using an anonymous repository location. This dictionary is used to tell JHBuild to use an alternative repository location for a particular repository (a developer would probably want to do this). This variable is a dictionary where the keys are short repository names (for example, svn.gnome.org is used for the GNOME SVN repository), and the values are the alternative repository location strings."
msgstr ""
#: C/jhbuild.xml:283(title)
msgid "Build Prerequisites"
msgstr ""
#: C/jhbuild.xml:285(para)
msgid "Before any modules can be built, it is necessary to have certain build tools installed. These can include the GNU Autotools (autoconf , automake , libtool and gettext ), The GNU Toolchain (binutils , gcc , g++ ), pkg-config and Python, depending on which modules will be built."
msgstr ""
#: C/jhbuild.xml:296(para)
msgid "JHBuild can check if your system has these tools installed using the sanitycheck command:"
msgstr ""
#: C/jhbuild.xml:299(userinput)
#: C/jhbuild.xml:993(command)
#, no-wrap
msgid "jhbuild sanitycheck"
msgstr ""
#: C/jhbuild.xml:301(para)
msgid "If this command prints any messages, these can be fixed in one of two ways:"
msgstr ""
#: C/jhbuild.xml:306(simpara)
msgid "Install the required package from your distribution's repository. A list of package names for different distributions is maintained on the GNOME wiki. The sanitycheck command should be run again afterwards to make sure required tools are present."
msgstr ""
#: C/jhbuild.xml:315(simpara)
msgid "Run the bootstrap command to install the build prerequsites."
msgstr ""
#: C/jhbuild.xml:320(para)
msgid "The bootstrap command can be invoked like so:"
msgstr ""
#: C/jhbuild.xml:323(userinput)
#: C/jhbuild.xml:512(command)
#, no-wrap
msgid "jhbuild bootstrap"
msgstr ""
#: C/jhbuild.xml:325(para)
msgid "This will download and install all the build prerequisites. Once it is finished, the sanitycheck command should be rerun to verify that everything is in place."
msgstr ""
#: C/jhbuild.xml:331(para)
msgid "The bootstrap command does not build all the packages required by these tools. If your distribution does not provide those packages, then they will need to be built separately."
msgstr ""
#: C/jhbuild.xml:336(para)
msgid "Some packages to check for include m4 , perl and a C compiler (For example, gcc )."
msgstr ""
#: C/jhbuild.xml:343(title)
msgid "Using JHBuild"
msgstr ""
#: C/jhbuild.xml:345(para)
msgid "Now that everything is set up, JHBuild can be used to build some software. To build all the modules selected in the ~/.jhbuildrc file, run the following command:"
msgstr ""
#: C/jhbuild.xml:349(userinput)
#: C/jhbuild.xml:531(command)
#, no-wrap
msgid "jhbuild build"
msgstr ""
#: C/jhbuild.xml:351(para)
msgid "This will download, configure, compile and install each of the modules. If an error occurs at any stage, JHBuild will present a menu asking what to do. These choices include dropping to a shell to fix the error, rerunning the build from various stages, giving up on the module (which will also cause any modules depending on it to fail), or ignore the error and continue."
msgstr ""
#: C/jhbuild.xml:359(para)
msgid "It is also possible to build a different set of modules (and their dependencies) by passing their names as arguments to the build command, for example, to build gtk+:"
msgstr ""
#: C/jhbuild.xml:363(userinput)
#, no-wrap
msgid "jhbuild build gtk+"
msgstr ""
#: C/jhbuild.xml:365(para)
msgid "If you exit JHBuild part way through a build for some reason, it is possible to pick up a build at a particular module using the --start-at option:"
msgstr ""
#: C/jhbuild.xml:369(userinput)
#, no-wrap
msgid "jhbuild build --start-at=pango"
msgstr ""
#: C/jhbuild.xml:371(para)
msgid "To build one or more modules, ignoring their dependencies, the buildone command can be used. This command should only be used if you have manually installed all dependencies, else the build will fail."
msgstr ""
#: C/jhbuild.xml:376(userinput)
#, no-wrap
msgid "jhbuild buildone gtk+"
msgstr ""
#: C/jhbuild.xml:378(para)
msgid "To get a list of the modules and dependencies jhbuild will build, and the order in which they will be built, use the list command:"
msgstr ""
#: C/jhbuild.xml:382(userinput)
#: C/jhbuild.xml:863(command)
#, no-wrap
msgid "jhbuild list"
msgstr ""
#: C/jhbuild.xml:384(para)
msgid "To get information about a particular module, the info command can be used:"
msgstr ""
#: C/jhbuild.xml:387(userinput)
#, no-wrap
msgid "jhbuild info gtk+"
msgstr ""
#: C/jhbuild.xml:389(para)
msgid "If your internet bandwidth varies, or you wish to modify the sources before building them, you can download or update all the software sources without actually building them:"
msgstr ""
#: C/jhbuild.xml:393(userinput)
#: C/jhbuild.xml:1088(command)
#, no-wrap
msgid "jhbuild update"
msgstr ""
#: C/jhbuild.xml:395(para)
msgid "Later on, you can tell JHBuild to build everything without downloading or updating the sources:"
msgstr ""
#: C/jhbuild.xml:398(userinput)
#, no-wrap
msgid "jhbuild build --no-network"
msgstr ""
#: C/jhbuild.xml:400(para)
msgid "If you want to run a particular command with the same environment variables set that JHBuild uses, use the run command:"
msgstr ""
#: C/jhbuild.xml:404(replaceable)
#: C/jhbuild.xml:966(replaceable)
msgid "program"
msgstr "program"
#: C/jhbuild.xml:404(userinput)
#, no-wrap
msgid "jhbuild run shell command:"
msgstr ""
#: C/jhbuild.xml:409(userinput)
#: C/jhbuild.xml:1029(command)
#, no-wrap
msgid "jhbuild shell"
msgstr ""
#: C/jhbuild.xml:415(title)
msgid "Command Reference"
msgstr "Kommandoreferens"
#: C/jhbuild.xml:417(para)
msgid "JHBuild uses a command line syntax similar to tools like CVS:"
msgstr ""
#: C/jhbuild.xml:420(command)
msgid "jhbuild"
msgstr "jhbuild"
#: C/jhbuild.xml:421(replaceable)
msgid "global-options"
msgstr ""
#: C/jhbuild.xml:422(replaceable)
msgid "command"
msgstr ""
#: C/jhbuild.xml:423(replaceable)
msgid "command-arguments"
msgstr ""
#: C/jhbuild.xml:426(para)
msgid "The global JHBuild options are:"
msgstr ""
#: C/jhbuild.xml:430(term)
msgid "-f , --file config "
msgstr ""
#: C/jhbuild.xml:433(simpara)
msgid "Use an alternative configuration file, instead of the default, ~/.jhbuildrc ."
msgstr ""
#: C/jhbuild.xml:439(term)
msgid "-m , --moduleset moduleset "
msgstr ""
#: C/jhbuild.xml:442(simpara)
msgid "Use a module set other than the one listed in the configuration file. This should be a relative path if the module set is located in the JHBuild moduleset folder, or an absolute path if it is located elsewhere."
msgstr ""
#: C/jhbuild.xml:450(option)
msgid "--no-interact"
msgstr ""
#: C/jhbuild.xml:452(simpara)
msgid "Do not prompt the user for any input. This is useful when leaving a build unattended, in order to ensure it is not interrupted."
msgstr ""
#: C/jhbuild.xml:459(para)
msgid "Command specific options are listed below."
msgstr ""
#: C/jhbuild.xml:462(title)
msgid "autobuild"
msgstr ""
#: C/jhbuild.xml:464(para)
msgid "The autobuild command is used to automatically build the modules specified in the configuration file, and then upload the results to JhAutobuild."
msgstr ""
#: C/jhbuild.xml:469(command)
msgid "jhbuild autobuild"
msgstr ""
#: C/jhbuild.xml:470(arg)
#: C/jhbuild.xml:532(arg)
#: C/jhbuild.xml:716(arg)
#: C/jhbuild.xml:1049(arg)
msgid "--autogen"
msgstr "--autogen"
#: C/jhbuild.xml:471(arg)
#: C/jhbuild.xml:533(arg)
#: C/jhbuild.xml:717(arg)
#: C/jhbuild.xml:1050(arg)
msgid "--clean"
msgstr "--clean"
#: C/jhbuild.xml:472(replaceable)
#: C/jhbuild.xml:473(replaceable)
#: C/jhbuild.xml:537(replaceable)
#: C/jhbuild.xml:538(replaceable)
#: C/jhbuild.xml:547(arg)
#: C/jhbuild.xml:724(arg)
#: C/jhbuild.xml:779(arg)
#: C/jhbuild.xml:838(arg)
#: C/jhbuild.xml:869(arg)
#: C/jhbuild.xml:935(arg)
#: C/jhbuild.xml:1053(replaceable)
#: C/jhbuild.xml:1054(replaceable)
#: C/jhbuild.xml:1058(arg)
#: C/jhbuild.xml:1089(replaceable)
#: C/jhbuild.xml:1090(replaceable)
#: C/jhbuild.xml:1093(arg)
#: C/jhbuild.xml:1113(arg)
msgid "module"
msgstr ""
#: C/jhbuild.xml:472(arg)
#: C/jhbuild.xml:537(arg)
#: C/jhbuild.xml:1053(arg)
#: C/jhbuild.xml:1089(arg)
msgid "--skip=--autogen , --clean , --skip and --start-at options are processed in the same way as for the build command."
msgstr ""
#: C/jhbuild.xml:485(term)
msgid "--report-url=reporturl , -r reporturl "
msgstr ""
#: C/jhbuild.xml:488(simpara)
msgid "This option specifies the JhAutobuild URL which JHBuild should report to"
msgstr ""
#: C/jhbuild.xml:494(term)
msgid "--verbose , -v "
msgstr ""
#: C/jhbuild.xml:496(simpara)
msgid "This option causes JHBuild's output to be more verbose"
msgstr ""
#: C/jhbuild.xml:505(title)
msgid "bootstrap"
msgstr ""
#: C/jhbuild.xml:507(para)
msgid "The bootstrap command is used to install a set of build utilities required to build most modules (eg. autoconf, automake, etc)."
msgstr ""
#: C/jhbuild.xml:515(para)
msgid "Internally, bootstrap is implemented using the same code as build , using the bootstrap.modules moduleset."
msgstr ""
#: C/jhbuild.xml:519(para)
msgid "Look at the build command is used to build one or more packages, including their dependencies."
msgstr ""
#: C/jhbuild.xml:534(arg)
msgid "--dist"
msgstr ""
#: C/jhbuild.xml:535(arg)
#: C/jhbuild.xml:583(option)
#: C/jhbuild.xml:718(arg)
msgid "--distcheck"
msgstr ""
#: C/jhbuild.xml:536(arg)
#: C/jhbuild.xml:719(arg)
#: C/jhbuild.xml:1051(arg)
msgid "--no-network"
msgstr ""
#: C/jhbuild.xml:539(replaceable)
#: C/jhbuild.xml:867(replaceable)
#: C/jhbuild.xml:1091(replaceable)
msgid "tags"
msgstr ""
#: C/jhbuild.xml:539(arg)
#: C/jhbuild.xml:867(arg)
#: C/jhbuild.xml:1091(arg)
msgid "--tags=-a , --autogen "
msgstr ""
#: C/jhbuild.xml:557(simpara)
msgid "Always run autogen.sh before building modules. By default, autogen.sh will only be called if the toplevel makefile is missing. Otherwise, it relies on the package's makefiles to detect if configure needs to be rebuilt or rerun."
msgstr ""
#: C/jhbuild.xml:567(term)
msgid "-c , --clean "
msgstr ""
#: C/jhbuild.xml:569(simpara)
msgid "Run make clean before building modules."
msgstr ""
#: C/jhbuild.xml:575(term)
msgid "-d , --dist "
msgstr ""
#: C/jhbuild.xml:577(simpara)
msgid "Run make dist after building modules."
msgstr ""
#: C/jhbuild.xml:585(simpara)
msgid "Run make distcheck after building modules."
msgstr ""
#: C/jhbuild.xml:591(term)
msgid "-n , --no-network "
msgstr ""
#: C/jhbuild.xml:593(simpara)
msgid "Do not access the network when building modules. This will skip download or update stages in a build. If a module can't be built without network access, it will fail."
msgstr ""
#: C/jhbuild.xml:601(term)
msgid "-s , --skip =module,... "
msgstr ""
#: C/jhbuild.xml:604(simpara)
msgid "Ignore the named modules when following dependencies to expand the list of modules to be built."
msgstr ""
#: C/jhbuild.xml:611(term)
#: C/jhbuild.xml:905(term)
msgid "--tags =tag,... "
msgstr ""
#: C/jhbuild.xml:614(simpara)
msgid "Ignore modules that do not match any of tag when following dependencies to expand the list of modules to be built."
msgstr ""
#: C/jhbuild.xml:617(simpara)
msgid "At the moment modules are automatically attributed a tag with the name of the module set they sit in."
msgstr ""
#: C/jhbuild.xml:623(term)
msgid "-t , --start-at =module "
msgstr ""
#: C/jhbuild.xml:626(simpara)
msgid "After expanding the list of modules to build, start at the named module rather than at the beginning of the list. This is useful if the build was interrupted for some reason."
msgstr ""
#: C/jhbuild.xml:634(option)
msgid "-D"
msgstr ""
#: C/jhbuild.xml:637(simpara)
msgid "If the underlying version control system supports it, try to update the source tree to its state at the given date before building. The date string should be in ISO format."
msgstr ""
#: C/jhbuild.xml:645(term)
msgid "-x , --no-xvfb "
msgstr ""
#: C/jhbuild.xml:647(simpara)
msgid "Run graphical tests on the actual X server rather than in a simulated Xvfb"
msgstr ""
#: C/jhbuild.xml:653(term)
msgid "-C , --try-checkout "
msgstr ""
#: C/jhbuild.xml:656(simpara)
msgid "If the build fails, and the version control system supports it, force a checkout and run autogen.sh before retrying the build."
msgstr ""
#: C/jhbuild.xml:664(term)
msgid "-N , --no-poison "
msgstr ""
#: C/jhbuild.xml:666(simpara)
msgid "If one or more of a module's dependencies failed, this option forces JHBuild to try to build the module anyway."
msgstr ""
#: C/jhbuild.xml:673(term)
msgid "-f , --force "
msgstr ""
#: C/jhbuild.xml:675(simpara)
msgid "Build the modules even if policy tells it is not required."
msgstr ""
#: C/jhbuild.xml:683(simpara)
msgid "Some modules, listed as optional dependencies, may not be required to build the target module, this option inncludes them nevertheless."
msgstr ""
#: C/jhbuild.xml:690(term)
msgid "--min-time =time "
msgstr ""
#: C/jhbuild.xml:692(simpara)
msgid "Skip modules installed more recently than the given relative time; the time string format is a number followed by a unit, with the following units being supported: seconds (s), minutes (m), hours (h) and days (d)."
msgstr ""
#: C/jhbuild.xml:697(simpara)
msgid "Example: --min-time=2h will skip modules that have been built less than two hours ago."
msgstr ""
#: C/jhbuild.xml:707(title)
msgid "buildone"
msgstr ""
#: C/jhbuild.xml:709(para)
msgid "The buildone command is similar to build , but it does not use dependency information to expand the module list. It is useful for quickly rebuilding one or more modules."
msgstr ""
#: C/jhbuild.xml:715(command)
msgid "jhbuild buildone"
msgstr ""
#: C/jhbuild.xml:727(para)
msgid "The --autogen , --clean , -d , --distcheck , --no-network , -D and -x options are processed in the same way as for the build command."
msgstr ""
#: C/jhbuild.xml:733(para)
msgid "Unlike the build command, at least one module must be listed on the command line."
msgstr ""
#: C/jhbuild.xml:739(title)
msgid "checkbranches"
msgstr ""
#: C/jhbuild.xml:741(para)
msgid "The checkbranches checks the modules in GNOME Subversion have the correct branch definition. For example, if modules are marked as not having branched, JHBuild checks this is true."
msgstr ""
#: C/jhbuild.xml:747(command)
msgid "jhbuild checkbranches"
msgstr ""
#: C/jhbuild.xml:748(replaceable)
msgid "branch"
msgstr ""
#: C/jhbuild.xml:748(arg)
msgid "--branch=--branch =branch , -b branch "
msgstr ""
#: C/jhbuild.xml:755(simpara)
msgid "Specify the branch to check"
msgstr ""
#: C/jhbuild.xml:760(userinput)
#, no-wrap
msgid "jhbuild -m gnome-2.20 checkbranches"
msgstr ""
#: C/jhbuild.xml:760(screen)
#, no-wrap
msgid ""
"dot command generates a file describing the directed graph formed by the dependencies between a set of modules. This file can then be processed using the GraphViz software to produce a nice diagram."
msgstr ""
#: C/jhbuild.xml:776(command)
msgid "jhbuild dot"
msgstr ""
#: C/jhbuild.xml:777(arg)
msgid "--soft-deps"
msgstr ""
#: C/jhbuild.xml:778(arg)
msgid "--clusters"
msgstr ""
#: C/jhbuild.xml:785(para)
msgid "The --soft-deps option will add dotted lines from the modules to their soft dependencies. The --clusters option will group modules from dot utility to generate a PostScript file:"
msgstr ""
#: C/jhbuild.xml:795(userinput)
#, no-wrap
msgid "jhbuild dot gui command starts a graphical interface to JHBuild which can be used to select modules to build and change some options."
msgstr ""
#: C/jhbuild.xml:822(command)
msgid "jhbuild gui"
msgstr ""
#: C/jhbuild.xml:825(para)
msgid "The gui graphical interface is rendered using GTK, so some extra support libraries will be required"
msgstr ""
#: C/jhbuild.xml:831(title)
msgid "info"
msgstr ""
#: C/jhbuild.xml:833(para)
msgid "The info command is used to display information about one or more modules."
msgstr ""
#: C/jhbuild.xml:837(command)
msgid "jhbuild info"
msgstr ""
#: C/jhbuild.xml:841(para)
msgid "The command prints the module name, type, dependencies, dependent packages, and the time it was last installed with JHBuild. It may also print some information specific to the module type, such as the CVS repository or download URL."
msgstr ""
#: C/jhbuild.xml:846(para)
msgid "If there is no module specified the command will print information about all the modules defined in the module set."
msgstr ""
#: C/jhbuild.xml:852(title)
msgid "list"
msgstr ""
#: C/jhbuild.xml:854(para)
msgid "The list command is used to show the expanded list of modules the build command would build."
msgstr ""
#: C/jhbuild.xml:858(para)
msgid "Run with the -a option, this command will list all the modules known from your moduleset configuration regardless of the build dependency."
msgstr ""
#: C/jhbuild.xml:864(arg)
msgid "-a"
msgstr ""
#: C/jhbuild.xml:865(arg)
msgid "-r"
msgstr ""
#: C/jhbuild.xml:866(arg)
msgid "-s"
msgstr ""
#: C/jhbuild.xml:868(arg)
#: C/jhbuild.xml:915(option)
msgid "--list-optional-modules"
msgstr ""
#: C/jhbuild.xml:877(term)
msgid "-a , --all-modules "
msgstr ""
#: C/jhbuild.xml:880(simpara)
msgid "List all the modules"
msgstr ""
#: C/jhbuild.xml:885(term)
msgid "-r , --show-revision "
msgstr ""
#: C/jhbuild.xml:888(simpara)
msgid "If a particular module is being checked out on a branch, show the branch tag name with the module name."
msgstr ""
#: C/jhbuild.xml:895(term)
msgid "s , --skip =module,... "
msgstr ""
#: C/jhbuild.xml:899(simpara)
msgid "Ignore the named modules when following dependencies to expand the list of modules."
msgstr ""
#: C/jhbuild.xml:908(simpara)
msgid "Ignore modules that do not match any of tag when following dependencies to expand the list of modules to be displayed."
msgstr ""
#: C/jhbuild.xml:917(simpara)
msgid "Some modules, listed as optional dependencies, may not be required to get to the target module, this option inncludes them nevertheless."
msgstr ""
#: C/jhbuild.xml:928(title)
msgid "rdepends"
msgstr ""
#: C/jhbuild.xml:930(para)
msgid "The rdepends command is used to show the reverse-dependencies of a module."
msgstr ""
#: C/jhbuild.xml:934(command)
msgid "jhbuild rdepends"
msgstr ""
#: C/jhbuild.xml:940(option)
msgid "--dependencies"
msgstr ""
#: C/jhbuild.xml:942(simpara)
msgid "Show dependency path next to modules."
msgstr ""
#: C/jhbuild.xml:947(option)
msgid "--direct"
msgstr ""
#: C/jhbuild.xml:949(simpara)
msgid "Limit display to modules directly depending on given module."
msgstr ""
#: C/jhbuild.xml:957(title)
msgid "run"
msgstr ""
#: C/jhbuild.xml:959(para)
msgid "The run command is used to run an arbitrary command using the same environment that JHBuild uses when building modules."
msgstr ""
#: C/jhbuild.xml:964(command)
msgid "jhbuild run"
msgstr ""
#: C/jhbuild.xml:965(arg)
msgid "--in-builddir"
msgstr ""
#: C/jhbuild.xml:967(replaceable)
msgid "argument"
msgstr ""
#: C/jhbuild.xml:970(para)
msgid "If using JHBuild to build GNOME, this command can be useful in X startup scripts."
msgstr ""
#: C/jhbuild.xml:975(term)
msgid "--in-builddir =module "
msgstr ""
#: C/jhbuild.xml:977(simpara)
msgid "Run the command in the build directory of the specified module."
msgstr ""
#: C/jhbuild.xml:986(title)
msgid "sanitycheck"
msgstr ""
#: C/jhbuild.xml:988(para)
msgid "The sanitycheck command performs a number of checks to see whether the build environment is okay."
msgstr ""
#: C/jhbuild.xml:996(para)
msgid "Some of the checks include:"
msgstr ""
#: C/jhbuild.xml:1000(simpara)
msgid "That the checkout and install prefixes are writable."
msgstr ""
#: C/jhbuild.xml:1004(simpara)
msgid "That some of the required build tools are installed."
msgstr ""
#: C/jhbuild.xml:1008(simpara)
msgid "That some commonly used macros are available in the search paths of the aclocal commands associated with the various versions of automake ."
msgstr ""
#: C/jhbuild.xml:1014(simpara)
msgid "That the XML catalog contains the DocBook DTD and stylesheets."
msgstr ""
#: C/jhbuild.xml:1022(title)
msgid "shell"
msgstr ""
#: C/jhbuild.xml:1024(para)
msgid "The shell command starts the user's shell with the same environment as JHBuild uses when building modules."
msgstr ""
#: C/jhbuild.xml:1032(para)
msgid "This command is roughly equivalent to the following:"
msgstr ""
#: C/jhbuild.xml:1035(userinput)
#, no-wrap
msgid "jhbuild run $SHELL"
msgstr ""
#: C/jhbuild.xml:1039(title)
msgid "tinderbox"
msgstr ""
#: C/jhbuild.xml:1041(para)
msgid "The tinderbox command is similar to build , but writes all terminal output to HTML files suitable for publishing on a website. It can be used to set up systems similar to Mozilla's Tinderbox, or Debian's Buildd."
msgstr ""
#: C/jhbuild.xml:1048(command)
msgid "jhbuild tinderbox"
msgstr ""
#: C/jhbuild.xml:1052(replaceable)
msgid "directory"
msgstr ""
#: C/jhbuild.xml:1052(arg)
msgid "--output=--autogen , --clean , --no-network , --skip , --start-at , -D , -C and -N options are processed the same as for build ."
msgstr ""
#: C/jhbuild.xml:1069(term)
msgid "-o , --output =directory "
msgstr ""
#: C/jhbuild.xml:1072(simpara)
msgid "The directory to write the HTML build logs."
msgstr ""
#: C/jhbuild.xml:1081(title)
msgid "update"
msgstr ""
#: C/jhbuild.xml:1083(para)
msgid "The update command is similar to build , but only performs the download or update stage for modules without building them."
msgstr ""
#: C/jhbuild.xml:1096(para)
msgid "The --skip , --start-at , --tags and -D options are processed the same as for build ."
msgstr ""
#: C/jhbuild.xml:1103(title)
msgid "updateone"
msgstr ""
#: C/jhbuild.xml:1105(para)
msgid "The updateone command is similar to update , but it does not use dependency information to expand the module list. It is useful for quickly updating one or more modules."
msgstr ""
#: C/jhbuild.xml:1111(command)
msgid "jhbuild updateone"
msgstr ""
#: C/jhbuild.xml:1116(para)
msgid "The -D option is processed the same as for update ."
msgstr ""
#: C/jhbuild.xml:1119(para)
msgid "Unlike the update command, at least one module must be listed on the command line."
msgstr ""
#: C/jhbuild.xml:1126(title)
msgid "Configuration File Reference"
msgstr ""
#: C/jhbuild.xml:1128(para)
msgid "The ~/.jhbuildrc file uses standard Python syntax. The file is run, and the resulting variables defined in the namespace are used to control how JHBuild acts. A set of default values are inserted into the namespace before running the user's configuration file."
msgstr ""
#: C/jhbuild.xml:1135(title)
msgid "Configuration Variables"
msgstr ""
#: C/jhbuild.xml:1140(varname)
msgid "alwaysautogen"
msgstr ""
#: C/jhbuild.xml:1142(simpara)
msgid "If set to True , then always run autogen.sh before make , even if a makefile exists. This is equivalent to passing --always-autogen option to JHBuild. Defaults to False ."
msgstr ""
#: C/jhbuild.xml:1153(simpara)
msgid "A string containing arguments passed to the autogen.sh script of all modules. Can be overriden for particular modules using the module_autogenargs dictionary."
msgstr ""
#: C/jhbuild.xml:1161(varname)
msgid "branches"
msgstr ""
#: C/jhbuild.xml:1163(simpara)
msgid "A dictionary that can be used to override the branch used for a particular module. This is useful if you are making some changes on a branch of a module and want JHBuild to build that branch instead of the one listed in the module set."
msgstr ""
#: C/jhbuild.xml:1171(varname)
msgid "builddir_pattern"
msgstr ""
#: C/jhbuild.xml:1173(simpara)
msgid "A printf style formatting pattern used to generate build directory names. This is only used when using separate source and build trees. The %s in the format string will be replaced with the source directory name. Defaults to '%s' ."
msgstr ""
#: C/jhbuild.xml:1182(varname)
msgid "buildroot"
msgstr ""
#: C/jhbuild.xml:1184(simpara)
msgid "A string giving the parent directory to place build trees. Defaults to None , which causes builds to be performed within the source trees."
msgstr ""
#: C/jhbuild.xml:1191(varname)
msgid "buildscript"
msgstr ""
#: C/jhbuild.xml:1193(simpara)
msgid "A string specifying which buildscript to use. This should probably be left as the default, terminal . In particular, do not set to gtk ."
msgstr ""
#: C/jhbuild.xml:1200(varname)
msgid "build_policy"
msgstr ""
#: C/jhbuild.xml:1202(simpara)
msgid "A string specifying which modules to build. The three possible options are all , to build all modules requested, updated to build only modules which have changed, or updated-deps to build modules which have changed or which have dependencies which have changed. Defaults to all ."
msgstr ""
#: C/jhbuild.xml:1214(simpara)
msgid "A string giving the directory to unpack source trees to. Unless buildroot is set, builds will occur in this directory too. Defaults to ~/cvs/gnome2 ."
msgstr ""
#: C/jhbuild.xml:1221(varname)
msgid "checkout_mode"
msgstr ""
#: C/jhbuild.xml:1223(simpara)
msgid "A string specifying how the checkout is done for directories in version control. Defaults to update . This can be set per module using module_checkout_mode ."
msgstr ""
#: C/jhbuild.xml:1230(varname)
msgid "copy_dir"
msgstr ""
#: C/jhbuild.xml:1232(simpara)
msgid "A string specifying the directory to copy to, if the copy checkout mode is in use. Defaults to the checkout directory."
msgstr ""
#: C/jhbuild.xml:1238(varname)
msgid "cvsroots"
msgstr ""
#: C/jhbuild.xml:1240(simpara)
msgid "A dictionary that can be used to change the CVS roots used to check out source code. If you have a CVS account for a particular project, you can set the associated key to use that account rather than the anonymous account. For example, you might want to set 'gnome.org' to ':ext:username @cvs.gnome.org:/cvs/gnome' ."
msgstr ""
#: C/jhbuild.xml:1250(varname)
msgid "cvs_program"
msgstr ""
#: C/jhbuild.xml:1252(simpara)
msgid "A string specifying which program to use for CVS support. Defaults to cvs ."
msgstr ""
#: C/jhbuild.xml:1257(varname)
msgid "interact"
msgstr ""
#: C/jhbuild.xml:1259(simpara)
msgid "A boolean value specifying whether to interact with the user. Setting this value to False is equivalent to passing the --no-interact option. Defaults to True "
msgstr ""
#: C/jhbuild.xml:1269(simpara)
msgid "A string listing additional arguments to be passed to make . Defaults to '' ."
msgstr ""
#: C/jhbuild.xml:1275(varname)
msgid "makecheck"
msgstr ""
#: C/jhbuild.xml:1277(simpara)
msgid "A boolean value specifying whether to run make check after make . Defaults to False ."
msgstr ""
#: C/jhbuild.xml:1284(varname)
msgid "makecheck_advisory"
msgstr ""
#: C/jhbuild.xml:1286(simpara)
msgid "A boolean value specifying whether failures when running make check should be advisory only and not cause a build failure. Defaults to False ."
msgstr ""
#: C/jhbuild.xml:1292(varname)
msgid "makeclean"
msgstr ""
#: C/jhbuild.xml:1294(simpara)
msgid "A boolean value specifying whether to run make clean before make . Defaults to False ."
msgstr ""
#: C/jhbuild.xml:1301(varname)
msgid "makedist"
msgstr ""
#: C/jhbuild.xml:1303(simpara)
msgid "A boolean value specifying whether to run make dist after make . Defaults to False . This setting is equivalent to passing the --dist option."
msgstr ""
#: C/jhbuild.xml:1311(varname)
msgid "makedistcheck"
msgstr ""
#: C/jhbuild.xml:1313(simpara)
msgid "A boolean value specifying whether to run make distcheck after make . Defaults to False . This setting is equivalent to passing the --distcheck option."
msgstr ""
#: C/jhbuild.xml:1321(varname)
msgid "module_autogenargs"
msgstr ""
#: C/jhbuild.xml:1323(simpara)
msgid "A dictionary mapping module names to strings giving arguments to be passed to autogen.sh . The setting in module_autogenargs is used instead of the global autogenargs setting. If a particular module isn't listed in the dictionary, the global autogenargs will be used instead."
msgstr ""
#: C/jhbuild.xml:1334(varname)
msgid "module_checkout_mode"
msgstr ""
#: C/jhbuild.xml:1336(simpara)
msgid "A dictionary specifying which checkout mode to use for modules. This overrides the global checkout_mode setting."
msgstr ""
#: C/jhbuild.xml:1342(varname)
msgid "module_makeargs"
msgstr ""
#: C/jhbuild.xml:1344(simpara)
msgid "A dictionary mapping module names to strings giving arguments to be passed to make . The setting in module_makeargs replaces the value of makeargs . If a particular module isn't listed in the dictionary, the global makeargs will be used instead."
msgstr ""
#: C/jhbuild.xml:1354(varname)
msgid "module_extra_env"
msgstr ""
#: C/jhbuild.xml:1356(simpara)
msgid "A dictionary mapping module names to dictionaries with extra environment variables to pass when executing commands for the module."
msgstr ""
#: C/jhbuild.xml:1365(simpara)
msgid "A list of module names to build. This list will be expanded using the dependency information found in the module set. Defaults to [ 'meta-gnome-desktop' ] ."
msgstr ""
#: C/jhbuild.xml:1374(simpara)
msgid "A string giving the name of the module set to use. This can either be the filename of a moduleset included with JHBuild (excluding the path and extension), or a full HTTP URL to refer to an externally managed module set. Currently defaults to 'gnome-2.22' , but is usually updated as GNOME development progresses."
msgstr ""
#: C/jhbuild.xml:1384(varname)
msgid "nobuild"
msgstr ""
#: C/jhbuild.xml:1386(simpara)
msgid "A boolean value which, if set to True causes JHBuild to not actually modules, but just download and unpack the sources. The default vale is False ."
msgstr ""
#: C/jhbuild.xml:1393(varname)
msgid "nonetwork"
msgstr ""
#: C/jhbuild.xml:1395(simpara)
msgid "A boolean value specifying whether to access the network or not. This affects checking out or updating CVS modules, downloading tarballs and updating module sets. Setting this to True is equivalent to passing the --no-network option to JHBuild. Defaults to False ."
msgstr ""
#: C/jhbuild.xml:1405(varname)
msgid "nonotify"
msgstr ""
#: C/jhbuild.xml:1407(simpara)
msgid "A boolean value specifying whether to emit notifications using the notification daemon. If set to True , notifications are not emitted. Defaults to False ."
msgstr ""
#: C/jhbuild.xml:1414(varname)
msgid "nopoison"
msgstr ""
#: C/jhbuild.xml:1416(simpara)
msgid "A boolean value which, if set to True causes JHBuild to try to build modules even if one or more of the module's dependancies failed to build. This option is equivalent to the --no-poison argument. The default value is False ."
msgstr ""
#: C/jhbuild.xml:1425(varname)
msgid "noxvfb"
msgstr ""
#: C/jhbuild.xml:1427(simpara)
msgid "A boolean value which, if set to True causes JHBuild to run any graphical tests on the real X server, rather than using Xvfb . This option is equivalent to passing --no-xvfb . The default value is False "
msgstr ""
#: C/jhbuild.xml:1438(simpara)
msgid "A string giving the prefix to install modules to. Defaults to '/opt/gnome2' ."
msgstr ""
#: C/jhbuild.xml:1443(varname)
msgid "pretty_print"
msgstr ""
#: C/jhbuild.xml:1445(simpara)
msgid "A boolean value that can be used to disable pretty formatting of subprocess output. Currently there is only support for pretty printing CVS output. You probably only want to disable this if the pretty printing causes problems. Defaults to True ."
msgstr ""
#: C/jhbuild.xml:1453(varname)
msgid "progress_bar"
msgstr ""
#: C/jhbuild.xml:1455(simpara)
msgid "A boolean value that can be used to display a progress bar when running in quiet mode (see below). Defaults to True ."
msgstr ""
#: C/jhbuild.xml:1461(varname)
msgid "quiet_mode"
msgstr ""
#: C/jhbuild.xml:1463(simpara)
msgid "A boolean value that can be used to disable output of running commands. Defaults to False ."
msgstr ""
#: C/jhbuild.xml:1485(simpara)
msgid "A list of modules to skip when expanding the list of modules to build. This is similar to the --skip option (in fact, the --skip option extends this list). This list is empty by default."
msgstr ""
#: C/jhbuild.xml:1493(varname)
msgid "sticky_date"
msgstr ""
#: C/jhbuild.xml:1495(simpara)
msgid "If set, JHBuild will attempt to check out modules as they existed at the given date. The date should be given in the form 'yyyy -mm -dd ' . Defaults to None ."
msgstr ""
#: C/jhbuild.xml:1503(varname)
msgid "svnroots"
msgstr ""
#: C/jhbuild.xml:1505(simpara)
msgid "Similar to cvsroots but for Subversion repositories."
msgstr ""
#: C/jhbuild.xml:1510(varname)
msgid "svn_program"
msgstr ""
#: C/jhbuild.xml:1512(simpara)
msgid "A string specifying which program to use for subversion support. This can be svn or bzr . Defaults to svn ."
msgstr ""
#: C/jhbuild.xml:1519(varname)
msgid "tarballdir"
msgstr ""
#: C/jhbuild.xml:1521(simpara)
msgid "If set, tarballs will be downloaded to this directory instead of checkoutroot . This is useful if you have multiple JHBuild environments or regularly clear out your checkoutroot and want to reduce bandwidth usage."
msgstr ""
#: C/jhbuild.xml:1530(varname)
msgid "tinderbox_outputdir"
msgstr ""
#: C/jhbuild.xml:1532(simpara)
msgid "A string giving the directory to store jhbuild tinderbox output. This string can be overridden by the --output option. Defaults to None , so either the command line option must be used or this variable must be set in the configuration file."
msgstr ""
#: C/jhbuild.xml:1541(varname)
msgid "trycheckout"
msgstr ""
#: C/jhbuild.xml:1543(simpara)
msgid "A boolean option which if set to True , causes JHBuild to try checking out a newer version of a module from version control and running autogen.sh , if the module fails to build. This option is equivalent to passing --try-checkout ."
msgstr ""
#: C/jhbuild.xml:1552(varname)
msgid "use_lib64"
msgstr ""
#: C/jhbuild.xml:1554(simpara)
msgid "A boolean value that specifies whether to install libraries to lib64 directories. If this is set, --libdir=\\${exec_prefix}/lib64 will be passed to configure. Defaults to True if running on x86_64 , ppc64 or s390x Linux, and False on other systems."
msgstr ""
#: C/jhbuild.xml:1566(varname)
msgid "xvfbargs"
msgstr ""
#: C/jhbuild.xml:1568(simpara)
msgid "A string listing arguments to pass to Xvfb if running graphical tests using it."
msgstr ""
#: C/jhbuild.xml:1577(title)
msgid "Other Configuration File Structures"
msgstr ""
#: C/jhbuild.xml:1579(para)
msgid "In addition to the above variables, there are some other things that can be set in the configuration file:"
msgstr ""
#: C/jhbuild.xml:1586(para)
msgid "This is dictionary represents the environment of the process (which also gets passed on to processes that JHBuild spawns)."
msgstr ""
#: C/jhbuild.xml:1589(para)
msgid "Some environment variables you may want to set include CFLAGS , INSTALL (to use the more efficient install-check program included with JHBuild) and LDFLAGS ."
msgstr ""
#: C/jhbuild.xml:1597(term)
msgid "addpath (envvar , pathname )"
msgstr ""
#: C/jhbuild.xml:1600(para)
msgid "This will add a directory to a PATH -style environment variable. It will correctly handle the case when the environment variable is initially empty (having a stray colon at the beginning or end of an environment variable can have unexpected consequences)."
msgstr ""
#: C/jhbuild.xml:1606(para)
msgid "This function has special handling for the ACLOCAL_FLAGS environment variable, which expects paths to be listed in the form -I pathname ."
msgstr ""
#: C/jhbuild.xml:1613(term)
msgid "prependpath (envvar , pathname )"
msgstr ""
#: C/jhbuild.xml:1616(para)
msgid "After processing the configuration file, JHBuild will alter some paths based on variables such as prefix (eg. adding $prefix/bin to the start of PATH )."
msgstr ""
#: C/jhbuild.xml:1621(para)
msgid "The prependpath function works like addpath , except that the environment variable is modified after JHBuild has made its changes to the environment."
msgstr ""
#: C/jhbuild.xml:1632(title)
msgid "Module Set File Syntax"
msgstr ""
#: C/jhbuild.xml:1634(para)
msgid "JHBuild uses XML files to describe the dependencies between modules. A RELAX-NG schema and Document Type Definition are included with JHBuild in the modulesets/ directory. The RELAX-NG schema can be used to edit module set files using nxml-mode in Emacs."
msgstr ""
#: C/jhbuild.xml:1640(para)
msgid "The toplevel element in a module set file is moduleset element. Currently no XML namespace is used, but in the future this might change. The elements below the toplevel come in three types: module sources, include statements and module definitions."
msgstr ""
#: C/jhbuild.xml:1647(title)
#: C/jhbuild.xml:2262(title)
msgid "Module Sources"
msgstr ""
#: C/jhbuild.xml:1649(para)
msgid "Rather than listing the full location of every module, a number of \"module sources\" are listed in the module set, and then referenced by name in the module definitions. As well as reducing the amount of redundant information in the module set, it makes it easy for a user to specify an alternative source for those modules (for CVS and Subversion, it is common for developers and users to use different repository access methods)."
msgstr ""
#: C/jhbuild.xml:1658(para)
msgid "The repository element is used to describe all types of repository."
msgstr ""
#: C/jhbuild.xml:1661(programlisting)
#, no-wrap
msgid ""
"\n"
"<repository name=\"name \"\n"
" type=\"type \"\n"
" [ default=\"default \" ]\n"
" [ password=\"password \" ]\n"
" [ cvsroot=\"cvsroot \" ]\n"
" [ archive=\"archive \" ]\n"
" [ href=\"href \" ]\n"
" [ server=\"server \" ]\n"
" [ database=\"database \" ]\n"
" [ defbranch=\"defbranch \" ]\n"
" [ developer-href-example=\"developer-href-example \" ] />\n"
msgstr ""
#: C/jhbuild.xml:1675(para)
msgid "The name attribute is a unique identifier for the repository."
msgstr ""
#: C/jhbuild.xml:1678(para)
msgid "The default attribute specifies whether this repository is the default source for this module set."
msgstr ""
#: C/jhbuild.xml:1682(para)
msgid "The type attribute specifies the type of repository. It can be one of: arch , bzr , cvs , darcs , git , hg , mtr , svn , tarball . Other attributes depends on the type , as well as the branch used inside module definitions. Those are described below."
msgstr ""
#: C/jhbuild.xml:1693(para)
msgid "The developer-href-example attribute is used to specify the format of the URL for the repository used by developers. This is informational only."
msgstr ""
#: C/jhbuild.xml:1698(title)
msgid "Arch"
msgstr "Arch"
#: C/jhbuild.xml:1700(para)
msgid "This repository type is used to define a Arch repository."
msgstr ""
#: C/jhbuild.xml:1702(para)
msgid "The archive attribute is used to specify the archive to use."
msgstr ""
#: C/jhbuild.xml:1705(para)
msgid "The href attribute is used to specify the URL of the repository."
msgstr ""
#: C/jhbuild.xml:1708(programlisting)
#, no-wrap
msgid ""
"\n"
"<repository type=\"arch\" name=\"rhythmbox\"\n"
" archive=\"rhythmbox-devel@gnome.org--2004\"\n"
" href=\"http://web.rhythmbox.org/arch/2004\"/>\n"
msgstr ""
#: C/jhbuild.xml:1717(title)
msgid "Bazaar"
msgstr "Bazaar"
#: C/jhbuild.xml:1718(para)
msgid "This repository type is used to define a Bazaar repository."
msgstr ""
#: C/jhbuild.xml:1720(programlisting)
#, no-wrap
msgid ""
"\n"
"<repository type=\"bzr\" name=\"launchpad.net\"\n"
" href=\"http://bazaar.launchpad.net/\"/>\n"
msgstr ""
#: C/jhbuild.xml:1727(title)
msgid "CVS"
msgstr "CVS"
#: C/jhbuild.xml:1728(para)
msgid "This repository type is used to define a CVS repository."
msgstr ""
#: C/jhbuild.xml:1730(para)
msgid "The password attribute is used to specify the password to the repository."
msgstr ""
#: C/jhbuild.xml:1734(para)
msgid "The cvsroot attribute is used to specify the root of the repository."
msgstr ""
#: C/jhbuild.xml:1738(programlisting)
#, no-wrap
msgid ""
"\n"
"<repository type=\"cvs\" name=\"tango.freedesktop.org\"\n"
" cvsroot=\":pserver:anoncvs@anoncvs.freedesktop.org:/cvs/tango\"\n"
" password=\"\"/>\n"
msgstr ""
#: C/jhbuild.xml:1747(title)
msgid "Darcs"
msgstr "Darcs"
#: C/jhbuild.xml:1748(para)
msgid "This repository type is used to define a Darcs repository."
msgstr ""
#: C/jhbuild.xml:1750(programlisting)
#, no-wrap
msgid ""
"\n"
"<repository type=\"darcs\" name=\"telepathy.freedesktop.org\"\n"
" href=\"http://projects.collabora.co.uk/darcs/telepathy/\"/>\n"
msgstr ""
#: C/jhbuild.xml:1757(title)
msgid "Git"
msgstr "Git"
#: C/jhbuild.xml:1758(para)
msgid "This repository type is used to define a Git repository."
msgstr ""
#: C/jhbuild.xml:1760(programlisting)
#, no-wrap
msgid ""
"\n"
"<repository type=\"git\" name=\"git.freedesktop.org\"\n"
" href=\"git://anongit.freedesktop.org/git/\"/>\n"
msgstr ""
#: C/jhbuild.xml:1765(programlisting)
#, no-wrap
msgid ""
"\n"
"<branch repo=\"git.freedesktop.org\" module=\"swfdec/swfdec\"\n"
" checkoutdir=\"swfdec\"/>\n"
msgstr ""
#: C/jhbuild.xml:1774(title)
msgid "Mercurial"
msgstr "Mercurial"
#: C/jhbuild.xml:1775(para)
msgid "This repository type is used to define a Mercurial repository."
msgstr ""
#: C/jhbuild.xml:1777(programlisting)
#, no-wrap
msgid ""
"\n"
"<repository type=\"hg\" name=\"hg.gtk-vnc\"\n"
" href=\"http://gtk-vnc.codemonkey.ws/hg/\" />\n"
msgstr ""
#: C/jhbuild.xml:1782(programlisting)
#, no-wrap
msgid ""
"\n"
"<branch repo=\"hg.gtk-vnc\" module=\"outgoing.hg\" checkoutdir=\"gtk-vnc\"/>\n"
msgstr ""
#: C/jhbuild.xml:1789(title)
msgid "Monotone"
msgstr "Monotone"
#: C/jhbuild.xml:1790(para)
msgid "This repository type is used to define a Monotone repository."
msgstr ""
#: C/jhbuild.xml:1792(para)
msgid "The server attribute is used to specify the repository server."
msgstr ""
#: C/jhbuild.xml:1795(para)
msgid "The database attribute is used to specify the database to use for the repository."
msgstr ""
#: C/jhbuild.xml:1799(para)
msgid "The defbranch attribute is used specify the branch of the repository to use."
msgstr ""
#: C/jhbuild.xml:1803(programlisting)
#, no-wrap
msgid ""
"\n"
"<repository type=\"mtn\" name=\"pidgin.im\"\n"
" server=\"pidgin.im\" database=\"pidgin.im.mtn\"\n"
" defbranch=\"im.pidgin.pidgin\"/>\n"
msgstr ""
#: C/jhbuild.xml:1812(title)
msgid "Subversion"
msgstr "Subversion"
#: C/jhbuild.xml:1813(para)
msgid "This repository type is used to define a Subversion repository."
msgstr ""
#: C/jhbuild.xml:1815(programlisting)
#, no-wrap
msgid ""
"\n"
"<repository type=\"svn\" name=\"svn.gnome.org\" default=\"yes\"\n"
" href=\"http://svn.gnome.org/svn/\"/>\n"
msgstr ""
#: C/jhbuild.xml:1820(para)
msgid "It allows a revision on the branch element. This attribute defines the branch to checkout or, if it is a number, a specific revision to checkout."
msgstr ""
#: C/jhbuild.xml:1825(programlisting)
#, no-wrap
msgid ""
"\n"
"<branch revision=\"gnome-2-20\"/>\n"
msgstr ""
#: C/jhbuild.xml:1832(title)
msgid "Tarballs"
msgstr ""
#: C/jhbuild.xml:1833(para)
msgid "This repository type is used to define a tarball repository."
msgstr ""
#: C/jhbuild.xml:1835(programlisting)
#, no-wrap
msgid ""
"\n"
"<repository type=\"tarball\" name=\"dbus/dbus-python\"\n"
" href=\"http://dbus.freedesktop.org/releases/dbus-python/\"/>\n"
msgstr ""
#: C/jhbuild.xml:1840(para)
msgid "It allows the following attributes on the branch element:"
msgstr ""
#: C/jhbuild.xml:1843(para)
msgid "The module attribute specifies the file to download and compile, the version attribute specifies the module version."
msgstr ""
#: C/jhbuild.xml:1848(para)
msgid "The size and md5sum attributes are optional. If these two attributes are present, they are used to check that the source package was downloaded correctly."
msgstr ""
#: C/jhbuild.xml:1853(para)
#: C/jhbuild.xml:2565(para)
msgid "The patches element is used to specify one or more patches to apply to the source tree after unpacking, the file attribute gives the patch filename, and the strip attribute says how many levels of directories to prune when applying the patch."
msgstr ""
#: C/jhbuild.xml:1861(para)
#: C/jhbuild.xml:2573(para)
msgid "For module sets shipped with JHbuild, the patch files are looked up in the jhbuild/patches/ directory; for module sets referred by URI, the patch files are looked for in the same directory as the moduleset file, or in its patches/ subdirectory. It is also possible for the file attribute to specify a URI, in which case it will be downloaded from that location."
msgstr ""
#: C/jhbuild.xml:1870(programlisting)
#, no-wrap
msgid ""
"\n"
"<branch module=\"dbus-python-0.80.2.tar.gz\" version=\"0.80.2\"\n"
" repo=\"dbus/dbus-python\"\n"
" md5sum=\"2807bc85215c995bd595e01edd9d2077\" size=\"453499\">\n"
" <patches>\n"
" <patch file=\"dbus-glib-build.patch\" strip=\"1\" />\n"
" </patches>\n"
"<branch>\n"
msgstr ""
#: C/jhbuild.xml:1885(title)
msgid "Including Other Module Sets"
msgstr ""
#: C/jhbuild.xml:1887(para)
msgid "JHBuild allows one module set to include the contents of another by reference using the include element."
msgstr ""
#: C/jhbuild.xml:1891(programlisting)
#, no-wrap
msgid ""
"\n"
"<include href=\"uri \"/>\n"
msgstr ""
#: C/jhbuild.xml:1895(para)
msgid "The href is a URI reference to the module set to be included, relative to the file containing the include element."
msgstr ""
#: C/jhbuild.xml:1900(para)
msgid "Only module definitions are imported from the referenced module set - module sources are not. Multiple levels of includes are allowed, but include loops are not (there isn't any code to handle loops at the moment)."
msgstr ""
#: C/jhbuild.xml:1907(title)
msgid "Module Definitions"
msgstr ""
#: C/jhbuild.xml:1909(para)
msgid "There are various types of module definitions that can be used in a module set file, and the list can easily be extended. Only the most common ones will be mentioned here."
msgstr ""
#: C/jhbuild.xml:1913(para)
msgid "They are all basically composed of a branch element describing how to get the module and dependencies , suggests and after elements to declare the dependencies of the module."
msgstr ""
#: C/jhbuild.xml:1920(para)
msgid "Any modules listed in the dependencies element will be added to the module list for jhbuild build if it isn't already included, and make sure the dependent modules are built first."
msgstr ""
#: C/jhbuild.xml:1926(para)
msgid "After generating the modules list, the modules listed in the suggests element will be used to further sort the modules list (although it will not pull any additional modules). This is intended for cases where a module has an optional dependency on another module."
msgstr ""
#: C/jhbuild.xml:1934(title)
msgid "autotools"
msgstr "autotools"
#: C/jhbuild.xml:1936(para)
msgid "The autotools element is used to define a module which is compiled using the GNU Autotools build system."
msgstr ""
#: C/jhbuild.xml:1940(programlisting)
#, no-wrap
msgid ""
"\n"
"<autotools id=\"id \"\n"
"\t [ autogenargs=\"autogenargs \" ]\n"
"\t [ makeargs=\"makeargs \" ]\n"
"\t [ makeinstallargs=\"makeinstallargs \" ]\n"
"\t [ autogen-sh=\"autogen-sh \" ]\n"
"\t [ makefile=\"makefile \" ]\n"
"\t [ skip-autogen=\"skip-autogen \" ]\n"
"\t [ autogen-template=\"autogen-template \" ]\n"
"\t [ supports-non-srcdir-builds=\"supports-non-srcdir-builds \" ]>\n"
"\n"
" <branch [ ... ] >\n"
" [...]\n"
" </branch>\n"
"\n"
" <dependencies>\n"
" <dep package=\"modulename \"/>\n"
" ...\n"
" </dependencies>\n"
" <after>\n"
" <dep package=\"modulename \"/>\n"
" ...\n"
" </after>\n"
"\n"
"</autotools>\n"
msgstr ""
#: C/jhbuild.xml:1967(para)
msgid "The autogenargs and makeargs and makeinstallargs attributes are used to specify additional arguments to pass to autogen.sh , make and make install respectively."
msgstr ""
#: C/jhbuild.xml:1974(para)
msgid "The autogen-sh attribute specifies the name of the autogen.sh script to run. The value autoreconf can be used if your module has no autogen.sh script equivalent. In that case, JHBuild will run autoreconf -i , followed by the proper configure . skip-autogen chooses whether or not to run autogen.sh. makefile specifies the filename of the makefile to use."
msgstr ""
#: C/jhbuild.xml:1987(para)
msgid "The supports-non-srcdir-builds attribute is used to mark modules that can't be cleanly built using a separate source directory."
msgstr ""
#: C/jhbuild.xml:1992(para)
msgid "The autogen-template attribute can be used if you need finer control over the autogen command line. It is a python format string, which will be substituted with the following variables: srcdir , autogen-sh , prefix , libdir , and autogenargs . For example, here is the default autogen-template:"
msgstr ""
#: C/jhbuild.xml:2001(programlisting)
#, no-wrap
msgid ""
"\n"
"%(srcdir)s/%(autogen-sh)s --prefix %(prefix)s --libdir %(libdir)s %(autogenargs)s\n"
msgstr ""
#: C/jhbuild.xml:2008(title)
msgid "cmake"
msgstr "cmake"
#: C/jhbuild.xml:2010(para)
msgid "The cmake element is used to define a module which is built using the CMake build system."
msgstr ""
#: C/jhbuild.xml:2013(programlisting)
#, no-wrap
msgid ""
"\n"
"<cmake id=\"modulename \">\n"
" <branch [ ... ] >\n"
" [...]\n"
" </branch>\n"
"\n"
" <dependencies>\n"
" <dep package=\"modulename \"/>\n"
" ...\n"
" </dependencies>\n"
" <after>\n"
" <dep package=\"modulename \"/>\n"
" ...\n"
" </after>\n"
"</cmake>\n"
msgstr ""
#: C/jhbuild.xml:2033(title)
msgid "distutils"
msgstr "distutils"
#: C/jhbuild.xml:2035(para)
msgid "The distutils element is used to define a module which is built using python's distutils"
msgstr ""
#: C/jhbuild.xml:2039(programlisting)
#, no-wrap
msgid ""
"\n"
"<distutils id=\"modulename \"\n"
" [ supports-non-srcdir-builds=\"yes|no \" ]>\n"
" <branch [ ... ] >\n"
" [...]\n"
" </branch>\n"
"\n"
" <dependencies>\n"
" <dep package=\"modulename \"/>\n"
" ...\n"
" </dependencies>\n"
" <after>\n"
" <dep package=\"modulename \"/>\n"
" ...\n"
" </after>\n"
"</distutils>\n"
msgstr ""
#: C/jhbuild.xml:2060(title)
msgid "linux"
msgstr "linux"
#: C/jhbuild.xml:2062(para)
msgid "The linux element defines a module used to build a linux kernel. In addition, a separate kernel configuration can be chosen using the kconfig subelement."
msgstr ""
#: C/jhbuild.xml:2068(programlisting)
#, no-wrap
msgid ""
"\n"
"<linux id=\"id \"\n"
"\t [ makeargs=\"makeargs \" ]>\n"
"\n"
" <branch [ ... ] >\n"
" [...]\n"
" </branch>\n"
"\n"
" <dependencies>\n"
" <dep package=\"modulename \"/>\n"
" ...\n"
" </dependencies>\n"
" <after>\n"
" <dep package=\"modulename \"/>\n"
" ...\n"
" </after>\n"
"\n"
" <kconfig [ repo=\"repo \" ]\n"
"\t version=\"version \"\n"
"\t [ module=\"module \" ]\n"
"\t [ config=\"config \" ] />\n"
"\n"
"</linux>\n"
msgstr ""
#: C/jhbuild.xml:2096(title)
msgid "perl"
msgstr "perl"
#: C/jhbuild.xml:2098(para)
msgid "The perl element is used to build perl modules."
msgstr ""
#: C/jhbuild.xml:2101(para)
msgid "The makeargs attribute is used to specify additional arguments to pass to make ."
msgstr ""
#: C/jhbuild.xml:2105(programlisting)
#, no-wrap
msgid ""
"\n"
"<perl id=\"modulename \"\n"
"\t [ makeargs=\"makeargs \" ]>\n"
"\n"
" <branch [ ... ] >\n"
" [...]\n"
" </branch>\n"
"\n"
" <dependencies>\n"
" <dep package=\"modulename \"/>\n"
" ...\n"
" </dependencies>\n"
" <after>\n"
" <dep package=\"modulename \"/>\n"
" ...\n"
" </after>\n"
"\n"
"</perl>\n"
msgstr ""
#: C/jhbuild.xml:2127(title)
msgid "waf"
msgstr "waf"
#: C/jhbuild.xml:2129(para)
msgid "The waf element is used to define a module which is built using the Waf build system."
msgstr ""
#: C/jhbuild.xml:2132(para)
msgid "The waf-command attribute is used to specify the waf command script to use; it defaults to waf ."
msgstr ""
#: C/jhbuild.xml:2136(programlisting)
#, no-wrap
msgid ""
"\n"
"<waf id=\"modulename \">\n"
"\t [ waf-command=\"waf-command \" ]>\n"
" <branch [ ... ] >\n"
" [...]\n"
" </branch>\n"
"\n"
" <dependencies>\n"
" <dep package=\"modulename \"/>\n"
" ...\n"
" </dependencies>\n"
" <after>\n"
" <dep package=\"modulename \"/>\n"
" ...\n"
" </after>\n"
"</waf>\n"
msgstr ""
#: C/jhbuild.xml:2157(title)
msgid "Ant"
msgstr "Ant"
#: C/jhbuild.xml:2159(para)
msgid "The ant element is used to define a module which is built using Ant, the Java based build tool."
msgstr ""
#: C/jhbuild.xml:2162(programlisting)
#, no-wrap
msgid ""
"\n"
"<ant id=\"modulename \">\n"
" <branch [ ... ] >\n"
" [...]\n"
" </branch>\n"
"\n"
" <dependencies>\n"
" <dep package=\"modulename \"/>\n"
" ...\n"
" </dependencies>\n"
" <after>\n"
" <dep package=\"modulename \"/>\n"
" ...\n"
" </after>\n"
"</ant>\n"
msgstr ""
#: C/jhbuild.xml:2180(title)
msgid "Example of a module built with ant"
msgstr ""
#: C/jhbuild.xml:2194(title)
msgid "testmodule"
msgstr ""
#: C/jhbuild.xml:2196(para)
msgid "The testmodule element is used to create a module which runs a suite of tests using LDTP or Dogtail."
msgstr ""
#: C/jhbuild.xml:2200(programlisting)
#, no-wrap
msgid ""
"\n"
"<testmodule id=\"id \"\n"
"\t type=\"type \">\n"
"\n"
" <branch [ ... ] >\n"
" [...]\n"
" </branch>\n"
"\n"
" <dependencies>\n"
" <dep package=\"modulename \"/>\n"
" ...\n"
" </dependencies>\n"
" <after>\n"
" <dep package=\"modulename \"/>\n"
" ...\n"
" </after>\n"
"\n"
" <testedmodules>\n"
" <tested package=\"package \" />\n"
" </testedmodules>\n"
"\n"
"</testmodule>\n"
msgstr ""
#: C/jhbuild.xml:2227(title)
msgid "metamodule"
msgstr ""
#: C/jhbuild.xml:2229(para)
msgid "The metamodule element defines a module that doesn't actually do anything. The only purpose of a module of this type is its dependencies."
msgstr ""
#: C/jhbuild.xml:2234(para)
msgid "For example, meta-gnome-desktop depends on all the key components of the GNOME desktop, therefore telling JHBuild to install it actually installs the full desktop."
msgstr ""
#: C/jhbuild.xml:2238(programlisting)
#, no-wrap
msgid ""
"\n"
"<metamodule id=\"modulename \">\n"
" <dependencies>\n"
" <dep package=\"modulename \"/>\n"
" ...\n"
" </dependencies>\n"
" <suggests>\n"
" <dep package=\"modulename \"/>\n"
" ...\n"
" </suggests>\n"
"</metamodule>\n"
msgstr ""
#: C/jhbuild.xml:2250(para)
msgid "The id attribute gives the name of the module. The child elements are handled as for cvsmodule ."
msgstr ""
#: C/jhbuild.xml:2259(title)
msgid "Deprecated Elements"
msgstr ""
#: C/jhbuild.xml:2265(title)
msgid "cvsroot"
msgstr ""
#: C/jhbuild.xml:2267(para)
msgid "The cvsroot element is now deprecated - the repository element should be used instead."
msgstr ""
#: C/jhbuild.xml:2272(para)
msgid "The cvsroot element is used to describe a CVS repository."
msgstr ""
#: C/jhbuild.xml:2275(programlisting)
#, no-wrap
msgid ""
"\n"
" <cvsroot name=\"rootname \"\n"
" [ default=\"yes|no \" ]\n"
" root=\"anon-cvsroot \"\n"
" password=\"anon-password \"/>\n"
msgstr ""
#: C/jhbuild.xml:2282(para)
msgid "The name attribute should be a unique identifier for the CVS repository."
msgstr ""
#: C/jhbuild.xml:2285(para)
msgid "The default attribute says whether this is the default module source for this module set file."
msgstr ""
#: C/jhbuild.xml:2289(para)
msgid "The root attribute lists the CVS root used for anonymous access to this repository, and the password attribute gives the password used for anonymous access."
msgstr ""
#: C/jhbuild.xml:2297(title)
msgid "svnroot"
msgstr ""
#: C/jhbuild.xml:2299(para)
msgid "The svnroot element is now deprecated - the repository element should be used instead."
msgstr ""
#: C/jhbuild.xml:2304(para)
msgid "The svnroot element is used to describe a Subversion repository."
msgstr ""
#: C/jhbuild.xml:2307(programlisting)
#, no-wrap
msgid ""
"\n"
" <svnroot name=\"rootname \"\n"
" [ default=\"yes|no \" ]\n"
" href=\"anon-svnroot \"/>\n"
msgstr ""
#: C/jhbuild.xml:2313(para)
msgid "The name attribute should be a unique identifier for the Subversion repository."
msgstr ""
#: C/jhbuild.xml:2317(para)
#: C/jhbuild.xml:2347(para)
msgid "If default attribute says whether this is the default module source for this module set file."
msgstr ""
#: C/jhbuild.xml:2321(para)
msgid "The href attribute lists the base URL for the repository. This will probably be either a http , https or svn URL."
msgstr ""
#: C/jhbuild.xml:2328(title)
msgid "arch-archive"
msgstr ""
#: C/jhbuild.xml:2330(para)
msgid "The arch-archive element is now deprecated - the repository element should be used instead."
msgstr ""
#: C/jhbuild.xml:2335(para)
msgid "The arch-archive element is used to describe a GNU Arch archive."
msgstr ""
#: C/jhbuild.xml:2338(programlisting)
#, no-wrap
msgid ""
"\n"
" <arch-archive name=\"archivename \"\n"
" [ default=\"yes|no \" ]\n"
" href=\"mirror-url \"/>\n"
msgstr ""
#: C/jhbuild.xml:2344(para)
msgid "The name attribute should be the Arch archive name."
msgstr ""
#: C/jhbuild.xml:2351(para)
msgid "The href attribute lists a public mirror URL for the archive."
msgstr ""
#: C/jhbuild.xml:2357(title)
msgid "Deprecated Module Types"
msgstr ""
#: C/jhbuild.xml:2360(para)
msgid "This section describes deprecated elements, they may still be used in existing module sets but it is advised not to use them anymore."
msgstr ""
#: C/jhbuild.xml:2366(title)
msgid "cvsmodule"
msgstr ""
#: C/jhbuild.xml:2368(para)
msgid "The cvsmodule element is now deprecated. The appropriate build system's module should be used instead."
msgstr ""
#: C/jhbuild.xml:2372(para)
msgid "The cvsmodule element is used to define a module that is to be built from CVS."
msgstr ""
#: C/jhbuild.xml:2376(programlisting)
#, no-wrap
msgid ""
"\n"
" <cvsmodule module=\"modulename \"\n"
" [ revision=\"branch-or-tag \" ]\n"
" [ checkoutdir=\"directory \" ]\n"
" [ root=\"rootname \" ]\n"
" [ autogenargs=\"autogenargs \" ]\n"
" [ makeargs=\"makeargs \" ]\n"
" [ supports-non-srcdir-builds=\"yes|no \" ]>\n"
" <dependencies>\n"
" <dep package=\"modulename \"/>\n"
" ...\n"
" </dependencies>\n"
" <suggests>\n"
" <dep package=\"modulename \"/>\n"
" ...\n"
" </suggests>\n"
" <after>\n"
" <dep package=\"modulename \"/>\n"
" ...\n"
" >\n"
" </cvsmodule>\n"
msgstr ""
#: C/jhbuild.xml:2399(para)
msgid "The module , revision and root attributes identify the module to check out from CVS. The checkoutdir attribute can be used to specify an alternative directory to check out to (by default, the value of module is used)."
msgstr ""
#: C/jhbuild.xml:2408(para)
msgid "The autogenargs , makeargs and supports-non-srcdir-builds attributes are common to many different module types. The autogenargs attribute lists additional arguments to be passed to autogen.sh , and makeargs lists additional arguments to be passed to make . The supports-non-srcdir-builds attribute is used to mark modules that can't be cleanly built using a separate source directory."
msgstr ""
#: C/jhbuild.xml:2422(para)
msgid "The dependencies , suggests and after elements are processed as for svnmodule element is now deprecated. The appropriate build system's module should be used instead."
msgstr ""
#: C/jhbuild.xml:2438(para)
msgid "The svnmodule element is used to define a module that is to be built from Subversion."
msgstr ""
#: C/jhbuild.xml:2442(programlisting)
#, no-wrap
msgid ""
"\n"
" <svnmodule module=\"modulename \"\n"
" [ checkoutdir=\"directory \" ]\n"
" [ root=\"rootname \" ]\n"
" [ autogenargs=\"autogenargs \" ]\n"
" [ makeargs=\"makeargs \" ]\n"
" [ supports-non-srcdir-builds=\"yes|no \" ]>\n"
" <dependencies>\n"
" <dep package=\"modulename \"/>\n"
" ...\n"
" </dependencies>\n"
" <suggests>\n"
" <dep package=\"modulename \"/>\n"
" ...\n"
" </suggests>\n"
" <after>\n"
" <dep package=\"modulename \"/>\n"
" ...\n"
" </after>\n"
" </svnmodule>\n"
msgstr ""
#: C/jhbuild.xml:2463(para)
msgid "The module attribute gives the path of the module relative to the repository URI. All other options for this element are processed as for cvsmodule ."
msgstr ""
#: C/jhbuild.xml:2472(title)
msgid "archmodule"
msgstr ""
#: C/jhbuild.xml:2474(para)
msgid "The archmodule element is now deprecated. The appropriate build system's module should be used instead."
msgstr ""
#: C/jhbuild.xml:2478(para)
msgid "The archmodule element is used to define a module that is to be built from a GNU Arch archive."
msgstr ""
#: C/jhbuild.xml:2482(programlisting)
#, no-wrap
msgid ""
"\n"
" <archmodule version=\"modulename \"\n"
" [ checkoutdir=\"directory \" ]\n"
" [ root=\"rootname \" ]\n"
" [ autogenargs=\"autogenargs \" ]\n"
" [ makeargs=\"makeargs \" ]\n"
" [ supports-non-srcdir-builds=\"yes|no \" ]>\n"
" <dependencies>\n"
" <dep package=\"modulename \"/>\n"
" ...\n"
" </dependencies>\n"
" <suggests>\n"
" <dep package=\"modulename \"/>\n"
" ...\n"
" </suggests>\n"
" <after>\n"
" <dep package=\"modulename \"/>\n"
" ...\n"
" </after>\n"
" </archmodule>\n"
msgstr ""
#: C/jhbuild.xml:2503(para)
msgid "The version attribute gives the version to be checked out from the archive specified by root . All other options for this element are processed as for cvsmodule ."
msgstr ""
#: C/jhbuild.xml:2512(title)
msgid "tarball"
msgstr ""
#: C/jhbuild.xml:2515(para)
msgid "The tarball element is now deprecated. The appropriate build type module should be used instead. As a transitive measure this element has however been reimplemented as a thin wrapper around both autotools module type and tarball repository type."
msgstr ""
#: C/jhbuild.xml:2524(para)
msgid "The tarball element is used to define a module that is to be built from a tarball."
msgstr ""
#: C/jhbuild.xml:2528(programlisting)
#, no-wrap
msgid ""
"\n"
" <tarball id=\"modulename \"\n"
" [ version=\"version \" ]\n"
" [ checkourdir=\"checkoutdir \" ]\n"
" [ autogenargs=\"autogenargs \" ]\n"
" [ makeargs=\"makeargs \" ]\n"
" [ autogen-sh=\"autogen-sh \" ]\n"
" [ supports-non-srcdir-builds=\"yes|no \" ]>\n"
" <source href=\"source-url \"\n"
" [ size=\"source-size \" ]\n"
" [ md5sum=\"source-md5sum \" ]/>\n"
" <patches>\n"
" <patch file=\"filename \" strip=\"level \"/>\n"
" ...\n"
" </patches>\n"
" <dependencies>\n"
" <dep package=\"modulename \"/>\n"
" ...\n"
" </dependencies>\n"
" <suggests>\n"
" <dep package=\"modulename \"/>\n"
" ...\n"
" </suggests>\n"
" </tarball>\n"
msgstr ""
#: C/jhbuild.xml:2553(para)
msgid "The id and version attributes are used to identify the module."
msgstr ""
#: C/jhbuild.xml:2557(para)
msgid "The source element specifies the file to download and compile. The href attribute is mandatory, while the size and md5sum attributes are optional. If these last two attributes are present, they are used to check that the source package was downloaded correctly."
msgstr ""
#: C/jhbuild.xml:2582(para)
msgid "The other attributes and the dependencies and suggests sub-elements are processed as for cvsmodule ."
msgstr ""
#: C/jhbuild.xml:2594(title)
msgid "Frequently Asked Questions"
msgstr ""
#: C/jhbuild.xml:2598(title)
msgid "General JHBuild Questions"
msgstr ""
#: C/jhbuild.xml:2601(simpara)
msgid "The wget command can't download any tarballs. How do I get it to work with my firewall?"
msgstr ""
#: C/jhbuild.xml:2606(para)
msgid "This can be fixed by creating or editing a ~/.wgetrc file. If you need to go through an HTTP proxy to access FTP sites, add a line like the following to the file:"
msgstr ""
#: C/jhbuild.xml:2610(programlisting)
#, no-wrap
msgid "ftp_proxy = http://hostname :port /"
msgstr ""
#: C/jhbuild.xml:2611(para)
msgid "If you just need to use passive FTP connections (sometimes needed with NAT firewalls), add the following line:"
msgstr ""
#: C/jhbuild.xml:2614(programlisting)
#, no-wrap
msgid "passive_ftp = on"
msgstr ""
#: C/jhbuild.xml:2615(para)
msgid "This will fix all uses of the wget command."
msgstr ""
#: C/jhbuild.xml:2621(simpara)
msgid "Building stuff is slow. Is there any way I can speed it up?"
msgstr ""
#: C/jhbuild.xml:2625(para)
msgid "Other than buying a faster CPU, hard disk or getting more memory, you might want to install CCache , which can cache compilation results for you. It is available with most distributions."
msgstr ""
#: C/jhbuild.xml:2630(para)
msgid "After installing CCache, set the cache size with the following command:"
msgstr ""
#: C/jhbuild.xml:2632(programlisting)
#, no-wrap
msgid "ccache -M 2G"
msgstr ""
#: C/jhbuild.xml:2633(para)
msgid "(replace 2G with the size you want for your cache). Then create symlinks to CCache for your compiler in ~/bin :"
msgstr ""
#: C/jhbuild.xml:2636(programlisting)
#, no-wrap
msgid ""
"cd ~/bin\n"
"for cmd in cc gcc c++ g++; do\n"
" ln -s /usr/bin/ccache $cmd\n"
"done"
msgstr ""
#: C/jhbuild.xml:2640(para)
msgid "You can check the status of your cache (such as cache hit rates) with the following command:"
msgstr ""
#: C/jhbuild.xml:2642(programlisting)
#, no-wrap
msgid "ccache -s"
msgstr ""
#: C/jhbuild.xml:2647(simpara)
msgid "Is there a better way to monitor the status of the build than looking at terminal window?"
msgstr ""
#: C/jhbuild.xml:2651(para)
msgid "If you have Zenity >= 2.9 installed on your system, JHBuild will display an icon in the system tray. The icon will display the current build stage, and the tooltip will show the last message from JHBuild."
msgstr ""
#: C/jhbuild.xml:2655(para)
msgid "The icon will also pop up a balloon on error."
msgstr ""
#: C/jhbuild.xml:2660(title)
msgid "Building GNOME"
msgstr ""
#: C/jhbuild.xml:2663(simpara)
msgid "What other prerequisites are needed to build GNOME with JHBuild?"
msgstr ""
#: C/jhbuild.xml:2667(para)
msgid "Some of the packages you will need on your system include:"
msgstr ""
#: C/jhbuild.xml:2671(simpara)
msgid "DocBook XML DTD and XSLT stylesheets. These need to be registered in the XML catalog (/etc/xml/catalog )."
msgstr ""
#: C/jhbuild.xml:2676(simpara)
msgid "X libraries"
msgstr ""
#: C/jhbuild.xml:2679(simpara)
msgid "fam or gamin (used by gnome-vfs for file monitoring)."
msgstr ""
#: C/jhbuild.xml:2683(simpara)
msgid "libsmbclient from Samba (used for browsing Windows networks)."
msgstr ""
#: C/jhbuild.xml:2687(simpara)
msgid "libbz2 from bzip2."
msgstr ""
#: C/jhbuild.xml:2691(simpara)
msgid "libpng , libjpeg and libtiff (used for image loading)."
msgstr ""
#: C/jhbuild.xml:2697(para)
msgid "If you are installing distro packages, you may need to install corresponding \"dev\" or \"devel\" packages. Note that this list is just a starting point - not a comprehensive list."
msgstr ""
#: C/jhbuild.xml:2705(simpara)
msgid "I've built GNOME with JHBuild. How do I run it?"
msgstr ""
#: C/jhbuild.xml:2709(para)
msgid "(a) You will want to create a ~/.xsession file, which is run by the display manager when you log in. This file should look something like this:"
msgstr ""
#: C/jhbuild.xml:2713(programlisting)
#, no-wrap
msgid ""
"#!/bin/sh\n"
"exec jhbuild run gnome-session"
msgstr ""
#: C/jhbuild.xml:2715(para)
msgid "Finally, you should make sure that the ~/.xsession file is executable."
msgstr ""
#: C/jhbuild.xml:2717(para)
msgid "(b) Use a more sophisticated session script that is run when you log in using a graphical login manager (gdm /kdm/xdm). The problem with D-Bus and HAL is that these daemons come with your distribution and are most likely already running, but may be unusable by the Gnome development version (i.e. they are too old or incompatible). The session script just starts hal and d-bus from the jhbuild installation in addition to the system-wide versions. Put the following script as e.g. /usr/bin/gnomesvn-session and make sure you adjust GNOME to your local settings:"
msgstr ""
#: C/jhbuild.xml:2730(programlisting)
#, no-wrap
msgid ""
"\n"
"GNOME=/opt/gnome2\n"
" \n"
"GDK_USE_XFT=1\n"
"#XDG_DATA_DIRS=$XDG_DATA_DIRS:$GNOME/share\n"
"#XDG_CONFIG_DIRS=$XDG_CONFIG_DIRS:$GNOME/etc/xdg\n"
"\n"
"DBUS_LAUNCH=\"$GNOME/bin/dbus-launch --exit-with-session\"\n"
" \n"
"sudo su -c \"$GNOME/bin/dbus-daemon --system; \\\n"
" $GNOME/sbin/hald\"\n"
" \n"
"jhbuild run $DBUS_LAUNCH gnome-session"
msgstr ""
#: C/jhbuild.xml:2743(para)
msgid "Uncomment the XDG_ lines if you want the system-wide program menus from your distribution in addition to the entries from the jhbuild GNOME. Make sure the file is executable:"
msgstr ""
#: C/jhbuild.xml:2748(programlisting)
#, no-wrap
msgid "chmod a+x /usr/bin/gnomesvn-session"
msgstr "chmod a+x /usr/bin/gnomesvn-session"
#: C/jhbuild.xml:2749(para)
msgid "Because you need to start system daemons, you will need root privileges which are obtained by sudo. Note that you need to configure sudo so that it won't ask for a password! Run visudo as root and enter (don't forget to change your username and the paths):"
msgstr ""
#: C/jhbuild.xml:2757(programlisting)
#, no-wrap
msgid ""
"\n"
"# Cmnd alias specification\n"
"Cmnd_Alias GNOME = /opt/gnome2/bin/dbus-daemon, \\\n"
" /opt/gnome2/sbin/hald\n"
"\n"
"# User privilege specification\n"
"gnometester ALL = NOPASSWD: GNOME"
msgstr ""
#: C/jhbuild.xml:2764(para)
msgid "In order to get a new session entry in the login manager, create /usr/share/xsessions/gnomesvn.desktop and put this or something similar:"
msgstr ""
#: C/jhbuild.xml:2768(programlisting)
#, no-wrap
msgid ""
"\n"
"[Desktop Entry]\n"
"Encoding=UTF-8\n"
"Name=Gnome svn (jhbuild)\n"
"Comment=This session logs you into Gnome testing session\n"
"Exec=/usr/bin/gnomesvn-session\n"
"Icon=\n"
"Type=Application"
msgstr ""
#: C/jhbuild.xml:2776(para)
msgid "Now you can restart gdm and log into your jhbuild GNOME. Make sure you select the jhbuild session before entering the login credentials. Advice: Use a seperate user account for testing!"
msgstr ""
#: C/jhbuild.xml:2785(simpara)
msgid "I built GNOME using JHBuild with prefix set to /usr , and now my system is broken. What should I do?"
msgstr ""
#: C/jhbuild.xml:2790(para)
msgid "Don't set prefix to /usr ."
msgstr ""
#: C/jhbuild.xml:2796(simpara)
msgid "How do I get gnome-volume-manager to work when running in a prefix?"
msgstr ""
#: C/jhbuild.xml:2801(para)
msgid "The gnome-volume-manager program reacts to messages from hald over the system message bus, which must be running as root. Assuming that your distribution comes with HAL , the main problem is getting gnome-volume-manager to talk to the system message bus."
msgstr ""
#: C/jhbuild.xml:2808(para)
msgid "Since communication is done over a UNIX domain socket, the easiest way to do this is to create a symlink from /var/run/dbus to $prefix/var/run/dbus :"
msgstr ""
#: C/jhbuild.xml:2812(programlisting)
#, no-wrap
msgid ""
"mkdir -p $prefix/var/run\n"
"cd $prefix/var/run\n"
"ln -s /var/run/dbus dbus"
msgstr ""
"mkdir -p $prefix/var/run\n"
"cd $prefix/var/run\n"
"ln -s /var/run/dbus dbus"
#: C/jhbuild.xml:2815(para)
msgid "You may also have trouble building HAL with JHBuild, since it tries to install some things outside of its build root. Running make -k install in the hal directory might help here."
msgstr ""
#. Put one translator per line, in the form of NAME , YEAR1, YEAR2.
#: C/jhbuild.xml:0(None)
msgid "translator-credits"
msgstr "Daniel Nylander , 2008"
jhbuild-3.5.91/doc/sv/sv.stamp 0000644 0001750 0001750 00000000000 11743103647 016043 0 ustar 00fred fred 0000000 0000000 jhbuild-3.5.91/doc/fr/ 0000755 0001750 0001750 00000000000 12021725615 014331 5 ustar 00fred fred 0000000 0000000 jhbuild-3.5.91/doc/fr/index.docbook 0000644 0001750 0001750 00000365251 11743103645 017021 0 ustar 00fred fred 0000000 0000000
Manuel de JHBuild
James
Henstridge
C.J.
Adams-Collier
Frederic
Peters
David
Turner
2004, 2008
James Henstridge
JHBuild Manual v0.5
January 2008
JHBuild Manual v0.1
August 2007
JHBuild est un outil utilisé pour compiler l'ensemble du bureau GNOME à partir du gestionnaire de versions. Il peut aussi être configuré pour compiler d'autres projets.
Introduction
JHBuild est un outil conçu pour faciliter la compilation d'ensembles de paquets source, appelés modules
. Il utilise des fichiers de « jeux de modules » (moduleset) pour décrire les modules disponibles pour la compilation. Ces fichiers contiennent des informations sur les dépendances, ce qui permet à JHBuild de déterminer les modules à compiler et dans quel ordre.
JHBuild a été d'abord créé pour compiler GNOME , mais il a été complété depuis pour être utilisable par d'autres projets. Un fichier jeux de modules (moduleset) peut se trouver sur un serveur Web, permettant ainsi de fournir des règles de compilation indépendamment du projet JHBuild.
JHBuild can build modules from a variety of sources, including
CVS ,
Subversion ,
Bazaar ,
Darcs ,
Git and
Mercurial
repositories, as well as Tar and Zip archives hosted on web or FTP sites.
JHBuild can build modules using a variety of build systems, including
Autotools, CMake, WAF, Python Distutils and Perl Makefiles.
JHBuild n'est pas destiné à remplacer le système de gestion de paquets d'une distribution. Au contraire, il simplifie la compilation de logiciels à l'intérieur d'un préfixe d'installation distinct afin de ne pas interférer avec le reste du système.
Premiers pas
Quelques manipulations sont nécessaires pour configurer JHBuild avant de pouvoir compiler des logiciels. Certains logiciels sont nécessaires au fonctionnement de JHBuild, et il est aussi nécessaire d'installer des outils indispensables à l'obtention et à la construction des sources de logiciels.
Installation de JHBuild
JHBuild nécessite un moteur d'exécution Python. Vérifiez que Python >= 2.3 est installé.
La façon recommandée de télécharger JHBuild est d'utiliser le gestionnaire de versions git . La commande à utiliser est présentée ci-dessous. Il est recommandé d'exécuter cette commande dans un nouveau répertoire où tout le code source sera téléchargé, par exemple ~/checkout/gnome ).
$ git clone git://git.gnome.org/jhbuild
...
$ Cela va télécharger JHBuild dans un nouveau dossier nommé jhbuild dans le répertoire actuel. Ensuite, pour le construire et l'installer :
$ cd jhbuild
$ ./autogen.sh
...
$ make
...
$ make install
...
$ If gnome-common ,
yelp-tools and
autotools are available,
autogen.sh will configure JHBuild to install via
autotools . If
gnome-common ,
yelp-tools and
autotools are not available,
autogen.sh will configure JHBuild to install via a
plain Makefile. To always use the plain Makefile method pass
--simple-install to autogen.sh .
Si les étapes ci-dessus se sont déroulées avec succès, un petit script shell sera installé dans ~/.local/bin pour lancer JHBuild. Ajoutez ce chemin dans votre variable PATH :
$ PATH=$PATH:~/.local/bin
$ Pour ajouter ~/.local/bin de façon permanente à la variable PATH , exécutez la commande suivante :
$ echo PATH=$PATH:~/.local/bin >> ~/.bashrc
$
Avant de lancer JHBuild, il est nécessaire de paramétrer le fichier de configuration ~/.jhbuildrc .
Prérequis pour la construction
Before any modules can be built, it is necessary to have certain
build tools installed. Common build tools include the GNU Autotools
(autoconf ,
automake , libtool
and gettext ), The GNU Toolchain
(binutils , gcc ,
g++ ), make, pkg-config and Python, depending
on which modules will be built.
JHBuild peut vérifier si ces outils sont installés sur votre système à l'aide de la commande sanitycheck :
$ jhbuild sanitycheck Si cette commande affiche un message, il est possible de corriger les erreurs de deux manières :
Installez le paquet requis à partir du dépôt de votre distribution. Une liste de noms de paquets de différentes distributions est disponible sur le wiki de GNOME. Exécutez à nouveau la commande sanitycheck après avoir installé les paquets de la distribution pour s'assurer que les outils requis sont maintenant présents.
Lancez la commande bootstrap pour télécharger, compiler et installer les prérequis de construction :
$ jhbuild bootstrap Lorsque l'opération est terminée, lancez la commande sanitycheck pour vérifier que les outils requis sont présents.
La commande bootstrap ne construit pas toutes les dépendances des paquets requis par les outils de construction. Si votre distribution ne fournit pas ces paquets, ils devront alors être construits en dehors de l'environnement JHBuild.
Les dépendances des outils de construction comprennent notamment m4 , perl et un compilateur C (par exemple gcc ).
Utilisation de JHBuild
Après que tout a été configuré, JHBuild peut se mettre à construire des logiciels. Pour construire tous les modules indiqués dans le fichier ~/.jhbuildrc , exécutez la commande suivante :
$ jhbuild build JHBuild va télécharger, configurer, compiler et installer chaque module. Si une erreur se produit à n'importe quelle étape, JHBuild présente un menu pour savoir ce qu'il doit faire. Les choix possibles comprennent le passage dans un shell pour corriger l'erreur, une nouvelle passe de construction à différentes étapes, l'abandon de la construction du module ou la non prise en compte de l'erreur en continuant le processus.
L'abandon d'un module provoque l'échec de construction de tout module dépendant de ce module.
Voici un exemple de menu qui est affiché :
[1] Rerun phase build
[2] Ignore error and continue to install
[3] Give up on module
[4] Start shell
[5] Reload configuration
[6] Go to phase "wipe directory and start over"
[7] Go to phase "configure"
[8] Go to phase "clean"
[9] Go to phase "distclean"
choice:
Il est aussi possible de construire un jeu différent de modules (et leurs dépendances) en passant les noms des modules en paramètre de la commande build . Par exemple, pour construire gtk+ :
$ jhbuild build gtk+ Si JHBuild est interrompu en cours de construction d'un module, quelle qu'en soit la raison, il est possible de reprendre la construction à partir d'un module précis en utilisant l'option --start-at :
$ jhbuild build --start-at=pango Pour construire un ou plusieurs modules en ignorant leurs dépendances, JHBuild fournit la commande buildone . Pour que cette commande se déroule correctement, toutes les dépendances du module indiqué doivent être préalablement construites et installées, ou fournies par des paquets de votre distribution.
$ jhbuild buildone gtk+ When actively developing a module, you are likely in a source
working directory. The make will invoke the build
system and install the module. This will be a key part of your
edit-compile-install-test cycle.
$ jhbuild make Si JHBuild est interrompu en cours de construction d'un module, quelle qu'en soit la raison, il est possible de reprendre la construction à partir d'un module précis en utilisant l'option --start-at :
Pour obtenir une liste ordonnancée des modules et des dépendances que JHBuild va construire, utilisez la commande list :
$ jhbuild list Pour obtenir des informations sur un module particulier, utilisez la commande info :
$ jhbuild info gtk+ Pour télécharger ou mettre à jour toutes les sources de logiciels sans rien compiler, utilisez la commande update . Cette commande donne l'occasion de modifier les sources avant la compilation et peut se révéler utile quand la disponibilité de bande passante Internet est instable.
$ jhbuild update Plus tard, JHBuild peut tout construire sans télécharger ni mettre à jour les sources :
$ jhbuild build --no-network Pour lancer une commande précise dans le même environnement utilisé par JHBuild, utilisez la commande run :
$ jhbuild run program Pour lancer un shell avec l'environnement utilisé par JHBuild, utilisez la commande shell :
$ jhbuild shell
JHBuild et GNOME
Cette section fournit des indications sur la compilation, l'installation et le fonctionnement de GNOME.
Construction de GNOME
Pour compiler GNOME, certains paquets de développement sont nécessaires, notamment :
La DTD DocBook XML et les feuilles de styles XSLT. Elles doivent être enregistrées dans le catalogue XML (/etc/xml/catalog ).
Les bibliothèques X
libsmbclient de Samba (utilisé pour parcourir les réseaux Windows).
libbz2 de bzip2.
libpng , libjpeg et libtiff (utilisés pour le chargement d'images).
Si vous installez des paquets de votre distribution et si cela s'applique à votre distribution, installez les paquets dev
ou devel
correspondants. Une liste de noms de paquets de différentes distributions est disponible sur le wiki de GNOME.
Lancement d'une application GNOME unique
Cette section décrit comment lancer une seule application GNOME. L'application se lance dans l'environnement de bureau actuel. Pour lancer une application dans le contexte d'un GNOME JHBuild complet, consultez
Exécutez un shell JHBuild. Ce shell dispose de toutes les variables d'environnement nécessaires déjà configurées.
$ jhbuild shell Vérifiez que la bonne application va être lancée. Par exemple :
$ which gedit
/opt/gnome/bin/geditlancez l'application :
$ gedit & Il est aussi possible de lancer l'application en utilisant la commande run :
$ jhbuild run gedit
Lancement de l'environnement de bureau GNOME
Créez un nouveau compte utilisateur pour faire fonctionner le GNOME JHBuild. Il est recommandé d'utiliser un compte utilisateur différent pour GNOME JHBuild, afin d'éviter des problèmes liés aux paramètres utilisateur stockés dans le dossier personnel. Ce manuel fait référence à ce nouveau compte par le nom gnomedev .
Configurez JHBuild dans le nouveau compte gnomedev . Copiez ou créez un lien symbolique pour ~/.jhbuildrc et ~/.local/bin/jhbuild dans le dossier personnel de gnomedev .
Ouvrez un terminal en tant qu'utilisateur gnomedev . Ajoutez ~/.local/bin de façon permanente à la variable PATH en exécutant la commande suivante :
$ echo PATH=$PATH:~/.local/bin >> ~/.bashrc Testez que JHBuild fonctionne :
$ jhbuild run pkg-config gtk+-2.0 --modversion
2.20.1
Configuration de GNOME en mode « gestionnaire d'affichage »
Compilez et installez GNOME JHBuild.
Activez les services système. GNOME JHBuild utilise le démon D-Bus système /usr/bin et les services système dans /usr/share/dbus-1/system-services/ . GNOME JHBuild utilise le démon D-Bus de session et les services dans /opt/gnome/ share/dbus-1/services//opt/gnome par le préfixe d'installation de GNOME dans la commande ci-après :
$ rm -rf /opt/gnome /var/run/dbus
$ ln -s /var/run/dbus /opt/gnome /var/run/dbus
$ rm -rf /opt/gnome /var/lib/dbus/machine-id
$ ln -s /var/lib/dbus/machine-id /opt/gnome /var/lib/dbus/machine-id Créez un script de démarrage GNOME dans /usr/bin/gnome-jhbuild-session contenant le texte suivant, en remplaçant /opt/gnome par le préfixe d'installation de GNOME :
#!/bin/sh
GNOME=/opt/gnome
GDK_USE_XFT=1
XDG_DATA_DIRS=$XDG_DATA_DIRS:$GNOME/share
XDG_CONFIG_DIRS=$XDG_CONFIG_DIRS:$GNOME/etc/xdg
jhbuild run gnome-session
Rendez exécutable le fichier /usr/bin/gnome-jhbuild-session :
$ chmod a+x /usr/bin/gnome-jhbuild-session Pour ajouter une nouvelle entrée de session dans le gestionnaire d'affichage, créez le fichier /usr/share/xsessions/gnome-jhbuild.desktop avec un contenu semblable à ceci :
[Desktop Entry]
Name=GNOME (JHBuild)
Comment=Cette session vous connecte dans une session GNOME de test
Exec=/usr/bin/gnome-jhbuild-session
Icon=
Type=Application
Redémarrez gdm .
Lancement de GNOME depuis le gestionnaire d'affichage
Pour lancer GNOME JHBuild, sélectionnez la session GNOME (JHBuild) dans l'écran de bienvenue du gestionnaire d'affichage, avant de saisir les informations de connexion du compte gnomedev . Si tout fonctionne correctement, GNOME JHBuild va apparaître. Sinon, inspectez le journal dans le fichier ~gnomedev/.xsession-errors .
Intégration à un robot de compilation (buildbot)
Associé au projet Buildbot , JHBuild peut aussi fonctionner comme outil d'intégration continue. Le projet GNOME utilise une configuration Buildbot sur build.gnome.org .
Configuration d'un esclave de robot de compilation
Un esclave de robot de compilation est une variante d'une installation JHBuild normale qui va servir les requêtes d'un maître de compilation. Il est conseillé de d'abord faire fonctionner JHBuild correctement en effectuant une compilation complète et réussie de la majorité des modules avant de le configurer en tant que robot de compilation.
Les commandes des robots de compilation sont des options de la commande bot . Pour télécharger et installer les logiciels supplémentaires requis, exécutez la commande suivante :
$ jhbuild bot --setup Après l'exécution réussie de cette étape, trois nouvelles variables de configuration sont nécessaires dans ~/.jhbuildrc .
Il n'est pas possible d'utiliser un fichier de configuration différent, l'option --file ne produira pas l'effet désiré.
jhbuildbot_master = 'build.gnome.org:9070'
jhbuildbot_slavename = 'nom_esclave'
jhbuildbot_password = 'mot_de_passe'
jhbuildbot_master est une chaîne indiquant le serveur maître du robot de compilation. Par défaut, c'est 'build.gnome.org:9070' . jhbuildbot_slavename et jhbuildbot_password permettent d'identifier l'esclave sur le serveur maître. Contactez les administrateurs du robot maître pour obtenir les nom d'utilisateur et mot de passe de l'esclave.
Les administrateurs de build.gnome.org peuvent être contactés via la liste de diffusion de l'équipe de compilation .
Référence des commandes
JHBuild utilise une syntaxe de ligne de commande similaire aux outils du style CVS :
jhbuild
global-options command command-arguments Les options globales de JHBuild sont :
-f , --file
config
Utilise un fichier de configuration alternatif au lieu du fichier ~/.jhbuildrc par défaut.
-m , --moduleset
moduleset
Utilise un autre jeu de modules que celui qui est indiqué dans le fichier de configuration. Cette option peut être un chemin relatif si le jeu de modules se trouve dans le dossier des jeux de modules de JHBuild, ou un chemin absolu s'il se trouve ailleurs.
--no-interact
N'interroge jamais l'utilisateur quant à un choix à faire. Cette option est utile pour effectuer une construction sans intervention humaine, afin de s'assurer que la construction ne soit pas interrompue.
Les options particulières à certaines commandes sont énumérées ci-dessous.
autobuild
La commande autobuild construit automatiquement les modules indiqués dans le fichier de configuration, puis envoie les résultats vers JHAutobuild.
jhbuild autobuild
--autogen
--clean
--distcheck
--skip=module
--start-at=module
--report-url=reporturl
--verbose
The --autogen , --clean ,
--distcheck , --skip and
--start-at options are processed as per the
build
command.
--report-url=url-de-rapport , -r url-de-rapport
Cette option indique l'URL de JhAutobuild où envoyer le rapport.
--verbose , -v
Si indiquée, cette option produit des messages de JHBuild plus verbeux.
bootstrap
La commande bootstrap installe un ensemble d'utilitaires de construction requis pour la plupart des modules (par ex. autoconf , automake , etc).
jhbuild bootstrap
La commande bootstrap construit les modules avec la même méthode que la commande build , mais en utilisant le jeu de modules bootstrap.modules .
Consultez la documentation de la commande build pour connaître les options disponibles.
build
La commande build construit un ou plusieurs paquets ainsi que leurs dépendances.
jhbuild build
--autogen
--clean
--check
--dist
--distcheck
--ignore-suggests
--no-network
--skip=module
--start-at=module
--tags=tags
-D date
--no-xvfb
--try-checkout
--no-poison
--force
--build-optional-modules
--min-age=time
module
Si aucun nom de module n'est indiqué dans la ligne de commande, c'est la liste des
-c , --clean
Exécute make clean avant de construire les modules.
--check
Exécute make check après la construction des modules.
-d , --dist
Exécute make dist après la construction des modules.
--distcheck
Exécute make distcheck après la construction des modules.
--ignore-suggests
Ne compile pas les dépendances faibles.
-n , --no-network
N'accède pas au réseau lors de la construction des modules. Cette option évite les étapes de téléchargement ou de mise à jour lors des constructions. Si un module ne peut pas être construit sans accès réseau, sa construction échouera.
-s , --skip =module,...
Ne compile pas les modules de la liste. Utilisé pour éviter la construction de dépendances spécifiques.
--tags =étiquette,...
Ignore les modules qui ne correspondent pas à étiquette . Une étiquette correspondant au nom du jeu de modules conteneur est automatiquement attribuée à chaque module.
-t , --start-at =module
Commence par le module indiqué plutôt qu'au début de la liste des dépendances. Cette option est utile quand la construction précédente a échoué.
-D date
Si le système de gestion de version sous-jacent le prend en charge, met à jour l'arborescence source selon son état à la date indiquée, avant de commencer la construction. La date doit être indiquée au format ISO, par exemple "2009-09-18 02:32Z" .
-x , --no-xvfb
Effectue les tests graphiques avec le serveur X réel au lieu d'utiliser une simulation Xvfb.
-C , --try-checkout
Si la construction échoue et que le système de gestion de version le prend en charge, force une extraction et exécute autogen.sh avant de recommencer la construction.
-N , --no-poison
Si l'une ou plusieurs des dépendances du module échouent, cette option force JHBuild à essayer tout de même de construire le module.
-f , --force
Construit les modules même si la stratégie habituelle indique que ce n'est pas nécessaire.
--build-optional-modules
Certains modules énumérés comme dépendances facultatives ne sont pas absolument nécessaires pour construire le module. Cette option force JHBuild à construire aussi les dépendances facultatives.
--min-age =time
Skip modules installed more recently than the specified
relative time. The time string format
is a number followed by a unit. The following units are supported:
seconds (s), minutes (m), hours (h) and days (d). For example,
--min-age=2h will skip modules built less than
two hours ago.
make
The make command is for actively developing on
a particular module. It requires the current directory be a source
checkout, and does the equivalent of buildone -nf $(basename
$(pwd)) .
jhbuild make
--clean
--check
--distcheck
--quiet
The options are the same as those available for the
buildone
command.
buildone
La commande buildone est semblable à build , mais elle ne construit pas les dépendances du module. Elle est utile pour reconstruire un ou plusieurs modules.
jhbuild buildone
--clean
--check
--distcheck
--no-network
-D date
--no-xvfb
--force
--min-age=time
module
The --check , --clean ,
-d , --distcheck ,
--no-network , -D and
-x options are processed as per the
build
command.
Cette commande nécessite au minimum un module dans la ligne de commande.
checkbranches
La commande checkbranches vérifie si les branches des modules sont définies correctement dans le gestionnaire de version et si les branches sont cohérentes avec le jeu de modules.
jhbuild checkbranches
--branch=branch
--branch =branch ,
-b branch
La branche à vérifier
$ jhbuild -m gnome-2.20 checkbranches
libgnomecanvas is missing branch definition for gnome-2-20
$
clean
La commande clean nettoie les répertoires de compilation d'un ou de plusieurs modules.
jhbuild clean
--skip=module
--start-at=module
Si aucun nom de module n'est indiqué dans la ligne de commande, c'est la liste des
Consultez la documentation de la commande build pour une description des options disponibles.
dot
La commande dot génère un fichier décrivant le graphe directionnel formé par les dépendances dans un jeu de modules. Ce fichier peut ensuite être traité par le logiciel GraphViz pour produire un diagramme.
jhbuild dot
--soft-deps
--clusters
module
Si aucun nom de module n'est indiqué dans la ligne de commande, c'est la liste des
L'option --soft-deps ajoute des lignes pointillées depuis les modules vers leurs dépendances faibles. L'option --clusters groupe les modules selon les
La sortie de la commande dot peut être redirigée vers l'utilitaire dot pour générer un fichier PostScript :
$ jhbuild dot modules | dot -Tps > dependencies.ps Ou une image PNG :
$ jhbuild dot modules | dot -Tpng > dependencies.png
Exemple de sortie dot de JHBuild
gui
La commande gui lance une interface graphique de JHBuild qui permet de sélectionner des modules à construire et de modifier certaines options.
jhbuild gui
L'interface graphique est basée sur GTK, ce qui requiert des bibliothèques supplémentaires.
info
La commande info affiche des informations sur un ou plusieurs modules.
jhbuild info
module
Cette commande affiche le nom du module, son type, ses dépendances, les paquets qui en dépendent, le répertoire source et la date de sa dernière installation avec JHBuild. Le cas échéant, elle affiche également certaines informations spécifiques au type de module, telles que le dépôt CVS ou l'URL de téléchargement.
Si aucun module n'est précisé dans la commande, des informations sont affichées au sujet de tous les modules définis dans le jeu de modules.
list
La commande list affiche la liste complète des modules que la commande build construirait.
jhbuild list
-a
-r
-s
--start-at=module
--tags=tags
--ignore-suggests
--list-optional-modules
module
Si aucun nom de module n'est indiqué dans la ligne de commande, c'est la liste des
Les options --skip , --start-at , --tags et --ignore-suggests sont traitées de la même manière que pour la commande build .
-a , --all-modules
Énumère tous les modules du jeu de modules, sans tenir compte des dépendances de construction.
-r , --show-revision
Si un module est défini par une de ses branches, affiche le nom de la branche avec le nom de module.
--list-optional-modules
Cette option force JHBuild à énumérer les dépendances facultatives.
rdepends
La commande rdepends affiche les dépendances inverses d'un module.
jhbuild rdepends
module
--dependencies
Affiche le chemin de dépendance à la suite des modules.
--direct
Limite l'affichage aux modules dépendant directement du module indiqué.
run
La commande run exécute la commande indiquée dans le même environnement que JHBuild utilise lors de la construction de modules.
jhbuild run
--in-builddir
--in-checkoutdir
program argument En cas d'utilisation de JHBuild pour construire GNOME, cette commande est utile dans les scripts de démarrage de X.
--in-builddir =module
Exécute la commande dans le répertoire de construction du module indiqué.
--in-checkoutdir =module
Exécute la commande dans le répertoire source du module indiqué.
sanitycheck
La commande sanitycheck effectue un certain nombre de contrôles pour vérifier que l'environnement de construction est correct.
jhbuild sanitycheck
Ces contrôles vérifient notamment que :
les préfixes d'extraction et d'installation sont accessibles en écriture ;
les outils de construction indispensables sont installés ;
certaines macros couramment utilisées sont disponibles dans les chemins de recherche des commandes aclocal associées aux différentes versions de automake ;
le catalogue XML contient les DTD et feuilles de style DocBook.
shell
La commande shell lance un shell utilisateur dans le même environnement que JHBuild lorsqu'il construit des modules.
jhbuild shell
Cette commande est équivalente à ceci :
$ jhbuild run $SHELL La variable d'environnement UNDER_JHBUILD est définie à « true » (vrai) lorsque ce shell est actif. Vous pouvez utiliser la présence de cette variable pour personnaliser votre invite de commande afin d'indiquer que vous êtes dans un shell contrôlé par JHBuild. Par exemple, il est possible d'indiquer cela dans votre .bashrc :
if [ -n "$UNDER_JHBUILD" ]; then
PS1="[jhbuild] $PS1"
fi
En conséquence, vous verrez apparaître la séquence [jhbuild] au début de votre invite de commande habituelle, ce qui rend plus évident la distinction entre un shell normal et un shell contrôlé par JHBuild.
sysdeps
The sysdeps command displays a list of
dependency modules that are provided by installed system packages.
JHBuild will not build the modules from source if the configuration
variable
partial_build
is True .
The sysdeps command also displays a list of
dependency modules where the installed system packages are too old.
JHBuild will build newer modules from source.
The sysdeps command also displays a list of
dependency modules with no matching system package installed.
jhbuild sysdeps
--install
--install
This option installs system packages which are
dependencies of the moduleset. The system packages are installed
using PackageKit .
<command>sysdeps</command> example
$ jhbuild sysdeps
System installed packages which are new enough:
speex (required=1.2rc1, installed=1.2rc1)
libdiscid (required=0.2.2, installed=0.2.2)
telepathy-farsight (required=0.0.14, installed=0.0.16)
lcms2 (required=2.2, installed=2.2)
...
System installed packages which are too old:
webkitgtk-3.0 (required=1.5.1, installed=1.4.0)
...
No matching system package installed:
libvala-0.14 (required=0.13.1)
...
tinderbox
La commande tinderbox est semblable à la commande build , mais écrit toutes les sorties de terminal dans des fichiers HTML prêts à être publiés sur un site Web. Elle permet de mettre en place des systèmes tels que Mozilla Tinderbox ou Debian Buildd.
jhbuild tinderbox
--clean
--no-network
--output=directory
--skip=module
--start-at=module
-D date
-C
-N
-f
module
The --clean , --no-network ,
--skip , --start-at ,
-D , -C , -N and
-f options are processed as per the
build
command.
-o , --output =répertoire
Le répertoire dans lequel écrire les fichiers HTML.
uninstall
La commande uninstall désinstalle un ou plusieurs modules.
jhbuild uninstall
module
update
La commande update est semblable à build , mais n'effectue que les étapes de téléchargement et de mise à jour des modules, sans les construire.
jhbuild update
--skip=module
--start-at=module
--tags=tags
--ignore-suggests
-D date
module
Les options --skip , --start-at , --tags , --ignore-suggests et -D sont traitées de la même manière que pour la commande build .
updateone
La commande updateone est semblable à update , mais elle ne met pas à jour les modules dépendants. Elle est utile pour mettre à jour un ou plusieurs modules.
jhbuild updateone
-D date
module
L'option -D est traitée de la même manière que pour build .
Cette commande nécessite au minimum un module dans la ligne de commande.
Référence du fichier de configuration
Le fichier ~/.jhbuildrc utilise la syntaxe Python standard. Le fichier est exécuté et les variables résultantes définies dans l'espace de noms sont utilisées pour contrôler le comportement de JHBuild. Un ensemble de valeurs par défaut sont insérées dans l'espace de noms avant d'exécuter le fichier de configuration de l'utilisateur.
Les variables de configuration booléennes sont définies avec une syntaxe correspondant à l'exemple suivant :
use_local_modulesets = True
Les variables de configuration « chaînes de caractères » sont définies avec une syntaxe correspondant à l'exemple suivant :
autogenargs = '--disable-static --disable-gtk-doc'
Les variables de configuration contenant des listes sont définies avec une syntaxe correspondant à l'exemple suivant :
skip = ['mozilla', 'pulseaudio']
Les variables de configuration contenant des dictionnaires sont définies avec une syntaxe correspondant à l'exemple suivant :
repos['git.gnome.org'] = 'ssh://username@git.gnome.org/git/'
Variables de configuration
autogenargs
Une chaîne contenant des paramètres passés au script autogen.sh de tous les modules. Peut être surchargée par des modules précis en utilisant le dictionnaire module_autogenargs .
branches
A dictionary specifying which branch to use for specific
modules. This is useful if you are making some changes on a branch
of a module and want JHBuild to build that branch instead of the
one listed in the module set.
La définition des branches dépend du gestionnaire de version du module :
CVS : révision. Par ex. 'BRANCH-PROJECT-0_8'
Bazaar : URI de la branche du module. Par ex. 'http://bzr.example.net/project/gnome-2-28'
Git : tuple dont la première partie est un dépôt (facultatif, peut contenir la valeur None) et la seconde partie le nom de la branche. Par ex. ('git://git.example.net/project', 'gnome-2-28')
Simple example
branches['modulename'] = (None, 'branchname')
Subversion : URI de la branche du module. Par ex. 'svn://svn.example.net/project/gnome-2-28'
builddir_pattern
A printf style formatting pattern
used to generate build directory names. This is only used when
using separate source and build trees. The %s
in the format string will be replaced with
checkoutdir . Defaults to
'%s' .
buildroot
Une chaîne indiquant le répertoire parent contenant les arborescences de construction. La valeur par défaut est None , ce qui signifie que la construction s'effectue dans les arborescences source.
buildscript
Une chaîne indiquant le script de construction à utiliser. La valeur recommandée est la valeur par défaut, terminal . En particulier, n'indiquez pas gtk .
build_policy
A string specifying which modules to build. The three
possible options are all , to build all modules
requested, updated to build only modules which
have changed, or updated-deps to build modules
which have changed or which have dependencies which have changed.
Defaults to updated-deps .
checkoutroot
Une chaîne indiquant le répertoire dans lequel décompresser les arborescences source. À moins que buildroot ne soit défini, la construction s'opère également dans ce répertoire. La valeur par défaut est ~/checkout/gnome .
checkout_mode
Une chaîne indiquant la méthode d'extraction des répertoires dans la gestion de versions. La valeur par défaut est update (mise à jour). Cette valeur peut être définie pour chaque module avec module_checkout_mode . Les valeurs possibles sont : update (mettre à jour le répertoire extrait), clobber (effacer le répertoire avant d'extraire les sources), export (effacer le répertoire puis créer une copie non versionnée des sources) et copy (extraire dans un répertoire différent de celui où il sera construit).
copy_dir
A string specifying the directory to copy to, if the copy
checkout_mode is in use. Defaults to the
checkout directory.
cvs_program
Une chaîne indiquant le programme à utiliser pour la prise en charge de CVS. Cela peut être git-cvsimport ou cvs . La valeur par défaut est cvs .
dvcs_mirror_dir
A string specifying a local mirror directory. JHBuild
will create local mirrors of repositories at the specified
directory. The mirrors can be shared by multiple repository
groups, saving space and time because hard-links will be used for
local clones. The commands update and
updateone will create the mirrors and fetch new
commits from the online repositories. This option is only
supported by Git and Bazaar repositories.
installprog
Une chaîne indiquant un programme à utiliser en remplacement de /usr/bin/install . Si présente, sa valeur par défaut correspond au script d'encapsulation install-check fourni par JHBuild. Ce script optimise l'installation des en-têtes afin de réduire le temps nécessaire aux recompilations.
ignore_suggests
Une valeur booléenne indiquant s'il faut ignorer les dépendances faibles lors de la génération de l'arbre des dépendances. La valeur par défaut est False .
interact
Une valeur booléenne indiquant si l'interaction avec l'utilisateur est autorisée. La définition de cette valeur à False équivaut à passer l'option --no-interact à JHBuild. La valeur par défaut est True .
makeargs
Une chaîne énumérant des paramètres supplémentaires à passer à make . La valeur par défaut est '' .
makecheck
Une valeur booléenne indiquant s'il faut exécuter make check après make . La valeur par défaut est False .
makecheck_advisory
Une valeur booléenne indiquant si les échecs d'exécution de la commande make check doivent être considérés comme des avertissements ou s'ils produisent un échec de la construction. La valeur par défaut est False .
makeclean
Une valeur booléenne indiquant s'il faut exécuter make clean après make . La valeur par défaut est False .
makedist
Une valeur booléenne indiquant s'il faut exécuter make dist après make . La valeur par défaut est False . Ce réglage équivaut à passer l'option --dist à JHBuild.
makedistcheck
Une valeur booléenne indiquant s'il faut exécuter make distcheck après make . La valeur par défaut est False . Ce réglage équivaut à passer l'option --distcheck à JHBuild.
module_autogenargs
Un dictionnaire faisant correspondre les noms de modules à des chaînes donnant des paramètres à passer à autogen.sh . Le paramètre dans module_autogenargs est utilisé à la place du paramètre global autogenargs . Si un module particulier n'est pas dans le dictionnaire, c'est le paramètre global autogenargs qui est utilisé.
module_checkout_mode
Un dictionnaire indiquant le mode d'extraction à employer pour les modules. Ce paramètre écrase le paramètre global checkout_mode .
module_makeargs
Un dictionnaire faisant correspondre les noms de modules à des chaînes indiquant les paramètres à passer à make . Le paramètre dans module_makeargs est utilisé à la place du paramètre global makeargs . Si un module particulier n'est pas dans le dictionnaire, c'est le paramètre global makeargs qui est utilisé.
module_makecheck
Un dictionnaire faisant correspondre les noms de modules à des valeurs booléennes indiquant s'il faut exécuter make check après make . Le paramètre dans module_makecheck remplace la valeur de makecheck . Si un module particulier n'est pas dans le dictionnaire, c'est le paramètre global makecheck qui est utilisé.
module_nopoison
Un dictionnaire faisant correspondre les noms de modules à des valeurs booléennes. Si la valeur pour un module vaut True , JHBuild essaye de construire les modules dépendants même si le module indiqué échoue. Le paramètre dans module_nopoison remplace la valeur de nopoison . Si un module particulier n'est pas dans le dictionnaire, c'est le paramètre global nopoisons qui est utilisé.
Un dictionnaire faisant correspondre les noms de modules à des dictionnaires contenant des variables d'environnement supplémentaires à passer lors de l'exécution de commandes pour le module.
modules
A list of strings specifying the modules to build. The
list of modules actually built will be recursively expanded to
include all the dependencies unless the
buildone command is used. Defaults to
['meta-gnome-desktop'] .
moduleset
Une chaîne ou une liste de chaînes indiquant le ou les noms des jeux de modules à utiliser. Cela peut être le nom de fichier d'un jeu de modules inclus dans JHBuild (sans chemin ni extension) ou un URL HTTP complet d'un jeu de modules géré en externe. Les jeux de modules ayant un URL HTTP sont placés dans un cache local. Si le nom d'un module figure dans plus d'un jeu de modules, le dernier jeu de modules dans la liste est prioritaire. Les jeux de modules fournis avec JHBuild sont mis à jour au gré de la progression du développement de GNOME.
modulesets_dir
Une chaîne indiquant le répertoire contenant les jeux de modules à utiliser. Par défaut, c'est le répertoire modulesets/ dans les sources de JHBuild.
nice_build
Run builds under the SCHED_IDLE
priority on Linux, nice on other Unix. This can
dramatically improve desktop interactivity for parallel builds
while having only a negligible impact on build throughput.
nobuild
Une valeur booléenne qui si elle est définie à True indique à JHBuild de ne pas construire les modules, mais uniquement de les télécharger et de décompresser les sources. La valeur par défaut est False .
nonetwork
Une valeur booléenne indiquant si l'accès au réseau est autorisé. Cela affecte l'extraction ou la mise à jour de modules CVS, le téléchargement d'archives tar et la mise à jour des jeux de modules. Définir cette valeur à True équivaut à passer l'option --no-network . La valeur par défaut est False .
nonotify
A boolean value specifying whether to emit notifications
using the notification daemon. If set to
False , notifications are emitted. Defaults to
True .
nopoison
Une valeur booléenne qui, si elle est définie à True , indique à JHBuild d'essayer la construction des modules même si la construction d'une ou de plusieurs dépendances a échoué. Cette option est équivalente au paramètre --no-poison . La valeur par défaut est False .
notrayicon
A boolean value specifying whether to show an icon in the
system tray using Zenity. If set to False ,
notifications are emitted. Defaults to True .
noxvfb
Une valeur booléenne qui, si elle est définie à True , indique à JHBuild d'exécuter tout test graphique avec le serveur X réel au lieu d'utiliser Xvfb . Cette option est équivalente au paramètre --no-xfvb . La valeur par défaut est False .
partial_build
A boolean value, if set to True
JHBuild will not build dependency modules if corresponding system
packages are installed and sufficient version. Defaults to
True .
prefix
A string specifying the prefix to install modules to.
prefix must be an absolute path. This directory
must be writable. Defaults to '/opt/gnome' .
pretty_print
Une valeur booléenne indiquant s'il s'agit d'améliorer la mise en forme de la sortie des sous-processus. Seules les sorties CVS gèrent la mise en forme améliorée. Cette option peut être désactivée si la mise en forme améliorée pose des problèmes. La valeur par défaut est True .
print_command_pattern
A string displayed before JHBuild executes a command.
%(command)s in the string will be replaced with
the command about to be executed. %(cwd)s in
the string will be replaced with the current working directory.
Defaults to '%(command)s' .
progress_bar
Une valeur booléenne indiquant s'il faut afficher une barre de progression lorsque JHBuild fonctionne en True .
quiet_mode
Une valeur booléenne. Si définie à True , elle désactive la sortie des commandes qui s'exécutent. La valeur par défaut est False .
repos
Un dictionnaire indiquant un emplacement de dépôt alternatif pour un dépôt spécifique. Cette variable de configuration est utile aux développeurs de modules. Par défaut, JHBuild extrait le code à partir des dépôts en utilisant des emplacements anonymes. Les clés du dictionnaire sont des noms de dépôts courts et les valeurs sont des chaînes d'emplacement des dépôts alternatifs. Par exemple :
repos['git.gnome.org'] = 'ssh://username@git.gnome.org/git/'
skip
Une liste de modules à ignorer. L'option de ligne de commande --skip étend cette liste. Par défaut, cette liste est vide.
sticky_date
Une chaîne de caractères. Si définie et si le gestionnaire de versions sous-jacent le prend en charge, JHBuild met à jour l'arborescence source selon son état à la date indiquée. La date doit être fournie au format ISO, par ex. 'aaaa -mm -jj ' . La valeur par défaut est None .
svn_program
Une chaîne indiquant le programme à utiliser pour la prise en charge de Subversion. Cela peut être svn , git-svn ou bzr . La valeur par défaut est svn .
tarballdir
Une chaîne de caractères ; si définie, les archives tar sont téléchargées dans ce répertoire au lieu de checkoutroot . C'est utile si vous avez plusieurs environnements JHBuild ou que vous nettoyez régulièrement checkoutroot et que vous souhaitez restreindre la consommation de bande passante.
tinderbox_outputdir
Une chaîne indiquant le répertoire de stockage de la sortie de jhbuild tinderbox . Cette chaîne peut être remplacée par l'option --output . La valeur par défaut est None , ce qui signifie qu'il faut obligatoirement définir cette option soit dans la ligne de commande, soit dans le fichier de configuration.
trycheckout
Une option booléenne qui, si elle est définie à True , indique à JHBuild d'essayer de résoudre automatiquement les échecs en 1) exécutant une nouvelle fois autogen.sh et 2) extrayant une nouvelle version du module à partir du contrôle de version. Ce paramètre équivaut à passer l'option --try-checkout .
use_lib64
Une valeur booléenne qui indique s'il faut installer les bibliothèques dans les répertoires lib64 . Lorsque c'est le cas, --libdir=\${exec_prefix}/lib64 est transmis à « configure ». Lorsque JHBuild fonctionne sur un système Linux x86_64 , ppc64 ou s390x , cette valeur vaut True par défaut, sinon elle est définie à False .
use_local_modulesets
Une valeur booléenne indiquant d'utiliser des jeux de modules qui ont été extraits parallèlement au code source de JHBuild, au lieu de les télécharger au fur et à mesure, à partir du dépôt du gestionnaire de versions de GNOME. La valeur par défaut est False .
xvfbargs
Une chaîne contenant des paramètres à passer à Xvfb si des tests graphiques sont effectués.
Autres structures du fichier de configuration
En plus des variables ci-dessus, d'autres paramètres peuvent être définis dans le fichier de configuration :
os.environ
Un dictionnaire représentant l'environnement. Cet environnement est transmis aux processus générés par JHBuild.
Certaines variables d'environnement ont un impact certain, comme CPPFLAGS , CFLAGS , INSTALL et LDFLAGS . Par exemple :
os.environ['CFLAGS'] = '-O0 -g'
addpath (var_env , chemin )
Cela ajoute un répertoire à la variable d'environnement PATH (chemin). addpath gère correctement le cas où la variable d'environnement est initialement vide (un deux-points isolé au début ou à la fin d'une variable d'environnement peut avoir des conséquences inattendues).
addpath prend en charge de manière particulière la variable d'environnement ACLOCAL_FLAGS dont la liste de chemins doit être de la forme -I chemin .
prependpath (var_env , chemin )
Après le traitement du fichier de configuration, JHBuild modifie certains chemins sur la base de variables telles que prefix (par ex. en ajoutant $prefix/bin au début de la variable PATH ).
La fonction prependpath fonctionne comme addpath , sauf que la variable d'environnement est modifiée après que JHBuild ait modifié l'environnement.
Syntaxe des fichiers de jeu de modules
JHBuild utilise des fichiers XML pour décrire les dépendances entre modules. Un schéma RELAX-NG et une définition de type de document (DTD : Document Type Definition) sont inclus avec JHBuild dans le répertoire modulesets/ . Le schéma RELAX-NG peut être utilisé pour modifier les fichiers de jeux de modules au moyen du mode nxml-mode dans Emacs.
L'élément de premier niveau dans un fichier de jeu de modules est l'élément moduleset . Aucun espace de nom XML n'est utilisé. Les éléments sous le premier niveau sont de trois types : sources de module, commandes d'inclusion et définitions de module.
Sources de module
Plutôt que d'énumérer l'emplacement exact de chaque module, plusieurs « sources de modules » sont listées dans le jeu de modules, puis référencées par leur nom dans les définitions de modules. En plus de réduire la quantité d'informations redondantes dans le jeu de modules, cela facilite l'indication d'une source alternative pour ces modules (avec CVS et Subversion, il arrive fréquemment que les développeurs et les utilisateurs utilisent des méthodes différentes pour accéder aux dépôts).
L'élément repository est utilisé pour décrire tout type de dépôt. L'élément branch est utilisé dans une définition de module pour préciser des paramètres supplémentaires.
<repository name="nom "
type="type "
[ default="valeur_par_défault " ]
[ password="mot_de_passe " ]
[ cvsroot="racine_cvs " ]
[ archive="archive " ]
[ href="href " ]
[ server="serveur " ]
[ database="base_de_données " ]
[ defbranch="définition_branche " ]
[ trunk-template="modèle_de_tronc " ]
[ branches-template="modèle_de_branche " ]
[ tags-template="modèle_de_tag " ]
[ developer-href-example="exemple_href_pour_développeur " ] />
L'attribut name est un identifiant unique pour le dépôt.
L'attribut default indique si ce dépôt est la source par défaut pour ce jeu de modules.
The type attribute specifies
the type of repository. It can be one of: bzr ,
cvs , darcs ,
fossil , git ,
hg , mnt , svn ,
tarball . Other attributes depend on the
type , as well as the
branch used inside module
definitions. Those are described below in the repository type
sub-sections.
L'attribut developer-href-example sert à indiquer le format de l'URL pour le dépôt tel qu'utilisé par les développeurs, à titre informatif.
L'élément branch est employé dans les définitions de modules.
<branch
[ repo="dépôt " ]
[ module="nom_de_module " ]
[ checkoutdir="dossier_extraction " ]
[ revision="révision " ]
[ tag="tag " ]
[ update-new-dirs="mise_à_jour_nouveaux_dossiers " ]
[ override-checkoutdir="écraser_dossier_extraction " ]
[ subdir="sous-dossier " ]
[ branch="branche " ]
[ version="version " ]
[ size="taille " ]
[ source-subdir="sous-dossier_source " ]
[ hash="hâchage " ]/>
Tous les attributs possèdent des valeurs par défaut convenables et dépendent des définitions de modules et de dépôts. Les attributs courants sont décrits ici.
L'attribut repo permet d'indiquer un nom de dépôt différent de la valeur par défaut.
L'attribut module permet d'indiquer un nom de module pour l'extraction du dépôt. Par défaut, c'est l'identifiant du module.
L'attribut checkoutdir permet d'indiquer le nom du dossier d'extraction. Par défaut, c'est l'identifiant du module.
D'autres attributs sont décrits ci-dessous
Bazaar
Ce type de dépôt permet de définir un dépôt Bazaar. Il est recommandé de posséder une version de Bazaar 1.16 ou plus élevée.
<repository type="bzr" name="launchpad.net"
href="lp:"/>
Voici des attributs supplémentaires : trunk-template (égal à « %(module)s » par défaut) et branches-template (égal à « %(branch)s » par défaut). Ces attributs sont utilisés pour indiquer des modèles dans la construction des URL. Un élément branch dans les définitions de modules peut préciser des attributs branch et user . Ces valeurs sont substituées dans les modèles. Si l'un des deux est défini, c'est branches-template qui est utilisé, sinon c'est trunk-template . Ainsi, vous pouvez redéfinir un dépôt pour construire des modules à partir de votre branche personnelle ou construire plusieurs modules à partir d'un dépôt qui n'est pas structuré de manière standard.
Un élément branch supplémentaire accepte un attribut revspec pour se fixer sur une révision particulière. N'importe quelle bzr revspec valide est acceptée, par exemple date:yesterday, -5, tag:0.1 pour obtenir la première révision depuis hier, 5 commits derrière la tête (tip) ou l'étiquette « 0.1 ». Consultez bzr help revisionspec pour connaître toutes les valeurs possibles.
Par exemple, un dépôt avec des attributs template :
<repository type="bzr" name="launchpad.net"
href="lp:"
trunk-template="~bzr-pqm/%(module)s/bzr.dev"
branches-template="~bzr-pqm/%(module)s/%(branch)s"/>
Des exemples d'éléments branch pour le dépôt ci-dessus :
<branch repo="launchpad.net"
module="bzr"
checkoutdir="bzr-next"/>
<branch repo="launchpad.net"
module="bzr"
branch="2.2"
checkoutdir="bzr-beta"/>
CVS
Ce type de dépôt permet de définir un dépôt CVS.
L'attribut password permet d'indiquer le mot de passe pour accéder au dépôt.
L'attribut cvsroot permet d'indiquer la racine du dépôt.
<repository type="cvs" name="tango.freedesktop.org"
cvsroot=":pserver:anoncvs@anoncvs.freedesktop.org:/cvs/tango"
password=""/>
Attributs supplémentaires : revision , update-new-dirs et override-checkoutdir .
Darcs
Ce type de dépôt permet de définir un dépôt Darcs.
<repository type="darcs" name="telepathy.freedesktop.org"
href="http://projects.collabora.co.uk/darcs/telepathy/"/>
Git
Ce type de dépôt permet de définir un dépôt Git.
<repository type="git" name="git.freedesktop.org"
href="git://anongit.freedesktop.org/git/"/>
Il autorise les attributs suivants sur l'élément branch :
L'attribut revision est utilisé pour indiquer une branche locale ou qui suit une branche distante vers laquelle basculer lors de la phase de mise à jour. Par défaut, il contient « master ». Il est possible de redéfinir cet attribut avec la variable de configuration branches . Ce basculement ne se produit que si la branche actuelle suit une branche distante, afin de ne pas interférer avec votre propre développement.
L'attribut tag indique la révision à extraire absolument durant la phase de mise à jour. Il surcharge l'attribut revision .
<branch repo="git.freedesktop.org" module="swfdec/swfdec"
checkoutdir="swfdec"
revision="branche-locale-ou-distante "
tag="étiquette "/>
Mercurial
Ce type de dépôt permet de définir un dépôt Mercurial.
<repository type="hg" name="hg.gtk-vnc"
href="http://gtk-vnc.codemonkey.ws/hg/" />
<branch repo="hg.gtk-vnc" module="outgoing.hg" checkoutdir="gtk-vnc"/>
Monotone
Ce type de dépôt permet de définir un dépôt Monotone.
L'attribut server permet d'indiquer le serveur du dépôt.
L'attribut database permet d'indiquer la base de données à utiliser pour le dépôt.
L'attribut defbranch permet d'indiquer la branche à utiliser dans le dépôt.
<repository type="mtn" name="pidgin.im"
server="pidgin.im" database="pidgin.im.mtn"
defbranch="im.pidgin.pidgin"/>
Subversion
Ce type de dépôt permet de définir un dépôt Subversion.
<repository type="svn" name="svn.gnome.org" default="yes"
href="http://svn.gnome.org/svn/"/>
Il autorise un attribut revision sur l'élément branch . Cet attribut définit la branche à extraire ou, si c'est un nombre, une révision spécifique à extraire.
<branch revision="gnome-2-20"/>
Il est possible de définir un agencement svn personnalisé en utilisant trunk-template (qui vaut par défaut « %(module)s/trunk »), branches-template (qui vaut par défaut « %(module)s/branches/%(branch)s ») et tags-template (qui vaut par défaut « %(module)s/tags/%(tag)s »).
Tarballs (archives tar)
Ce type de dépôt permet de définir un dépôt tarball.
<repository type="tarball" name="dbus/dbus-python"
href="http://dbus.freedesktop.org/releases/dbus-python/"/>
Il autorise les attributs suivants sur l'élément branch :
L'attribut module indique le fichier à télécharger et compiler. L'attribut version indique la version du module.
Les attributs size et hash , ainsi que l'ancien attribut md5sum sont facultatifs. Si ces attributs existent, ils sont utilisés pour vérifier que le paquet source a été correctement téléchargé.
Any number of patch elements
may be nested inside the branch
element. These patches are applied, in order, to the source tree after
unpacking. The file attribute
gives the patch filename, and the
strip attribute says how many
levels of directories to prune when applying the patch.
Pour les jeux de modules livrés avec JHBuild, les fichiers de correctifs sont situés dans le répertoire jhbuild/patches/ ; pour les jeux de modules référencés par URI, les fichiers de correctifs doivent se trouver dans le même répertoire que le jeu de modules ou dans le sous-répertoire patches/ . Il est aussi possible que l'attribut file indique un URI, auquel cas il sera téléchargé à cet emplacement.
<branch module="dbus-python-0.80.2.tar.gz" version="0.80.2"
repo="dbus/dbus-python"
hash="md5:2807bc85215c995bd595e01edd9d2077" size="453499">
<patch file="dbus-glib-build.patch" strip="1" />
</branch>
A tarball branch element may
also contain quilt elements which
specify nested branch to import.
Inclusion d'autres jeux de modules
JHBuild autorise un jeu de modules à inclure le contenu d'un autre jeu de modules en le référençant au moyen de l'élément include .
<include href="uri "/>
L'attribut href est une référence sous forme d'URI vers le jeu de modules à inclure, relatif au fichier contenant l'élément include .
Seules les définitions de modules sont importées à partir du jeu de modules référencé, et non pas les sources de modules. Plusieurs niveaux d'imbrication sont autorisés, mais pas les inclusions en boucle (il n'y a pas de code de détection de boucle pour l'instant).
Définitions de modules
Il existe plusieurs types de définitions de modules utilisables dans un fichier de jeu de modules, et la liste peut facilement être augmentée. Seuls les types les plus courants sont mentionnés ici.
À la base, ils sont tous formés d'un élément branch décrivant la manière d'obtenir le module et d'éléments dependencies , suggests et after pour déclarer les dépendances du module.
Tout module mentionné dans l'élément dependencies est ajouté à la liste des modules lors de la commande jhbuild build (s'il n'y est pas déjà) ; JHBuild s'assure que les modules dépendants soient construits en premier.
Après avoir généré la liste des modules, les modules mentionnés dans l'élément suggests sont utilisés pour trier la liste des modules (sans y ajouter de module supplémentaire). Ceci est prévu pour les cas où un module possède une dépendance facultative sur un autre module.
cmake
L'élément cmake permet de définir un module construit à l'aide du système de construction CMake.
<cmake id="nom_module ">
<branch [ ... ] >
[...]
</branch>
<dependencies>
<dep package="nom_module "/>
...
</dependencies>
<after>
<dep package="nom_module "/>
...
</after>
</cmake>
distutils
L'élément distutils permet de définir un module construit à l'aide de Python distutils.
<distutils id="nom_module "
[ supports-non-srcdir-builds="yes|no " ]>
<branch [ ... ] >
[...]
</branch>
<dependencies>
<dep package="nom_module "/>
...
</dependencies>
<after>
<dep package="nom_module "/>
...
</after>
</distutils>
linux
L'élément linux permet de définir un module utilisé pour construire un noyau linux. De plus, une configuration de noyau séparée peut être choisie en utilisant le sous-élément kconfig .
<linux id="id "
[ makeargs="paramètres_make " ]>
<branch [ ... ] >
[...]
</branch>
<dependencies>
<dep package="nom_module "/>
...
</dependencies>
<after>
<dep package="nom_module "/>
...
</after>
<kconfig [ repo="dépôt " ]
version="version "
[ module="module " ]
[ config="config " ] />
</linux>
perl
L'élément perl permet de construire des modules Perl.
L'attribut makeargs permet de définir des paramètres supplémentaires à passer à make .
<perl id="nom_module "
[ makeargs="paramètres_make " ]>
<branch [ ... ] >
[...]
</branch>
<dependencies>
<dep package="nom_module "/>
...
</dependencies>
<after>
<dep package="nom_module "/>
...
</after>
</perl>
waf
L'élément waf permet de définir un module construit à l'aide du système de construction Waf.
L'attribut waf-command permet de définir le script de commande waf à utiliser ; la valeur par défaut est waf .
<waf id="nom_module ">
[ waf-command="commande_waf " ]>
<branch [ ... ] >
[...]
</branch>
<dependencies>
<dep package="nom_module "/>
...
</dependencies>
<after>
<dep package="nom_module "/>
...
</after>
</waf>
testmodule
L'élément testmodule permet de créer un module qui exécute une suite de tests en utilisant LDTP ou Dogtail.
<testmodule id="id "
type="type ">
<branch [ ... ] >
[...]
</branch>
<dependencies>
<dep package="nom_module "/>
...
</dependencies>
<after>
<dep package="nom_module "/>
...
</after>
<testedmodules>
<tested package="paquet " />
</testedmodules>
</testmodule>
L'attribut type indique le type de tests à exécuter dans le module. « dogtail » utilise Python pour appeler tous les fichiers .py. « ldtp » fait appel à « ldtprunner run.xml ».
Tant que l'option de configuration noxvfb n'est pas définie, un serveur Xvfb est démarré pour y lancer les tests.
Éléments désapprouvés
Sources de module
cvsroot
L'élément cvsroot est maintenant désapprouvé. Il faut utiliser l'élément repository à la place.
L'élément cvsroot permet de décrire un dépôt CVS.
<cvsroot name="nom_racine "
[ default="yes|no " ]
root="cvsroot_anon "
password="mot_de_passe_anon "/>
L'attribut name doit être un identifiant unique pour le dépôt CVS.
L'attribut default indique si cette source de module est la source par défaut pour ce fichier de jeu de modules.
L'attribut root contient la racine CVS utilisée pour l'accès anonyme à ce dépôt, et l'attribut password précise le mot de passe utilisé pour l'accès anonyme.
svnroot
L'élément svnroot est maintenant désapprouvé. Il faut utiliser l'élément repository à la place.
L'élément svnroot permet de décrire un dépôt Subversion.
<svnroot name="nom_racine "
[ default="yes|no " ]
href="svnroot_anonyme "/>
L'attribut name doit être un identifiant unique pour le dépôt Subversion.
L'attribut default indique si cette source de module est la source par défaut pour ce fichier de jeu de modules.
L'attribut href contient l'URL de base du dépôt. En général, c'est un URL http , https ou svn .
Types de modules désapprouvés
Cette section présente des éléments désapprouvés. Il se peut qu'ils soient encore utilisés dans des jeux de modules existants, mais il est conseillé de ne plus les utiliser.
tarball
Cet élément désapprouvé est une simple couche fine autour du type de module autotools et du type de dépôt tarball .
L'élément tarball permet de définir un module à construire à partir d'une archive tar.
<tarball id="nom_de_module "
[ version="version " ]
[ checkourdir="répertoire_extraction " ]
[ autogenargs="paramètres_autogen " ]
[ makeargs="paramètres_make " ]
[ autogen-sh="autogen-sh " ]
[ supports-non-srcdir-builds="yes|no " ]>
<source href="url_source "
[ size="taille_source " ]
[ hash="algorithme_source:hash_source " ]
[ md5sum="somme_md5_source " ]/>
<patches>
<patch file="nom_de_fichier " strip="niveau "/>
...
</patches>
<dependencies>
<dep package="nom_de_module "/>
...
</dependencies>
<suggests>
<dep package="nom_de_module "/>
...
</suggests>
</tarball>
Les attributs id et version sont utilisés pour identifier le module.
L'élément source indique le fichier à télécharger et compiler. L'attribut href est obligatoire, alors que les attributs size et hash , comme l'attribut obsolète md5sum , sont facultatifs. Si ces deux derniers attributs sont présents, ils sont utilisés pour vérifier que le paquet source a été correctement téléchargé.
L'élément patches sert à indiquer un ou plusieurs correctifs à appliquer à l'arborescence source après décompression. L'attribut file indique le nom de fichier du correctif et l'attribut strip précise le nombre de niveaux de répertoires à retirer dans les chemins en appliquant le correctif.
Pour les jeux de modules livrés avec JHBuild, les fichiers de correctifs sont situés dans le répertoire jhbuild/patches/ ; pour les jeux de modules référencés par URI, les fichiers de correctifs doivent se trouver dans le même répertoire que le jeu de modules ou dans le sous-répertoire patches/ . Il est aussi possible que l'attribut file indique un URI, auquel cas il sera téléchargé à cet emplacement.
Les autres attributs et les éléments dependencies , suggests et after sont traités de la même manière que pour
jhbuild-3.5.91/doc/fr/fr.po 0000644 0001750 0001750 00000606204 11753134411 015307 0 ustar 00fred fred 0000000 0000000 # French translation of jhbuild documentation.
# Copyright (C) 2008-2010 Free Software Foundation, Inc.
# This file is distributed under the same license as the jhbuild
# documentation package.
#
# Claude Paroz , 2008-2010.
# Bruno Brouard , 2009.
#
msgid ""
msgstr ""
"Project-Id-Version: jhbuild doc fr\n"
"POT-Creation-Date: 2010-07-24 07:07+0000\n"
"PO-Revision-Date: 2010-09-25 14:34+0200\n"
"Last-Translator: Claude Paroz \n"
"Language-Team: GNOME French Team \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. When image changes, this message will be marked fuzzy or untranslated for you.
#. It doesn't matter what you translate it to: it's not used at all.
#: C/jhbuild.xml:1171(None)
msgid ""
"@@image: 'figures/jhbuild_sample_dot_output.png'; "
"md5=af9fe7edb29fcaefeadfb2f5987aa6e4"
msgstr ""
"s@@image: 'figures/jhbuild_sample_dot_output.png'; "
"md5=af9fe7edb29fcaefeadfb2f5987aa6e4"
#: C/jhbuild.xml:7(title)
msgid "JHBuild Manual"
msgstr "Manuel de JHBuild"
#: C/jhbuild.xml:10(firstname)
msgid "James"
msgstr "James"
#: C/jhbuild.xml:11(surname)
msgid "Henstridge"
msgstr "Henstridge"
#: C/jhbuild.xml:14(firstname)
msgid "C.J."
msgstr "C.J."
#: C/jhbuild.xml:15(surname)
msgid "Adams-Collier"
msgstr "Adams-Collier"
#: C/jhbuild.xml:18(firstname)
msgid "Frederic"
msgstr "Frederic"
#: C/jhbuild.xml:19(surname)
msgid "Peters"
msgstr "Peters"
#: C/jhbuild.xml:22(firstname)
msgid "David"
msgstr "David"
#: C/jhbuild.xml:23(surname)
msgid "Turner"
msgstr "Turner"
#: C/jhbuild.xml:27(year)
msgid "2004, 2008"
msgstr "2004, 2008"
#: C/jhbuild.xml:28(holder)
msgid "James Henstridge"
msgstr "James Henstridge"
#: C/jhbuild.xml:33(revnumber)
msgid "JHBuild Manual v0.5"
msgstr "Manuel de JHBuild v0.5"
#: C/jhbuild.xml:34(date)
msgid "January 2008"
msgstr "Janvier 2008"
#: C/jhbuild.xml:37(revnumber)
msgid "JHBuild Manual v0.1"
msgstr "Manuel de JHBuild v0.1"
#: C/jhbuild.xml:38(date)
msgid "August 2007"
msgstr "Août 2007"
#: C/jhbuild.xml:43(para)
msgid ""
"JHBuild is a tool used to build the whole GNOME desktop from the version "
"control system. JHBuild can also be customized to build other projects too."
msgstr ""
"JHBuild est un outil utilisé pour compiler l'ensemble du bureau GNOME à "
"partir du gestionnaire de versions. Il peut aussi être configuré pour "
"compiler d'autres projets."
#: C/jhbuild.xml:50(title)
msgid "Introduction"
msgstr "Introduction"
#: C/jhbuild.xml:52(para)
msgid ""
"JHBuild is a tool designed to ease building collections of source packages, "
"called modules
. JHBuild uses module set
files "
"to describe the modules available to build. The module set
"
"files include dependency information that allows JHBuild to discover what "
"modules need to be built and in what order."
msgstr ""
"JHBuild est un outil conçu pour faciliter la compilation d'ensembles de "
"paquets source, appelés modules
. Il utilise des fichiers de "
"« jeux de modules » (moduleset) pour décrire les modules disponibles pour la "
"compilation. Ces fichiers contiennent des informations sur les dépendances, "
"ce qui permet à JHBuild de déterminer les modules à compiler et dans quel "
"ordre."
#: C/jhbuild.xml:59(para)
msgid ""
"JHBuild was originally written for building GNOME , but has since been extended to be usable with other "
"projects. A module set
file can be hosted on a web server, "
"allowing for build rules independent of the JHBuild project."
msgstr ""
"JHBuild a été d'abord créé pour compiler GNOME , mais il a été complété depuis pour être utilisable par "
"d'autres projets. Un fichier jeux de modules (moduleset) peut se trouver sur "
"un serveur Web, permettant ainsi de fournir des règles de compilation "
"indépendamment du projet JHBuild."
#: C/jhbuild.xml:65(para)
msgid ""
"JHBuild can build modules from a variety of sources, including CVS , Subversion, Arch , Bazaar , "
"Darcs , Git and Mercurial repositories, as well as Tar and Zip archives hosted on "
"web or FTP sites. JHBuild can build modules using a variety of build "
"systems, including Autotools, CMake, WAF, Ant, Python Distutils and Perl "
"Makefiles."
msgstr ""
"JHBuild peut compiler des modules de sources diverses, y compris depuis des "
"dépôts CVS , Subversion , Arch , Bazaar , Darcs , Git et Mercurial , ainsi que des archives Tar et Zip hébergées "
"sur le Web ou des sites FTP. JHBuild sait aussi compiler des modules avec "
"plusieurs systèmes de construction, dont Autotools, CMake, WAF, Ant, Python "
"Distutils et les Makefiles Perl."
#: C/jhbuild.xml:79(para)
msgid ""
"JHBuild is not intended as a replacement for the distribution's package "
"management system. Instead, it makes it easy to build software into a "
"separate install prefix without interfering with the rest of the system."
msgstr ""
"JHBuild n'est pas destiné à remplacer le système de gestion de paquets d'une "
"distribution. Au contraire, il simplifie la compilation de logiciels à "
"l'intérieur d'un préfixe d'installation distinct afin de ne pas interférer "
"avec le reste du système."
#: C/jhbuild.xml:87(title)
msgid "Getting Started"
msgstr "Premiers pas"
#: C/jhbuild.xml:89(para)
msgid ""
"JHBuild requires a few set up steps to be run before building software. "
"JHBuild requires some prerequisite software, and it is necessary to install "
"prerequisite tools needed to obtain and build the software modules."
msgstr ""
"Quelques manipulations sont nécessaires pour configurer JHBuild avant de "
"pouvoir compiler des logiciels. Certains logiciels sont nécessaires au "
"fonctionnement de JHBuild, et il est aussi nécessaire d'installer des outils "
"indispensables à l'obtention et à la construction des sources de logiciels."
#: C/jhbuild.xml:95(title)
msgid "Installing JHBuild"
msgstr "Installation de JHBuild"
#: C/jhbuild.xml:97(para)
msgid ""
"JHBuild requires a Python runtime. Verify Python >= 2.3 is installed."
msgstr ""
"JHBuild nécessite un moteur d'exécution Python. Vérifiez que Python >= "
"2.3 est installé."
#: C/jhbuild.xml:100(para)
msgid ""
"The recommended way to download JHBuild is via the version control system, "
"git . This can be achieved with the following command. It "
"is recommended to run the command from a new directory where all source code "
"will be installed, for example, ~/checkout/gnome ."
msgstr ""
"La façon recommandée de télécharger JHBuild est d'utiliser le gestionnaire "
"de versions git . La commande à utiliser est présentée ci-"
"dessous. Il est recommandé d'exécuter cette commande dans un nouveau "
"répertoire où tout le code source sera téléchargé, par exemple ~/"
"checkout/gnome )."
#: C/jhbuild.xml:107(prompt) C/jhbuild.xml:109(prompt)
#: C/jhbuild.xml:115(prompt) C/jhbuild.xml:116(prompt)
#: C/jhbuild.xml:118(prompt) C/jhbuild.xml:120(prompt)
#: C/jhbuild.xml:122(prompt) C/jhbuild.xml:127(prompt)
#: C/jhbuild.xml:128(prompt) C/jhbuild.xml:130(prompt)
#: C/jhbuild.xml:132(prompt) C/jhbuild.xml:139(prompt)
#: C/jhbuild.xml:140(prompt) C/jhbuild.xml:147(prompt)
#: C/jhbuild.xml:148(prompt) C/jhbuild.xml:278(prompt)
#: C/jhbuild.xml:296(prompt) C/jhbuild.xml:325(prompt)
#: C/jhbuild.xml:354(prompt) C/jhbuild.xml:360(prompt)
#: C/jhbuild.xml:368(prompt) C/jhbuild.xml:374(prompt)
#: C/jhbuild.xml:379(prompt) C/jhbuild.xml:387(prompt)
#: C/jhbuild.xml:392(prompt) C/jhbuild.xml:397(prompt)
#: C/jhbuild.xml:402(prompt) C/jhbuild.xml:459(prompt)
#: C/jhbuild.xml:464(prompt) C/jhbuild.xml:469(prompt)
#: C/jhbuild.xml:474(prompt) C/jhbuild.xml:497(prompt)
#: C/jhbuild.xml:501(prompt) C/jhbuild.xml:529(prompt)
#: C/jhbuild.xml:548(prompt) C/jhbuild.xml:549(prompt)
#: C/jhbuild.xml:572(prompt) C/jhbuild.xml:604(prompt)
#: C/jhbuild.xml:605(prompt) C/jhbuild.xml:628(prompt)
#: C/jhbuild.xml:687(prompt) C/jhbuild.xml:1103(prompt)
#: C/jhbuild.xml:1105(prompt) C/jhbuild.xml:1160(prompt)
#: C/jhbuild.xml:1164(prompt) C/jhbuild.xml:1392(prompt)
msgid "$"
msgstr "$"
#: C/jhbuild.xml:107(userinput)
#, no-wrap
msgid "git clone git://git.gnome.org/jhbuild"
msgstr "git clone git://git.gnome.org/jhbuild"
#: C/jhbuild.xml:108(computeroutput) C/jhbuild.xml:117(computeroutput)
#: C/jhbuild.xml:119(computeroutput) C/jhbuild.xml:121(computeroutput)
#: C/jhbuild.xml:129(computeroutput) C/jhbuild.xml:131(computeroutput)
#, no-wrap
msgid "..."
msgstr "..."
#: C/jhbuild.xml:111(para)
msgid ""
"This will download JHBuild into a new folder named jhbuild under the current directory. Now to build and install JHBuild:"
msgstr ""
"Cela va télécharger JHBuild dans un nouveau dossier nommé jhbuild dans le répertoire actuel. Ensuite, pour le construire et "
"l'installer :"
#: C/jhbuild.xml:115(userinput) C/jhbuild.xml:127(userinput)
#, no-wrap
msgid "cd jhbuild"
msgstr "cd jhbuild"
#: C/jhbuild.xml:116(userinput)
#, no-wrap
msgid "./autogen.sh"
msgstr "./autogen.sh"
#: C/jhbuild.xml:118(userinput)
#, no-wrap
msgid "make"
msgstr "make"
#: C/jhbuild.xml:120(userinput)
#, no-wrap
msgid "make install"
msgstr "make install"
#: C/jhbuild.xml:124(para)
msgid ""
"Alternatively, if autotools or gnome-doc-utils is not installed, install "
"JHBuild as follows:"
msgstr ""
"Dans le cas où autotools ou gnome-doc-utils ne sont pas installés dans votre "
"environnement, installez JHBuild de la façon suivante :"
#: C/jhbuild.xml:128(userinput)
#, no-wrap
msgid "make -f Makefile.plain"
msgstr "make -f Makefile.plain"
#: C/jhbuild.xml:130(userinput)
#, no-wrap
msgid "make -f Makefile.plain install"
msgstr "make -f Makefile.plain install"
#: C/jhbuild.xml:134(para)
msgid ""
"If the above steps complete successfully, a small shell script will be "
"installed in ~/.local/bin to start JHBuild. Add "
"~/.local/bin to the PATH :"
msgstr ""
"Si les étapes ci-dessus se sont déroulées avec succès, un petit script shell "
"sera installé dans ~/.local/bin pour lancer JHBuild. "
"Ajoutez ce chemin dans votre variable PATH :"
#: C/jhbuild.xml:139(userinput)
#, no-wrap
msgid "PATH=$PATH:~/.local/bin"
msgstr "PATH=$PATH:~/.local/bin"
#: C/jhbuild.xml:142(para)
msgid ""
"To permanently add ~/.local/bin to the PATH variable, run the following command:"
msgstr ""
"Pour ajouter ~/.local/bin de façon permanente à la "
"variable PATH , exécutez la commande suivante :"
#: C/jhbuild.xml:147(userinput) C/jhbuild.xml:497(userinput)
#, no-wrap
msgid "echo PATH=$PATH:~/.local/bin >> ~/.bashrc"
msgstr "echo PATH=$PATH:~/.local/bin >> ~/.bashrc"
#: C/jhbuild.xml:150(para)
msgid ""
"Before running JHBuild, it is necessary to set up a configuration file "
"located at ~/.jhbuildrc ."
msgstr ""
"Avant de lancer JHBuild, il est nécessaire de paramétrer le fichier de "
"configuration ~/.jhbuildrc ."
#: C/jhbuild.xml:157(title)
msgid "Configuring JHBuild"
msgstr "Configuration de JHBuild"
#: C/jhbuild.xml:159(para)
msgid ""
"The ~/.jhbuildrc file uses Python syntax to set "
"configuration variables for JHBuild. An example is provided within the "
"jhbuild directory, see sample.jhbuildrc . Copy "
"sample.jhbuildrc to ~/.jhbuildrc "
"and customize as required."
msgstr ""
"Le fichier ~/.jhbuildrc emploie la syntaxe Python pour "
"définir les variables de configuration de JHBuild. Un exemple est fourni "
"dans le répertoire jhbuild, sample.jhbuildrc . Copiez ce "
"fichier vers ~/.jhbuildrc et personnalisez-le selon vos "
"besoins."
#: C/jhbuild.xml:167(para)
msgid ""
"The sample configuration will make JHBuild build the meta-gnome-"
"desktop module and its dependencies from the gnome-"
"2.30 module set. JHBuild will unpack source trees to "
"~/checkout/gnome and install all files to "
"subdirectories of /opt/gnome . The two directories must "
"be writable."
msgstr ""
"Cette configuration modèle indique à JHBuild de construire le module "
"meta-gnome-desktop et ses dépendances à partir du "
"jeu de modules gnome-2.30 . JHBuild se charge de "
"placer les arborescences des sources dans ~/checkout/gnome et installe tous les fichiers dans des sous-répertoires de "
"/opt/gnome . Les deux répertoires doivent être "
"accessibles en écriture."
#: C/jhbuild.xml:175(para)
msgid ""
"Configuration variables are documented in . The most commonly used variables are:"
msgstr ""
"Les variables de configuration sont documentées dans username @git.gnome.org/git/'"
msgstr "repos['git.gnome.org'] = 'ssh://nom_utilisateur @git.gnome.org/git/'"
#: C/jhbuild.xml:195(varname) C/jhbuild.xml:1843(varname)
msgid "moduleset"
msgstr "moduleset"
#: C/jhbuild.xml:197(simpara) C/jhbuild.xml:1845(simpara)
msgid ""
"A string or list of strings specifying the name(s) of the module set(s) to "
"use. This can either be the filename of a moduleset included with JHBuild "
"(excluding the path and extension), or a full HTTP URL to an externally "
"managed moduleset. HTTP URL modulesets are cached locally. If a module with "
"the same name is present in more than one moduleset, the last set listed "
"takes priority. Modulesets provided with JHBuild are updated to match the "
"current GNOME development release."
msgstr ""
"Une chaîne ou une liste de chaînes indiquant le ou les noms des jeux de "
"modules à utiliser. Cela peut être le nom de fichier d'un jeu de modules "
"inclus dans JHBuild (sans chemin ni extension) ou un URL HTTP complet d'un "
"jeu de modules géré en externe. Les jeux de modules ayant un URL HTTP sont "
"placés dans un cache local. Si le nom d'un module figure dans plus d'un jeu "
"de modules, le dernier jeu de modules dans la liste est prioritaire. Les "
"jeux de modules fournis avec JHBuild sont mis à jour au gré de la "
"progression du développement de GNOME."
#: C/jhbuild.xml:209(varname) C/jhbuild.xml:1160(replaceable)
#: C/jhbuild.xml:1164(replaceable) C/jhbuild.xml:1832(varname)
msgid "modules"
msgstr "modules"
#: C/jhbuild.xml:211(simpara) C/jhbuild.xml:1834(simpara)
msgid ""
"A list of strings specifying the modules to build. The list of modules "
"actually built will be recursively expanded to include all the dependencies "
"unless the buildone command is used. Defaults to ['meta-gnome-desktop']"
" ."
msgstr ""
"Une liste de chaînes indiquant les modules à construire. La liste des "
"modules réellement construits est étendue récursivement afin d'inclure "
"toutes les dépendances, sauf si la commande buildone est utilisée. La "
"valeur par défaut est ['meta-gnome-desktop'] ."
#: C/jhbuild.xml:222(varname) C/jhbuild.xml:1638(varname)
msgid "checkoutroot"
msgstr "checkoutroot"
#: C/jhbuild.xml:224(simpara)
msgid ""
"A string specifying the directory to unpack source trees to. Unless buildroot is set, builds "
"will occur in this directory too. Defaults to ~/checkout/gnome."
msgstr ""
"Une chaîne indiquant le répertoire dans lequel décompresser les "
"arborescences source. À moins que buildroot ne soit défini, la construction "
"s'opère également dans ce répertoire. La valeur par défaut est ~/"
"checkout/gnome ."
#: C/jhbuild.xml:232(varname) C/jhbuild.xml:1926(varname)
msgid "prefix"
msgstr "prefix"
#: C/jhbuild.xml:234(simpara) C/jhbuild.xml:1928(simpara)
msgid ""
"A string specifying the prefix to install modules to. This directory must be "
"writable. Defaults to '/opt/gnome' ."
msgstr ""
"Une chaîne définissant le préfixe d'installation des modules. Ce répertoire "
"doit être accessible en écriture. La valeur par défaut est '/opt/"
"gnome' ."
#: C/jhbuild.xml:240(varname) C/jhbuild.xml:1559(varname)
msgid "autogenargs"
msgstr "autogenargs"
#: C/jhbuild.xml:242(simpara)
msgid ""
"A string containing arguments passed to the autogen.sh "
"script of all modules. Can be overridden for particular modules using the "
"module_autogenargs dictionary."
msgstr ""
"Une chaîne contenant des paramètres passés au script autogen.sh de tous les modules. Peut être surchargée par des modules précis en "
"utilisant le dictionnaire module_autogenargs ."
#: C/jhbuild.xml:251(varname) C/jhbuild.xml:1711(varname)
msgid "makeargs"
msgstr "makeargs"
#: C/jhbuild.xml:253(simpara) C/jhbuild.xml:1713(simpara)
msgid ""
"A string listing additional arguments to be passed to make. Defaults to '' ."
msgstr ""
"Une chaîne énumérant des paramètres supplémentaires à passer à "
"make . La valeur par défaut est '' ."
#: C/jhbuild.xml:262(title)
msgid "Build Prerequisites"
msgstr "Prérequis pour la construction"
#: C/jhbuild.xml:264(para)
msgid ""
"Before any modules can be built, it is necessary to have certain build tools "
"installed. Common build tools include the GNU Autotools "
"(autoconf , automake , "
"libtool and gettext ), "
"The GNU Toolchain (binutils , gcc, g++ ), pkg-config and Python, "
"depending on which modules will be built."
msgstr ""
"Avant de pouvoir construire un module, il faut avoir installé certains "
"outils de construction. Les plus courants sont les autotools GNU "
"(autoconf , automake , "
"libtool et gettext ), "
"la chaîne d'outils GNU (binutils , "
"gcc , g++ ), pkg-config "
"et Python, selon les modules à construire."
#: C/jhbuild.xml:275(para)
msgid ""
"JHBuild can check the tools are installed using the sanitycheck command:"
msgstr ""
"JHBuild peut vérifier si ces outils sont installés sur votre système à "
"l'aide de la commande sanitycheck :"
#: C/jhbuild.xml:278(userinput) C/jhbuild.xml:1352(command)
#, no-wrap
msgid "jhbuild sanitycheck"
msgstr "jhbuild sanitycheck"
#: C/jhbuild.xml:280(para)
msgid ""
"If this command displays any messages, the errors can be fixed in one of two "
"ways:"
msgstr ""
"Si cette commande affiche un message, il est possible de corriger les "
"erreurs de deux manières :"
#: C/jhbuild.xml:285(simpara)
msgid ""
"Install the required package from your distribution's repository. A list of "
"package names for different distributions is maintained on the GNOME wiki. Run the "
"sanitycheck command again after installing the "
"distribution's packages to ensure the required tools are present."
msgstr ""
"Installez le paquet requis à partir du dépôt de votre distribution. Une "
"liste de noms de "
"paquets de différentes distributions est disponible sur le wiki de "
"GNOME. Exécutez à nouveau la commande sanitycheck après "
"avoir installé les paquets de la distribution pour s'assurer que les outils "
"requis sont maintenant présents."
#: C/jhbuild.xml:294(simpara)
msgid ""
"Run the bootstrap command to download, build and install "
"the build prerequisites:"
msgstr ""
"Lancez la commande bootstrap pour télécharger, compiler "
"et installer les prérequis de construction :"
#: C/jhbuild.xml:296(userinput) C/jhbuild.xml:838(command)
#, no-wrap
msgid "jhbuild bootstrap"
msgstr "jhbuild bootstrap"
#: C/jhbuild.xml:297(para)
msgid ""
"When complete, run the sanitycheck command to verify the "
"required tools are present."
msgstr ""
"Lorsque l'opération est terminée, lancez la commande sanitycheck pour vérifier que les outils requis sont présents."
#: C/jhbuild.xml:302(para)
msgid ""
"The bootstrap command does not build all the package "
"dependencies required by the build tools. If your distribution does not "
"provide the required packages, they will need to be built outside of the "
"JHBuild environment."
msgstr ""
"La commande bootstrap ne construit pas toutes les "
"dépendances des paquets requis par les outils de construction. Si votre "
"distribution ne fournit pas ces paquets, ils devront alors être construits "
"en dehors de l'environnement JHBuild."
#: C/jhbuild.xml:308(para)
msgid ""
"The build tools dependencies include m4 , "
"perl and a C compiler (for example, "
"gcc )."
msgstr ""
"Les dépendances des outils de construction comprennent notamment "
"m4 , perl et un "
"compilateur C (par exemple gcc )."
#: C/jhbuild.xml:319(title)
msgid "Using JHBuild"
msgstr "Utilisation de JHBuild"
#: C/jhbuild.xml:321(para)
msgid ""
"After set up is complete, JHBuild can be used to build software. To build "
"all the modules selected in the ~/.jhbuildrc file, run "
"the following command:"
msgstr ""
"Après que tout a été configuré, JHBuild peut se mettre à construire des "
"logiciels. Pour construire tous les modules indiqués dans le fichier "
"~/.jhbuildrc , exécutez la commande suivante :"
#: C/jhbuild.xml:325(userinput) C/jhbuild.xml:858(command)
#, no-wrap
msgid "jhbuild build"
msgstr "jhbuild build"
#: C/jhbuild.xml:327(para)
msgid ""
"JHBuild will download, configure, compile and install each of the modules. "
"If an error occurs at any stage, JHBuild will present a menu asking what to "
"do. The choices include dropping to a shell to fix the error, rerunning the "
"build from various stages, giving up on the module, or ignore the error and "
"continue."
msgstr ""
"JHBuild va télécharger, configurer, compiler et installer chaque module. Si "
"une erreur se produit à n'importe quelle étape, JHBuild présente un menu "
"pour savoir ce qu'il doit faire. Les choix possibles comprennent le passage "
"dans un shell pour corriger l'erreur, une nouvelle passe de construction à "
"différentes étapes, l'abandon de la construction du module ou la non prise "
"en compte de l'erreur en continuant le processus."
#: C/jhbuild.xml:334(simpara)
msgid ""
"Giving up on a module will cause any modules depending on the module to fail."
msgstr ""
"L'abandon d'un module provoque l'échec de construction de tout module "
"dépendant de ce module."
#: C/jhbuild.xml:337(para)
msgid "Below is an example of the menu displayed:"
msgstr "Voici un exemple de menu qui est affiché :"
#: C/jhbuild.xml:347(prompt)
msgid "choice:"
msgstr "choix :"
#: C/jhbuild.xml:338(screen)
#, no-wrap
msgid ""
" [1] Rerun phase build\n"
" [2] Ignore error and continue to install\n"
" [3] Give up on module\n"
" [4] Start shell\n"
" [5] Reload configuration\n"
" [6] Go to phase \"wipe directory and start over\"\n"
" [7] Go to phase \"configure\"\n"
" [8] Go to phase \"clean\"\n"
" [9] Go to phase \"distclean\"\n"
"build command. For example, to build gtk+:"
msgstr ""
"Il est aussi possible de construire un jeu différent de modules (et leurs "
"dépendances) en passant les noms des modules en paramètre de la commande "
"build . Par exemple, pour construire gtk+ :"
#: C/jhbuild.xml:354(userinput)
#, no-wrap
msgid "jhbuild build gtk+"
msgstr "jhbuild build gtk+"
#: C/jhbuild.xml:356(para)
msgid ""
"If JHBuild is cancelled part way through a build, it is possible to resume "
"the build at a particular module using the --start-at "
"option:"
msgstr ""
"Si JHBuild est interrompu en cours de construction d'un module, quelle qu'en "
"soit la raison, il est possible de reprendre la construction à partir d'un "
"module précis en utilisant l'option --start-at :"
#: C/jhbuild.xml:360(userinput)
#, no-wrap
msgid "jhbuild build --start-at=pango"
msgstr "jhbuild build --start-at=pango"
#: C/jhbuild.xml:362(para)
msgid ""
"To build one or more modules, ignoring their dependencies, JHBuild provides "
"the buildone command. For the buildone "
"command to complete successfully, all dependencies must be previously built "
"and installed or provided by distribution packages."
msgstr ""
"Pour construire un ou plusieurs modules en ignorant leurs dépendances, "
"JHBuild fournit la commande buildone . Pour que cette "
"commande se déroule correctement, toutes les dépendances du module indiqué "
"doivent être préalablement construites et installées, ou fournies par des "
"paquets de votre distribution."
#: C/jhbuild.xml:368(userinput)
#, no-wrap
msgid "jhbuild buildone gtk+"
msgstr "jhbuild buildone gtk+"
#: C/jhbuild.xml:370(para)
msgid ""
"To get a list of the modules and dependencies JHBuild will build, and the "
"order they will be built, use the list command:"
msgstr ""
"Pour obtenir une liste ordonnancée des modules et des dépendances que "
"JHBuild va construire, utilisez la commande list :"
#: C/jhbuild.xml:374(userinput) C/jhbuild.xml:1224(command)
#, no-wrap
msgid "jhbuild list"
msgstr "jhbuild list"
#: C/jhbuild.xml:376(para)
msgid ""
"To get information about a particular module, use the info command:"
msgstr ""
"Pour obtenir des informations sur un module particulier, utilisez la "
"commande info :"
#: C/jhbuild.xml:379(userinput)
#, no-wrap
msgid "jhbuild info gtk+"
msgstr "jhbuild info gtk+"
#: C/jhbuild.xml:381(para)
msgid ""
"To download or update all the software sources without building, use the "
"update command. The update command "
"provides an opportunity to modify the sources before building and can be "
"useful if internet bandwidth varies."
msgstr ""
"Pour télécharger ou mettre à jour toutes les sources de logiciels sans rien "
"compiler, utilisez la commande update . Cette commande "
"donne l'occasion de modifier les sources avant la compilation et peut se "
"révéler utile quand la disponibilité de bande passante Internet est instable."
#: C/jhbuild.xml:387(userinput) C/jhbuild.xml:1477(command)
#, no-wrap
msgid "jhbuild update"
msgstr "jhbuild update"
#: C/jhbuild.xml:389(para)
msgid ""
"Later, JHBuild can build everything without downloading or updating the "
"sources:"
msgstr ""
"Plus tard, JHBuild peut tout construire sans télécharger ni mettre à jour "
"les sources :"
#: C/jhbuild.xml:392(userinput)
#, no-wrap
msgid "jhbuild build --no-network"
msgstr "jhbuild build --no-network"
#: C/jhbuild.xml:394(para)
msgid ""
"To run a particular command with the same environment used by JHBuild, use "
"the run command:"
msgstr ""
"Pour lancer une commande précise dans le même environnement utilisé par "
"JHBuild, utilisez la commande run :"
#: C/jhbuild.xml:397(replaceable) C/jhbuild.xml:1316(replaceable)
msgid "program"
msgstr "commande"
#: C/jhbuild.xml:397(userinput)
#, no-wrap
msgid "jhbuild run shell command:"
msgstr ""
"Pour lancer un shell avec l'environnement utilisé par JHBuild, utilisez la "
"commande shell :"
#: C/jhbuild.xml:402(userinput) C/jhbuild.xml:459(userinput)
#: C/jhbuild.xml:1387(command)
#, no-wrap
msgid "jhbuild shell"
msgstr "jhbuild shell"
#: C/jhbuild.xml:408(title)
msgid "JHBuild and GNOME"
msgstr "JHBuild et GNOME"
#: C/jhbuild.xml:410(para)
msgid ""
"This section provides guidance on building, installing and running GNOME."
msgstr ""
"Cette section fournit des indications sur la compilation, l'installation et "
"le fonctionnement de GNOME."
#: C/jhbuild.xml:413(title)
msgid "Building GNOME"
msgstr "Construction de GNOME"
#: C/jhbuild.xml:415(para)
msgid "To build GNOME some development packages are required. This includes:"
msgstr ""
"Pour compiler GNOME, certains paquets de développement sont nécessaires, "
"notamment :"
#: C/jhbuild.xml:419(simpara)
msgid ""
"DocBook XML DTD and XSLT stylesheets. These need to be registered in the XML "
"catalog (/etc/xml/catalog )."
msgstr ""
"La DTD DocBook XML et les feuilles de styles XSLT. Elles doivent être "
"enregistrées dans le catalogue XML (/etc/xml/catalog )."
#: C/jhbuild.xml:424(simpara)
msgid "X libraries"
msgstr "Les bibliothèques X"
#: C/jhbuild.xml:427(simpara)
msgid ""
"libsmbclient from Samba (used for browsing Windows "
"networks)."
msgstr ""
"libsmbclient de Samba (utilisé pour parcourir les "
"réseaux Windows)."
#: C/jhbuild.xml:431(simpara)
msgid "libbz2 from bzip2."
msgstr "libbz2 de bzip2."
#: C/jhbuild.xml:434(simpara)
msgid ""
"libpng , libjpeg and "
"libtiff (used for image loading)."
msgstr ""
"libpng , libjpeg et "
"libtiff (utilisés pour le chargement d'images)."
#: C/jhbuild.xml:440(para)
msgid ""
"If installing distribution packages, and if applicable for your "
"distribution, install the corresponding dev
or devel packages. A list of package names for different distributions is "
"maintained on the GNOME wiki."
msgstr ""
"Si vous installez des paquets de votre distribution et si cela s'applique à "
"votre distribution, installez les paquets dev
ou "
"devel
correspondants. Une liste de noms de paquets de différentes "
"distributions est disponible sur le wiki de GNOME."
#: C/jhbuild.xml:449(title)
msgid "Running a Single GNOME Application"
msgstr "Lancement d'une application GNOME unique"
#: C/jhbuild.xml:451(para)
msgid ""
"This section details how to run a single GNOME application. The application "
"will run within the current desktop environment. To run the application "
"within the complete JHBuild GNOME see ."
msgstr ""
"Cette section décrit comment lancer une seule application GNOME. L'application "
"se lance dans l'environnement de bureau actuel. Pour lancer une application "
"dans le contexte d'un GNOME JHBuild complet, consultez ."
#: C/jhbuild.xml:456(para)
msgid ""
"Launch a JHBuild shell. The JHBuild shell has all the necessary environment "
"variables set."
msgstr ""
"Exécutez un shell JHBuild. Ce shell dispose de toutes les variables d'environnement "
"nécessaires déjà configurées."
#: C/jhbuild.xml:461(para)
msgid "Verify the correct application will be run. For example:"
msgstr "Vérifiez que la bonne application va être lancée. Par exemple :"
#: C/jhbuild.xml:464(userinput)
#, no-wrap
msgid "which gedit"
msgstr "which gedit"
#: C/jhbuild.xml:464(screen)
#, no-wrap
msgid ""
"run command:"
msgstr ""
"Il est aussi possible de lancer l'application en utilisant la commande "
"run :"
#: C/jhbuild.xml:474(userinput)
#, no-wrap
msgid "jhbuild run gedit"
msgstr "jhbuild run gedit"
#: C/jhbuild.xml:478(title)
msgid "Running the GNOME Desktop Environment"
msgstr "Lancement de l'environnement de bureau GNOME"
#: C/jhbuild.xml:480(para)
msgid ""
"Create a new user account to run the JHBuild GNOME. Running JHBuild GNOME "
"using different user account is recommended to avoid problems caused by user "
"settings stored in the home directory. This manual refers to the new account "
"as gnomedev ."
msgstr ""
"Créez un nouveau compte utilisateur pour faire fonctionner le GNOME JHBuild. "
"Il est recommandé d'utiliser un compte utilisateur différent pour GNOME "
"JHBuild, afin d'éviter des problèmes liés aux paramètres utilisateur stockés "
"dans le dossier personnel. Ce manuel fait référence à ce nouveau compte par "
"le nom gnomedev ."
#: C/jhbuild.xml:486(para)
msgid ""
"Setup JHBuild on the new gnomedev account. Copy or soft-link ~/.jhbuildrc and "
"~/.local/bin/jhbuild to gnomedev home directory."
msgstr ""
"Configurez JHBuild dans le nouveau compte gnomedev . Copiez ou créez un lien symbolique pour "
"~/.jhbuildrc et ~/.local/bin/jhbuild dans le dossier personnel de gnomedev ."
#: C/jhbuild.xml:491(para)
msgid ""
"Open a terminal as the user gnomedev. Permanently add ~/.local/bin to the "
"PATH variable, run the following command:"
msgstr ""
"Ouvrez un terminal en tant qu'utilisateur gnomedev . Ajoutez ~/.local/bin de façon "
"permanente à la variable PATH en exécutant la commande "
"suivante :"
#: C/jhbuild.xml:499(para)
msgid "Test JHBuild works:"
msgstr "Testez que JHBuild fonctionne :"
#: C/jhbuild.xml:501(userinput)
#, no-wrap
msgid "jhbuild run pkg-config gtk+-2.0 --modversion"
msgstr "jhbuild run pkg-config gtk+-2.0 --modversion"
#: C/jhbuild.xml:501(screen)
#, no-wrap
msgid ""
"(recommended) ."
msgstr "Dans une fenêtre (recommandé) ."
#: C/jhbuild.xml:512(para)
msgid "Display manager."
msgstr "Par le gestionnaire d'affichage."
#: C/jhbuild.xml:517(title)
msgid "Setup GNOME to run in a nested window"
msgstr "Configuration de GNOME en mode « fenêtre »"
#: C/jhbuild.xml:519(para) C/jhbuild.xml:590(para)
msgid "Build and install JHBuild GNOME."
msgstr "Compilez et installez GNOME JHBuild."
#: C/jhbuild.xml:521(para)
msgid ""
"Install the Xephyr application. On Fedora the "
"system package is called xorg-x11-server-Xephyr , on "
"Ubuntu and Debian the system package is called xserver-xephyr."
msgstr ""
"Installez l'application Xephyr . Avec Fedora, le "
"paquet système s'appelle xorg-x11-server-Xephyr . Avec "
"Ubuntu et Debian, le paquet système s'appelle xserver-xephyr."
#: C/jhbuild.xml:527(para)
msgid "Test Xephyr works:"
msgstr "Testez que Xephyr fonctionne :"
#: C/jhbuild.xml:529(userinput) C/jhbuild.xml:579(userinput)
#, no-wrap
msgid "Xephyr -ac -screen 800x600 :1 2> /dev/null &"
msgstr "Xephyr -ac -screen 800x600 :1 2> /dev/null &"
#: C/jhbuild.xml:531(para)
msgid ""
"If successful, a window with black background will be displayed. Close the "
"Xephyr window."
msgstr ""
"Si tout marche bien, une fenêtre avec un fond noir apparaît. Fermez la "
"fenêtre Xephyr ."
#: C/jhbuild.xml:536(para) C/jhbuild.xml:592(para)
msgid ""
"Enable system services. JHBuild GNOME will use the /usr/bin system D-Bus daemon and the system "
"services within /usr/share/dbus-1/system-services/ . "
"JHBuild GNOME will use the JHBuild session D-Bus "
"daemon and the services within /opt/gnome/share/dbus-1/services/ /opt/"
"gnome with GNOME install prefix in the command "
"below:"
msgstr ""
"Activez les services système. GNOME JHBuild utilise le démon D-"
"Bus système /usr/bin et les services "
"système dans /usr/share/dbus-1/system-services/ . GNOME "
"JHBuild utilise le démon D-Bus de session et les "
"services dans /opt/gnome/ share/dbus-1/"
"services//opt/gnome par le "
"préfixe d'installation de GNOME dans la commande ci-après :"
#: C/jhbuild.xml:548(replaceable) C/jhbuild.xml:549(replaceable)
#: C/jhbuild.xml:604(replaceable) C/jhbuild.xml:605(replaceable)
msgid "/opt/gnome"
msgstr "/opt/gnome"
#: C/jhbuild.xml:548(userinput) C/jhbuild.xml:604(userinput)
#, no-wrap
msgid "rm -rf ~/.local/bin/gnome-jhbuild-xephyr-"
"session with the following, replacing /opt/gnome with GNOME install prefix :"
msgstr ""
"Créez un script de démarrage GNOME dans ~/.local/bin/gnome-jhbuild-"
"xephyr-session contenant le texte suivant, en remplaçant "
"/opt/gnome par le préfixe d'installation de GNOME :"
#: C/jhbuild.xml:557(programlisting) C/jhbuild.xml:613(programlisting)
#, no-wrap
msgid ""
"#!/bin/sh\n"
"\n"
"GNOME=/opt/gnome \n"
" \n"
"GDK_USE_XFT=1\n"
"XDG_DATA_DIRS=$XDG_DATA_DIRS:$GNOME/share\n"
"XDG_CONFIG_DIRS=$XDG_CONFIG_DIRS:$GNOME/etc/xdg\n"
"\n"
"jhbuild run gnome-session\n"
msgstr ""
"#!/bin/sh\n"
"\n"
"GNOME=/opt/gnome \n"
" \n"
"GDK_USE_XFT=1\n"
"XDG_DATA_DIRS=$XDG_DATA_DIRS:$GNOME/share\n"
"XDG_CONFIG_DIRS=$XDG_CONFIG_DIRS:$GNOME/etc/xdg\n"
"\n"
"jhbuild run gnome-session\n"
#: C/jhbuild.xml:568(para)
msgid ""
"Make the file ~/.local/bin/gnome-jhbuild-xephyr-session "
"executable:"
msgstr ""
"Rendez exécutable le fichier ~/.local/bin/gnome-jhbuild-xephyr-"
"session :"
#: C/jhbuild.xml:572(userinput)
#, no-wrap
msgid "chmod u+x ~/.local/bin/gnome-jhbuild-xephyr-session"
msgstr "chmod u+x ~/.local/bin/gnome-jhbuild-xephyr-session"
#: C/jhbuild.xml:575(title)
msgid "Running GNOME in a nested window"
msgstr "Lancement de GNOME en mode « fenêtre »"
#: C/jhbuild.xml:576(para)
msgid ""
"Open a terminal as the user gnomedev."
msgstr ""
"Ouvrez un terminal en tant qu'utilisateur gnomedev ."
#: C/jhbuild.xml:578(para)
msgid "Run Xephyr :"
msgstr "Exécutez Xephyr :"
#: C/jhbuild.xml:579(prompt) C/jhbuild.xml:581(prompt)
#: C/jhbuild.xml:583(prompt)
msgid "#"
msgstr "#"
#: C/jhbuild.xml:580(para)
msgid "Set the DISPLAY environment variable:"
msgstr "Définissez la variable d'environnement DISPLAY :"
#: C/jhbuild.xml:581(userinput)
#, no-wrap
msgid "export DISPLAY=:1"
msgstr "export DISPLAY=:1"
#: C/jhbuild.xml:582(para)
msgid "Start GNOME:"
msgstr "Lancez GNOME :"
#: C/jhbuild.xml:583(userinput)
#, no-wrap
msgid "gnome-jhbuild-xephyr-session"
msgstr "gnome-jhbuild-xephyr-session"
#: C/jhbuild.xml:585(para)
msgid ""
"If successful, JHBuild GNOME will be displayed in Xephyr window. If "
"unsuccessful, check the output of the terminal window."
msgstr ""
"Si tout fonctionne correctement, GNOME JHBuild s'affiche dans la fenêtre "
"Xephyr. Dans le cas contraire, inspectez la sortie affichée dans le fenêtre "
"du terminal."
#: C/jhbuild.xml:588(title)
msgid "Setup GNOME to run from the display manager"
msgstr "Configuration de GNOME en mode « gestionnaire d'affichage »"
#: C/jhbuild.xml:607(para)
msgid ""
"Create a GNOME startup script at /usr/bin/gnome-jhbuild-session with the following, replacing /opt/gnome with "
"GNOME install prefix :"
msgstr ""
"Créez un script de démarrage GNOME dans /usr/bin/gnome-jhbuild-"
"session contenant le texte suivant, en remplaçant /opt/"
"gnome par le préfixe d'installation de GNOME :"
#: C/jhbuild.xml:624(para)
msgid ""
"Make the file /usr/bin/gnome-jhbuild-session executable:"
msgstr ""
"Rendez exécutable le fichier /usr/bin/gnome-jhbuild-session :"
#: C/jhbuild.xml:628(userinput)
#, no-wrap
msgid "chmod a+x /usr/bin/gnome-jhbuild-session"
msgstr "chmod a+x /usr/bin/gnome-jhbuild-session"
#: C/jhbuild.xml:630(para)
msgid ""
"To add a new session entry in the display manager, create /usr/"
"share/xsessions/gnome-jhbuild.desktop and enter:"
msgstr ""
"Pour ajouter une nouvelle entrée de session dans le gestionnaire "
"d'affichage, créez le fichier /usr/share/xsessions/gnome-jhbuild."
"desktop avec un contenu semblable à ceci :"
#: C/jhbuild.xml:635(programlisting)
#, no-wrap
msgid ""
"[Desktop Entry]\n"
"Name=GNOME (JHBuild)\n"
"Comment=This session logs you into GNOME testing session\n"
"TryExec=/usr/bin/gnome-jhbuild-session\n"
"Exec=/usr/bin/gnome-jhbuild-session\n"
"Icon=\n"
"Type=Application"
msgstr ""
"[Desktop Entry]\n"
"Name=GNOME (JHBuild)\n"
"Comment=Cette session vous connecte dans une session GNOME de test\n"
"Exec=/usr/bin/gnome-jhbuild-session\n"
"Icon=\n"
"Type=Application"
#: C/jhbuild.xml:643(para)
msgid "Restart gdm ."
msgstr "Redémarrez gdm ."
#: C/jhbuild.xml:648(title)
msgid "Running GNOME from the display manager"
msgstr "Lancement de GNOME depuis le gestionnaire d'affichage"
#: C/jhbuild.xml:650(para)
msgid ""
"To run the JHBuild GNOME, select the GNOME (JHBuild) session at the display "
"manager before entering gnomedev "
"login credentials. If successful, JHBuild GNOME will be displayed. If "
"unsuccessful, check the log within the ~gnomedev/.xsession-errors file."
msgstr ""
"Pour lancer GNOME JHBuild, sélectionnez la session GNOME (JHBuild) dans "
"l'écran de bienvenue du gestionnaire d'affichage, avant de saisir les "
"informations de connexion du compte gnomedev. Si tout fonctionne correctement, GNOME JHBuild va apparaître. "
"Sinon, inspectez le journal dans le fichier ~gnomedev/.xsession-"
"errors ."
#: C/jhbuild.xml:662(title)
msgid "Buildbot Integration"
msgstr "Intégration à un robot de compilation (buildbot)"
#: C/jhbuild.xml:664(para)
msgid ""
"Coupled with the Buildbot "
"project, JHBuild can also function as a continuous integration tool. The "
"Buildbot configuration is used by the GNOME project at build.gnome.org ."
msgstr ""
"Associé au projet Buildbot , "
"JHBuild peut aussi fonctionner comme outil d'intégration continue. Le projet "
"GNOME utilise une configuration Buildbot sur build.gnome.org ."
#: C/jhbuild.xml:672(title)
msgid "Configuring a Buildbot Slave"
msgstr "Configuration d'un esclave de robot de compilation"
#: C/jhbuild.xml:674(para)
msgid ""
"A Buildbot slave is a variation of a normal JHBuild installation that serves "
"the requests of a Buildbot master. It is recommended to set up JHBuild and "
"complete a build with most modules building successfully before adding the "
"Buildbot customizations."
msgstr ""
"Un esclave de robot de compilation est une variante d'une installation "
"JHBuild normale qui va servir les requêtes d'un maître de compilation. Il "
"est conseillé de d'abord faire fonctionner JHBuild correctement en "
"effectuant une compilation complète et réussie de la majorité des modules "
"avant de le configurer en tant que robot de compilation."
#: C/jhbuild.xml:681(para)
msgid ""
"Buildbot commands are options to the bot command. To "
"download and install the extra required software, run the following command:"
msgstr ""
"Les commandes des robots de compilation sont des options de la commande "
"bot . Pour télécharger et installer les logiciels "
"supplémentaires requis, exécutez la commande suivante :"
#: C/jhbuild.xml:687(userinput)
#, no-wrap
msgid "jhbuild bot --setup"
msgstr "jhbuild bot --setup"
#: C/jhbuild.xml:689(para)
msgid ""
"Once this step has completed successfully, three new configuration variables "
"are required in ~/.jhbuildrc ."
msgstr ""
"Après l'exécution réussie de cette étape, trois nouvelles variables de "
"configuration sont nécessaires dans ~/.jhbuildrc ."
#: C/jhbuild.xml:695(para)
msgid ""
"It is not possible to use an alternate configuration file, the --file will not get desired effects."
msgstr ""
"Il n'est pas possible d'utiliser un fichier de configuration différent, "
"l'option --file ne "
"produira pas l'effet désiré."
#: C/jhbuild.xml:702(programlisting)
#, no-wrap
msgid ""
"\n"
"jhbuildbot_master = 'build.gnome.org:9070'\n"
"jhbuildbot_slavename = 'slavename'\n"
"jhbuildbot_password = 'password'\n"
msgstr ""
"\n"
"jhbuildbot_master = 'build.gnome.org:9070'\n"
"jhbuildbot_slavename = 'nom_esclave'\n"
"jhbuildbot_password = 'mot_de_passe'\n"
#: C/jhbuild.xml:708(para)
msgid ""
"jhbuildbot_master is a string specifying the Buildbot "
"master server; it defaults to 'build.gnome.org:9070' . "
"jhbuildbot_slavename and jhbuildbot_password identify the slave on the master server. Contact the Buildbot "
"master administrators to obtain the slave name and password."
msgstr ""
"jhbuildbot_master est une chaîne indiquant le serveur "
"maître du robot de compilation. Par défaut, c'est 'build.gnome."
"org:9070' . jhbuildbot_slavename et "
"jhbuildbot_password permettent d'identifier l'esclave sur "
"le serveur maître. Contactez les administrateurs du robot maître pour "
"obtenir les nom d'utilisateur et mot de passe de l'esclave."
#: C/jhbuild.xml:719(para)
msgid ""
"The administrators of build.gnome.org can be reached on the Build Brigade mailing list ."
msgstr ""
"Les administrateurs de build.gnome."
"org peuvent être contactés via la liste de diffusion de l'équipe de compilation ."
#: C/jhbuild.xml:739(title)
msgid "Command Reference"
msgstr "Référence des commandes"
#: C/jhbuild.xml:741(para)
msgid "JHBuild uses a command line syntax similar to tools like CVS:"
msgstr ""
"JHBuild utilise une syntaxe de ligne de commande similaire aux outils du "
"style CVS :"
#: C/jhbuild.xml:744(command)
msgid "jhbuild"
msgstr "jhbuild"
#: C/jhbuild.xml:745(replaceable)
msgid "global-options"
msgstr "options-globales"
#: C/jhbuild.xml:746(replaceable)
msgid "command"
msgstr "commande"
#: C/jhbuild.xml:747(replaceable)
msgid "command-arguments"
msgstr "paramètres-de-commande"
#: C/jhbuild.xml:750(para)
msgid "The global JHBuild options are:"
msgstr "Les options globales de JHBuild sont :"
#: C/jhbuild.xml:754(term)
msgid ""
"-f , --file config "
msgstr ""
"-f , --file configuration"
#: C/jhbuild.xml:757(simpara)
msgid ""
"Use an alternative configuration file instead of the default ~/."
"jhbuildrc ."
msgstr ""
"Utilise un fichier de configuration alternatif au lieu du fichier "
"~/.jhbuildrc par défaut."
#: C/jhbuild.xml:763(term)
msgid ""
"-m , --moduleset moduleset"
msgstr ""
"-m , --moduleset jeu-de-"
"modules "
#: C/jhbuild.xml:766(simpara)
msgid ""
"Use a module set other than the module set listed in the configuration file. "
"This option can be a relative path if the module set is located in the "
"JHBuild moduleset folder, or an absolute path if located elsewhere."
msgstr ""
"Utilise un autre jeu de modules que celui qui est indiqué dans le fichier de "
"configuration. Cette option peut être un chemin relatif si le jeu de modules "
"se trouve dans le dossier des jeux de modules de JHBuild, ou un chemin "
"absolu s'il se trouve ailleurs."
#: C/jhbuild.xml:774(option)
msgid "--no-interact"
msgstr "--no-interact"
#: C/jhbuild.xml:776(simpara)
msgid ""
"Do not prompt the user for any input. This option is useful if leaving a "
"build unattended, in order to ensure the build is not interrupted."
msgstr ""
"N'interroge jamais l'utilisateur quant à un choix à faire. Cette option est "
"utile pour effectuer une construction sans intervention humaine, afin de "
"s'assurer que la construction ne soit pas interrompue."
#: C/jhbuild.xml:783(para)
msgid "Command specific options are listed below."
msgstr ""
"Les options particulières à certaines commandes sont énumérées ci-dessous."
#: C/jhbuild.xml:786(title)
msgid "autobuild"
msgstr "autobuild"
#: C/jhbuild.xml:788(para)
msgid ""
"The autobuild command automatically builds the modules as "
"specified in the configuration file, and then upload the results to "
"JhAutobuild."
msgstr ""
"La commande autobuild construit automatiquement les "
"modules indiqués dans le fichier de configuration, puis envoie les résultats "
"vers JHAutobuild."
#: C/jhbuild.xml:793(command)
msgid "jhbuild autobuild"
msgstr "jhbuild autobuild"
#: C/jhbuild.xml:794(arg) C/jhbuild.xml:859(arg) C/jhbuild.xml:1057(arg)
#: C/jhbuild.xml:1423(arg)
msgid "--autogen"
msgstr "--autogen"
#: C/jhbuild.xml:795(arg) C/jhbuild.xml:860(arg) C/jhbuild.xml:1058(arg)
#: C/jhbuild.xml:1424(arg)
msgid "--clean"
msgstr "--clean"
#: C/jhbuild.xml:796(replaceable) C/jhbuild.xml:797(replaceable)
#: C/jhbuild.xml:866(replaceable) C/jhbuild.xml:867(replaceable)
#: C/jhbuild.xml:876(arg) C/jhbuild.xml:1066(arg)
#: C/jhbuild.xml:1117(replaceable) C/jhbuild.xml:1118(replaceable)
#: C/jhbuild.xml:1144(arg) C/jhbuild.xml:1202(arg)
#: C/jhbuild.xml:1228(replaceable) C/jhbuild.xml:1232(arg)
#: C/jhbuild.xml:1284(arg) C/jhbuild.xml:1427(replaceable)
#: C/jhbuild.xml:1428(replaceable) C/jhbuild.xml:1433(arg)
#: C/jhbuild.xml:1464(arg) C/jhbuild.xml:1478(replaceable)
#: C/jhbuild.xml:1479(replaceable) C/jhbuild.xml:1483(arg)
#: C/jhbuild.xml:1504(arg)
msgid "module"
msgstr "module"
#: C/jhbuild.xml:796(arg) C/jhbuild.xml:866(arg) C/jhbuild.xml:1117(arg)
#: C/jhbuild.xml:1427(arg) C/jhbuild.xml:1478(arg)
msgid "--skip=--autogen , --clean , --skip and --start-at options are processed as per the "
"build "
"command."
msgstr ""
"Les options --autogen , --clean , --"
"skip et --start-at sont traitées de la même "
"manière que pour la commande build ."
#: C/jhbuild.xml:810(term)
msgid ""
"--report-url=reporturl , -"
"r reporturl "
msgstr ""
"--report-url=url-de-rapport , "
"-r url-de-rapport "
#: C/jhbuild.xml:813(simpara)
msgid "This option specifies the JhAutobuild URL to report to."
msgstr "Cette option indique l'URL de JhAutobuild où envoyer le rapport."
#: C/jhbuild.xml:819(term)
msgid "--verbose , -v "
msgstr "--verbose , -v "
#: C/jhbuild.xml:821(simpara)
msgid "If specified, JHBuild's output will be more verbose."
msgstr ""
"Si indiquée, cette option produit des messages de JHBuild plus verbeux."
#: C/jhbuild.xml:830(title)
msgid "bootstrap"
msgstr "bootstrap"
#: C/jhbuild.xml:832(para)
msgid ""
"The bootstrap command installs a set of build utilities "
"required to build most modules (e.g. autoconf , "
"automake , etc)."
msgstr ""
"La commande bootstrap installe un ensemble d'utilitaires "
"de construction requis pour la plupart des modules (par ex. "
"autoconf , automake , "
"etc)."
#: C/jhbuild.xml:841(para)
msgid ""
"The bootstrap command builds modules using the same "
"method as the build command, but uses the "
"bootstrap.modules moduleset."
msgstr ""
"La commande bootstrap construit les modules avec la même "
"méthode que la commande build , mais en utilisant le jeu "
"de modules bootstrap.modules ."
#: C/jhbuild.xml:845(para)
msgid ""
"See the build command documentation for available options."
msgstr ""
"Consultez la documentation de la commande build pour connaître les options "
"disponibles."
#: C/jhbuild.xml:852(title)
msgid "build"
msgstr "build"
#: C/jhbuild.xml:854(para)
msgid ""
"The build command builds one or more packages, including "
"their dependencies."
msgstr ""
"La commande build construit un ou plusieurs paquets ainsi "
"que leurs dépendances."
#: C/jhbuild.xml:861(arg) C/jhbuild.xml:905(option) C/jhbuild.xml:1059(arg)
msgid "--check"
msgstr "--check"
#: C/jhbuild.xml:862(arg)
msgid "--dist"
msgstr "--dist"
#: C/jhbuild.xml:863(arg) C/jhbuild.xml:921(option) C/jhbuild.xml:1060(arg)
msgid "--distcheck"
msgstr "--distcheck"
#: C/jhbuild.xml:864(arg) C/jhbuild.xml:929(option) C/jhbuild.xml:1230(arg)
#: C/jhbuild.xml:1481(arg)
msgid "--ignore-suggests"
msgstr "--ignore-suggests"
#: C/jhbuild.xml:865(arg) C/jhbuild.xml:1061(arg) C/jhbuild.xml:1425(arg)
msgid "--no-network"
msgstr "--no-network"
#: C/jhbuild.xml:868(replaceable) C/jhbuild.xml:1229(replaceable)
#: C/jhbuild.xml:1480(replaceable)
msgid "tags"
msgstr "étiquettes"
#: C/jhbuild.xml:868(arg) C/jhbuild.xml:1229(arg) C/jhbuild.xml:1480(arg)
msgid "--tags=-a , --autogen "
msgstr "-a , --autogen "
#: C/jhbuild.xml:887(simpara)
msgid ""
"Always run autogen.sh before building modules. By "
"default, autogen.sh will only be called if the top-level "
"makefile is missing. Otherwise, JHBuild relies on the package's makefiles to "
"detect if configure needs to be rebuilt or rerun."
msgstr ""
"Exécute toujours autogen.sh avant de construire les "
"modules. Par défaut, autogen.sh n'est lancé que si le "
"Makefile de premier niveau est absent. Sinon, JHBuild se base sur les "
"Makefiles du paquet pour déterminer si la phase de configuration doit être "
"relancée."
#: C/jhbuild.xml:897(term)
msgid "-c , --clean "
msgstr "-c , --clean "
#: C/jhbuild.xml:899(simpara)
msgid "Run make clean before building modules."
msgstr "Exécute make clean avant de construire les modules."
#: C/jhbuild.xml:907(simpara)
msgid "Run make check after building modules."
msgstr ""
"Exécute make check après la construction des modules."
#: C/jhbuild.xml:913(term)
msgid "-d , --dist "
msgstr "-d , --dist "
#: C/jhbuild.xml:915(simpara)
msgid "Run make dist after building modules."
msgstr ""
"Exécute make dist après la construction des modules."
#: C/jhbuild.xml:923(simpara)
msgid "Run make distcheck after building modules."
msgstr ""
"Exécute make distcheck après la construction des modules."
#: C/jhbuild.xml:931(simpara)
msgid "Do not build soft dependencies."
msgstr "Ne compile pas les dépendances faibles."
#: C/jhbuild.xml:936(term)
msgid "-n , --no-network "
msgstr "-n , --no-network "
#: C/jhbuild.xml:938(simpara)
msgid ""
"Do not access the network when building modules. This will skip download or "
"update stages in a build. If a module can't be built without network access, "
"the module build will fail."
msgstr ""
"N'accède pas au réseau lors de la construction des modules. Cette option "
"évite les étapes de téléchargement ou de mise à jour lors des constructions. "
"Si un module ne peut pas être construit sans accès réseau, sa construction "
"échouera."
#: C/jhbuild.xml:946(term)
msgid ""
"-s , --skip =module,..."
msgstr ""
"-s , --skip =module,..."
#: C/jhbuild.xml:949(simpara)
msgid ""
"Do not build the listed modules. Used to skip the building of specified "
"dependencies."
msgstr ""
"Ne compile pas les modules de la liste. Utilisé pour éviter la construction "
"de dépendances spécifiques."
#: C/jhbuild.xml:955(term)
msgid "--tags =tag,... "
msgstr "--tags =étiquette,... "
#: C/jhbuild.xml:958(simpara)
msgid ""
"Ignore modules that do not match tag . Modules are "
"automatically attributed a tag matching the name of the module's module set."
msgstr ""
"Ignore les modules qui ne correspondent pas à étiquette. Une étiquette correspondant au nom du jeu de modules conteneur "
"est automatiquement attribuée à chaque module."
#: C/jhbuild.xml:966(term)
msgid ""
"-t , --start-at =module"
msgstr ""
"-t , --start-at =module"
#: C/jhbuild.xml:969(simpara)
msgid ""
"Start at the named module rather than at the beginning of the list. This "
"option is useful if the build was interrupted."
msgstr ""
"Commence par le module indiqué plutôt qu'au début de la liste des "
"dépendances. Cette option est utile quand la construction précédente a "
"échoué."
#: C/jhbuild.xml:976(option)
msgid "-D"
msgstr "-D"
#: C/jhbuild.xml:979(simpara)
msgid ""
"If supported by the underlying version control system, update the source "
"tree to the specified date before building. An ISO date format is required, "
"e.g. \"2009-09-18 02:32Z\" ."
msgstr ""
"Si le système de gestion de version sous-jacent le prend en charge, met à "
"jour l'arborescence source selon son état à la date indiquée, avant de "
"commencer la construction. La date doit être indiquée au format ISO, par "
"exemple \"2009-09-18 02:32Z\" ."
#: C/jhbuild.xml:987(term)
msgid "-x , --no-xvfb "
msgstr "-x , --no-xvfb "
#: C/jhbuild.xml:989(simpara)
msgid ""
"Run graphical tests on the actual X server rather than in a simulated Xvfb."
msgstr ""
"Effectue les tests graphiques avec le serveur X réel au lieu d'utiliser une "
"simulation Xvfb."
#: C/jhbuild.xml:995(term)
msgid "-C , --try-checkout "
msgstr "-C , --try-checkout "
#: C/jhbuild.xml:998(simpara)
msgid ""
"If the build fails, and if supported by the version control system, force a "
"checkout and run autogen.sh before retrying the build."
msgstr ""
"Si la construction échoue et que le système de gestion de version le prend "
"en charge, force une extraction et exécute autogen.sh "
"avant de recommencer la construction."
#: C/jhbuild.xml:1006(term)
msgid "-N , --no-poison "
msgstr "-N , --no-poison "
#: C/jhbuild.xml:1008(simpara)
msgid ""
"If one or more of a module's dependencies failed, this option forces JHBuild "
"to try to build the module anyway."
msgstr ""
"Si l'une ou plusieurs des dépendances du module échouent, cette option force "
"JHBuild à essayer tout de même de construire le module."
#: C/jhbuild.xml:1015(term)
msgid "-f , --force "
msgstr "-f , --force "
#: C/jhbuild.xml:1017(simpara)
msgid "Build the modules even if policy states it is not required."
msgstr ""
"Construit les modules même si la stratégie habituelle indique que ce n'est "
"pas nécessaire."
#: C/jhbuild.xml:1025(simpara)
msgid ""
"Modules listed as optional dependencies, may not be required to build the "
"module. This option forces JHBuild to build optional dependencies."
msgstr ""
"Certains modules énumérés comme dépendances facultatives ne sont pas "
"absolument nécessaires pour construire le module. Cette option force JHBuild "
"à construire aussi les dépendances facultatives."
#: C/jhbuild.xml:1032(term)
msgid "--min-time =time "
msgstr "--min-time =temps "
#: C/jhbuild.xml:1034(simpara)
msgid ""
"Skip modules installed more recently than the specified relative time. The "
"time string format is a number followed by a "
"unit. The following units are supported: seconds (s), minutes (m), hours (h) "
"and days (d). For example, --min-time=2h will skip modules "
"built less than two hours ago."
msgstr ""
"Ignore les modules installés plus récemment que l'intervalle de temps donné. "
"Le format de la chaîne temps est un nombre suivi "
"d'une unité. Les unités reconnues sont : secondes (s), minutes (m), heures "
"(h) et jours (d). Par exemple, --min-time=2h ignore les "
"modules construits il y a moins de deux heures."
#: C/jhbuild.xml:1049(title)
msgid "buildone"
msgstr "buildone"
#: C/jhbuild.xml:1051(para)
msgid ""
"The buildone command is similar to build, but it does not build the dependent modules. It is useful for "
"rebuilding one or more modules."
msgstr ""
"La commande buildone est semblable à build, mais elle ne construit pas les dépendances du module. Elle est "
"utile pour reconstruire un ou plusieurs modules."
#: C/jhbuild.xml:1056(command)
msgid "jhbuild buildone"
msgstr "jhbuild buildone"
#: C/jhbuild.xml:1069(para)
msgid ""
"The --autogen , --check , --clean, -d , --distcheck , --no-"
"network , -D and -x options are "
"processed as per the build command."
msgstr ""
"Les options --autogen , --check , --"
"clean , -d , --distcheck , --"
"no-network , -D et -x sont "
"traitées de la même manière que pour la commande build ."
#: C/jhbuild.xml:1077(para) C/jhbuild.xml:1511(para)
msgid "At least one module must be listed on the command line."
msgstr ""
"Cette commande nécessite au minimum un module dans la ligne de commande."
#: C/jhbuild.xml:1083(title)
msgid "checkbranches"
msgstr "checkbranches"
#: C/jhbuild.xml:1085(para)
msgid ""
"The checkbranches checks the module's branches are "
"defined correctly within the version control system and the branches are "
"consistent with the module set."
msgstr ""
"La commande checkbranches vérifie si les branches des "
"modules sont définies correctement dans le gestionnaire de version et si les "
"branches sont cohérentes avec le jeu de modules."
#: C/jhbuild.xml:1090(command)
msgid "jhbuild checkbranches"
msgstr "jhbuild checkbranches"
#: C/jhbuild.xml:1091(replaceable)
msgid "branch"
msgstr "branche"
#: C/jhbuild.xml:1091(arg)
msgid "--branch=--branch =branch , -bbranch "
msgstr ""
" --branch =branche , -bbranche "
#: C/jhbuild.xml:1098(simpara)
msgid "The branch to check."
msgstr "La branche à vérifier"
#: C/jhbuild.xml:1103(userinput)
#, no-wrap
msgid "jhbuild -m gnome-2.20 checkbranches"
msgstr "jhbuild -m gnome-2.20 checkbranches"
#: C/jhbuild.xml:1103(screen)
#, no-wrap
msgid ""
"clean command cleans the build directories of one or "
"more modules."
msgstr ""
"La commande clean nettoie les répertoires de compilation "
"d'un ou de plusieurs modules."
#: C/jhbuild.xml:1116(command)
msgid "jhbuild clean"
msgstr "jhbuild clean"
#: C/jhbuild.xml:1125(para)
msgid ""
"See the build command documentation for a description of available options."
msgstr ""
"Consultez la documentation de la commande build pour une description des options "
"disponibles."
#: C/jhbuild.xml:1132(title)
msgid "dot"
msgstr "dot"
#: C/jhbuild.xml:1134(para)
msgid ""
"The dot command generates a file describing the directed "
"graph formed by the dependencies between a set of modules. This file can "
"then be processed using the GraphViz software to produce a diagram."
msgstr ""
"La commande dot génère un fichier décrivant le graphe "
"directionnel formé par les dépendances dans un jeu de modules. Ce fichier "
"peut ensuite être traité par le logiciel GraphViz pour produire un diagramme."
#: C/jhbuild.xml:1141(command)
msgid "jhbuild dot"
msgstr "jhbuild dot"
#: C/jhbuild.xml:1142(arg)
msgid "--soft-deps"
msgstr "--soft-deps"
#: C/jhbuild.xml:1143(arg)
msgid "--clusters"
msgstr "--clusters"
#: C/jhbuild.xml:1151(para)
msgid ""
"The --soft-deps option adds dotted lines from the modules "
"to the soft dependencies. The --clusters option groups "
"modules from --soft-deps ajoute des lignes pointillées depuis "
"les modules vers leurs dépendances faibles. L'option --clusters groupe les modules selon les gui command starts a graphical interface to JHBuild "
"which can be used to select modules to build and change some options."
msgstr ""
"La commande gui lance une interface graphique de JHBuild "
"qui permet de sélectionner des modules à construire et de modifier certaines "
"options."
#: C/jhbuild.xml:1187(command)
msgid "jhbuild gui"
msgstr "jhbuild gui"
#: C/jhbuild.xml:1190(para)
msgid ""
"The graphical interface is rendered using GTK, so extra support libraries "
"are required."
msgstr ""
"L'interface graphique est basée sur GTK, ce qui requiert des bibliothèques "
"supplémentaires."
#: C/jhbuild.xml:1195(title)
msgid "info"
msgstr "info"
#: C/jhbuild.xml:1197(para)
msgid ""
"The info command displays information about one or more "
"modules."
msgstr ""
"La commande info affiche des informations sur un ou "
"plusieurs modules."
#: C/jhbuild.xml:1201(command)
msgid "jhbuild info"
msgstr "jhbuild info"
#: C/jhbuild.xml:1205(para)
msgid ""
"The command displays the module name, type, dependencies, dependent "
"packages, the source directory, and the time it was last installed with "
"JHBuild. If available, information specific to the module type such as the "
"CVS repository or download URL will also be displayed."
msgstr ""
"Cette commande affiche le nom du module, son type, ses dépendances, les "
"paquets qui en dépendent, le répertoire source et la date de sa dernière "
"installation avec JHBuild. Le cas échéant, elle affiche également certaines informations "
"spécifiques au type de module, telles que le dépôt CVS ou l'URL de "
"téléchargement."
#: C/jhbuild.xml:1211(para)
msgid ""
"If there is no module specified the command will display information about "
"all the modules defined in the module set."
msgstr ""
"Si aucun module n'est précisé dans la commande, des informations sont "
"affichées au sujet de tous les modules définis dans le jeu de modules."
#: C/jhbuild.xml:1217(title)
msgid "list"
msgstr "list"
#: C/jhbuild.xml:1219(para)
msgid ""
"The list command displays the expanded list of modules "
"the build command would build."
msgstr ""
"La commande list affiche la liste complète des modules "
"que la commande build construirait."
#: C/jhbuild.xml:1225(arg)
msgid "-a"
msgstr "-a"
#: C/jhbuild.xml:1226(arg)
msgid "-r"
msgstr "-r"
#: C/jhbuild.xml:1227(arg)
msgid "-s"
msgstr "-s"
#: C/jhbuild.xml:1231(arg) C/jhbuild.xml:1266(option)
msgid "--list-optional-modules"
msgstr "--list-optional-modules"
#: C/jhbuild.xml:1239(para)
msgid ""
"The --skip , --start-at , --tags, and --ignore-suggests options are processed as per "
"the build command."
msgstr ""
"Les options --skip , --start-at , --"
"tags et --ignore-suggests sont traitées de la même "
"manière que pour la commande build ."
#: C/jhbuild.xml:1248(term)
msgid "-a , --all-modules "
msgstr "-a , --all-modules "
#: C/jhbuild.xml:1251(simpara)
msgid ""
"List all the modules from the module set regardless of the build "
"dependencies."
msgstr ""
"Énumère tous les modules du jeu de modules, sans tenir compte des "
"dépendances de construction."
#: C/jhbuild.xml:1257(term)
msgid "-r , --show-revision "
msgstr "-r , --show-revision "
#: C/jhbuild.xml:1260(simpara)
msgid ""
"If a module is set to a branch, show the branch name with the module name."
msgstr ""
"Si un module est défini par une de ses branches, affiche le nom de la "
"branche avec le nom de module."
#: C/jhbuild.xml:1268(simpara)
msgid "This option forces JHBuild to list optional dependencies."
msgstr "Cette option force JHBuild à énumérer les dépendances facultatives."
#: C/jhbuild.xml:1277(title)
msgid "rdepends"
msgstr "rdepends"
#: C/jhbuild.xml:1279(para)
msgid ""
"The rdepends command displays the reverse dependencies of "
"a module."
msgstr ""
"La commande rdepends affiche les dépendances inverses "
"d'un module."
#: C/jhbuild.xml:1283(command)
msgid "jhbuild rdepends"
msgstr "jhbuild rdepends"
#: C/jhbuild.xml:1289(option)
msgid "--dependencies"
msgstr "--dependencies"
#: C/jhbuild.xml:1291(simpara)
msgid "Show dependency path next to modules."
msgstr "Affiche le chemin de dépendance à la suite des modules."
#: C/jhbuild.xml:1296(option)
msgid "--direct"
msgstr "--direct"
#: C/jhbuild.xml:1298(simpara)
msgid "Limit display to modules directly depending on specified module."
msgstr ""
"Limite l'affichage aux modules dépendant directement du module indiqué."
#: C/jhbuild.xml:1306(title)
msgid "run"
msgstr "run"
#: C/jhbuild.xml:1308(para)
msgid ""
"The run command runs the specified command using the same "
"environment that JHBuild uses when building modules."
msgstr ""
"La commande run exécute la commande indiquée dans le même "
"environnement que JHBuild utilise lors de la construction de modules."
#: C/jhbuild.xml:1313(command)
msgid "jhbuild run"
msgstr "jhbuild run"
#: C/jhbuild.xml:1314(arg)
msgid "--in-builddir"
msgstr "--in-builddir"
#: C/jhbuild.xml:1315(arg)
msgid "--in-checkoutdir"
msgstr "--in-checkoutdir"
#: C/jhbuild.xml:1317(replaceable)
msgid "argument"
msgstr "paramètre"
#: C/jhbuild.xml:1320(para)
msgid ""
"If using JHBuild to build GNOME, this command can be useful in X startup "
"scripts."
msgstr ""
"En cas d'utilisation de JHBuild pour construire GNOME, cette commande est "
"utile dans les scripts de démarrage de X."
#: C/jhbuild.xml:1325(term)
msgid "--in-builddir =module "
msgstr "--in-builddir =module "
#: C/jhbuild.xml:1327(simpara)
msgid "Run the command in the build directory of the specified module."
msgstr ""
"Exécute la commande dans le répertoire de construction du module indiqué."
#: C/jhbuild.xml:1335(term)
msgid "--in-checkoutdir =module "
msgstr "--in-checkoutdir =module "
#: C/jhbuild.xml:1337(simpara)
msgid "Run the command in the source directory of the specified module."
msgstr "Exécute la commande dans le répertoire source du module indiqué."
#: C/jhbuild.xml:1346(title)
msgid "sanitycheck"
msgstr "sanitycheck"
#: C/jhbuild.xml:1348(para)
msgid ""
"The sanitycheck command performs a number of checks to "
"verify the build environment is okay."
msgstr ""
"La commande sanitycheck effectue un certain nombre de "
"contrôles pour vérifier que l'environnement de construction est correct."
#: C/jhbuild.xml:1355(para)
msgid "Some of the checks include:"
msgstr "Ces contrôles vérifient notamment que :"
#: C/jhbuild.xml:1359(simpara)
msgid "The checkout and install prefixes are writable."
msgstr ""
"les préfixes d'extraction et d'installation sont accessibles en écriture ;"
#: C/jhbuild.xml:1363(simpara)
msgid "The required build tools are installed."
msgstr "les outils de construction indispensables sont installés ;"
#: C/jhbuild.xml:1366(simpara)
msgid ""
"Some commonly used macros are available in the search paths of the "
"aclocal commands associated with the various versions of "
"automake ."
msgstr ""
"certaines macros couramment utilisées sont disponibles dans les chemins de "
"recherche des commandes aclocal associées aux différentes "
"versions de automake ;"
#: C/jhbuild.xml:1372(simpara)
msgid "The XML catalog contains the DocBook DTD and stylesheets."
msgstr "le catalogue XML contient les DTD et feuilles de style DocBook."
#: C/jhbuild.xml:1380(title)
msgid "shell"
msgstr "shell"
#: C/jhbuild.xml:1382(para)
msgid ""
"The shell command starts the user's shell with the same "
"environment as JHBuild uses when building modules."
msgstr ""
"La commande shell lance un shell utilisateur dans le même "
"environnement que JHBuild lorsqu'il construit des modules."
#: C/jhbuild.xml:1390(para)
msgid "This command is equivalent to the following:"
msgstr "Cette commande est équivalente à ceci :"
#: C/jhbuild.xml:1392(userinput)
#, no-wrap
msgid "jhbuild run $SHELL"
msgstr "jhbuild run $SHELL"
#: C/jhbuild.xml:1394(para)
msgid ""
"The UNDER_JHBUILD environment variable will be set to \"true"
"\" when this shell is active. You can use the presence of that variable to "
"customize your shell's prompt to indicate that you indeed are under a "
"jhbuild-controlled shell. For example, you may want to put this in your "
".bashrc :"
msgstr ""
"La variable d'environnement UNDER_JHBUILD est définie à "
"« true » (vrai) lorsque ce shell est actif. Vous pouvez utiliser la présence "
"de cette variable pour personnaliser votre invite de commande afin d'indiquer "
"que vous êtes dans un shell contrôlé par JHBuild. Par exemple, il est possible "
"d'indiquer cela dans votre .bashrc :"
#: C/jhbuild.xml:1400(screen)
#, no-wrap
msgid ""
"\n"
"\tif [ -n \"$UNDER_JHBUILD\" ]; then\n"
"\t PS1=\"[jhbuild] $PS1\"\n"
"\tfi\n"
" "
msgstr ""
"\n"
"\tif [ -n \"$UNDER_JHBUILD\" ]; then\n"
"\t PS1=\"[jhbuild] $PS1\"\n"
"\tfi\n"
" "
#: C/jhbuild.xml:1406(para)
msgid ""
"This will make your bash shell display [jhbuild] before "
"your normal prompt, making it easier to see which shells are under a jhbuild "
"environment."
msgstr ""
"En conséquence, vous verrez apparaître la séquence [jhbuild] "
"au début de votre invite de commande habituelle, ce qui rend plus évident la "
"distinction entre un shell normal et un shell contrôlé par JHBuild."
#: C/jhbuild.xml:1413(title)
msgid "tinderbox"
msgstr "tinderbox"
#: C/jhbuild.xml:1415(para)
msgid ""
"The tinderbox command is similar to build, but writes all terminal output to HTML files suitable for "
"publishing on a website. It can be used to set up systems similar to "
"Mozilla's Tinderbox, or Debian's Buildd."
msgstr ""
"La commande tinderbox est semblable à la commande "
"build , mais écrit toutes les sorties de terminal dans des "
"fichiers HTML prêts à être publiés sur un site Web. Elle permet de mettre en "
"place des systèmes tels que Mozilla Tinderbox ou Debian Buildd."
#: C/jhbuild.xml:1422(command)
msgid "jhbuild tinderbox"
msgstr "jhbuild tinderbox"
#: C/jhbuild.xml:1426(replaceable)
msgid "directory"
msgstr "répertoire"
#: C/jhbuild.xml:1426(arg)
msgid "--output=--autogen , --clean , --no-"
"network , --skip , --start-at , "
"-D , -C , -N and -"
"f options are processed as per the build command."
msgstr ""
"Les options --autogen , --clean , --"
"no-network , --skip , --start-at , "
"-D , -C , -N et -f sont traitées de la même manière que pour la commande build ."
#: C/jhbuild.xml:1446(term)
msgid ""
" -o , --output =directory"
msgstr ""
"-o , --output =répertoire"
#: C/jhbuild.xml:1449(simpara)
msgid "The directory to write the HTML files."
msgstr "Le répertoire dans lequel écrire les fichiers HTML."
#: C/jhbuild.xml:1457(title)
msgid "uninstall"
msgstr "uninstall"
#: C/jhbuild.xml:1459(para)
msgid ""
"The uninstall command uninstalls one or more modules."
msgstr ""
"La commande uninstall désinstalle un ou plusieurs modules."
#: C/jhbuild.xml:1463(command)
msgid "jhbuild uninstall"
msgstr "jhbuild uninstall"
#: C/jhbuild.xml:1470(title)
msgid "update"
msgstr "update"
#: C/jhbuild.xml:1472(para)
msgid ""
"The update command is similar to build, but only performs the download or update stage for modules without "
"building them."
msgstr ""
"La commande update est semblable à build, mais n'effectue que les étapes de téléchargement et de mise à jour "
"des modules, sans les construire."
#: C/jhbuild.xml:1486(para)
msgid ""
"The --skip , --start-at , --tags, --ignore-suggests and -D options "
"are processed as per the build command."
msgstr ""
"Les options --skip , --start-at , --"
"tags , --ignore-suggests et -D "
"sont traitées de la même manière que pour la commande build ."
#: C/jhbuild.xml:1495(title)
msgid "updateone"
msgstr "updateone"
#: C/jhbuild.xml:1497(para)
msgid ""
"The updateone command is similar to update, but it does not update the dependent modules. It is useful for "
"updating one or more modules."
msgstr ""
"La commande updateone est semblable à update, mais elle ne met pas à jour les modules dépendants. Elle est utile "
"pour mettre à jour un ou plusieurs modules."
#: C/jhbuild.xml:1502(command)
msgid "jhbuild updateone"
msgstr "jhbuild updateone"
#: C/jhbuild.xml:1507(para)
msgid ""
"The -D option is processed as per the build command."
msgstr ""
"L'option -D est traitée de la même manière que pour build ."
#: C/jhbuild.xml:1518(title)
msgid "Configuration File Reference"
msgstr "Référence du fichier de configuration"
#: C/jhbuild.xml:1520(para)
msgid ""
"The ~/.jhbuildrc file uses standard Python syntax. The "
"file is run, and the resulting variables defined in the namespace are used "
"to control how JHBuild acts. A set of default values are inserted into the "
"namespace before running the user's configuration file."
msgstr ""
"Le fichier ~/.jhbuildrc utilise la syntaxe Python "
"standard. Le fichier est exécuté et les variables résultantes définies dans "
"l'espace de noms sont utilisées pour contrôler le comportement de JHBuild. "
"Un ensemble de valeurs par défaut sont insérées dans l'espace de noms avant "
"d'exécuter le fichier de configuration de l'utilisateur."
#: C/jhbuild.xml:1526(para)
msgid ""
"Boolean configuration variables are set using syntax as demonstrated in the "
"following example:"
msgstr ""
"Les variables de configuration booléennes sont définies avec une syntaxe "
"correspondant à l'exemple suivant :"
#: C/jhbuild.xml:1528(programlisting)
#, no-wrap
msgid "use_local_modulesets = True"
msgstr "use_local_modulesets = True"
#: C/jhbuild.xml:1530(para)
msgid ""
"String configuration variables are set using syntax as demonstrated in the "
"following example:"
msgstr ""
"Les variables de configuration « chaînes de caractères » sont définies avec "
"une syntaxe correspondant à l'exemple suivant :"
#: C/jhbuild.xml:1532(programlisting)
#, no-wrap
msgid "autogenargs = '--disable-static --disable-gtk-doc'"
msgstr "autogenargs = '--disable-static --disable-gtk-doc'"
#: C/jhbuild.xml:1534(para)
msgid ""
"List configuration variables are set using syntax as demonstrated in the "
"following example:"
msgstr ""
"Les variables de configuration contenant des listes sont définies avec une "
"syntaxe correspondant à l'exemple suivant :"
#: C/jhbuild.xml:1536(programlisting)
#, no-wrap
msgid "skip = ['mozilla', 'pulseaudio']"
msgstr "skip = ['mozilla', 'pulseaudio']"
#: C/jhbuild.xml:1538(para)
msgid ""
"Dictionary configuration variables are set using syntax as demonstrated in "
"the following example:"
msgstr ""
"Les variables de configuration contenant des dictionnaires sont définies "
"avec une syntaxe correspondant à l'exemple suivant :"
#: C/jhbuild.xml:1540(programlisting) C/jhbuild.xml:1968(programlisting)
#, no-wrap
msgid "repos['git.gnome.org'] = 'ssh://username@git.gnome.org/git/'"
msgstr "repos['git.gnome.org'] = 'ssh://username@git.gnome.org/git/'"
#: C/jhbuild.xml:1543(title)
msgid "Configuration Variables"
msgstr "Variables de configuration"
#: C/jhbuild.xml:1548(varname)
msgid "alwaysautogen"
msgstr "alwaysautogen"
#: C/jhbuild.xml:1550(simpara)
msgid ""
"A boolean value if set to True , always run "
"autogen.sh before make , even if a "
"makefile exists. This is equivalent to passing --always-autogen option to JHBuild. Defaults to False ."
msgstr ""
"Une valeur booléenne. Si défini à True (vrai), exécute "
"toujours autogen.sh avant make , même "
"si un makefile existe. Cela équivaut à passer l'option --always-"
"autogen à JHBuild. La valeur par défaut est False."
#: C/jhbuild.xml:1561(simpara)
msgid ""
"A string containing arguments passed to the autogen.sh "
"script of all modules. Can be overridden for particular modules using the "
"module_autogenargs dictionary."
msgstr ""
"Une chaîne contenant des paramètres passés au script autogen.sh de tous les modules. Peut être surchargée par des modules précis en "
"utilisant le dictionnaire module_autogenargs ."
#: C/jhbuild.xml:1569(varname)
msgid "branches"
msgstr "branches"
#: C/jhbuild.xml:1571(simpara)
msgid ""
"A dictionary that can be used to override the branch used for a particular "
"module. This is useful if you are making some changes on a branch of a "
"module and want JHBuild to build that branch instead of the one listed in "
"the module set."
msgstr ""
"Un dictionnaire pouvant servir à surcharger la branche utilisée pour un "
"module particulier. C'est utile si vous effectuez certaines modifications "
"sur la branche d'un module et que vous souhaitez que JHBuild construise "
"cette branche au lieu de celle qui est indiquée dans le jeu de modules."
#: C/jhbuild.xml:1576(simpara)
msgid "The definition of branches depends on the module VCS:"
msgstr ""
"La définition des branches dépend du gestionnaire de version du module :"
#: C/jhbuild.xml:1579(simpara)
msgid "CVS: revision. E.g. 'BRANCH-PROJECT-0_8' "
msgstr "CVS : révision. Par ex. 'BRANCH-PROJECT-0_8' "
#: C/jhbuild.xml:1582(simpara)
msgid ""
"Bazaar: URI of module branch. E.g. 'http://bzr.example.net/project/"
"gnome-2-28' "
msgstr ""
"Bazaar : URI de la branche du module. Par ex. 'http://bzr.example."
"net/project/gnome-2-28' "
#: C/jhbuild.xml:1585(simpara)
msgid ""
"Git: tuple, with first part being an optional repository (or the None value) "
"and the second part the name of the branch. E.g. ('git://git."
"example.net/project', 'gnome-2-28') "
msgstr ""
"Git : tuple dont la première partie est un dépôt (facultatif, peut contenir "
"la valeur None) et la seconde partie le nom de la branche. Par ex. "
"('git://git.example.net/project', 'gnome-2-28') "
#: C/jhbuild.xml:1590(simpara)
msgid ""
"Subversion: URI of module branch E.g. 'svn://svn.example.net/"
"project/gnome-2-28' "
msgstr ""
"Subversion : URI de la branche du module. Par ex. 'svn://svn."
"example.net/project/gnome-2-28' "
#: C/jhbuild.xml:1597(varname)
msgid "builddir_pattern"
msgstr "builddir_pattern"
#: C/jhbuild.xml:1599(simpara)
msgid ""
"A printf style formatting pattern used to generate "
"build directory names. This is only used when using separate source and "
"build trees. The %s in the format string will be replaced "
"with the source directory name. Defaults to '%s' ."
msgstr ""
"Un motif de formatage du style printf utilisé pour "
"générer les noms des répertoires de construction. Ceci est uniquement "
"valable lors de l'utilisation d'arborescences source et de construction "
"séparées. L'expression %s dans la chaîne de formatage est "
"remplacée par le nom du répertoire source. La valeur par défaut est "
"'%s' ."
#: C/jhbuild.xml:1608(varname)
msgid "buildroot"
msgstr "buildroot"
#: C/jhbuild.xml:1610(simpara)
msgid ""
"A string specifying the parent directory to place build trees. Defaults to "
"None , which causes builds to be performed within the "
"source trees."
msgstr ""
"Une chaîne indiquant le répertoire parent contenant les arborescences de "
"construction. La valeur par défaut est None , ce qui "
"signifie que la construction s'effectue dans les arborescences source."
#: C/jhbuild.xml:1617(varname)
msgid "buildscript"
msgstr "buildscript"
#: C/jhbuild.xml:1619(simpara)
msgid ""
"A string specifying which buildscript to use. The recommended setting is the "
"default, terminal . In particular, do not set to "
"gtk ."
msgstr ""
"Une chaîne indiquant le script de construction à utiliser. La valeur "
"recommandée est la valeur par défaut, terminal . En "
"particulier, n'indiquez pas gtk ."
#: C/jhbuild.xml:1626(varname)
msgid "build_policy"
msgstr "build_policy"
#: C/jhbuild.xml:1628(simpara)
msgid ""
"A string specifying which modules to build. The three possible options are "
"all , to build all modules requested, updated to build only modules which have changed, or updated-deps to build modules which have changed or which have dependencies "
"which have changed. Defaults to all ."
msgstr ""
"Une chaîne indiquant les modules à construire. Les trois options possibles "
"sont all pour construire tous les modules référencés, "
"updated pour ne construire que les modules qui ont subi "
"des modifications ou updated-deps pour construire les "
"modules modifiés ou qui ont des dépendances qui ont été modifiées. La valeur "
"par défaut est all ."
#: C/jhbuild.xml:1640(simpara)
msgid ""
"A string specifying the directory to unpack source trees to. Unless "
"buildroot is set, builds will occur in this directory "
"too. Defaults to ~/checkout/gnome ."
msgstr ""
"Une chaîne indiquant le répertoire dans lequel décompresser les "
"arborescences source. À moins que buildroot ne soit "
"défini, la construction s'opère également dans ce répertoire. La valeur par "
"défaut est ~/checkout/gnome ."
#: C/jhbuild.xml:1647(varname)
msgid "checkout_mode"
msgstr "checkout_mode"
#: C/jhbuild.xml:1649(simpara)
msgid ""
"A string specifying how the checkout is performed for directories in version "
"control. Defaults to update . This can be set per module "
"using module_checkout_mode . Possible values are "
"update (update checkout directory), clobber (wipe out directory before checking out the sources), "
"export (wipe out directory then create an unversioned "
"copy of the sources) and copy (checkout in a directory "
"different from the one it will build)."
msgstr ""
"Une chaîne indiquant la méthode d'extraction des répertoires dans la gestion "
"de versions. La valeur par défaut est update (mise à "
"jour). Cette valeur peut être définie pour chaque module avec "
"module_checkout_mode . Les valeurs possibles sont : "
"update (mettre à jour le répertoire extrait), "
"clobber (effacer le répertoire avant d'extraire les "
"sources), export (effacer le répertoire puis créer une "
"copie non versionnée des sources) et copy (extraire dans "
"un répertoire différent de celui où il sera construit)."
#: C/jhbuild.xml:1663(varname)
msgid "copy_dir"
msgstr "copy_dir"
#: C/jhbuild.xml:1665(simpara)
msgid ""
"A string specifying the directory to copy to, if the copy checkout_mode is in use. "
"Defaults to the checkout directory."
msgstr ""
"Une chaîne indiquant le répertoire de copie, si le mode d'extraction « copy » "
"est employé (checkout_mode). Par défaut, c'est le répertoire d'extraction lui-même."
#: C/jhbuild.xml:1672(varname)
msgid "cvs_program"
msgstr "cvs_program"
#: C/jhbuild.xml:1674(simpara)
msgid ""
"A string specifying which program to use for CVS support. This can be "
"git-cvsimport , or cvs . Defaults to "
"cvs ."
msgstr ""
"Une chaîne indiquant le programme à utiliser pour la prise en charge de CVS. "
"Cela peut être git-cvsimport ou cvs . "
"La valeur par défaut est cvs ."
#: C/jhbuild.xml:1681(varname)
msgid "installprog"
msgstr "installprog"
#: C/jhbuild.xml:1683(simpara)
msgid ""
"A string specifying a program to use as replacement for /usr/bin/"
"install . If available, defaults to the install-check wrapper provided by JHBuild. The install-check "
"wrapper optimizes header installation to reduce the time taken for rebuilds."
msgstr ""
"Une chaîne indiquant un programme à utiliser en remplacement de /"
"usr/bin/install . Si présente, sa valeur par défaut correspond au "
"script d'encapsulation install-check fourni par JHBuild. "
"Ce script optimise l'installation des en-têtes afin de réduire le temps "
"nécessaire aux recompilations."
#: C/jhbuild.xml:1693(varname)
msgid "ignore_suggests"
msgstr "ignore_suggests"
#: C/jhbuild.xml:1695(simpara)
msgid ""
"A boolean value specifying whether to ignore soft dependencies when "
"calculating the dependency tree. Defaults to False ."
msgstr ""
"Une valeur booléenne indiquant s'il faut ignorer les dépendances faibles "
"lors de la génération de l'arbre des dépendances. La valeur par défaut est "
"False ."
#: C/jhbuild.xml:1701(varname)
msgid "interact"
msgstr "interact"
#: C/jhbuild.xml:1703(simpara)
msgid ""
"A boolean value specifying whether to interact with the user. Setting this "
"value to False is equivalent to passing the --"
"no-interact option. Defaults to True ."
msgstr ""
"Une valeur booléenne indiquant si l'interaction avec l'utilisateur est "
"autorisée. La définition de cette valeur à False "
"équivaut à passer l'option --no-interact à JHBuild. La "
"valeur par défaut est True ."
#: C/jhbuild.xml:1719(varname)
msgid "makecheck"
msgstr "makecheck"
#: C/jhbuild.xml:1721(simpara)
msgid ""
"A boolean value specifying whether to run make check "
"after make . Defaults to False ."
msgstr ""
"Une valeur booléenne indiquant s'il faut exécuter make check après make . La valeur par défaut est "
"False ."
#: C/jhbuild.xml:1728(varname)
msgid "makecheck_advisory"
msgstr "makecheck_advisory"
#: C/jhbuild.xml:1730(simpara)
msgid ""
"A boolean value specifying whether failures when running make "
"check should be advisory only and not cause a build failure. "
"Defaults to False ."
msgstr ""
"Une valeur booléenne indiquant si les échecs d'exécution de la commande "
"make check doivent être considérés comme des "
"avertissements ou s'ils produisent un échec de la construction. La valeur "
"par défaut est False ."
#: C/jhbuild.xml:1736(varname)
msgid "makeclean"
msgstr "makeclean"
#: C/jhbuild.xml:1738(simpara)
msgid ""
"A boolean value specifying whether to run make clean "
"before make . Defaults to False ."
msgstr ""
"Une valeur booléenne indiquant s'il faut exécuter make clean après make . La valeur par défaut est "
"False ."
#: C/jhbuild.xml:1745(varname)
msgid "makedist"
msgstr "makedist"
#: C/jhbuild.xml:1747(simpara)
msgid ""
"A boolean value specifying whether to run make dist after "
"make . Defaults to False . This "
"setting is equivalent to passing the --dist option."
msgstr ""
"Une valeur booléenne indiquant s'il faut exécuter make dist après make . La valeur par défaut est "
"False . Ce réglage équivaut à passer l'option --"
"dist à JHBuild."
#: C/jhbuild.xml:1755(varname)
msgid "makedistcheck"
msgstr "makedistcheck"
#: C/jhbuild.xml:1757(simpara)
msgid ""
"A boolean value specifying whether to run make distcheck "
"after make . Defaults to False . This "
"setting is equivalent to passing the --distcheck option."
msgstr ""
"Une valeur booléenne indiquant s'il faut exécuter make distcheck après make . La valeur par défaut est "
"False . Ce réglage équivaut à passer l'option --"
"distcheck à JHBuild."
#: C/jhbuild.xml:1765(varname)
msgid "module_autogenargs"
msgstr "module_autogenargs"
#: C/jhbuild.xml:1767(simpara)
msgid ""
"A dictionary mapping module names to strings specifying the arguments to be "
"passed to autogen.sh . The setting in "
"module_autogenargs is used instead of the global "
"autogenargs setting. If a particular module isn't listed "
"in the dictionary, the global autogenargs will be used."
msgstr ""
"Un dictionnaire faisant correspondre les noms de modules à des chaînes "
"donnant des paramètres à passer à autogen.sh . Le "
"paramètre dans module_autogenargs est utilisé à la place "
"du paramètre global autogenargs . Si un module particulier "
"n'est pas dans le dictionnaire, c'est le paramètre global "
"autogenargs qui est utilisé."
#: C/jhbuild.xml:1777(varname)
msgid "module_checkout_mode"
msgstr "module_checkout_mode"
#: C/jhbuild.xml:1779(simpara)
msgid ""
"A dictionary specifying which checkout mode to use for modules. This "
"overrides the global checkout_mode setting."
msgstr ""
"Un dictionnaire indiquant le mode d'extraction à employer pour les modules. "
"Ce paramètre écrase le paramètre global checkout_mode ."
#: C/jhbuild.xml:1785(varname)
msgid "module_makeargs"
msgstr "module_makeargs"
#: C/jhbuild.xml:1787(simpara)
msgid ""
"A dictionary mapping module names to strings specifying the arguments to "
"pass to make . The setting in module_makeargs replaces the value of makeargs . If a particular "
"module isn't listed in the dictionary, the global makeargs will be used."
msgstr ""
"Un dictionnaire faisant correspondre les noms de modules à des chaînes "
"indiquant les paramètres à passer à make . Le paramètre "
"dans module_makeargs est utilisé à la place du paramètre "
"global makeargs . Si un module particulier n'est pas dans "
"le dictionnaire, c'est le paramètre global makeargs qui "
"est utilisé."
#: C/jhbuild.xml:1797(varname)
msgid "module_makecheck"
msgstr "module_makecheck"
#: C/jhbuild.xml:1799(simpara)
msgid ""
"A dictionary mapping module names to boolean values specifying whether to "
"run make check after make . The setting "
"in module_makecheck replaces the value of "
"makecheck . If a particular module isn't listed in the "
"dictionary, the global makecheck will be used."
msgstr ""
"Un dictionnaire faisant correspondre les noms de modules à des valeurs "
"booléennes indiquant s'il faut exécuter make check après "
"make . Le paramètre dans module_makecheck remplace la valeur de makecheck . Si un module "
"particulier n'est pas dans le dictionnaire, c'est le paramètre global "
"makecheck qui est utilisé."
#: C/jhbuild.xml:1810(varname)
msgid "module_nopoison"
msgstr "module_nopoison"
#: C/jhbuild.xml:1812(simpara)
msgid ""
"A dictionary mapping module names to boolean values. If a module is set to "
"True , JHBuild will attempt to build dependent modules "
"even if the specified module failed. The setting in "
"module_nopoison replaces the value of nopoison. If a particular module isn't listed in the dictionary, the global "
"nopoison will be used."
msgstr ""
"Un dictionnaire faisant correspondre les noms de modules à des valeurs "
"booléennes. Si la valeur pour un module vaut True , "
"JHBuild essaye de construire les modules dépendants même si le module "
"indiqué échoue. Le paramètre dans module_nopoison "
"remplace la valeur de nopoison . Si un module particulier "
"n'est pas dans le dictionnaire, c'est le paramètre global "
"nopoisons qui est utilisé."
#: C/jhbuild.xml:1823(varname)
msgid "module_extra_env"
msgstr "module_extra_env"
#: C/jhbuild.xml:1825(simpara)
msgid ""
"A dictionary mapping module names to dictionaries with extra environment "
"variables to pass when executing commands for the module."
msgstr ""
"Un dictionnaire faisant correspondre les noms de modules à des dictionnaires "
"contenant des variables d'environnement supplémentaires à passer lors de "
"l'exécution de commandes pour le module."
#: C/jhbuild.xml:1857(varname)
msgid "modulesets_dir"
msgstr "modulesets_dir"
#: C/jhbuild.xml:1859(simpara)
msgid ""
"A string specifying the directory containing the modulesets to use. Defaults "
"to the modulesets/ directory in JHBuild sources."
msgstr ""
"Une chaîne indiquant le répertoire contenant les jeux de modules à utiliser. "
"Par défaut, c'est le répertoire modulesets/ dans les "
"sources de JHBuild."
#: C/jhbuild.xml:1866(varname)
msgid "nobuild"
msgstr "nobuild"
#: C/jhbuild.xml:1868(simpara)
msgid ""
"A boolean value, if set to True JHBuild will not build "
"modules, but just download and unpack the sources. The default vale is "
"False ."
msgstr ""
"Une valeur booléenne qui si elle est définie à True "
"indique à JHBuild de ne pas construire les modules, mais uniquement de les "
"télécharger et de décompresser les sources. La valeur par défaut est "
"False ."
#: C/jhbuild.xml:1875(varname)
msgid "nonetwork"
msgstr "nonetwork"
#: C/jhbuild.xml:1877(simpara)
msgid ""
"A boolean value specifying whether to access the network. This affects "
"checking out or updating CVS modules, downloading tarballs and updating "
"module sets. Setting this to True is equivalent to "
"passing the --no-network option. Defaults to "
"False ."
msgstr ""
"Une valeur booléenne indiquant si l'accès au réseau est autorisé. Cela "
"affecte l'extraction ou la mise à jour de modules CVS, le téléchargement "
"d'archives tar et la mise à jour des jeux de modules. Définir cette valeur à "
"True équivaut à passer l'option --no-network. La valeur par défaut est False ."
#: C/jhbuild.xml:1886(varname)
msgid "nonotify"
msgstr "nonotify"
#: C/jhbuild.xml:1888(simpara)
msgid ""
"A boolean value specifying whether to emit notifications using the "
"notification daemon. If set to True , notifications are "
"not emitted. Defaults to False , except on Win32 where "
"it defaults to True ."
msgstr ""
"Une valeur booléenne indiquant s'il faut émettre des notifications au moyen "
"du démon de notification. Si la valeur vaut True , les "
"notifications ne sont pas émises. La valeur par défaut est False, sauf sur Win32 où la valeur par défaut est True."
#: C/jhbuild.xml:1896(varname)
msgid "nopoison"
msgstr "nopoison"
#: C/jhbuild.xml:1898(simpara)
msgid ""
"A boolean value, if set to True JHBuild attempts to "
"build modules even if one or more of the module's dependencies failed to "
"build. This option is equivalent to the --no-poison "
"argument. The default value is False ."
msgstr ""
"Une valeur booléenne qui, si elle est définie à True , "
"indique à JHBuild d'essayer la construction des modules même si la "
"construction d'une ou de plusieurs dépendances a échoué. Cette option est "
"équivalente au paramètre --no-poison . La valeur par défaut "
"est False ."
#: C/jhbuild.xml:1906(varname)
msgid "notrayicon"
msgstr "notrayicon"
#: C/jhbuild.xml:1908(simpara)
msgid ""
"A boolean value specifying whether to show an icon in the system tray using "
"Zenity. If set to True , notifications are not emitted. "
"Defaults to False except from on Win32, where it "
"defaults to True ."
msgstr ""
"Une valeur booléenne indiquant s'il faut afficher une icône dans la zone de "
"notifications via Zenity. Si la valeur vaut True , les "
"notifications ne sont pas émises. La valeur par défaut est False, sauf sur Win32 où la valeur par défaut est True."
#: C/jhbuild.xml:1916(varname)
msgid "noxvfb"
msgstr "noxvfb"
#: C/jhbuild.xml:1918(simpara)
msgid ""
"A boolean value, if set to True JHBuild will run any "
"graphical tests on the real X server, rather than using Xvfb. This option is equivalent to passing --no-xvfb . "
"The default value is False "
msgstr ""
"Une valeur booléenne qui, si elle est définie à True , "
"indique à JHBuild d'exécuter tout test graphique avec le serveur X réel au "
"lieu d'utiliser Xvfb . Cette option est équivalente au "
"paramètre --no-xfvb . La valeur par défaut est "
"False ."
#: C/jhbuild.xml:1934(varname)
msgid "pretty_print"
msgstr "pretty_print"
#: C/jhbuild.xml:1936(simpara)
msgid ""
"A boolean value specifying whether to pretty format the subprocess output. "
"Only CVS output supports pretty printing. Disable if the pretty printing "
"causes problems. Defaults to True ."
msgstr ""
"Une valeur booléenne indiquant s'il s'agit d'améliorer la mise en forme de "
"la sortie des sous-processus. Seules les sorties CVS gèrent la mise en forme "
"améliorée. Cette option peut être désactivée si la mise en forme améliorée "
"pose des problèmes. La valeur par défaut est True ."
#: C/jhbuild.xml:1943(varname)
msgid "progress_bar"
msgstr "progress_bar"
#: C/jhbuild.xml:1945(simpara)
msgid ""
"A boolean value specifying whether to display a progress bar during True."
msgstr ""
"Une valeur booléenne indiquant s'il faut afficher une barre de progression "
"lorsque JHBuild fonctionne en True ."
#: C/jhbuild.xml:1951(varname)
msgid "quiet_mode"
msgstr "quiet_mode"
#: C/jhbuild.xml:1953(simpara)
msgid ""
"A boolean value, if set to True disables the output of "
"running commands. Defaults to False ."
msgstr ""
"Une valeur booléenne. Si définie à True , elle désactive "
"la sortie des commandes qui s'exécutent. La valeur par défaut est "
"False ."
#: C/jhbuild.xml:1961(simpara)
msgid ""
"A dictionary specifying an alternative repository location for a particular "
"repository. This configuration variable is useful to a module developer. By "
"default, JHBuild will check out code from repositories using an anonymous "
"repository location. The dictionary keys are short repository names and the "
"values are the alternative repository location strings. For example:"
msgstr ""
"Un dictionnaire indiquant un emplacement de dépôt alternatif pour un dépôt "
"spécifique. Cette variable de configuration est utile aux développeurs de "
"modules. Par défaut, JHBuild extrait le code à partir des dépôts en "
"utilisant des emplacements anonymes. Les clés du dictionnaire sont des noms "
"de dépôts courts et les valeurs sont des chaînes d'emplacement des dépôts "
"alternatifs. Par exemple :"
#: C/jhbuild.xml:1972(varname)
msgid "skip"
msgstr "skip"
#: C/jhbuild.xml:1974(simpara)
msgid ""
"A list of modules to skip. This --skip command line option "
"extends the list. This list is empty by default."
msgstr ""
"Une liste de modules à ignorer. L'option de ligne de commande --"
"skip étend cette liste. Par défaut, cette liste est vide."
#: C/jhbuild.xml:1980(varname)
msgid "sticky_date"
msgstr "sticky_date"
#: C/jhbuild.xml:1982(simpara)
msgid ""
"A string if set, and if supported by the underlying version control system, "
"JHBuild will update the source tree to the specified date before building. "
"An ISO date format is required, e.g. 'yyyy-mm -dd '. Defaults to None ."
msgstr ""
"Une chaîne de caractères. Si définie et si le gestionnaire de versions sous-"
"jacent le prend en charge, JHBuild met à jour l'arborescence source selon "
"son état à la date indiquée. La date doit être fournie au format ISO, par "
"ex. 'aaaa -mm -"
"jj ' . La valeur par défaut est "
"None ."
#: C/jhbuild.xml:1991(varname)
msgid "svn_program"
msgstr "svn_program"
#: C/jhbuild.xml:1993(simpara)
msgid ""
"A string specifying which program to use for subversion support. This can be "
"svn , git-svn or bzr. Defaults to svn ."
msgstr ""
"Une chaîne indiquant le programme à utiliser pour la prise en charge de "
"Subversion. Cela peut être svn , git-svn ou bzr . La valeur par défaut est svn."
#: C/jhbuild.xml:2000(varname)
msgid "tarballdir"
msgstr "tarballdir"
#: C/jhbuild.xml:2002(simpara)
msgid ""
"A string if set, tarballs will be downloaded to the specified directory "
"instead of checkoutroot . This is useful if you have "
"multiple JHBuild environments or regularly clear out checkoutroot and want to reduce bandwidth usage."
msgstr ""
"Une chaîne de caractères ; si définie, les archives tar sont téléchargées "
"dans ce répertoire au lieu de checkoutroot . C'est utile "
"si vous avez plusieurs environnements JHBuild ou que vous nettoyez "
"régulièrement checkoutroot et que vous souhaitez "
"restreindre la consommation de bande passante."
#: C/jhbuild.xml:2010(varname)
msgid "tinderbox_outputdir"
msgstr "tinderbox_outputdir"
#: C/jhbuild.xml:2012(simpara)
msgid ""
"A string specifying the directory to store jhbuild tinderbox output. This string can be overridden by the --output option. Defaults to None , so either the command "
"line option must be used or this variable must be set in the configuration "
"file."
msgstr ""
"Une chaîne indiquant le répertoire de stockage de la sortie de "
"jhbuild tinderbox . Cette chaîne peut être remplacée par "
"l'option --output . La valeur par défaut est None, ce qui signifie qu'il faut obligatoirement définir cette option "
"soit dans la ligne de commande, soit dans le fichier de configuration."
#: C/jhbuild.xml:2021(varname)
msgid "trycheckout"
msgstr "trycheckout"
#: C/jhbuild.xml:2023(simpara)
msgid ""
"A boolean value, if set to True JHBuild will "
"automatically try to solve failures by 1) running autogen.sh again, and 2) checking out a newer version of a module from version "
"control. This setting is equivalent to passing the --try-checkout option."
msgstr ""
"Une option booléenne qui, si elle est définie à True , "
"indique à JHBuild d'essayer de résoudre automatiquement les échecs en 1) "
"exécutant une nouvelle fois autogen.sh et 2) extrayant "
"une nouvelle version du module à partir du contrôle de version. Ce paramètre "
"équivaut à passer l'option --try-checkout ."
#: C/jhbuild.xml:2032(varname)
msgid "use_lib64"
msgstr "use_lib64"
#: C/jhbuild.xml:2034(simpara)
msgid ""
"A boolean value that specifies whether to install libraries to "
"lib64 directories. If set, --libdir=\\"
"${exec_prefix}/lib64 will be passed to configure. Defaults to "
"True if running on x86_64 , "
"ppc64 or s390x Linux, and "
"False on other systems."
msgstr ""
"Une valeur booléenne qui indique s'il faut installer les bibliothèques dans "
"les répertoires lib64 . Lorsque c'est le cas, --"
"libdir=\\${exec_prefix}/lib64 est transmis à « configure ». Lorsque "
"JHBuild fonctionne sur un système Linux x86_64 , "
"ppc64 ou s390x , cette valeur vaut "
"True par défaut, sinon elle est définie à "
"False ."
#: C/jhbuild.xml:2045(varname)
msgid "use_local_modulesets"
msgstr "use_local_modulesets"
#: C/jhbuild.xml:2047(simpara)
msgid ""
"A boolean value that specifies to use modulesets that were checked out along "
"the JHBuild source code; instead of downloading them on-the-fly from GNOME "
"version control system. Defaults to False ."
msgstr ""
"Une valeur booléenne indiquant d'utiliser des jeux de modules qui ont été "
"extraits parallèlement au code source de JHBuild, au lieu de les télécharger "
"au fur et à mesure, à partir du dépôt du gestionnaire de versions de GNOME. "
"La valeur par défaut est False ."
#: C/jhbuild.xml:2055(varname)
msgid "xvfbargs"
msgstr "xvfbargs"
#: C/jhbuild.xml:2057(simpara)
msgid ""
"A string listing arguments to pass to Xvfb if running "
"graphical tests."
msgstr ""
"Une chaîne contenant des paramètres à passer à Xvfb si "
"des tests graphiques sont effectués."
#: C/jhbuild.xml:2065(title)
msgid "Other Configuration File Structures"
msgstr "Autres structures du fichier de configuration"
#: C/jhbuild.xml:2067(para)
msgid ""
"In addition to the above variables, there are other settings that can be set "
"in the configuration file:"
msgstr ""
"En plus des variables ci-dessus, d'autres paramètres peuvent être définis "
"dans le fichier de configuration :"
#: C/jhbuild.xml:2072(varname)
msgid "os.environ"
msgstr "os.environ"
#: C/jhbuild.xml:2074(para)
msgid ""
"A dictionary representing the environment. This environment is passed to "
"processes that JHBuild spawns."
msgstr ""
"Un dictionnaire représentant l'environnement. Cet environnement est transmis "
"aux processus générés par JHBuild."
#: C/jhbuild.xml:2076(para)
msgid ""
"Some influential environment variables include CPPFLAGS , "
"CFLAGS , INSTALL and LDFLAGS . "
"For example:"
msgstr ""
"Certaines variables d'environnement ont un impact certain, comme "
"CPPFLAGS , CFLAGS , INSTALL et "
"LDFLAGS . Par exemple :"
#: C/jhbuild.xml:2080(programlisting)
#, no-wrap
msgid "os.environ['CFLAGS'] = '-O0 -g'"
msgstr "os.environ['CFLAGS'] = '-O0 -g'"
#: C/jhbuild.xml:2084(term)
msgid ""
"addpath (envvar , "
"pathname )"
msgstr ""
"addpath (var_env , "
"chemin )"
#: C/jhbuild.xml:2087(para)
msgid ""
"This will add a directory to the PATH environment variable. "
"addpath will correctly handle the case when the "
"environment variable is initially empty (having a stray colon at the "
"beginning or end of an environment variable can have unexpected "
"consequences)."
msgstr ""
"Cela ajoute un répertoire à la variable d'environnement PATH "
"(chemin). addpath gère correctement le cas où la "
"variable d'environnement est initialement vide (un deux-points isolé au "
"début ou à la fin d'une variable d'environnement peut avoir des conséquences "
"inattendues)."
#: C/jhbuild.xml:2093(para)
msgid ""
"addpath has special handling for the "
"ACLOCAL_FLAGS environment variable, which expects paths to be "
"listed in the form -I pathname ."
msgstr ""
"addpath prend en charge de manière particulière la "
"variable d'environnement ACLOCAL_FLAGS dont la liste de "
"chemins doit être de la forme -I chemin ."
#: C/jhbuild.xml:2100(term)
msgid ""
"prependpath (envvar , "
"pathname )"
msgstr ""
"prependpath (var_env , "
"chemin )"
#: C/jhbuild.xml:2103(para)
msgid ""
"After processing the configuration file, JHBuild will alter some paths based "
"on variables such as prefix (e.g. adding $prefix/"
"bin to the start of PATH )."
msgstr ""
"Après le traitement du fichier de configuration, JHBuild modifie certains "
"chemins sur la base de variables telles que prefix (par "
"ex. en ajoutant $prefix/bin au début de la variable "
"PATH )."
#: C/jhbuild.xml:2108(para)
msgid ""
"The prependpath function works like addpath, except that the environment variable is modified after JHBuild "
"has made its changes to the environment."
msgstr ""
"La fonction prependpath fonctionne comme "
"addpath , sauf que la variable d'environnement est "
"modifiée après que JHBuild ait modifié l'environnement."
#: C/jhbuild.xml:2119(title)
msgid "Module Set File Syntax"
msgstr "Syntaxe des fichiers de jeu de modules"
#: C/jhbuild.xml:2121(para)
msgid ""
"JHBuild uses XML files to describe the dependencies between modules. A RELAX-"
"NG schema and Document Type Definition are included with JHBuild in the "
"modulesets/ directory. The RELAX-NG schema can be used "
"to edit module set files using nxml-mode in Emacs."
msgstr ""
"JHBuild utilise des fichiers XML pour décrire les dépendances entre modules. "
"Un schéma RELAX-NG et une définition de type de document (DTD : Document "
"Type Definition) sont inclus avec JHBuild dans le répertoire "
"modulesets/ . Le schéma RELAX-NG peut être utilisé pour "
"modifier les fichiers de jeux de modules au moyen du mode nxml-"
"mode dans Emacs."
#: C/jhbuild.xml:2127(para)
msgid ""
"The top-level element in a module set file is moduleset element. No XML namespace is used. The elements below "
"the top-level come in three types: module sources, include statements and "
"module definitions."
msgstr ""
"L'élément de premier niveau dans un fichier de jeu de modules est l'élément "
"moduleset . Aucun espace de nom XML "
"n'est utilisé. Les éléments sous le premier niveau sont de trois types : "
"sources de module, commandes d'inclusion et définitions de module."
#: C/jhbuild.xml:2133(title) C/jhbuild.xml:2889(title)
msgid "Module Sources"
msgstr "Sources de module"
#: C/jhbuild.xml:2135(para)
msgid ""
"Rather than listing the full location of every module, a number of \"module "
"sources\" are listed in the module set, and then referenced by name in the "
"module definitions. As well as reducing the amount of redundant information "
"in the module set, it makes it easy for a user to specify an alternative "
"source for those modules (for CVS and Subversion, it is common for "
"developers and users to use different repository access methods)."
msgstr ""
"Plutôt que d'énumérer l'emplacement exact de chaque module, plusieurs "
"« sources de modules » sont listées dans le jeu de modules, puis référencées "
"par leur nom dans les définitions de modules. En plus de réduire la quantité "
"d'informations redondantes dans le jeu de modules, cela facilite "
"l'indication d'une source alternative pour ces modules (avec CVS et "
"Subversion, il arrive fréquemment que les développeurs et les utilisateurs "
"utilisent des méthodes différentes pour accéder aux dépôts)."
#: C/jhbuild.xml:2144(para)
msgid ""
"The repository element is used to "
"describe all types of repository. The branch element is used inside module definition to specify additional "
"settings."
msgstr ""
"L'élément repository est utilisé pour "
"décrire tout type de dépôt. L'élément branch est utilisé dans une définition de module pour préciser des "
"paramètres supplémentaires."
#: C/jhbuild.xml:2149(programlisting)
#, no-wrap
msgid ""
"\n"
"<repository name=\"name \"\n"
" type=\"type \"\n"
" [ default=\"default \" ]\n"
" [ password=\"password \" ]\n"
" [ cvsroot=\"cvsroot \" ]\n"
" [ archive=\"archive \" ]\n"
" [ href=\"href \" ]\n"
" [ server=\"server \" ]\n"
" [ database=\"database \" ]\n"
" [ defbranch=\"defbranch \" ]\n"
" [ trunk-template=\"trunk-template \" ]\n"
" [ branches-template=\"branches-template \" ]\n"
" [ tags-template=\"tags-template \" ]\n"
" [ developer-href-example=\"developer-href-example \" ] />\n"
msgstr ""
"\n"
"<repository name=\"nom \"\n"
" type=\"type \"\n"
" [ default=\"valeur_par_défault \" ]\n"
" [ password=\"mot_de_passe \" ]\n"
" [ cvsroot=\"racine_cvs \" ]\n"
" [ archive=\"archive \" ]\n"
" [ href=\"href \" ]\n"
" [ server=\"serveur \" ]\n"
" [ database=\"base_de_données \" ]\n"
" [ defbranch=\"définition_branche \" ]\n"
" [ trunk-template=\"modèle_de_tronc \" ]\n"
" [ branches-template=\"modèle_de_branche \" ]\n"
" [ tags-template=\"modèle_de_tag \" ]\n"
" [ developer-href-example=\"exemple_href_pour_développeur \" ] />\n"
#: C/jhbuild.xml:2166(para)
msgid ""
"The name attribute is a unique "
"identifier for the repository."
msgstr ""
"L'attribut name est un identifiant "
"unique pour le dépôt."
#: C/jhbuild.xml:2169(para)
msgid ""
"The default attribute specifies "
"whether this repository is the default source for this module set."
msgstr ""
"L'attribut default indique si ce "
"dépôt est la source par défaut pour ce jeu de modules."
#: C/jhbuild.xml:2173(para)
msgid ""
"The type attribute specifies the type "
"of repository. It can be one of: arch , bzr, cvs , darcs , fossil, git , hg , mnt, svn , tarball . Other "
"attributes depend on the type , as "
"well as the branch used inside module "
"definitions. Those are described below in the repository type sub-sections."
msgstr ""
"L'attribut type indique le type de "
"dépôt. Les valeurs possibles sont : arch , bzr, cvs , darcs , fossil, git , hg , mnt, svn , tarball . D'autres "
"attributs dépendent de l'attribut type ainsi que de l'attribut branch "
"utilisé dans les définitions de modules. Ceux-ci sont décrits ci-dessous "
"dans les sous-sections types de dépôts."
#: C/jhbuild.xml:2184(para)
msgid ""
"The developer-href-example attribute "
"is used to specify the format of the URL for the repository used by "
"developers. This is informational only."
msgstr ""
"L'attribut developer-href-example "
"sert à indiquer le format de l'URL pour le dépôt tel qu'utilisé par les "
"développeurs, à titre informatif."
#: C/jhbuild.xml:2188(para)
msgid ""
"The branch element is used inside "
"module definitions."
msgstr ""
"L'élément branch est employé dans les "
"définitions de modules."
#: C/jhbuild.xml:2191(programlisting)
#, no-wrap
msgid ""
"\n"
"<branch\n"
" [ repo=\"repository \" ]\n"
" [ module=\"module name \" ]\n"
" [ checkoutdir=\"checkoutdir \" ]\n"
" [ revision=\"revision \" ]\n"
" [ tag=\"tag \" ]\n"
" [ update-new-dirs=\"update-new-dirs \" ]\n"
" [ override-checkoutdir=\"override-checkoutdir \" ]\n"
" [ subdir=\"subdir \" ]\n"
" [ branch=\"branch \" ]\n"
" [ version=\"version \" ]\n"
" [ size=\"size \" ]\n"
" [ source-subdir=\"source-subdir \" ]\n"
" [ hash=\"hash \" ]/>\n"
msgstr ""
"\n"
"<branch\n"
" [ repo=\"dépôt \" ]\n"
" [ module=\"nom_de_module \" ]\n"
" [ checkoutdir=\"dossier_extraction \" ]\n"
" [ revision=\"révision \" ]\n"
" [ tag=\"tag \" ]\n"
" [ update-new-dirs=\"mise_à_jour_nouveaux_dossiers \" ]\n"
" [ override-checkoutdir=\"écraser_dossier_extraction \" ]\n"
" [ subdir=\"sous-dossier \" ]\n"
" [ branch=\"branche \" ]\n"
" [ version=\"version \" ]\n"
" [ size=\"taille \" ]\n"
" [ source-subdir=\"sous-dossier_source \" ]\n"
" [ hash=\"hâchage \" ]/>\n"
#: C/jhbuild.xml:2208(para)
msgid ""
"All atributes have sensible defaults and depend on the module and repository "
"definitions. Common attributes are described here."
msgstr ""
"Tous les attributs possèdent des valeurs par défaut convenables et dépendent "
"des définitions de modules et de dépôts. Les attributs courants sont décrits "
"ici."
#: C/jhbuild.xml:2211(para)
msgid ""
"The repo attribute is used to specify "
"non-default repository name."
msgstr ""
"L'attribut repo permet d'indiquer un "
"nom de dépôt différent de la valeur par défaut."
#: C/jhbuild.xml:2214(para)
msgid ""
"The module attribute is used to "
"specify module name to checkout from the repository. Defaults to module id."
msgstr ""
"L'attribut module permet d'indiquer "
"un nom de module pour l'extraction du dépôt. Par défaut, c'est l'identifiant "
"du module."
#: C/jhbuild.xml:2218(para)
msgid ""
"The checkoutdir attribute is used to "
"specify the checkout directory name. Defaults to module id."
msgstr ""
"L'attribut checkoutdir permet "
"d'indiquer le nom du dossier d'extraction. Par défaut, c'est l'identifiant "
"du module."
#: C/jhbuild.xml:2221(para)
msgid "Other attributes are described below"
msgstr "D'autres attributs sont décrits ci-dessous"
#: C/jhbuild.xml:2224(title)
msgid "Arch"
msgstr "Arch"
#: C/jhbuild.xml:2226(para)
msgid "This repository type is used to define a Arch repository."
msgstr "Ce type de dépôt permet de définir un dépôt Arch."
#: C/jhbuild.xml:2228(para)
msgid ""
"The archive attribute is used to "
"specify the archive to use."
msgstr ""
"L'attribut archive permet d'indiquer "
"l'archive à utiliser."
#: C/jhbuild.xml:2231(para)
msgid ""
"The href attribute is used to specify "
"the URL of the repository."
msgstr ""
"L'attribut href permet d'indiquer "
"l'URL du dépôt."
#: C/jhbuild.xml:2234(programlisting)
#, no-wrap
msgid ""
"\n"
"<repository type=\"arch\" name=\"rhythmbox\"\n"
" archive=\"rhythmbox-devel@gnome.org--2004\"\n"
" href=\"http://web.rhythmbox.org/arch/2004\"/>\n"
msgstr ""
"\n"
"<repository type=\"arch\" name=\"rhythmbox\"\n"
" archive=\"rhythmbox-devel@gnome.org--2004\"\n"
" href=\"http://web.rhythmbox.org/arch/2004\"/>\n"
#: C/jhbuild.xml:2243(title)
msgid "Bazaar"
msgstr "Bazaar"
#: C/jhbuild.xml:2244(para)
msgid ""
"This repository type is used to define a Bazaar repository. It is "
"recommended to have Bazaar 1.16 or higher."
msgstr ""
"Ce type de dépôt permet de définir un dépôt Bazaar. Il est recommandé "
"de posséder une version de Bazaar 1.16 ou plus élevée."
#: C/jhbuild.xml:2247(programlisting)
#, no-wrap
msgid ""
"\n"
"<repository type=\"bzr\" name=\"launchpad.net\"\n"
" href=\"lp:\"/>\n"
" "
msgstr ""
"\n"
"<repository type=\"bzr\" name=\"launchpad.net\"\n"
" href=\"lp:\"/>\n"
" "
#: C/jhbuild.xml:2252(para)
msgid ""
"Additional attributes are: trunk-template (defaults to \"%(module)s\" ) and branches-template (defaults to \"%(module)s/"
"%(branch)s \"). These attributes are used to specify templates for "
"constructing URL. A branch element in "
"the module definitions can specify branch and user attributes. These "
"values will be substitued in the templates. If either of those are defined "
"branches-template is used, otherwise "
"trunk-template is used. This way you "
"can ovveride repository to build modules from your personal branch or build "
"many modules fron a repository with non-standard layout."
msgstr ""
"Voici des attributs supplémentaires : trunk-"
"template (égal à « %(module)s » par défaut) et branches-template (égal à « %(branch)s » par défaut). "
"Ces attributs sont utilisés pour indiquer des modèles dans la construction des "
"URL. Un élément branch dans les définitions de modules peut "
"préciser des attributs branch et "
"user . Ces valeurs sont substituées dans les modèles. Si "
"l'un des deux est défini, c'est branches-template qui est utilisé, "
"sinon c'est trunk-template . Ainsi, vous pouvez redéfinir "
"un dépôt pour construire des modules à partir de votre branche personnelle ou construire plusieurs "
"modules à partir d'un dépôt qui n'est pas structuré de manière standard."
#: C/jhbuild.xml:2267(para)
msgid ""
"An addition branch element accepts "
"revspec attibute to anchor on a "
"particular revision. Any valid bzr revspec is accepted, "
"for example date:yesterday, -5, tag:0.1 to get first "
"revision since yesterday, 5 commits behind the tip or tag \"0.1\". See "
"bzr help revisionspec for all possible values."
msgstr ""
"Un élément branch supplémentaire "
"accepte un attribut revspec pour se "
"fixer sur une révision particulière. N'importe quelle bzr revspec "
"valide est acceptée, par exemple date:yesterday, -5, tag:0.1 "
"pour obtenir la première révision depuis hier, 5 commits derrière la tête (tip) ou "
"l'étiquette « 0.1 ». Consultez bzr help revisionspec pour "
"connaître toutes les valeurs possibles."
#: C/jhbuild.xml:2276(para)
msgid ""
"For example repository with template "
"attributes defined:"
msgstr ""
"Par exemple, un dépôt avec des attributs template :"
#: C/jhbuild.xml:2279(programlisting)
#, no-wrap
msgid ""
"\n"
"<repository type=\"bzr\" name=\"launchpad.net\"\n"
" href=\"lp:\"\n"
" trunk-template=\"~bzr-pqm/%(module)s/bzr.dev\"\n"
" branches-template=\"~bzr-pqm/%(module)s/%(branch)s\"/>\n"
" "
msgstr ""
"\n"
"<repository type=\"bzr\" name=\"launchpad.net\"\n"
" href=\"lp:\"\n"
" trunk-template=\"~bzr-pqm/%(module)s/bzr.dev\"\n"
" branches-template=\"~bzr-pqm/%(module)s/%(branch)s\"/>\n"
" "
#: C/jhbuild.xml:2286(para)
msgid ""
"Example branch elements for the above "
"repository:"
msgstr ""
"Des exemples d'éléments branch pour le "
"dépôt ci-dessus :"
#: C/jhbuild.xml:2289(programlisting)
#, no-wrap
msgid ""
"\n"
"<branch repo=\"launchpad.net\"\n"
" module=\"bzr\"\n"
" checkoutdir=\"bzr-next\"/>\n"
" "
msgstr ""
"\n"
"<branch repo=\"launchpad.net\"\n"
" module=\"bzr\"\n"
" checkoutdir=\"bzr-next\"/>\n"
" "
#: C/jhbuild.xml:2294(programlisting)
#, no-wrap
msgid ""
"\n"
"<branch repo=\"launchpad.net\"\n"
" module=\"bzr\"\n"
" branch=\"2.2\"\n"
" checkoutdir=\"bzr-beta\"/>\n"
" "
msgstr ""
"\n"
"<branch repo=\"launchpad.net\"\n"
" module=\"bzr\"\n"
" branch=\"2.2\"\n"
" checkoutdir=\"bzr-beta\"/>\n"
" "
#: C/jhbuild.xml:2304(title)
msgid "CVS"
msgstr "CVS"
#: C/jhbuild.xml:2305(para)
msgid "This repository type is used to define a CVS repository."
msgstr "Ce type de dépôt permet de définir un dépôt CVS."
#: C/jhbuild.xml:2307(para)
msgid ""
"The password attribute is used to "
"specify the password to the repository."
msgstr ""
"L'attribut password permet d'indiquer "
"le mot de passe pour accéder au dépôt."
#: C/jhbuild.xml:2311(para)
msgid ""
"The cvsroot attribute is used to "
"specify the root of the repository."
msgstr ""
"L'attribut cvsroot permet d'indiquer "
"la racine du dépôt."
#: C/jhbuild.xml:2315(programlisting)
#, no-wrap
msgid ""
"\n"
"<repository type=\"cvs\" name=\"tango.freedesktop.org\"\n"
" cvsroot=\":pserver:anoncvs@anoncvs.freedesktop.org:/cvs/tango\"\n"
" password=\"\"/>\n"
" "
msgstr ""
"\n"
"<repository type=\"cvs\" name=\"tango.freedesktop.org\"\n"
" cvsroot=\":pserver:anoncvs@anoncvs.freedesktop.org:/cvs/tango\"\n"
" password=\"\"/>\n"
" "
#. TODO describe these attributes
#: C/jhbuild.xml:2322(para)
msgid ""
"Additional attributes are: revision , "
"update-new-dirs and override-checkoutdir ."
msgstr ""
"Attributs supplémentaires : revision , "
"update-new-dirs et override-checkoutdir ."
#: C/jhbuild.xml:2330(title)
msgid "Darcs"
msgstr "Darcs"
#: C/jhbuild.xml:2331(para)
msgid "This repository type is used to define a Darcs repository."
msgstr "Ce type de dépôt permet de définir un dépôt Darcs."
#: C/jhbuild.xml:2333(programlisting)
#, no-wrap
msgid ""
"\n"
"<repository type=\"darcs\" name=\"telepathy.freedesktop.org\"\n"
" href=\"http://projects.collabora.co.uk/darcs/telepathy/\"/>\n"
msgstr ""
"\n"
"<repository type=\"darcs\" name=\"telepathy.freedesktop.org\"\n"
" href=\"http://projects.collabora.co.uk/darcs/telepathy/\"/>\n"
#: C/jhbuild.xml:2340(title)
msgid "Git"
msgstr "Git"
#: C/jhbuild.xml:2341(para)
msgid "This repository type is used to define a Git repository."
msgstr "Ce type de dépôt permet de définir un dépôt Git."
#: C/jhbuild.xml:2343(programlisting)
#, no-wrap
msgid ""
"\n"
"<repository type=\"git\" name=\"git.freedesktop.org\"\n"
" href=\"git://anongit.freedesktop.org/git/\"/>\n"
" "
msgstr ""
"\n"
"<repository type=\"git\" name=\"git.freedesktop.org\"\n"
" href=\"git://anongit.freedesktop.org/git/\"/>\n"
" "
#: C/jhbuild.xml:2348(para) C/jhbuild.xml:2453(para)
msgid ""
"It allows the following attributes on the branch element:"
msgstr ""
"Il autorise les attributs suivants sur l'élément branch :"
#: C/jhbuild.xml:2351(para)
msgid ""
"The revision attribute is used to "
"specify a local or remote-tracking branch to switch to in the update phase. "
"It defaults to 'master'. It is possible to override this attribute with the "
"branches configuration variable. The switch will only be "
"performed, if the current branch is tracking a remote branch, to not disturb "
"your own work."
msgstr ""
"L'attribut revision est utilisé pour "
"indiquer une branche locale ou qui suit une branche distante vers laquelle "
"basculer lors de la phase de mise à jour. Par défaut, il contient « master ». "
"Il est possible de redéfinir cet attribut avec la variable de configuration "
"branches . Ce basculement ne se produit que si la branche "
"actuelle suit une branche distante, afin de ne pas interférer avec votre "
"propre développement."
#: C/jhbuild.xml:2359(para)
msgid ""
"The tag attribute is used to specify "
"a revision to unconditionally check out in the update phase. It overrides "
"the revision attribute."
msgstr ""
"L'attribut tag indique la révision à "
"extraire absolument durant la phase de mise à jour. Il surcharge l'attribut "
"revision ."
#. TODO I can't say much about the subdir attribute. In the
#. end it will just be appended to checkoutdir.
#. https://bugzilla.gnome.org/show_bug.cgi?id=342846
#: C/jhbuild.xml:2369(programlisting)
#, no-wrap
msgid ""
"\n"
"<branch repo=\"git.freedesktop.org\" module=\"swfdec/swfdec\"\n"
" checkoutdir=\"swfdec\"\n"
" revision=\"local-or-remote-branch \"\n"
" tag=\"tree-ish \"/>\n"
" "
msgstr ""
"\n"
"<branch repo=\"git.freedesktop.org\" module=\"swfdec/swfdec\"\n"
" checkoutdir=\"swfdec\"\n"
" revision=\"branche-locale-ou-distante \"\n"
" tag=\"étiquette \"/>\n"
" "
#: C/jhbuild.xml:2378(title)
msgid "Mercurial"
msgstr "Mercurial"
#: C/jhbuild.xml:2379(para)
msgid "This repository type is used to define a Mercurial repository."
msgstr "Ce type de dépôt permet de définir un dépôt Mercurial."
#: C/jhbuild.xml:2381(programlisting)
#, no-wrap
msgid ""
"\n"
"<repository type=\"hg\" name=\"hg.gtk-vnc\"\n"
" href=\"http://gtk-vnc.codemonkey.ws/hg/\" />\n"
msgstr ""
"\n"
"<repository type=\"hg\" name=\"hg.gtk-vnc\"\n"
" href=\"http://gtk-vnc.codemonkey.ws/hg/\" />\n"
#: C/jhbuild.xml:2386(programlisting)
#, no-wrap
msgid ""
"\n"
"<branch repo=\"hg.gtk-vnc\" module=\"outgoing.hg\" checkoutdir=\"gtk-vnc\"/>\n"
msgstr ""
"\n"
"<branch repo=\"hg.gtk-vnc\" module=\"outgoing.hg\" checkoutdir=\"gtk-vnc\"/>\n"
#: C/jhbuild.xml:2393(title)
msgid "Monotone"
msgstr "Monotone"
#: C/jhbuild.xml:2394(para)
msgid "This repository type is used to define a Monotone repository."
msgstr "Ce type de dépôt permet de définir un dépôt Monotone."
#: C/jhbuild.xml:2396(para)
msgid ""
"The server attribute is used to "
"specify the repository server."
msgstr ""
"L'attribut server permet d'indiquer "
"le serveur du dépôt."
#: C/jhbuild.xml:2399(para)
msgid ""
"The database attribute is used to "
"specify the database to use for the repository."
msgstr ""
"L'attribut database permet d'indiquer "
"la base de données à utiliser pour le dépôt."
#: C/jhbuild.xml:2403(para)
msgid ""
"The defbranch attribute is used "
"specify the branch of the repository to use."
msgstr ""
"L'attribut defbranch permet "
"d'indiquer la branche à utiliser dans le dépôt."
#: C/jhbuild.xml:2407(programlisting)
#, no-wrap
msgid ""
"\n"
"<repository type=\"mtn\" name=\"pidgin.im\"\n"
" server=\"pidgin.im\" database=\"pidgin.im.mtn\"\n"
" defbranch=\"im.pidgin.pidgin\"/>\n"
msgstr ""
"\n"
"<repository type=\"mtn\" name=\"pidgin.im\"\n"
" server=\"pidgin.im\" database=\"pidgin.im.mtn\"\n"
" defbranch=\"im.pidgin.pidgin\"/>\n"
#: C/jhbuild.xml:2416(title)
msgid "Subversion"
msgstr "Subversion"
#: C/jhbuild.xml:2417(para)
msgid "This repository type is used to define a Subversion repository."
msgstr "Ce type de dépôt permet de définir un dépôt Subversion."
#: C/jhbuild.xml:2419(programlisting)
#, no-wrap
msgid ""
"\n"
"<repository type=\"svn\" name=\"svn.gnome.org\" default=\"yes\"\n"
" href=\"http://svn.gnome.org/svn/\"/>\n"
" "
msgstr ""
"\n"
"<repository type=\"svn\" name=\"svn.gnome.org\" default=\"yes\"\n"
" href=\"http://svn.gnome.org/svn/\"/>\n"
" "
#. So how do I checkut out branch at a specific revision?
#: C/jhbuild.xml:2425(para)
msgid ""
"It allows a revision on the branch element. This attribute defines the "
"branch to checkout or, if it is a number, a specific revision to checkout."
msgstr ""
"Il autorise un attribut revision sur "
"l'élément branch . Cet attribut définit "
"la branche à extraire ou, si c'est un nombre, une révision spécifique à "
"extraire."
#: C/jhbuild.xml:2430(programlisting)
#, no-wrap
msgid ""
"\n"
"<branch revision=\"gnome-2-20\"/>\n"
" "
msgstr ""
"\n"
"<branch revision=\"gnome-2-20\"/>\n"
" "
#: C/jhbuild.xml:2434(para)
msgid ""
"It is possible to specify custom svn layout using "
"trunk-template (defaults to \"%"
"(module)s/trunk\"), branches-template "
"(defaults to \"%(module)s/branches/%(branch)s\") and tags-template (defaults to \"%(module)s/tags/%(tag)s"
"\")"
msgstr ""
"Il est possible de définir un agencement svn personnalisé "
"en utilisant trunk-template (qui vaut "
"par défaut « %(module)s/trunk »), branches-"
"template (qui vaut par défaut « %(module)s/branches/%(branch)s ») "
"et tags-template (qui vaut par défaut "
"« %(module)s/tags/%(tag)s »)."
#: C/jhbuild.xml:2445(title)
msgid "Tarballs"
msgstr "Tarballs (archives tar)"
#: C/jhbuild.xml:2446(para)
msgid "This repository type is used to define a tarball repository."
msgstr "Ce type de dépôt permet de définir un dépôt tarball."
#: C/jhbuild.xml:2448(programlisting)
#, no-wrap
msgid ""
"\n"
"<repository type=\"tarball\" name=\"dbus/dbus-python\"\n"
" href=\"http://dbus.freedesktop.org/releases/dbus-python/\"/>\n"
msgstr ""
"\n"
"<repository type=\"tarball\" name=\"dbus/dbus-python\"\n"
" href=\"http://dbus.freedesktop.org/releases/dbus-python/\"/>\n"
#: C/jhbuild.xml:2456(para)
msgid ""
"The module attribute specifies the "
"file to download and compile, the version attribute specifies the module version."
msgstr ""
"L'attribut module indique le fichier "
"à télécharger et compiler. L'attribut version indique la version du module."
#: C/jhbuild.xml:2461(para)
msgid ""
"The size and hash , as well as the obsolete md5sum , attributes are optional. If these attributes "
"are present, they are used to check that the source package was downloaded "
"correctly."
msgstr ""
"Les attributs size et hash , ainsi que l'ancien attribut md5sum sont facultatifs. Si ces attributs existent, "
"ils sont utilisés pour vérifier que le paquet source a été correctement "
"téléchargé."
#: C/jhbuild.xml:2467(para) C/jhbuild.xml:3045(para)
msgid ""
"The patches element is used to specify "
"one or more patches to apply to the source tree after unpacking, the "
"file attribute gives the patch "
"filename, and the strip attribute "
"says how many levels of directories to prune when applying the patch."
msgstr ""
"L'élément patches sert à indiquer un ou "
"plusieurs correctifs à appliquer à l'arborescence source après "
"décompression. L'attribut file "
"indique le nom de fichier du correctif et l'attribut strip précise le nombre de niveaux de répertoires à "
"retirer dans les chemins en appliquant le correctif."
#: C/jhbuild.xml:2475(para) C/jhbuild.xml:3053(para)
msgid ""
"For module sets shipped with JHBuild, the patch files are looked up in the "
"jhbuild/patches/ directory; for module sets referred by "
"URI, the patch files are looked for in the same directory as the moduleset "
"file, or in its patches/ subdirectory. It is also "
"possible for the file attribute to "
"specify a URI, in which case it will be downloaded from that location."
msgstr ""
"Pour les jeux de modules livrés avec JHBuild, les fichiers de correctifs "
"sont situés dans le répertoire jhbuild/patches/ ; pour "
"les jeux de modules référencés par URI, les fichiers de correctifs doivent "
"se trouver dans le même répertoire que le jeu de modules ou dans le sous-"
"répertoire patches/ . Il est aussi possible que "
"l'attribut file indique un URI, "
"auquel cas il sera téléchargé à cet emplacement."
#: C/jhbuild.xml:2484(programlisting)
#, no-wrap
msgid ""
"\n"
"<branch module=\"dbus-python-0.80.2.tar.gz\" version=\"0.80.2\"\n"
" repo=\"dbus/dbus-python\"\n"
" hash=\"md5:2807bc85215c995bd595e01edd9d2077\" size=\"453499\">\n"
" <patch file=\"dbus-glib-build.patch\" strip=\"1\" />\n"
"<branch>\n"
msgstr ""
"\n"
"<branch module=\"dbus-python-0.80.2.tar.gz\" version=\"0.80.2\"\n"
" repo=\"dbus/dbus-python\"\n"
" hash=\"md5:2807bc85215c995bd595e01edd9d2077\" size=\"453499\">\n"
" <patch file=\"dbus-glib-build.patch\" strip=\"1\" />\n"
"<branch>\n"
#: C/jhbuild.xml:2497(title)
msgid "Including Other Module Sets"
msgstr "Inclusion d'autres jeux de modules"
#: C/jhbuild.xml:2499(para)
msgid ""
"JHBuild allows one module set to include the contents of another by "
"reference using the include element."
msgstr ""
"JHBuild autorise un jeu de modules à inclure le contenu d'un autre jeu de "
"modules en le référençant au moyen de l'élément include ."
#: C/jhbuild.xml:2503(programlisting)
#, no-wrap
msgid ""
"\n"
"<include href=\"uri \"/>\n"
msgstr ""
"\n"
"<include href=\"uri \"/>\n"
#: C/jhbuild.xml:2507(para)
msgid ""
"The href is a URI reference to the "
"module set to be included, relative to the file containing the include element."
msgstr ""
"L'attribut href est une référence "
"sous forme d'URI vers le jeu de modules à inclure, relatif au fichier "
"contenant l'élément include ."
#: C/jhbuild.xml:2512(para)
msgid ""
"Only module definitions are imported from the referenced module set - module "
"sources are not. Multiple levels of includes are allowed, but include loops "
"are not (there isn't any code to handle loops at the moment)."
msgstr ""
"Seules les définitions de modules sont importées à partir du jeu de modules "
"référencé, et non pas les sources de modules. Plusieurs niveaux "
"d'imbrication sont autorisés, mais pas les inclusions en boucle (il n'y a "
"pas de code de détection de boucle pour l'instant)."
#: C/jhbuild.xml:2519(title)
msgid "Module Definitions"
msgstr "Définitions de modules"
#: C/jhbuild.xml:2521(para)
msgid ""
"There are various types of module definitions that can be used in a module "
"set file, and the list can easily be extended. Only the most common ones "
"will be mentioned here."
msgstr ""
"Il existe plusieurs types de définitions de modules utilisables dans un "
"fichier de jeu de modules, et la liste peut facilement être augmentée. Seuls "
"les types les plus courants sont mentionnés ici."
#: C/jhbuild.xml:2525(para)
msgid ""
"They are all basically composed of a branch element describing how to get the module and dependencies , suggests and after elements to declare "
"the dependencies of the module."
msgstr ""
"À la base, ils sont tous formés d'un élément branch décrivant la manière d'obtenir le module et d'éléments "
"dependencies , suggests et after pour "
"déclarer les dépendances du module."
#: C/jhbuild.xml:2532(para)
msgid ""
"Any modules listed in the dependencies "
"element will be added to the module list for jhbuild build if it isn't already included, and make sure the dependent modules "
"are built first."
msgstr ""
"Tout module mentionné dans l'élément dependencies est ajouté à la liste des modules lors de la "
"commande jhbuild build (s'il n'y est pas déjà) ; JHBuild "
"s'assure que les modules dépendants soient construits en premier."
#: C/jhbuild.xml:2538(para)
msgid ""
"After generating the modules list, the modules listed in the suggests element will be used to further sort the "
"modules list (although it will not pull any additional modules). This is "
"intended for cases where a module has an optional dependency on another "
"module."
msgstr ""
"Après avoir généré la liste des modules, les modules mentionnés dans "
"l'élément suggests sont utilisés pour "
"trier la liste des modules (sans y ajouter de module supplémentaire). Ceci "
"est prévu pour les cas où un module possède une dépendance facultative sur "
"un autre module."
#: C/jhbuild.xml:2546(title)
msgid "autotools"
msgstr "autotools"
#: C/jhbuild.xml:2548(para)
msgid ""
"The autotools element is used to define "
"a module which is compiled using the GNU Autotools build system."
msgstr ""
"L'élément autotools sert à définir un "
"module qui doit être compilé à l'aide du système de construction GNU "
"Autotools."
#: C/jhbuild.xml:2552(programlisting)
#, no-wrap
msgid ""
"\n"
"<autotools id=\"id \"\n"
"\t [ autogenargs=\"autogenargs \" ]\n"
"\t [ makeargs=\"makeargs \" ]\n"
"\t [ makeinstallargs=\"makeinstallargs \" ]\n"
"\t [ autogen-sh=\"autogen-sh \" ]\n"
"\t [ makefile=\"makefile \" ]\n"
"\t [ skip-autogen=\"skip-autogen \" ]\n"
"\t [ autogen-template=\"autogen-template \" ]\n"
"\t [ check-target=\"check-target \" ]\n"
"\t [ supports-non-srcdir-builds=\"supports-non-srcdir-builds \" ]>\n"
"\n"
" <branch [ ... ] >\n"
" [...]\n"
" </branch>\n"
"\n"
" <dependencies>\n"
" <dep package=\"modulename \"/>\n"
" ...\n"
" </dependencies>\n"
" <after>\n"
" <dep package=\"modulename \"/>\n"
" ...\n"
" </after>\n"
"\n"
"</autotools>\n"
msgstr ""
"\n"
"<autotools id=\"id \"\n"
"\t [ autogenargs=\"paramètres_autogen \" ]\n"
"\t [ makeargs=\"paramètres_make \" ]\n"
"\t [ makeinstallargs=\"paramètres_make_install \" ]\n"
"\t [ autogen-sh=\"autogen-sh \" ]\n"
"\t [ makefile=\"makefile \" ]\n"
"\t [ skip-autogen=\"ignorer-autogen \" ]\n"
"\t [ autogen-template=\"modèle_autogen \" ]\n"
"\t [ check-target=\"cible_contrôle \" ]\n"
"\t [ supports-non-srcdir-builds=\"gère_construction_non_srcdir \" ]>\n"
"\n"
" <branch [ ... ] >\n"
" [...]\n"
" </branch>\n"
"\n"
" <dependencies>\n"
" <dep package=\"nom_module \"/>\n"
" ...\n"
" </dependencies>\n"
" <after>\n"
" <dep package=\"nom_module \"/>\n"
" ...\n"
" </after>\n"
"\n"
"</autotools>\n"
#: C/jhbuild.xml:2580(para)
msgid ""
"The autogenargs and makeargs and makeinstallargs attributes are used to specify additional "
"arguments to pass to autogen.sh , make "
"and make install respectively."
msgstr ""
"Les attributs autogenargs , makeargs et makeinstallargs servent à indiquer des paramètres "
"supplémentaires à transmettre respectivement à autogen.sh, make et make install ."
#: C/jhbuild.xml:2587(para)
msgid ""
"The autogen-sh attribute specifies "
"the name of the autogen.sh script to run. The value autoreconf can be used if your module has no autogen.sh "
"script equivalent. In that case, JHBuild will run autoreconf -i, followed by the proper configure . skip-autogen chooses whether or not to run "
"autogen.sh, it is a boolean with an extra never value to "
"tell JHBuild to never skip running autogen.sh . makefile specifies the filename of the "
"makefile to use."
msgstr ""
"L'attribut autogen-sh indique le nom "
"du script autogen.sh à exécuter. La valeur autoreconf "
"peut être utilisée si le module n'a pas d'équivalent du script "
"autogen.sh . Dans ce cas, JHBuild exécutera "
"autoreconf -i , suivi par la phase configure. L'attribut skip-autogen "
"indique s'il faut exécuter autogen.sh, il s'agit d'une valeur booléenne "
"admettant également la valeur never pour signifier à "
"JHBuild de ne jamais ignorer le lancement de autogen.sh . "
"L'attribut makefile indique le nom du "
"fichier makefile à utiliser."
#: C/jhbuild.xml:2602(para)
msgid ""
"The supports-non-srcdir-builds "
"attribute is used to mark modules that can't be cleanly built using a "
"separate source directory."
msgstr ""
"L'attribut supports-non-srcdir-builds "
"sert à marquer les modules qui ne peuvent être proprement construits en "
"utilisant un répertoire source séparé."
#: C/jhbuild.xml:2607(para)
msgid ""
"The autogen-template attribute can be "
"used if you need finer control over the autogen command line. It is a python "
"format string, which will be substituted with the following variables: "
"srcdir , autogen-sh , prefix, libdir , and autogenargs . For "
"example, here is the default autogen-template:"
msgstr ""
"L'attribut autogen-template peut être "
"utilisé en cas de besoin de contrôle fin sur la ligne de commande autogen. "
"C'est une chaîne de formatage Python, qui sera substituée par les variables "
"suivantes : srcdir , autogen-sh , "
"prefix , libdir , et "
"autogenargs . Par exemple, voici la valeur par défaut de "
"autogen-template :"
#: C/jhbuild.xml:2616(programlisting)
#, no-wrap
msgid ""
"\n"
"%(srcdir)s/%(autogen-sh)s --prefix %(prefix)s --libdir %(libdir)s %(autogenargs)s\n"
msgstr ""
"\n"
"%(srcdir)s/%(autogen-sh)s --prefix %(prefix)s --libdir %(libdir)s %(autogenargs)s\n"
#: C/jhbuild.xml:2620(para)
msgid ""
"The check-target attribute must be "
"specified (with false as value) for modules that do not have a make "
"check target."
msgstr ""
"L'attribut check-target doit être "
"indiqué (avec la valeur « false ») pour les modules qui n'ont pas de cible "
"make check ."
#: C/jhbuild.xml:2627(title)
msgid "cmake"
msgstr "cmake"
#: C/jhbuild.xml:2629(para)
msgid ""
"The cmake element is used to define a "
"module which is built using the CMake build system."
msgstr ""
"L'élément cmake permet de définir un "
"module construit à l'aide du système de construction CMake."
#: C/jhbuild.xml:2632(programlisting)
#, no-wrap
msgid ""
"\n"
"<cmake id=\"modulename \">\n"
" <branch [ ... ] >\n"
" [...]\n"
" </branch>\n"
"\n"
" <dependencies>\n"
" <dep package=\"modulename \"/>\n"
" ...\n"
" </dependencies>\n"
" <after>\n"
" <dep package=\"modulename \"/>\n"
" ...\n"
" </after>\n"
"</cmake>\n"
msgstr ""
"\n"
"<cmake id=\"nom_module \">\n"
" <branch [ ... ] >\n"
" [...]\n"
" </branch>\n"
"\n"
" <dependencies>\n"
" <dep package=\"nom_module \"/>\n"
" ...\n"
" </dependencies>\n"
" <after>\n"
" <dep package=\"nom_module \"/>\n"
" ...\n"
" </after>\n"
"</cmake>\n"
#: C/jhbuild.xml:2652(title)
msgid "distutils"
msgstr "distutils"
#: C/jhbuild.xml:2654(para)
msgid ""
"The distutils element is used to define "
"a module which is built using python's distutils"
msgstr ""
"L'élément distutils permet de définir "
"un module construit à l'aide de Python distutils."
#: C/jhbuild.xml:2658(programlisting)
#, no-wrap
msgid ""
"\n"
"<distutils id=\"modulename \"\n"
" [ supports-non-srcdir-builds=\"yes|no \" ]>\n"
" <branch [ ... ] >\n"
" [...]\n"
" </branch>\n"
"\n"
" <dependencies>\n"
" <dep package=\"modulename \"/>\n"
" ...\n"
" </dependencies>\n"
" <after>\n"
" <dep package=\"modulename \"/>\n"
" ...\n"
" </after>\n"
"</distutils>\n"
msgstr ""
"\n"
"<distutils id=\"nom_module \"\n"
" [ supports-non-srcdir-builds=\"yes|no \" ]>\n"
" <branch [ ... ] >\n"
" [...]\n"
" </branch>\n"
"\n"
" <dependencies>\n"
" <dep package=\"nom_module \"/>\n"
" ...\n"
" </dependencies>\n"
" <after>\n"
" <dep package=\"nom_module \"/>\n"
" ...\n"
" </after>\n"
"</distutils>\n"
#: C/jhbuild.xml:2679(title)
msgid "linux"
msgstr "linux"
#: C/jhbuild.xml:2681(para)
msgid ""
"The linux element defines a module used "
"to build a linux kernel. In addition, a separate kernel configuration can be "
"chosen using the kconfig subelement."
msgstr ""
"L'élément linux permet de définir un "
"module utilisé pour construire un noyau linux. De plus, une configuration de "
"noyau séparée peut être choisie en utilisant le sous-élément kconfig ."
#: C/jhbuild.xml:2687(programlisting)
#, no-wrap
msgid ""
"\n"
"<linux id=\"id \"\n"
"\t [ makeargs=\"makeargs \" ]>\n"
"\n"
" <branch [ ... ] >\n"
" [...]\n"
" </branch>\n"
"\n"
" <dependencies>\n"
" <dep package=\"modulename \"/>\n"
" ...\n"
" </dependencies>\n"
" <after>\n"
" <dep package=\"modulename \"/>\n"
" ...\n"
" </after>\n"
"\n"
" <kconfig [ repo=\"repo \" ]\n"
"\t version=\"version \"\n"
"\t [ module=\"module \" ]\n"
"\t [ config=\"config \" ] />\n"
"\n"
"</linux>\n"
msgstr ""
"\n"
"<linux id=\"id \"\n"
"\t [ makeargs=\"paramètres_make \" ]>\n"
"\n"
" <branch [ ... ] >\n"
" [...]\n"
" </branch>\n"
"\n"
" <dependencies>\n"
" <dep package=\"nom_module \"/>\n"
" ...\n"
" </dependencies>\n"
" <after>\n"
" <dep package=\"nom_module \"/>\n"
" ...\n"
" </after>\n"
"\n"
" <kconfig [ repo=\"dépôt \" ]\n"
"\t version=\"version \"\n"
"\t [ module=\"module \" ]\n"
"\t [ config=\"config \" ] />\n"
"\n"
"</linux>\n"
#: C/jhbuild.xml:2715(title)
msgid "perl"
msgstr "perl"
#: C/jhbuild.xml:2717(para)
msgid ""
"The perl element is used to build perl "
"modules."
msgstr ""
"L'élément perl permet de construire des "
"modules Perl."
#: C/jhbuild.xml:2720(para)
msgid ""
"The makeargs attribute is used to "
"specify additional arguments to pass to make ."
msgstr ""
"L'attribut makeargs permet de définir "
"des paramètres supplémentaires à passer à make ."
#: C/jhbuild.xml:2724(programlisting)
#, no-wrap
msgid ""
"\n"
"<perl id=\"modulename \"\n"
"\t [ makeargs=\"makeargs \" ]>\n"
"\n"
" <branch [ ... ] >\n"
" [...]\n"
" </branch>\n"
"\n"
" <dependencies>\n"
" <dep package=\"modulename \"/>\n"
" ...\n"
" </dependencies>\n"
" <after>\n"
" <dep package=\"modulename \"/>\n"
" ...\n"
" </after>\n"
"\n"
"</perl>\n"
msgstr ""
"\n"
"<perl id=\"nom_module \"\n"
"\t [ makeargs=\"paramètres_make \" ]>\n"
"\n"
" <branch [ ... ] >\n"
" [...]\n"
" </branch>\n"
"\n"
" <dependencies>\n"
" <dep package=\"nom_module \"/>\n"
" ...\n"
" </dependencies>\n"
" <after>\n"
" <dep package=\"nom_module \"/>\n"
" ...\n"
" </after>\n"
"\n"
"</perl>\n"
#: C/jhbuild.xml:2746(title)
msgid "waf"
msgstr "waf"
#: C/jhbuild.xml:2748(para)
msgid ""
"The waf element is used to define a "
"module which is built using the Waf build system."
msgstr ""
"L'élément waf permet de définir un "
"module construit à l'aide du système de construction Waf."
#: C/jhbuild.xml:2751(para)
msgid ""
"The waf-command attribute is used to "
"specify the waf command script to use; it defaults to waf ."
msgstr ""
"L'attribut waf-command permet de "
"définir le script de commande waf à utiliser ; la valeur par défaut est "
"waf ."
#: C/jhbuild.xml:2755(programlisting)
#, no-wrap
msgid ""
"\n"
"<waf id=\"modulename \">\n"
"\t [ waf-command=\"waf-command \" ]>\n"
" <branch [ ... ] >\n"
" [...]\n"
" </branch>\n"
"\n"
" <dependencies>\n"
" <dep package=\"modulename \"/>\n"
" ...\n"
" </dependencies>\n"
" <after>\n"
" <dep package=\"modulename \"/>\n"
" ...\n"
" </after>\n"
"</waf>\n"
msgstr ""
"\n"
"<waf id=\"nom_module \">\n"
"\t [ waf-command=\"commande_waf \" ]>\n"
" <branch [ ... ] >\n"
" [...]\n"
" </branch>\n"
"\n"
" <dependencies>\n"
" <dep package=\"nom_module \"/>\n"
" ...\n"
" </dependencies>\n"
" <after>\n"
" <dep package=\"nom_module \"/>\n"
" ...\n"
" </after>\n"
"</waf>\n"
#: C/jhbuild.xml:2776(title)
msgid "Ant"
msgstr "Ant"
#: C/jhbuild.xml:2778(para)
msgid ""
"The ant element is used to define a "
"module which is built using Ant, the Java based build tool."
msgstr ""
"L'élément ant permet de définir un "
"module construit à l'aide de Ant, l'outil de construction basé sur Java."
#: C/jhbuild.xml:2781(programlisting)
#, no-wrap
msgid ""
"\n"
"<ant id=\"modulename \">\n"
" <branch [ ... ] >\n"
" [...]\n"
" </branch>\n"
"\n"
" <dependencies>\n"
" <dep package=\"modulename \"/>\n"
" ...\n"
" </dependencies>\n"
" <after>\n"
" <dep package=\"modulename \"/>\n"
" ...\n"
" </after>\n"
"</ant>\n"
msgstr ""
"\n"
"<ant id=\"nom_module \">\n"
" <branch [ ... ] >\n"
" [...]\n"
" </branch>\n"
"\n"
" <dependencies>\n"
" <dep package=\"nom_module \"/>\n"
" ...\n"
" </dependencies>\n"
" <after>\n"
" <dep package=\"nom_module \"/>\n"
" ...\n"
" </after>\n"
"</ant>\n"
#: C/jhbuild.xml:2799(title)
msgid "Example of a module built with ant"
msgstr "Exemple d'un module construit avec ant"
#: C/jhbuild.xml:2813(title)
msgid "testmodule"
msgstr "testmodule"
#: C/jhbuild.xml:2815(para)
msgid ""
"The testmodule element is used to "
"create a module which runs a suite of tests using LDTP or Dogtail."
msgstr ""
"L'élément testmodule permet de créer un "
"module qui exécute une suite de tests en utilisant LDTP ou Dogtail."
#: C/jhbuild.xml:2819(programlisting)
#, no-wrap
msgid ""
"\n"
"<testmodule id=\"id \"\n"
"\t type=\"type \">\n"
"\n"
" <branch [ ... ] >\n"
" [...]\n"
" </branch>\n"
"\n"
" <dependencies>\n"
" <dep package=\"modulename \"/>\n"
" ...\n"
" </dependencies>\n"
" <after>\n"
" <dep package=\"modulename \"/>\n"
" ...\n"
" </after>\n"
"\n"
" <testedmodules>\n"
" <tested package=\"package \" />\n"
" </testedmodules>\n"
"\n"
"</testmodule>\n"
msgstr ""
"\n"
"<testmodule id=\"id \"\n"
"\t type=\"type \">\n"
"\n"
" <branch [ ... ] >\n"
" [...]\n"
" </branch>\n"
"\n"
" <dependencies>\n"
" <dep package=\"nom_module \"/>\n"
" ...\n"
" </dependencies>\n"
" <after>\n"
" <dep package=\"nom_module \"/>\n"
" ...\n"
" </after>\n"
"\n"
" <testedmodules>\n"
" <tested package=\"paquet \" />\n"
" </testedmodules>\n"
"\n"
"</testmodule>\n"
#: C/jhbuild.xml:2843(para)
msgid ""
"The type attribute gives the type of "
"tests to be run in the module. 'dogtail' uses python to invoke all .py "
"files. 'ldtp' invokes 'ldtprunner run.xml'."
msgstr ""
"L'attribut type indique le type de "
"tests à exécuter dans le module. « dogtail » utilise Python pour appeler tous "
"les fichiers .py. « ldtp » fait appel à « ldtprunner run.xml »."
#: C/jhbuild.xml:2848(para)
msgid ""
"Unless the noxvfb configuration option is set, an Xvfb server is started to "
"run the tests in"
msgstr ""
"Tant que l'option de configuration noxvfb n'est pas définie, un serveur Xvfb "
"est démarré pour y lancer les tests."
#: C/jhbuild.xml:2854(title)
msgid "metamodule"
msgstr "metamodule"
#: C/jhbuild.xml:2856(para)
msgid ""
"The metamodule element defines a module "
"that doesn't actually do anything. The only purpose of a module of this type "
"is its dependencies."
msgstr ""
"L'élément metamodule permet de définir "
"un module qui ne fait vraiment rien. Le seul but d'un tel module est de "
"définir des dépendances."
#: C/jhbuild.xml:2861(para)
msgid ""
"For example, meta-gnome-desktop depends on all the key components of the "
"GNOME desktop, therefore telling JHBuild to install it actually installs the "
"full desktop."
msgstr ""
"Par exemple, meta-gnome-desktop dépend de tous les éléments clés du bureau "
"GNOME. En conséquence, demander à JHBuild de l'installer revient à installer "
"le bureau complet."
#: C/jhbuild.xml:2865(programlisting)
#, no-wrap
msgid ""
"\n"
"<metamodule id=\"modulename \">\n"
" <dependencies>\n"
" <dep package=\"modulename \"/>\n"
" ...\n"
" </dependencies>\n"
" <suggests>\n"
" <dep package=\"modulename \"/>\n"
" ...\n"
" </suggests>\n"
"</metamodule>\n"
msgstr ""
"\n"
"<metamodule id=\"nom_module \">\n"
" <dependencies>\n"
" <dep package=\"nom_module \"/>\n"
" ...\n"
" </dependencies>\n"
" <suggests>\n"
" <dep package=\"nom_module \"/>\n"
" ...\n"
" </suggests>\n"
"</metamodule>\n"
#: C/jhbuild.xml:2877(para)
msgid ""
"The id attribute gives the name of "
"the module. The child elements are handled as for autotools ."
msgstr ""
"L'attribut id donne le nom du module. "
"Les éléments enfants sont traités de la même manière que autotools."
#: C/jhbuild.xml:2886(title)
msgid "Deprecated Elements"
msgstr "Éléments désapprouvés"
#: C/jhbuild.xml:2892(title)
msgid "cvsroot"
msgstr "cvsroot"
#: C/jhbuild.xml:2894(para)
msgid ""
"The cvsroot element is now deprecated - "
"the repository element should be used "
"instead."
msgstr ""
"L'élément cvsroot est maintenant "
"désapprouvé. Il faut utiliser l'élément repository à la place."
#: C/jhbuild.xml:2899(para)
msgid ""
"The cvsroot element is used to describe "
"a CVS repository."
msgstr ""
"L'élément cvsroot permet de décrire un "
"dépôt CVS."
#: C/jhbuild.xml:2902(programlisting)
#, no-wrap
msgid ""
"\n"
" <cvsroot name=\"rootname \"\n"
" [ default=\"yes|no \" ]\n"
" root=\"anon-cvsroot \"\n"
" password=\"anon-password \"/>\n"
msgstr ""
"\n"
" <cvsroot name=\"nom_racine \"\n"
" [ default=\"yes|no \" ]\n"
" root=\"cvsroot_anon \"\n"
" password=\"mot_de_passe_anon \"/>\n"
#: C/jhbuild.xml:2909(para)
msgid ""
"The name attribute should be a unique "
"identifier for the CVS repository."
msgstr ""
"L'attribut name doit être un "
"identifiant unique pour le dépôt CVS."
#: C/jhbuild.xml:2912(para)
msgid ""
"The default attribute says whether "
"this is the default module source for this module set file."
msgstr ""
"L'attribut default indique si cette "
"source de module est la source par défaut pour ce fichier de jeu de modules."
#: C/jhbuild.xml:2916(para)
msgid ""
"The root attribute lists the CVS root "
"used for anonymous access to this repository, and the password attribute gives the password used for "
"anonymous access."
msgstr ""
"L'attribut root contient la racine "
"CVS utilisée pour l'accès anonyme à ce dépôt, et l'attribut password précise le mot de passe utilisé pour "
"l'accès anonyme."
#: C/jhbuild.xml:2924(title)
msgid "svnroot"
msgstr "svnroot"
#: C/jhbuild.xml:2926(para)
msgid ""
"The svnroot element is now deprecated - "
"the repository element should be used "
"instead."
msgstr ""
"L'élément svnroot est maintenant "
"désapprouvé. Il faut utiliser l'élément repository à la place."
#: C/jhbuild.xml:2931(para)
msgid ""
"The svnroot element is used to describe "
"a Subversion repository."
msgstr ""
"L'élément svnroot permet de décrire un "
"dépôt Subversion."
#: C/jhbuild.xml:2934(programlisting)
#, no-wrap
msgid ""
"\n"
" <svnroot name=\"rootname \"\n"
" [ default=\"yes|no \" ]\n"
" href=\"anon-svnroot \"/>\n"
msgstr ""
"\n"
" <svnroot name=\"nom_racine \"\n"
" [ default=\"yes|no \" ]\n"
" href=\"svnroot_anonyme \"/>\n"
#: C/jhbuild.xml:2940(para)
msgid ""
"The name attribute should be a unique "
"identifier for the Subversion repository."
msgstr ""
"L'attribut name doit être un "
"identifiant unique pour le dépôt Subversion."
#: C/jhbuild.xml:2944(para) C/jhbuild.xml:2974(para)
msgid ""
"If default attribute says whether "
"this is the default module source for this module set file."
msgstr ""
"L'attribut default indique si cette "
"source de module est la source par défaut pour ce fichier de jeu de modules."
#: C/jhbuild.xml:2948(para)
msgid ""
"The href attribute lists the base URL "
"for the repository. This will probably be either a http , "
"https or svn URL."
msgstr ""
"L'attribut href contient l'URL de "
"base du dépôt. En général, c'est un URL http , "
"https ou svn ."
#: C/jhbuild.xml:2955(title)
msgid "arch-archive"
msgstr "arch-archive"
#: C/jhbuild.xml:2957(para)
msgid ""
"The arch-archive element is now "
"deprecated - the repository element "
"should be used instead."
msgstr ""
"L'élément arch-archive est maintenant "
"désapprouvé. Il faut utiliser l'élément repository à la place."
#: C/jhbuild.xml:2962(para)
msgid ""
"The arch-archive element is used to "
"describe a GNU Arch archive."
msgstr ""
"L'élément arch-archive permet de "
"décrire une archive GNU Arch."
#: C/jhbuild.xml:2965(programlisting)
#, no-wrap
msgid ""
"\n"
" <arch-archive name=\"archivename \"\n"
" [ default=\"yes|no \" ]\n"
" href=\"mirror-url \"/>\n"
msgstr ""
"\n"
" <arch-archive name=\"nom_archive \"\n"
" [ default=\"yes|no \" ]\n"
" href=\"url_miroir \"/>\n"
#: C/jhbuild.xml:2971(para)
msgid ""
"The name attribute should be the Arch "
"archive name."
msgstr ""
"L'attribut name doit correspondre au "
"nom de l'archive Arch."
#: C/jhbuild.xml:2978(para)
msgid ""
"The href attribute lists a public "
"mirror URL for the archive."
msgstr ""
"L'attribut href contient l'URL d'un "
"miroir public de l'archive."
#: C/jhbuild.xml:2984(title)
msgid "Deprecated Module Types"
msgstr "Types de modules désapprouvés"
#: C/jhbuild.xml:2987(para)
msgid ""
"This section describes deprecated elements, they may still be used in "
"existing module sets but it is advised not to use them anymore."
msgstr ""
"Cette section présente des éléments désapprouvés. Il se peut qu'ils soient "
"encore utilisés dans des jeux de modules existants, mais il est conseillé de "
"ne plus les utiliser."
#: C/jhbuild.xml:2993(title)
msgid "tarball"
msgstr "tarball"
#: C/jhbuild.xml:2996(para)
msgid ""
"This deprecated element is just a thin wrapper around both autotools module type and tarball repository type."
msgstr ""
"Cet élément désapprouvé est une simple couche fine autour du type de module "
"autotools et du type de dépôt tarball ."
#: C/jhbuild.xml:3002(para)
msgid ""
"The tarball element is used to define a "
"module that is to be built from a tarball."
msgstr ""
"L'élément tarball permet de définir un "
"module à construire à partir d'une archive tar."
#: C/jhbuild.xml:3006(programlisting)
#, no-wrap
msgid ""
"\n"
" <tarball id=\"modulename \"\n"
" [ version=\"version \" ]\n"
" [ checkourdir=\"checkoutdir \" ]\n"
" [ autogenargs=\"autogenargs \" ]\n"
" [ makeargs=\"makeargs \" ]\n"
" [ autogen-sh=\"autogen-sh \" ]\n"
" [ supports-non-srcdir-builds=\"yes|no \" ]>\n"
" <source href=\"source-url \"\n"
" [ size=\"source-size \" ]\n"
" [ hash=\"source-algo:source-hash \" ]\n"
" [ md5sum=\"source-md5sum \" ]/>\n"
" <patches>\n"
" <patch file=\"filename \" strip=\"level \"/>\n"
" ...\n"
" </patches>\n"
" <dependencies>\n"
" <dep package=\"modulename \"/>\n"
" ...\n"
" </dependencies>\n"
" <suggests>\n"
" <dep package=\"modulename \"/>\n"
" ...\n"
" </suggests>\n"
" </tarball>\n"
msgstr ""
"\n"
" <tarball id=\"nom_de_module \"\n"
" [ version=\"version \" ]\n"
" [ checkourdir=\"répertoire_extraction \" ]\n"
" [ autogenargs=\"paramètres_autogen \" ]\n"
" [ makeargs=\"paramètres_make \" ]\n"
" [ autogen-sh=\"autogen-sh \" ]\n"
" [ supports-non-srcdir-builds=\"yes|no \" ]>\n"
" <source href=\"url_source \"\n"
" [ size=\"taille_source \" ]\n"
" [ hash=\"algorithme_source:hash_source \" ]\n"
" [ md5sum=\"somme_md5_source \" ]/>\n"
" <patches>\n"
" <patch file=\"nom_de_fichier \" strip=\"niveau \"/>\n"
" ...\n"
" </patches>\n"
" <dependencies>\n"
" <dep package=\"nom_de_module \"/>\n"
" ...\n"
" </dependencies>\n"
" <suggests>\n"
" <dep package=\"nom_de_module \"/>\n"
" ...\n"
" </suggests>\n"
" </tarball>\n"
#: C/jhbuild.xml:3032(para)
msgid ""
"The id and version attributes are used to identify the module."
msgstr ""
"Les attributs id et version sont utilisés pour identifier le module."
#: C/jhbuild.xml:3036(para)
msgid ""
"The source element specifies the file "
"to download and compile. The href "
"attribute is mandatory, while the size and hash , as well as the "
"obsolete md5sum , attributes are "
"optional. If these last two attributes are present, they are used to check "
"that the source package was downloaded correctly."
msgstr ""
"L'élément source indique le fichier à "
"télécharger et compiler. L'attribut href est obligatoire, alors que les attributs size et hash , comme "
"l'attribut obsolète md5sum , sont "
"facultatifs. Si ces deux derniers attributs sont présents, ils sont utilisés "
"pour vérifier que le paquet source a été correctement téléchargé."
#: C/jhbuild.xml:3063(para)
msgid ""
"The other attributes and the dependencies, suggests and after elements are processed as for dependencies , suggests et "
"after sont traités de la même manière "
"que pour , YEAR1, YEAR2
#: C/jhbuild.xml:0(None)
msgid "translator-credits"
msgstr ""
"Claude Paroz , 2008-2010\n"
"Bruno Brouard , 2009"
jhbuild-3.5.91/doc/fr/fr.stamp 0000644 0001750 0001750 00000000000 11743103645 015777 0 ustar 00fred fred 0000000 0000000 jhbuild-3.5.91/doc/sl/ 0000755 0001750 0001750 00000000000 12021725615 014340 5 ustar 00fred fred 0000000 0000000 jhbuild-3.5.91/doc/sl/index.docbook 0000644 0001750 0001750 00000363126 11743103646 017030 0 ustar 00fred fred 0000000 0000000
JHBuild Manual
James
Henstridge
C.J.
Adams-Collier
Frederic
Peters
David
Turner
2004, 2008
James Henstridge
JHBuild Manual v0.5
January 2008
JHBuild Manual v0.1
August 2007
JHBuild is a tool used to build the whole GNOME desktop from the
version control system. JHBuild can also be customized to build other
projects too.
Introduction
JHBuild is a tool designed to ease building collections of source
packages, called modules
. JHBuild uses module
set
files to describe the modules available to build. The
module set
files include dependency information that allows
JHBuild to discover what modules need to be built and in what order.
JHBuild was originally written for building
GNOME , but has since been
extended to be usable with other projects. A module set
file can be hosted on a web server, allowing for build rules independent
of the JHBuild project.
JHBuild can build modules from a variety of sources, including
CVS ,
Subversion ,
Bazaar ,
Darcs ,
Git and
Mercurial
repositories, as well as Tar and Zip archives hosted on web or FTP sites.
JHBuild can build modules using a variety of build systems, including
Autotools, CMake, WAF, Python Distutils and Perl Makefiles.
JHBuild is not intended as a replacement for the distribution's
package management system. Instead, it makes it easy to build software
into a separate install prefix without interfering with the rest of the
system.
Getting Started
JHBuild requires a few set up steps to be run before building
software. JHBuild requires some prerequisite software, and it is necessary
to install prerequisite tools needed to obtain and build the software
modules.
Installing JHBuild
JHBuild requires a Python runtime. Verify Python >= 2.3 is
installed.
The recommended way to download JHBuild is via the version control
system, git . This can be achieved with the following
command. It is recommended to run the command from a new directory where
all source code will be installed, for example,
~/checkout/gnome .
$ git clone git://git.gnome.org/jhbuild
...
$ This will download JHBuild into a new folder named
jhbuild under the current directory. Now to build
and install JHBuild:
$ cd jhbuild
$ ./autogen.sh
...
$ make
...
$ make install
...
$ If gnome-common ,
yelp-tools and
autotools are available,
autogen.sh will configure JHBuild to install via
autotools . If
gnome-common ,
yelp-tools and
autotools are not available,
autogen.sh will configure JHBuild to install via a
plain Makefile. To always use the plain Makefile method pass
--simple-install to autogen.sh .
If the above steps complete successfully, a small shell script
will be installed in ~/.local/bin to start JHBuild.
Add ~/.local/bin to the PATH :
$ PATH=$PATH:~/.local/bin
$ To permanently add ~/.local/bin to the
PATH variable, run the following command:
$ echo PATH=$PATH:~/.local/bin >> ~/.bashrc
$
Before running JHBuild, it is necessary to set up a configuration
file located at ~/.jhbuildrc .
Build Prerequisites
Before any modules can be built, it is necessary to have certain
build tools installed. Common build tools include the GNU Autotools
(autoconf ,
automake , libtool
and gettext ), The GNU Toolchain
(binutils , gcc ,
g++ ), make, pkg-config and Python, depending
on which modules will be built.
JHBuild can check the tools are installed using the
sanitycheck command:
$ jhbuild sanitycheck If this command displays any messages, the errors can be fixed in
one of two ways:
Install the required package from your distribution's
repository. A list of
package
names for different distributions is maintained on the GNOME
wiki. Run the sanitycheck command again after
installing the distribution's packages to ensure the required tools
are present.
Run the bootstrap command to download,
build and install the build prerequisites:
$ jhbuild bootstrap When complete, run the sanitycheck command
to verify the required tools are present.
The bootstrap command does not build all
the package dependencies required by the build tools. If your
distribution does not provide the required packages, they will
need to be built outside of the JHBuild environment.
The build tools dependencies include
m4 , perl and
a C compiler (for example, gcc ).
Using JHBuild
After set up is complete, JHBuild can be used to build software.
To build all the modules selected in the
~/.jhbuildrc file, run the following command:
$ jhbuild build JHBuild will download, configure, compile and install each of the
modules. If an error occurs at any stage, JHBuild will present a menu
asking what to do. The choices include dropping to a shell to fix the
error, rerunning the build from various stages, giving up on the module,
or ignore the error and continue.
Giving up on a module will cause any modules depending on the
module to fail.
Below is an example of the menu displayed:
[1] Rerun phase build
[2] Ignore error and continue to install
[3] Give up on module
[4] Start shell
[5] Reload configuration
[6] Go to phase "wipe directory and start over"
[7] Go to phase "configure"
[8] Go to phase "clean"
[9] Go to phase "distclean"
choice:
It is also possible to build a different set of modules and their
dependencies by passing the module names as arguments to the
build command. For example, to build gtk+:
$ jhbuild build gtk+ If JHBuild is cancelled part way through a build, it is possible
to resume the build at a particular module using the
--start-at option:
$ jhbuild build --start-at=pango To build one or more modules, ignoring their dependencies, JHBuild
provides the buildone command. For the
buildone command to complete successfully, all
dependencies must be previously built and installed or provided by
distribution packages.
$ jhbuild buildone gtk+ When actively developing a module, you are likely in a source
working directory. The make will invoke the build
system and install the module. This will be a key part of your
edit-compile-install-test cycle.
$ jhbuild make If JHBuild is cancelled part way through a build, it is possible
to resume the build at a particular module using the
--start-at option:
To get a list of the modules and dependencies JHBuild will build,
and the order they will be built, use the list
command:
$ jhbuild list To get information about a particular module, use the
info command:
$ jhbuild info gtk+ To download or update all the software sources without building,
use the update command. The update
command provides an opportunity to modify the sources before building
and can be useful if internet bandwidth varies.
$ jhbuild update Later, JHBuild can build everything without downloading or
updating the sources:
$ jhbuild build --no-network To run a particular command with the same environment used by
JHBuild, use the run command:
$ jhbuild run program To start a shell with the same environment used by JHBuild, use
the shell command:
$ jhbuild shell
JHBuild and GNOME
This section provides guidance on building, installing and running
GNOME.
Building GNOME
To build GNOME some development packages are required. This
includes:
DocBook XML DTD and XSLT stylesheets. These need to be
registered in the XML catalog
(/etc/xml/catalog ).
X libraries
libsmbclient from Samba (used for
browsing Windows networks).
libbz2 from bzip2.
libpng , libjpeg
and libtiff (used for image loading).
If installing distribution packages, and if applicable for your
distribution, install the corresponding dev
or
devel
packages. A list of
package
names for different distributions is maintained on the GNOME
wiki.
Running a Single GNOME Application
This section details how to run a single GNOME application. The
application will run within the current desktop environment. To run the
application within the complete JHBuild GNOME see
Launch a JHBuild shell. The JHBuild shell has all the necessary
environment variables set.
$ jhbuild shell Verify the correct application will be run. For example:
$ which gedit
/opt/gnome/bin/geditRun the application:
$ gedit & Alternatively, run the application using the
run command:
$ jhbuild run gedit
Running the GNOME Desktop Environment
Create a new user account to run the JHBuild GNOME. Running
JHBuild GNOME using different user account is recommended to avoid
problems caused by user settings stored in the home directory. This
manual refers to the new account as
gnomedev .
Setup JHBuild on the new
gnomedev account. Copy or
soft-link ~/.jhbuildrc and
~/.local/bin/jhbuild to
gnomedev home directory.
Open a terminal as the user
gnomedev . Permanently add
~/.local/bin to the PATH variable,
run the following command:
$ echo PATH=$PATH:~/.local/bin >> ~/.bashrc Test JHBuild works:
$ jhbuild run pkg-config gtk+-2.0 --modversion
2.20.1
Setup GNOME to run from the display manager
Build and install JHBuild GNOME.
Enable system services. JHBuild GNOME will use the
/usr/bin system D-Bus
daemon and the system services within
/usr/share/dbus-1/system-services/ . JHBuild GNOME
will use the JHBuild session D-Bus daemon
and the services within
/opt/gnome /share/dbus-1/services//opt/gnome with GNOME install
prefix in the command below:
$ rm -rf /opt/gnome /var/run/dbus
$ ln -s /var/run/dbus /opt/gnome /var/run/dbus
$ rm -rf /opt/gnome /var/lib/dbus/machine-id
$ ln -s /var/lib/dbus/machine-id /opt/gnome /var/lib/dbus/machine-id Create a GNOME startup script at
/usr/bin/gnome-jhbuild-session with the
following, replacing /opt/gnome with GNOME
install prefix :
#!/bin/sh
GNOME=/opt/gnome
GDK_USE_XFT=1
XDG_DATA_DIRS=$XDG_DATA_DIRS:$GNOME/share
XDG_CONFIG_DIRS=$XDG_CONFIG_DIRS:$GNOME/etc/xdg
jhbuild run gnome-session
Make the file
/usr/bin/gnome-jhbuild-session executable:
$ chmod a+x /usr/bin/gnome-jhbuild-session To add a new session entry in the display manager, create
/usr/share/xsessions/gnome-jhbuild.desktop and
enter:
[Desktop Entry]
Name=GNOME (JHBuild)
Comment=This session logs you into GNOME testing session
TryExec=/usr/bin/gnome-jhbuild-session
Exec=/usr/bin/gnome-jhbuild-session
Icon=
Type=Application
Restart gdm .
Running GNOME from the display manager
To run the JHBuild GNOME, select the GNOME (JHBuild) session at
the display manager before entering
gnomedev login credentials.
If successful, JHBuild GNOME will be displayed. If unsuccessful, check
the log within the ~gnomedev/.xsession-errors
file.
Buildbot Integration
Coupled with the Buildbot
project, JHBuild can also function as a continuous integration tool. The
Buildbot configuration is used by the GNOME project at
build.gnome.org .
Configuring a Buildbot Slave
A Buildbot slave is a variation of a normal JHBuild installation
that serves the requests of a Buildbot master. It is recommended to set
up JHBuild and complete a build with most modules building successfully
before adding the Buildbot customizations.
Buildbot commands are options to the bot
command. To download and install the extra required software, run the
following command:
$ jhbuild bot --setup Once this step has completed successfully, three new configuration
variables are required in ~/.jhbuildrc .
It is not possible to use an alternate configuration file, the
--file will not
get desired effects.
jhbuildbot_master = 'build.gnome.org:9070'
jhbuildbot_slavename = 'slavename'
jhbuildbot_password = 'password'
jhbuildbot_master is a string specifying the
Buildbot master server; it defaults to
'build.gnome.org:9070' .
jhbuildbot_slavename and
jhbuildbot_password identify the slave on the master
server. Contact the Buildbot master administrators to obtain the slave
name and password.
The administrators of
build.gnome.org can be
reached on the Build
Brigade mailing list .
Command Reference
JHBuild uses a command line syntax similar to tools like CVS:
jhbuild
global-options command command-arguments The global JHBuild options are:
-f , --file
config
Use an alternative configuration file instead of the
default ~/.jhbuildrc .
-m , --moduleset
moduleset
Use a module set other than the module set listed in the
configuration file. This option can be a relative path if the module
set is located in the JHBuild moduleset folder, or an absolute path
if located elsewhere.
--no-interact
Do not prompt the user for any input. This option is useful
if leaving a build unattended, in order to ensure the build is not
interrupted.
Command specific options are listed below.
autobuild
The autobuild command automatically builds the
modules as specified in the configuration file, and then upload the
results to JhAutobuild.
jhbuild autobuild
--autogen
--clean
--distcheck
--skip=module
--start-at=module
--report-url=reporturl
--verbose
The --autogen , --clean ,
--distcheck , --skip and
--start-at options are processed as per the
build
command.
--report-url=reporturl ,
-r reporturl
This option specifies the JhAutobuild URL to report to.
--verbose , -v
If specified, JHBuild's output will be more verbose.
bootstrap
The bootstrap command installs a set of build
utilities required to build most modules (e.g.
autoconf ,
automake , etc).
jhbuild bootstrap
The bootstrap command builds modules using the
same method as the build command, but uses the
bootstrap.modules moduleset.
See the
build
command documentation for available options.
build
The build command builds one or more packages,
including their dependencies.
jhbuild build
--autogen
--clean
--check
--dist
--distcheck
--ignore-suggests
--no-network
--skip=module
--start-at=module
--tags=tags
-D date
--no-xvfb
--try-checkout
--no-poison
--force
--build-optional-modules
--min-age=time
module
If no module names are provided on the command line, the
-c , --clean
Run make clean before building
modules.
--check
Run make check after building modules.
-d , --dist
Run make dist after building modules.
--distcheck
Run make distcheck after building
modules.
--ignore-suggests
Do not build soft dependencies.
-n , --no-network
Do not access the network when building modules. This
will skip download or update stages in a build. If a module can't
be built without network access, the module build will fail.
-s ,
--skip =module,...
Do not build the listed modules. Used to skip the
building of specified dependencies.
--tags =tag,...
Ignore modules that do not match
tag . Modules are automatically
attributed a tag matching the name of the module's module set.
-t ,
--start-at =module
Start at the named module rather than at the beginning of
the list. This option is useful if the build was interrupted.
-D date
If supported by the underlying version control system,
update the source tree to the specified date before building. An
ISO date format is required, e.g. "2009-09-18
02:32Z" .
-x , --no-xvfb
Run graphical tests on the actual X server rather than in
a simulated Xvfb.
-C , --try-checkout
If the build fails, and if supported by the version
control system, force a checkout and run
autogen.sh before retrying the build.
-N , --no-poison
If one or more of a module's dependencies failed, this
option forces JHBuild to try to build the module anyway.
-f , --force
Build the modules even if policy states it is not
required.
--build-optional-modules
Modules listed as optional dependencies, may not be
required to build the module. This option forces JHBuild to build
optional dependencies.
--min-age =time
Skip modules installed more recently than the specified
relative time. The time string format
is a number followed by a unit. The following units are supported:
seconds (s), minutes (m), hours (h) and days (d). For example,
--min-age=2h will skip modules built less than
two hours ago.
make
The make command is for actively developing on
a particular module. It requires the current directory be a source
checkout, and does the equivalent of buildone -nf $(basename
$(pwd)) .
jhbuild make
--clean
--check
--distcheck
--quiet
The options are the same as those available for the
buildone
command.
buildone
The buildone command is similar to
build , but it does not build the dependent modules.
It is useful for rebuilding one or more modules.
jhbuild buildone
--clean
--check
--distcheck
--no-network
-D date
--no-xvfb
--force
--min-age=time
module
The --check , --clean ,
-d , --distcheck ,
--no-network , -D and
-x options are processed as per the
build
command.
At least one module must be listed on the command line.
checkbranches
The checkbranches checks the module's branches
are defined correctly within the version control system and the branches
are consistent with the module set.
jhbuild checkbranches
--branch=branch
--branch =branch ,
-b branch
The branch to check.
$ jhbuild -m gnome-2.20 checkbranches
libgnomecanvas is missing branch definition for gnome-2-20
$
clean
The clean command cleans the build directories
of one or more modules.
jhbuild clean
--skip=module
--start-at=module
If no module names are provided on the command line, the
See the
build
command documentation for a description of available options.
dot
The dot command generates a file describing the
directed graph formed by the dependencies between a set of modules. This
file can then be processed using the
GraphViz software to
produce a diagram.
jhbuild dot
--soft-deps
--clusters
module
If no module names are provided on the command line, the
The --soft-deps option adds dotted lines from the
modules to the soft dependencies. The --clusters option
groups modules from
The output of the dot command can be piped to the dot utility to
generate a PostScript file:
$ jhbuild dot modules | dot -Tps > dependencies.ps Or a PNG image:
$ jhbuild dot modules | dot -Tpng > dependencies.png
Sample JHBuild dot output
gui
The gui command starts a graphical interface to
JHBuild which can be used to select modules to build and change some
options.
jhbuild gui
The graphical interface is rendered using GTK, so extra support
libraries are required.
info
The info command displays information about one
or more modules.
jhbuild info
module
The command displays the module name, type, dependencies,
dependent packages, the source directory, and the time it was last
installed with JHBuild. If available, information specific to the module
type such as the CVS repository or download URL will also be displayed.
If there is no module specified the command will display
information about all the modules defined in the module set.
list
The list command displays the expanded list of
modules the build command would build.
jhbuild list
-a
-r
-s
--start-at=module
--tags=tags
--ignore-suggests
--list-optional-modules
module
If no module names are provided on the command line, the
The --skip , --start-at ,
--tags , and --ignore-suggests options
are processed as per the
build
command.
-a , --all-modules
List all the modules from the module set regardless of
the build dependencies.
-r , --show-revision
If a module is set to a branch, show the branch name with
the module name.
--list-optional-modules
This option forces JHBuild to list optional dependencies.
rdepends
The rdepends command displays the reverse
dependencies of a module.
jhbuild rdepends
module
--dependencies
Show dependency path next to modules.
--direct
Limit display to modules directly depending on specified
module.
run
The run command runs the specified command
using the same environment that JHBuild uses when building modules.
jhbuild run
--in-builddir
--in-checkoutdir
program argument If using JHBuild to build GNOME, this command can be useful in X
startup scripts.
--in-builddir =module
Run the command in the build directory of the specified
module.
--in-checkoutdir =module
Run the command in the source directory of the specified
module.
sanitycheck
The sanitycheck command performs a number of
checks to verify the build environment is okay.
jhbuild sanitycheck
Some of the checks include:
The checkout and install prefixes are writable.
The required build tools are installed.
Some commonly used macros are available in the search paths
of the aclocal commands associated with the
various versions of automake .
The XML catalog contains the DocBook DTD and stylesheets.
shell
The shell command starts the user's shell with
the same environment as JHBuild uses when building modules.
jhbuild shell
This command is equivalent to the following:
$ jhbuild run $SHELL The UNDER_JHBUILD environment variable will be set
to "true" when this shell is active. You can use the presence of that
variable to customize your shell's prompt to indicate that you indeed
are under a jhbuild-controlled shell. For example, you may want to put
this in your .bashrc :
if [ -n "$UNDER_JHBUILD" ]; then
PS1="[jhbuild] $PS1"
fi
This will make your bash shell display
[jhbuild] before your normal prompt, making it easier
to see which shells are under a jhbuild environment.
sysdeps
The sysdeps command displays a list of
dependency modules that are provided by installed system packages.
JHBuild will not build the modules from source if the configuration
variable
partial_build
is True .
The sysdeps command also displays a list of
dependency modules where the installed system packages are too old.
JHBuild will build newer modules from source.
The sysdeps command also displays a list of
dependency modules with no matching system package installed.
jhbuild sysdeps
--install
--install
This option installs system packages which are
dependencies of the moduleset. The system packages are installed
using PackageKit .
<command>sysdeps</command> example
$ jhbuild sysdeps
System installed packages which are new enough:
speex (required=1.2rc1, installed=1.2rc1)
libdiscid (required=0.2.2, installed=0.2.2)
telepathy-farsight (required=0.0.14, installed=0.0.16)
lcms2 (required=2.2, installed=2.2)
...
System installed packages which are too old:
webkitgtk-3.0 (required=1.5.1, installed=1.4.0)
...
No matching system package installed:
libvala-0.14 (required=0.13.1)
...
tinderbox
The tinderbox command is similar to
build , but writes all terminal output to HTML files
suitable for publishing on a website. It can be used to set up systems
similar to Mozilla's Tinderbox, or Debian's Buildd.
jhbuild tinderbox
--clean
--no-network
--output=directory
--skip=module
--start-at=module
-D date
-C
-N
-f
module
The --clean , --no-network ,
--skip , --start-at ,
-D , -C , -N and
-f options are processed as per the
build
command.
-o ,
--output =directory
The directory to write the HTML files.
uninstall
The uninstall command uninstalls one or more
modules.
jhbuild uninstall
module
update
The update command is similar to
build , but only performs the download or update stage
for modules without building them.
jhbuild update
--skip=module
--start-at=module
--tags=tags
--ignore-suggests
-D date
module
The --skip , --start-at ,
--tags , --ignore-suggests and
-D options are processed as per the
build
command.
updateone
The updateone command is similar to
update , but it does not update the dependent modules.
It is useful for updating one or more modules.
jhbuild updateone
-D date
module
The -D option is processed as per the
build
command.
At least one module must be listed on the command line.
Configuration File Reference
The ~/.jhbuildrc file uses standard Python
syntax. The file is run, and the resulting variables defined in the
namespace are used to control how JHBuild acts. A set of default values
are inserted into the namespace before running the user's configuration
file.
Boolean configuration variables are set using syntax as demonstrated
in the following example:
use_local_modulesets = True
String configuration variables are set using syntax as demonstrated
in the following example:
autogenargs = '--disable-static --disable-gtk-doc'
List configuration variables are set using syntax as demonstrated in
the following example:
skip = ['mozilla', 'pulseaudio']
Dictionary configuration variables are set using syntax as
demonstrated in the following example:
repos['git.gnome.org'] = 'ssh://username@git.gnome.org/git/'
Configuration Variables
autogenargs
A string containing arguments passed to the
autogen.sh script of all modules. Can be
overridden for particular modules using the
module_autogenargs dictionary.
branches
A dictionary specifying which branch to use for specific
modules. This is useful if you are making some changes on a branch
of a module and want JHBuild to build that branch instead of the
one listed in the module set.
The definition of branches depends on the module VCS:
CVS: revision. E.g.
'BRANCH-PROJECT-0_8'
Bazaar: URI of module branch. E.g.
'http://bzr.example.net/project/gnome-2-28'
Git: tuple, with first part being an optional
repository (or the None value) and the second part the name of
the branch. E.g. ('git://git.example.net/project',
'gnome-2-28')
Simple example
branches['modulename'] = (None, 'branchname')
Subversion: URI of module branch E.g.
'svn://svn.example.net/project/gnome-2-28'
builddir_pattern
A printf style formatting pattern
used to generate build directory names. This is only used when
using separate source and build trees. The %s
in the format string will be replaced with
checkoutdir . Defaults to
'%s' .
buildroot
A string specifying the parent directory to place build
trees. Defaults to None , which causes builds
to be performed within the source trees.
buildscript
A string specifying which buildscript to use. The
recommended setting is the default, terminal .
In particular, do not set to gtk .
build_policy
A string specifying which modules to build. The three
possible options are all , to build all modules
requested, updated to build only modules which
have changed, or updated-deps to build modules
which have changed or which have dependencies which have changed.
Defaults to updated-deps .
checkoutroot
A string specifying the directory to unpack source trees
to. Unless buildroot is set, builds will occur
in this directory too. Defaults to
~/checkout/gnome .
checkout_mode
A string specifying how the checkout is performed for
directories in version control. Defaults to
update . This can be set per module using
module_checkout_mode . Possible values are
update (update checkout directory),
clobber (wipe out directory before checking out
the sources), export (wipe out directory then
create an unversioned copy of the sources) and
copy (checkout in a directory different from
the one it will build).
copy_dir
A string specifying the directory to copy to, if the copy
checkout_mode is in use. Defaults to the
checkout directory.
cvs_program
A string specifying which program to use for CVS support.
This can be git-cvsimport , or
cvs . Defaults to cvs .
dvcs_mirror_dir
A string specifying a local mirror directory. JHBuild
will create local mirrors of repositories at the specified
directory. The mirrors can be shared by multiple repository
groups, saving space and time because hard-links will be used for
local clones. The commands update and
updateone will create the mirrors and fetch new
commits from the online repositories. This option is only
supported by Git and Bazaar repositories.
installprog
A string specifying a program to use as replacement for
/usr/bin/install . If available, defaults to the
install-check wrapper provided by JHBuild. The
install-check wrapper optimizes header
installation to reduce the time taken for rebuilds.
ignore_suggests
A boolean value specifying whether to ignore soft
dependencies when calculating the dependency tree. Defaults to
False .
interact
A boolean value specifying whether to interact with the
user. Setting this value to False is
equivalent to passing the --no-interact option.
Defaults to True .
makeargs
A string listing additional arguments to be passed to
make . Defaults to '' .
makecheck
A boolean value specifying whether to run make
check after make . Defaults to
False .
makecheck_advisory
A boolean value specifying whether failures when running
make check should be advisory only and not
cause a build failure. Defaults to False .
makeclean
A boolean value specifying whether to run make
clean before make . Defaults to
False .
makedist
A boolean value specifying whether to run make
dist after make . Defaults to
False . This setting is equivalent to passing
the --dist option.
makedistcheck
A boolean value specifying whether to run make
distcheck after make . Defaults to
False . This setting is equivalent to passing
the --distcheck option.
module_autogenargs
A dictionary mapping module names to strings specifying
the arguments to be passed to autogen.sh . The
setting in module_autogenargs is used instead
of the global autogenargs setting. If a
particular module isn't listed in the dictionary, the global
autogenargs will be used.
module_checkout_mode
A dictionary specifying which checkout mode to use for
modules. This overrides the global
checkout_mode setting.
module_makeargs
A dictionary mapping module names to strings specifying
the arguments to pass to make . The setting in
module_makeargs replaces the value of
makeargs . If a particular module isn't listed
in the dictionary, the global makeargs will be
used.
module_makecheck
A dictionary mapping module names to boolean values
specifying whether to run make check after
make . The setting in
module_makecheck replaces the value of
makecheck . If a particular module isn't listed
in the dictionary, the global makecheck will be
used.
module_nopoison
A dictionary mapping module names to boolean values. If a
module is set to True , JHBuild will attempt
to build dependent modules even if the specified module failed.
The setting in module_nopoison replaces the
value of nopoison . If a particular module isn't
listed in the dictionary, the global nopoison
will be used.
A dictionary mapping module names to dictionaries with
extra environment variables to pass when executing commands for
the module.
modules
A list of strings specifying the modules to build. The
list of modules actually built will be recursively expanded to
include all the dependencies unless the
buildone command is used. Defaults to
['meta-gnome-desktop'] .
moduleset
A string or list of strings specifying the name(s) of the
module set(s) to use. This can either be the filename of a
moduleset included with JHBuild (excluding the path and
extension), or a full HTTP URL to an externally managed moduleset.
HTTP URL modulesets are cached locally. If a module with the same
name is present in more than one moduleset, the last set listed
takes priority. Modulesets provided with JHBuild are updated to
match the current GNOME development release.
modulesets_dir
A string specifying the directory containing the
modulesets to use. Defaults to the
modulesets/ directory in JHBuild sources.
nice_build
Run builds under the SCHED_IDLE
priority on Linux, nice on other Unix. This can
dramatically improve desktop interactivity for parallel builds
while having only a negligible impact on build throughput.
nobuild
A boolean value, if set to True
JHBuild will not build modules, but just download and unpack the
sources. The default vale is False .
nonetwork
A boolean value specifying whether to access the network.
This affects checking out or updating CVS modules, downloading
tarballs and updating module sets. Setting this to
True is equivalent to passing the
--no-network option. Defaults to
False .
nonotify
A boolean value specifying whether to emit notifications
using the notification daemon. If set to
False , notifications are emitted. Defaults to
True .
nopoison
A boolean value, if set to True
JHBuild attempts to build modules even if one or more of the
module's dependencies failed to build. This option is equivalent
to the --no-poison argument. The default value is
False .
notrayicon
A boolean value specifying whether to show an icon in the
system tray using Zenity. If set to False ,
notifications are emitted. Defaults to True .
noxvfb
A boolean value, if set to True
JHBuild will run any graphical tests on the real X server, rather
than using Xvfb . This option is equivalent to
passing --no-xvfb . The default value is
False
partial_build
A boolean value, if set to True
JHBuild will not build dependency modules if corresponding system
packages are installed and sufficient version. Defaults to
True .
prefix
A string specifying the prefix to install modules to.
prefix must be an absolute path. This directory
must be writable. Defaults to '/opt/gnome' .
pretty_print
A boolean value specifying whether to pretty format the
subprocess output. Only CVS output supports pretty printing.
Disable if the pretty printing causes problems. Defaults to
True .
print_command_pattern
A string displayed before JHBuild executes a command.
%(command)s in the string will be replaced with
the command about to be executed. %(cwd)s in
the string will be replaced with the current working directory.
Defaults to '%(command)s' .
progress_bar
A boolean value specifying whether to display a progress
bar during True .
quiet_mode
A boolean value, if set to True
disables the output of running commands. Defaults to
False .
repos
A dictionary specifying an alternative repository
location for a particular repository. This configuration variable
is useful to a module developer. By default, JHBuild will check
out code from repositories using an anonymous repository location.
The dictionary keys are short repository names and the values are
the alternative repository location strings. For example:
repos['git.gnome.org'] = 'ssh://username@git.gnome.org/git/'
skip
A list of modules to skip. This --skip
command line option extends the list. This list is empty by
default.
sticky_date
A string if set, and if supported by the underlying
version control system, JHBuild will update the source tree to the
specified date before building. An ISO date format is required,
e.g.
'yyyy -mm -dd ' .
Defaults to None .
svn_program
A string specifying which program to use for subversion
support. This can be svn ,
git-svn or bzr . Defaults to
svn .
tarballdir
A string if set, tarballs will be downloaded to the
specified directory instead of checkoutroot .
This is useful if you have multiple JHBuild environments or
regularly clear out checkoutroot and want to
reduce bandwidth usage.
tinderbox_outputdir
A string specifying the directory to store
jhbuild tinderbox output. This string can be
overridden by the --output option. Defaults to
None , so either the command line option must
be used or this variable must be set in the configuration file.
trycheckout
A boolean value, if set to True
JHBuild will automatically try to solve failures by 1) running
autogen.sh again, and 2) checking out a newer
version of a module from version control. This setting is
equivalent to passing the --try-checkout option.
use_lib64
A boolean value that specifies whether to install
libraries to lib64 directories. If set,
--libdir=\${exec_prefix}/lib64 will be passed
to configure. Defaults to True if running on
x86_64 , ppc64 or
s390x Linux, and False on
other systems.
use_local_modulesets
A boolean value that specifies to use modulesets that
were checked out along the JHBuild source code; instead of
downloading them on-the-fly from GNOME version control system.
Defaults to False .
xvfbargs
A string listing arguments to pass to
Xvfb if running graphical tests.
Other Configuration File Structures
In addition to the above variables, there are other settings that
can be set in the configuration file:
os.environ
A dictionary representing the environment. This environment
is passed to processes that JHBuild spawns.
Some influential environment variables include
CPPFLAGS , CFLAGS ,
INSTALL and LDFLAGS . For example:
os.environ['CFLAGS'] = '-O0 -g'
addpath (envvar ,
pathname )
This will add a directory to the PATH
environment variable. addpath will correctly
handle the case when the environment variable is initially empty
(having a stray colon at the beginning or end of an environment
variable can have unexpected consequences).
addpath has special handling for the
ACLOCAL_FLAGS environment variable, which expects
paths to be listed in the form -I
pathname .
prependpath (envvar ,
pathname )
After processing the configuration file, JHBuild will alter
some paths based on variables such as prefix
(e.g. adding $prefix/bin to the start of
PATH ).
The prependpath function works like
addpath , except that the environment variable
is modified after JHBuild has made its changes to the environment.
Module Set File Syntax
JHBuild uses XML files to describe the dependencies between modules.
A RELAX-NG schema and Document Type Definition are included with JHBuild
in the modulesets/ directory. The RELAX-NG schema can
be used to edit module set files using nxml-mode in
Emacs.
The top-level element in a module set file is
moduleset element. No XML namespace is
used. The elements below the top-level come in three types: module
sources, include statements and module definitions.
Viri modulov
Rather than listing the full location of every module, a number of
"module sources" are listed in the module set, and then referenced by
name in the module definitions. As well as reducing the amount of
redundant information in the module set, it makes it easy for a user to
specify an alternative source for those modules (for CVS and Subversion,
it is common for developers and users to use different repository access
methods).
The repository element is used
to describe all types of repository. The
branch element is used inside module
definition to specify additional settings.
<repository name="name "
type="type "
[ default="default " ]
[ password="password " ]
[ cvsroot="cvsroot " ]
[ archive="archive " ]
[ href="href " ]
[ server="server " ]
[ database="database " ]
[ defbranch="defbranch " ]
[ trunk-template="trunk-template " ]
[ branches-template="branches-template " ]
[ tags-template="tags-template " ]
[ developer-href-example="developer-href-example " ] />
The name attribute is a
unique identifier for the repository.
The default attribute
specifies whether this repository is the default source for this module
set.
The type attribute specifies
the type of repository. It can be one of: bzr ,
cvs , darcs ,
fossil , git ,
hg , mnt , svn ,
tarball . Other attributes depend on the
type , as well as the
branch used inside module
definitions. Those are described below in the repository type
sub-sections.
The developer-href-example
attribute is used to specify the format of the URL for the repository
used by developers. This is informational only.
The branch element is used
inside module definitions.
<branch
[ repo="repository " ]
[ module="module name " ]
[ checkoutdir="checkoutdir " ]
[ revision="revision " ]
[ tag="tag " ]
[ update-new-dirs="update-new-dirs " ]
[ override-checkoutdir="override-checkoutdir " ]
[ subdir="subdir " ]
[ branch="branch " ]
[ version="version " ]
[ size="size " ]
[ source-subdir="source-subdir " ]
[ hash="hash " ]/>
All atributes have sensible defaults and depend on the module and
repository definitions. Common attributes are described here.
The repo attribute is used to
specify non-default repository name.
The module attribute is used
to specify module name to checkout from the repository. Defaults to
module id.
The checkoutdir attribute is
used to specify the checkout directory name. Defaults to module id.
Other attributes are described below
Bazaar
This repository type is used to define a Bazaar repository. It
is recommended to have Bazaar 1.16 or higher.
<repository type="bzr" name="launchpad.net"
href="lp:"/>
Additional attributes are:
trunk-template (defaults to
"%(module)s" ) and
branches-template (defaults to
"%(module)s/%(branch)s "). These attributes are used
to specify templates for constructing URL. A
branch element in the module
definitions can specify branch
and user attributes. These values
will be substitued in the templates. If either of those are defined
branches-template is used,
otherwise trunk-template is used.
This way you can ovveride repository to build modules from your
personal branch or build many modules fron a repository with
non-standard layout.
An addition branch element
accepts revspec attibute to
anchor on a particular revision. Any valid bzr
revspec is accepted, for example date:yesterday,
-5, tag:0.1 to get first revision since yesterday, 5 commits
behind the tip or tag "0.1". See bzr help
revisionspec for all possible values.
For example repository with
template attributes defined:
<repository type="bzr" name="launchpad.net"
href="lp:"
trunk-template="~bzr-pqm/%(module)s/bzr.dev"
branches-template="~bzr-pqm/%(module)s/%(branch)s"/>
Example branch elements for
the above repository:
<branch repo="launchpad.net"
module="bzr"
checkoutdir="bzr-next"/>
<branch repo="launchpad.net"
module="bzr"
branch="2.2"
checkoutdir="bzr-beta"/>
CVS
This repository type is used to define a CVS repository.
The password attribute is
used to specify the password to the repository.
The cvsroot attribute is
used to specify the root of the repository.
<repository type="cvs" name="tango.freedesktop.org"
cvsroot=":pserver:anoncvs@anoncvs.freedesktop.org:/cvs/tango"
password=""/>
Additional attributes are:
revision ,
update-new-dirs and
override-checkoutdir .
DArcs arhiv:
This repository type is used to define a Darcs repository.
<repository type="darcs" name="telepathy.freedesktop.org"
href="http://projects.collabora.co.uk/darcs/telepathy/"/>
Git
This repository type is used to define a Git repository.
<repository type="git" name="git.freedesktop.org"
href="git://anongit.freedesktop.org/git/"/>
It allows the following attributes on the
branch element:
The revision attribute is
used to specify a local or remote-tracking branch to switch to in the
update phase. It defaults to 'master'. It is possible to override this
attribute with the branches configuration variable.
The switch will only be performed, if the current branch is tracking a
remote branch, to not disturb your own work.
The tag attribute is used
to specify a revision to unconditionally check out in the update
phase. It overrides the revision
attribute.
<branch repo="git.freedesktop.org" module="swfdec/swfdec"
checkoutdir="swfdec"
revision="local-or-remote-branch "
tag="tree-ish "/>
Mercurial
This repository type is used to define a Mercurial repository.
<repository type="hg" name="hg.gtk-vnc"
href="http://gtk-vnc.codemonkey.ws/hg/" />
<branch repo="hg.gtk-vnc" module="outgoing.hg" checkoutdir="gtk-vnc"/>
Monotone
This repository type is used to define a Monotone repository.
The server attribute is
used to specify the repository server.
The database attribute is
used to specify the database to use for the repository.
The defbranch attribute is
used specify the branch of the repository to use.
<repository type="mtn" name="pidgin.im"
server="pidgin.im" database="pidgin.im.mtn"
defbranch="im.pidgin.pidgin"/>
Subversion
This repository type is used to define a Subversion repository.
<repository type="svn" name="svn.gnome.org" default="yes"
href="http://svn.gnome.org/svn/"/>
It allows a revision on the
branch element. This attribute
defines the branch to checkout or, if it is a number, a specific
revision to checkout.
<branch revision="gnome-2-20"/>
It is possible to specify custom svn layout
using trunk-template (defaults to
"%(module)s/trunk"),
branches-template (defaults to
"%(module)s/branches/%(branch)s") and
tags-template (defaults to
"%(module)s/tags/%(tag)s")
Tarballs
This repository type is used to define a tarball repository.
<repository type="tarball" name="dbus/dbus-python"
href="http://dbus.freedesktop.org/releases/dbus-python/"/>
It allows the following attributes on the
branch element:
The module attribute
specifies the file to download and compile, the
version attribute specifies the
module version.
The size and
hash , as well as the obsolete
md5sum , attributes are optional.
If these attributes are present, they are used to check that the
source package was downloaded correctly.
Any number of patch elements
may be nested inside the branch
element. These patches are applied, in order, to the source tree after
unpacking. The file attribute
gives the patch filename, and the
strip attribute says how many
levels of directories to prune when applying the patch.
For module sets shipped with JHBuild, the patch files are looked
up in the jhbuild/patches/ directory; for module
sets referred by URI, the patch files are looked for in the same
directory as the moduleset file, or in its
patches/ subdirectory. It is also possible for
the file attribute to specify a
URI, in which case it will be downloaded from that location.
<branch module="dbus-python-0.80.2.tar.gz" version="0.80.2"
repo="dbus/dbus-python"
hash="md5:2807bc85215c995bd595e01edd9d2077" size="453499">
<patch file="dbus-glib-build.patch" strip="1" />
</branch>
A tarball branch element may
also contain quilt elements which
specify nested branch to import.
Including Other Module Sets
JHBuild allows one module set to include the contents of another
by reference using the include
element.
<include href="uri "/>
The href is a URI reference
to the module set to be included, relative to the file containing the
include element.
Only module definitions are imported from the referenced module
set - module sources are not. Multiple levels of includes are allowed,
but include loops are not (there isn't any code to handle loops at the
moment).
Module Definitions
There are various types of module definitions that can be used in
a module set file, and the list can easily be extended. Only the most
common ones will be mentioned here.
They are all basically composed of a
branch element describing how to get
the module and dependencies ,
suggests and
after elements to declare the
dependencies of the module.
Any modules listed in the
dependencies element will be added to
the module list for jhbuild build if it isn't already
included, and make sure the dependent modules are built first.
After generating the modules list, the modules listed in the
suggests element will be used to
further sort the modules list (although it will not pull any additional
modules). This is intended for cases where a module has an optional
dependency on another module.
cmake
The cmake element is used to
define a module which is built using the CMake build system.
<cmake id="modulename ">
<branch [ ... ] >
[...]
</branch>
<dependencies>
<dep package="modulename "/>
...
</dependencies>
<after>
<dep package="modulename "/>
...
</after>
</cmake>
distutils
The distutils element is used
to define a module which is built using python's distutils
<distutils id="modulename "
[ supports-non-srcdir-builds="yes|no " ]>
<branch [ ... ] >
[...]
</branch>
<dependencies>
<dep package="modulename "/>
...
</dependencies>
<after>
<dep package="modulename "/>
...
</after>
</distutils>
linux
The linux element defines a
module used to build a linux kernel. In addition, a separate kernel
configuration can be chosen using the
kconfig subelement.
<linux id="id "
[ makeargs="makeargs " ]>
<branch [ ... ] >
[...]
</branch>
<dependencies>
<dep package="modulename "/>
...
</dependencies>
<after>
<dep package="modulename "/>
...
</after>
<kconfig [ repo="repo " ]
version="version "
[ module="module " ]
[ config="config " ] />
</linux>
perl
The perl element is used to
build perl modules.
The makeargs attribute is
used to specify additional arguments to pass to
make .
<perl id="modulename "
[ makeargs="makeargs " ]>
<branch [ ... ] >
[...]
</branch>
<dependencies>
<dep package="modulename "/>
...
</dependencies>
<after>
<dep package="modulename "/>
...
</after>
</perl>
waf
The waf element is used to
define a module which is built using the Waf build system.
The waf-command attribute
is used to specify the waf command script to use; it defaults to
waf .
<waf id="modulename ">
[ waf-command="waf-command " ]>
<branch [ ... ] >
[...]
</branch>
<dependencies>
<dep package="modulename "/>
...
</dependencies>
<after>
<dep package="modulename "/>
...
</after>
</waf>
testmodule
The testmodule element is
used to create a module which runs a suite of tests using LDTP or
Dogtail.
<testmodule id="id "
type="type ">
<branch [ ... ] >
[...]
</branch>
<dependencies>
<dep package="modulename "/>
...
</dependencies>
<after>
<dep package="modulename "/>
...
</after>
<testedmodules>
<tested package="package " />
</testedmodules>
</testmodule>
The type attribute gives
the type of tests to be run in the module. 'dogtail' uses python to
invoke all .py files. 'ldtp' invokes 'ldtprunner run.xml'.
Unless the noxvfb configuration option is set, an Xvfb server is
started to run the tests in
Deprecated Elements
Viri modulov
cvsroot
The cvsroot element is now
deprecated - the repository
element should be used instead.
The cvsroot element is used
to describe a CVS repository.
<cvsroot name="rootname "
[ default="yes|no " ]
root="anon-cvsroot "
password="anon-password "/>
The name attribute should
be a unique identifier for the CVS repository.
The default attribute
says whether this is the default module source for this module set
file.
The root attribute lists
the CVS root used for anonymous access to this repository, and the
password attribute gives the
password used for anonymous access.
svnroot
The svnroot element is now
deprecated - the repository
element should be used instead.
The svnroot element is used
to describe a Subversion repository.
<svnroot name="rootname "
[ default="yes|no " ]
href="anon-svnroot "/>
The name attribute should
be a unique identifier for the Subversion repository.
If default attribute says
whether this is the default module source for this module set file.
The href attribute lists
the base URL for the repository. This will probably be either a
http , https or
svn URL.
Deprecated Module Types
This section describes deprecated elements, they may still be
used in existing module sets but it is advised not to use them
anymore.
tarball
This deprecated element is just a thin wrapper around both
autotools module type and
tarball repository type.
The tarball element is used
to define a module that is to be built from a tarball.
<tarball id="modulename "
[ version="version " ]
[ checkourdir="checkoutdir " ]
[ autogenargs="autogenargs " ]
[ makeargs="makeargs " ]
[ autogen-sh="autogen-sh " ]
[ supports-non-srcdir-builds="yes|no " ]>
<source href="source-url "
[ size="source-size " ]
[ hash="source-algo:source-hash " ]
[ md5sum="source-md5sum " ]/>
<patches>
<patch file="filename " strip="level "/>
...
</patches>
<dependencies>
<dep package="modulename "/>
...
</dependencies>
<suggests>
<dep package="modulename "/>
...
</suggests>
</tarball>
The id and
version attributes are used to
identify the module.
The source element
specifies the file to download and compile. The
href attribute is mandatory,
while the size and
hash , as well as the obsolete
md5sum , attributes are
optional. If these last two attributes are present, they are used to
check that the source package was downloaded correctly.
The patches element is used
to specify one or more patches to apply to the source tree after
unpacking, the file attribute
gives the patch filename, and the
strip attribute says how many
levels of directories to prune when applying the patch.
For module sets shipped with JHBuild, the patch files are
looked up in the jhbuild/patches/ directory;
for module sets referred by URI, the patch files are looked for in
the same directory as the moduleset file, or in its
patches/ subdirectory. It is also possible for
the file attribute to specify a
URI, in which case it will be downloaded from that location.
The other attributes and the
dependencies ,
suggests and
after elements are processed as
for
jhbuild-3.5.91/doc/sl/sl.stamp 0000644 0001750 0001750 00000000000 11743103646 016016 0 ustar 00fred fred 0000000 0000000 jhbuild-3.5.91/doc/sl/sl.po 0000644 0001750 0001750 00000404452 11757765667 015361 0 ustar 00fred fred 0000000 0000000 # Copyright (C) 2010 jhbuild's COPYRIGHT HOLDER
# This file is distributed under the same license as the jhbuild package.
#
# Matej Urbančič , 2010.
#
msgid ""
msgstr ""
"Project-Id-Version: jhbuild-help master\n"
"POT-Creation-Date: 2012-05-17 11:56+0000\n"
"PO-Revision-Date: 2012-05-21 21:55+0100\n"
"Last-Translator: filmsi\n"
"Language-Team: Slovenian GNOME Translation Team \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=4; plural=(n%100==1 ? 1 : n%100==2 ? 2 : n%100==3 || n%100==4 ? 3 : 0);\n"
"X-Poedit-Language: Slovenian\n"
"X-Poedit-Country: SLOVENIA\n"
"X-Poedit-SourceCharset: utf-8\n"
#. Put one translator per line, in the form NAME , YEAR1, YEAR2
msgctxt "_"
msgid "translator-credits"
msgstr "Matej Urbančič , 2010"
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#.
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index.docbook:1079(imagedata)
msgctxt "_"
msgid "external ref='figures/jhbuild_sample_dot_output.png' md5='af9fe7edb29fcaefeadfb2f5987aa6e4'"
msgstr "external ref='figures/jhbuild_sample_dot_output.png' md5='af9fe7edb29fcaefeadfb2f5987aa6e4'"
#: C/index.docbook:7(articleinfo/title)
msgid "JHBuild Manual"
msgstr "Priročnik programa JHBuild"
#: C/index.docbook:9(authorgroup/author)
msgid "James Henstridge "
msgstr "James Henstridge "
#: C/index.docbook:13(authorgroup/author)
msgid "C.J. Adams-Collier "
msgstr "C.J. Adams-Collier "
#: C/index.docbook:17(authorgroup/author)
msgid "Frederic Peters "
msgstr "Frederic Peters "
#: C/index.docbook:21(authorgroup/author)
msgid "David Turner "
msgstr "David Turner "
#: C/index.docbook:26(articleinfo/copyright)
msgid "2004, 2008 James Henstridge "
msgstr "2004, 2008 James Henstridge "
#: C/index.docbook:31(revhistory/revision)
msgid "JHBuild Manual v0.5 January 2008 "
msgstr "Priročnik (različica 0.5) za JHBuild - januar 2008 "
#: C/index.docbook:35(revhistory/revision)
msgid "JHBuild Manual v0.1 August 2007 "
msgstr "Priročnik (različica 0.1) za JHBuild - avgust 2007 "
#: C/index.docbook:41(abstract/para)
msgid "JHBuild is a tool used to build the whole GNOME desktop from the version control system. JHBuild can also be customized to build other projects too."
msgstr "JHBuild je orodje za gradnjo celotnega namizja GNOME iz sistema nadzora različic. JHBuild lahko prilagodite tudi za gradnjo drugih projektov."
#: C/index.docbook:48(section/title)
msgid "Introduction"
msgstr "Uvod"
#: C/index.docbook:50(section/para)
msgid "JHBuild is a tool designed to ease building collections of source packages, called modules
. JHBuild uses module set
files to describe the modules available to build. The module set
files include dependency information that allows JHBuild to discover what modules need to be built and in what order."
msgstr ""
#: C/index.docbook:57(section/para)
msgid "JHBuild was originally written for building GNOME , but has since been extended to be usable with other projects. A module set
file can be hosted on a web server, allowing for build rules independent of the JHBuild project."
msgstr "JHBuild je izvorno nastal za izgradnjo okolja GNOME , a je bil odsihmal razširjen na druge projekte. Datoteko nabora modulov
lahko gostite na spletnem strežniku, kar omogoča, da so pravila izgradnje neodvisna od projekta JHBuild."
#: C/index.docbook:63(section/para)
msgid "JHBuild can build modules from a variety of sources, including CVS , Subversion , Bazaar , Darcs , Git and Mercurial repositories, as well as Tar and Zip archives hosted on web or FTP sites. JHBuild can build modules using a variety of build systems, including Autotools, CMake, WAF, Python Distutils and Perl Makefiles."
msgstr ""
#: C/index.docbook:74(section/para)
msgid "JHBuild is not intended as a replacement for the distribution's package management system. Instead, it makes it easy to build software into a separate install prefix without interfering with the rest of the system."
msgstr ""
#: C/index.docbook:81(section/title)
msgid "Getting Started"
msgstr "Prvi koraki"
#: C/index.docbook:83(section/para)
msgid "JHBuild requires a few set up steps to be run before building software. JHBuild requires some prerequisite software, and it is necessary to install prerequisite tools needed to obtain and build the software modules."
msgstr ""
#: C/index.docbook:89(section/title)
msgid "Installing JHBuild"
msgstr "Nameščanje JHBuild"
#: C/index.docbook:91(section/para)
msgid "JHBuild requires a Python runtime. Verify Python >= 2.3 is installed."
msgstr "JHBuild zahteva izvajalno različico Pythona. Preverite, da je nameščen Python >= 2.3."
#: C/index.docbook:94(section/para)
msgid "The recommended way to download JHBuild is via the version control system, git . This can be achieved with the following command. It is recommended to run the command from a new directory where all source code will be installed, for example, ~/checkout/gnome ."
msgstr ""
#: C/index.docbook:100(section/screen)
#, no-wrap
msgid ""
"$ git clone git://git.gnome.org/jhbuild \n"
"... \n"
"$ "
msgstr ""
"$ git clone git://git.gnome.org/jhbuild \n"
"... \n"
"$ "
#: C/index.docbook:104(section/para)
msgid "This will download JHBuild into a new folder named jhbuild under the current directory. Now to build and install JHBuild:"
msgstr "S tem prenesete JHBuild v novo mapo jhbuild pod trenutno mapo. Zdaj pa k izgradnji in namestitvi JHBuild:"
#: C/index.docbook:108(section/screen)
#, no-wrap
msgid ""
"$ cd jhbuild \n"
"$ ./autogen.sh \n"
"... \n"
"$ make \n"
"... \n"
"$ make install \n"
"... \n"
"$ "
msgstr ""
"$ cd jhbuild \n"
"$ ./autogen.sh \n"
"... \n"
"$ make \n"
"... \n"
"$ make install \n"
"... \n"
"$ "
#: C/index.docbook:117(section/para)
msgid "If gnome-common , yelp-tools and autotools are available, autogen.sh will configure JHBuild to install via autotools . If gnome-common , yelp-tools and autotools are not available, autogen.sh will configure JHBuild to install via a plain Makefile. To always use the plain Makefile method pass --simple-install to autogen.sh ."
msgstr ""
#: C/index.docbook:130(section/para)
msgid "If the above steps complete successfully, a small shell script will be installed in ~/.local/bin to start JHBuild. Add ~/.local/bin to the PATH :"
msgstr ""
#: C/index.docbook:134(section/screen)
#, no-wrap
msgid ""
"$ PATH=$PATH:~/.local/bin \n"
"$ "
msgstr ""
"$ PATH=$PATH:~/.local/bin \n"
"$ "
#: C/index.docbook:137(section/para)
msgid "To permanently add ~/.local/bin to the PATH variable, run the following command:"
msgstr ""
#: C/index.docbook:140(section/screen)
#, no-wrap
#| msgid "echo PATH=$PATH:~/.local/bin >> ~/.bashrc"
msgid ""
"\n"
"$ echo PATH=$PATH:~/.local/bin >> ~/.bashrc \n"
"$ "
msgstr ""
"\n"
"$ echo PATH=$PATH:~/.local/bin >> ~/.bashrc \n"
"$ "
#: C/index.docbook:144(section/para)
msgid "Before running JHBuild, it is necessary to set up a configuration file located at ~/.jhbuildrc ."
msgstr "Pred zagonom JHBuild morate nastaviti datoteko prilagoditev, nahaja se v ~/.jhbuildrc ."
#: C/index.docbook:149(section/title)
msgid "Configuring JHBuild"
msgstr "Prilagajanje JHBuild"
#: C/index.docbook:151(section/para)
msgid "The ~/.jhbuildrc file uses Python syntax to set configuration variables for JHBuild. An example is provided with JHBuild, see examples/sample.jhbuildrc . Copy examples/sample.jhbuildrc to ~/.jhbuildrc and customize as required."
msgstr ""
#: C/index.docbook:157(section/para)
msgid "The sample configuration will make JHBuild build the meta-gnome-core and meta-gnome-apps-tested modules and dependencies from the gnome-apps module set. JHBuild will unpack source trees to ~/checkout/gnome and install all files to subdirectories of /opt/gnome . The two directories must be writable."
msgstr ""
#: C/index.docbook:166(section/para)
msgid "Configuration variables are documented in . The most commonly used variables are:"
msgstr "Spremenljivke nastavitev so dokumentirane v . Najpogosteje uporabljene spremenljivke so:"
#: C/index.docbook:173(varlistentry/term)
#, fuzzy
msgid "repos "
msgstr "repos "
#: C/index.docbook:177(listitem/simpara)
msgid "A dictionary that can be used to specify an alternative repository location for a particular repository. This configuration variable is useful to a module developer. By default, JHBuild will check out code from repositories using an anonymous repository location. The dictionary keys are short repository names and the values are alternative repository location strings. For example:"
msgstr ""
#: C/index.docbook:185(listitem/programlisting)
#, no-wrap
msgid "repos['git.gnome.org'] = 'ssh://username @git.gnome.org/git/'"
msgstr "repos['git.gnome.org'] = 'ssh://username @git.gnome.org/git/'"
#: C/index.docbook:189(varlistentry/term)
#, fuzzy
msgid "moduleset "
msgstr "moduleset "
#: C/index.docbook:193(listitem/simpara)
#: C/index.docbook:1859(listitem/simpara)
msgid "A string or list of strings specifying the name(s) of the module set(s) to use. This can either be the filename of a moduleset included with JHBuild (excluding the path and extension), or a full HTTP URL to an externally managed moduleset. HTTP URL modulesets are cached locally. If a module with the same name is present in more than one moduleset, the last set listed takes priority. Modulesets provided with JHBuild are updated to match the current GNOME development release."
msgstr ""
#: C/index.docbook:204(varlistentry/term)
msgid "modules "
msgstr ""
#: C/index.docbook:208(listitem/simpara)
#: C/index.docbook:1846(listitem/simpara)
msgid "A list of strings specifying the modules to build. The list of modules actually built will be recursively expanded to include all the dependencies unless the buildone command is used. Defaults to ['meta-gnome-desktop'] ."
msgstr ""
#: C/index.docbook:217(varlistentry/term)
msgid "checkoutroot "
msgstr ""
#: C/index.docbook:221(listitem/simpara)
msgid "A string specifying the directory to unpack source trees to. Unless buildroot is set, builds will occur in this directory too. Defaults to ~/checkout/gnome ."
msgstr ""
#: C/index.docbook:229(varlistentry/term)
msgid "prefix "
msgstr ""
#: C/index.docbook:233(listitem/simpara)
#: C/index.docbook:1977(listitem/simpara)
msgid "A string specifying the prefix to install modules to. prefix must be an absolute path. This directory must be writable. Defaults to '/opt/gnome' ."
msgstr ""
#: C/index.docbook:240(varlistentry/term)
msgid "autogenargs "
msgstr ""
#: C/index.docbook:244(listitem/simpara)
msgid "A string containing arguments passed to the autogen.sh script of all modules. Can be overridden for particular modules using the module_autogenargs dictionary."
msgstr ""
#: C/index.docbook:252(varlistentry/term)
msgid "makeargs "
msgstr ""
#: C/index.docbook:256(listitem/simpara)
#: C/index.docbook:1709(listitem/simpara)
msgid "A string listing additional arguments to be passed to make . Defaults to '' ."
msgstr ""
#: C/index.docbook:265(section/title)
#, fuzzy
msgid "Build Prerequisites"
msgstr "Mapa za izgradnjo:"
#: C/index.docbook:267(section/para)
msgid "Before any modules can be built, it is necessary to have certain build tools installed. Common build tools include the GNU Autotools (autoconf , automake , libtool and gettext ), The GNU Toolchain (binutils , gcc , g++ ), make, pkg-config and Python, depending on which modules will be built."
msgstr ""
#: C/index.docbook:276(section/para)
msgid "JHBuild can check the tools are installed using the sanitycheck command:"
msgstr ""
#: C/index.docbook:279(section/screen)
#, no-wrap
msgid "$ jhbuild sanitycheck "
msgstr "$ jhbuild sanitycheck "
#: C/index.docbook:281(section/para)
msgid "If this command displays any messages, please install the required package from your distribution's repository. A list of package names for different distributions is maintained on the GNOME wiki. Run the sanitycheck command again after installing the distribution's packages to ensure the required tools are present."
msgstr ""
#: C/index.docbook:291(section/title)
msgid "Using JHBuild"
msgstr "Uporaba JHBuild"
#: C/index.docbook:293(section/para)
msgid "After set up is complete, JHBuild can be used to build software. To build all the modules selected in the ~/.jhbuildrc file, run the following command:"
msgstr ""
#: C/index.docbook:298(section/screen)
#, no-wrap
msgid "$ jhbuild build "
msgstr "$ jhbuild build "
#: C/index.docbook:300(section/para)
msgid "JHBuild will download, configure, compile and install each of the modules. If an error occurs at any stage, JHBuild will present a menu asking what to do. The choices include dropping to a shell to fix the error, rerunning the build from various stages, giving up on the module, or ignore the error and continue."
msgstr ""
#: C/index.docbook:307(note/simpara)
msgid "Giving up on a module will cause any modules depending on the module to fail."
msgstr "Opustitev modula povzroči, da ne bo uspelo pri nobenem modulu, ki je od njega odvisen."
#: C/index.docbook:311(section/para)
msgid "Below is an example of the menu displayed:"
msgstr "Spodaj je primer prikazanega menija:"
#: C/index.docbook:313(section/screen)
#, no-wrap
msgid ""
" [1] Rerun phase build\n"
" [2] Ignore error and continue to install\n"
" [3] Give up on module\n"
" [4] Start shell\n"
" [5] Reload configuration\n"
" [6] Go to phase \"wipe directory and start over\"\n"
" [7] Go to phase \"configure\"\n"
" [8] Go to phase \"clean\"\n"
" [9] Go to phase \"distclean\"\n"
"choice: "
msgstr ""
#: C/index.docbook:324(section/para)
msgid "It is also possible to build a different set of modules and their dependencies by passing the module names as arguments to the build command. For example, to build gtk+:"
msgstr ""
#: C/index.docbook:328(section/screen)
#, no-wrap
msgid "$ jhbuild build gtk+ "
msgstr "$ jhbuild build gtk+ "
#: C/index.docbook:330(section/para)
#: C/index.docbook:351(section/para)
msgid "If JHBuild is cancelled part way through a build, it is possible to resume the build at a particular module using the --start-at option:"
msgstr ""
#: C/index.docbook:334(section/screen)
#, no-wrap
msgid "$ jhbuild build --start-at=pango "
msgstr "$ jhbuild build --start-at=pango "
#: C/index.docbook:336(section/para)
msgid "To build one or more modules, ignoring their dependencies, JHBuild provides the buildone command. For the buildone command to complete successfully, all dependencies must be previously built and installed or provided by distribution packages."
msgstr ""
#: C/index.docbook:342(section/screen)
#, no-wrap
msgid "$ jhbuild buildone gtk+ "
msgstr "$ jhbuild buildone gtk+ "
#: C/index.docbook:344(section/para)
msgid "When actively developing a module, you are likely in a source working directory. The make will invoke the build system and install the module. This will be a key part of your edit-compile-install-test cycle."
msgstr ""
#: C/index.docbook:349(section/screen)
#, no-wrap
msgid "$ jhbuild make "
msgstr "$ jhbuild make "
#: C/index.docbook:355(section/para)
msgid "To get a list of the modules and dependencies JHBuild will build, and the order they will be built, use the list command:"
msgstr ""
#: C/index.docbook:359(section/screen)
#, no-wrap
msgid "$ jhbuild list "
msgstr "$ jhbuild list "
#: C/index.docbook:361(section/para)
msgid "To get information about a particular module, use the info command:"
msgstr "Informacije o določenem modulu pridobite z ukazom info :"
#: C/index.docbook:364(section/screen)
#, no-wrap
msgid "$ jhbuild info gtk+ "
msgstr "$ jhbuild info gtk+ "
#: C/index.docbook:366(section/para)
msgid "To download or update all the software sources without building, use the update command. The update command provides an opportunity to modify the sources before building and can be useful if internet bandwidth varies."
msgstr ""
#: C/index.docbook:371(section/screen)
#, no-wrap
msgid "$ jhbuild update "
msgstr "$ jhbuild update "
#: C/index.docbook:373(section/para)
msgid "Later, JHBuild can build everything without downloading or updating the sources:"
msgstr "Kasneje lahko JHBuild izgradi vse brez prenašanja ali posodabljanja izvorne kode:"
#: C/index.docbook:376(section/screen)
#, no-wrap
msgid "$ jhbuild build --no-network "
msgstr "$ jhbuild build --no-network "
#: C/index.docbook:378(section/para)
msgid "To run a particular command with the same environment used by JHBuild, use the run command:"
msgstr ""
#: C/index.docbook:381(section/screen)
#, no-wrap
msgid "$ jhbuild run program "
msgstr "$ jhbuild run program "
#: C/index.docbook:383(section/para)
msgid "To start a shell with the same environment used by JHBuild, use the shell command:"
msgstr ""
#: C/index.docbook:386(section/screen)
#, no-wrap
msgid "$ jhbuild shell "
msgstr "$ jhbuild shell "
#: C/index.docbook:391(section/title)
msgid "JHBuild and GNOME"
msgstr "JHBuild in GNOME"
#: C/index.docbook:393(section/para)
msgid "This section provides guidance on building, installing and running GNOME."
msgstr "Ta del ponuja napotke za izgradnjo, nameščanje in poganjanje GNOME."
#: C/index.docbook:397(section/title)
msgid "Building GNOME"
msgstr "Gradnja GNOME"
#: C/index.docbook:399(section/para)
msgid "To build GNOME some development packages are required. This includes:"
msgstr "Za izgradnjo GNOME je potrebnih nekaj razvojnih paketov. Slednji so:"
#: C/index.docbook:404(listitem/simpara)
msgid "DocBook XML DTD and XSLT stylesheets. These need to be registered in the XML catalog (/etc/xml/catalog )."
msgstr ""
#: C/index.docbook:409(listitem/simpara)
msgid "X libraries"
msgstr "Knjižnice X"
#: C/index.docbook:412(listitem/simpara)
msgid "libsmbclient from Samba (used for browsing Windows networks)."
msgstr ""
#: C/index.docbook:416(listitem/simpara)
msgid "libbz2 from bzip2."
msgstr "libbz2 iz bzip2."
#: C/index.docbook:419(listitem/simpara)
msgid "libpng , libjpeg and libtiff (used for image loading)."
msgstr "libpng , libjpeg in libtiff (uporabljene za nalaganje slik)."
#: C/index.docbook:424(section/para)
msgid "If installing distribution packages, and if applicable for your distribution, install the corresponding dev
or devel
packages. A list of package names for different distributions is maintained on the GNOME wiki."
msgstr ""
#: C/index.docbook:433(section/title)
msgid "Running a Single GNOME Application"
msgstr "Poganjanje posameznega programa GNOME"
#: C/index.docbook:435(section/para)
msgid "This section details how to run a single GNOME application. The application will run within the current desktop environment. To run the application within the complete JHBuild GNOME see ."
msgstr ""
#: C/index.docbook:440(section/para)
msgid "Launch a JHBuild shell. The JHBuild shell has all the necessary environment variables set."
msgstr ""
#: C/index.docbook:443(section/screen)
#, no-wrap
msgid "$ jhbuild shell "
msgstr "$ jhbuild shell "
#: C/index.docbook:445(section/para)
msgid "Verify the correct application will be run. For example:"
msgstr ""
#: C/index.docbook:447(section/screen)
#, no-wrap
msgid ""
"$ which gedit \n"
"/opt/gnome/bin/gedit"
msgstr ""
"$ which gedit \n"
"/opt/gnome/bin/gedit"
#: C/index.docbook:450(section/para)
msgid "Run the application:"
msgstr "Zaženite program:"
#: C/index.docbook:452(section/screen)
#, no-wrap
msgid "$ gedit & "
msgstr "$ gedit & "
#: C/index.docbook:454(section/para)
msgid "Alternatively, run the application using the run command:"
msgstr ""
#: C/index.docbook:457(section/screen)
#, no-wrap
msgid "$ jhbuild run gedit "
msgstr "$ jhbuild run gedit "
#: C/index.docbook:461(section/title)
msgid "Running the GNOME Desktop Environment"
msgstr "Poganjanje namiznega okolja GNOME"
#: C/index.docbook:463(section/para)
msgid "Create a new user account to run the JHBuild GNOME. Running JHBuild GNOME using different user account is recommended to avoid problems caused by user settings stored in the home directory. This manual refers to the new account as gnomedev ."
msgstr ""
#: C/index.docbook:469(section/para)
msgid "Setup JHBuild on the new gnomedev account. Copy or soft-link ~/.jhbuildrc and ~/.local/bin/jhbuild to gnomedev home directory."
msgstr ""
#: C/index.docbook:476(section/para)
msgid "Open a terminal as the user gnomedev . Permanently add ~/.local/bin to the PATH variable, run the following command:"
msgstr "Odprite terminal kot uporabnik gnomedev . Za stalno dodajte ~/.local/bin spremenljivki PATH , zaženite naslednji ukaz:"
#: C/index.docbook:481(section/screen)
#, no-wrap
#| msgid "echo PATH=$PATH:~/.local/bin >> ~/.bashrc"
msgid "$ echo PATH=$PATH:~/.local/bin >> ~/.bashrc "
msgstr "$ echo PATH=$PATH:~/.local/bin >> ~/.bashrc "
#: C/index.docbook:483(section/para)
msgid "Test JHBuild works:"
msgstr "Preizkusite delovanje JHBuild:"
#: C/index.docbook:485(section/screen)
#, no-wrap
msgid ""
"$ jhbuild run pkg-config gtk+-2.0 --modversion \n"
"2.20.1"
msgstr ""
"$ jhbuild run pkg-config gtk+-2.0 --modversion \n"
"2.20.1"
#: C/index.docbook:489(section/title)
msgid "Setup GNOME to run from the display manager"
msgstr ""
#: C/index.docbook:491(section/para)
msgid "Build and install JHBuild GNOME."
msgstr "Izgradite in namestite JHBuild GNOME."
#: C/index.docbook:493(section/para)
msgid "Enable system services. JHBuild GNOME will use the /usr/bin system D-Bus daemon and the system services within /usr/share/dbus-1/system-services/ . JHBuild GNOME will use the JHBuild session D-Bus daemon and the services within /opt/gnome /share/dbus-1/services//opt/gnome with GNOME install prefix in the command below:"
msgstr ""
#: C/index.docbook:503(section/screen)
#, no-wrap
msgid ""
"$ rm -rf /opt/gnome /var/run/dbus \n"
"$ ln -s /var/run/dbus /opt/gnome /var/run/dbus \n"
"$ rm -rf /opt/gnome /var/lib/dbus/machine-id \n"
"$ ln -s /var/lib/dbus/machine-id /opt/gnome /var/lib/dbus/machine-id "
msgstr ""
"$ rm -rf /opt/gnome /var/run/dbus \n"
"$ ln -s /var/run/dbus /opt/gnome /var/run/dbus \n"
"$ rm -rf /opt/gnome /var/lib/dbus/machine-id \n"
"$ ln -s /var/lib/dbus/machine-id /opt/gnome /var/lib/dbus/machine-id "
#: C/index.docbook:508(section/para)
msgid "Create a GNOME startup script at /usr/bin/gnome-jhbuild-session with the following, replacing /opt/gnome with GNOME install prefix :"
msgstr ""
#: C/index.docbook:513(section/programlisting)
#, no-wrap
msgid ""
"#!/bin/sh\n"
"\n"
"GNOME=/opt/gnome \n"
" \n"
"GDK_USE_XFT=1\n"
"XDG_DATA_DIRS=$XDG_DATA_DIRS:$GNOME/share\n"
"XDG_CONFIG_DIRS=$XDG_CONFIG_DIRS:$GNOME/etc/xdg\n"
"\n"
"jhbuild run gnome-session\n"
msgstr ""
"#!/bin/sh\n"
"\n"
"GNOME=/opt/gnome \n"
" \n"
"GDK_USE_XFT=1\n"
"XDG_DATA_DIRS=$XDG_DATA_DIRS:$GNOME/share\n"
"XDG_CONFIG_DIRS=$XDG_CONFIG_DIRS:$GNOME/etc/xdg\n"
"\n"
"jhbuild run gnome-session\n"
#: C/index.docbook:524(section/para)
msgid "Make the file /usr/bin/gnome-jhbuild-session executable:"
msgstr ""
#: C/index.docbook:527(section/screen)
#, no-wrap
msgid "$ chmod a+x /usr/bin/gnome-jhbuild-session "
msgstr "$ chmod a+x /usr/bin/gnome-jhbuild-session "
#: C/index.docbook:529(section/para)
msgid "To add a new session entry in the display manager, create /usr/share/xsessions/gnome-jhbuild.desktop and enter:"
msgstr ""
#: C/index.docbook:533(section/programlisting)
#, no-wrap
msgid ""
"[Desktop Entry]\n"
"Name=GNOME (JHBuild)\n"
"Comment=This session logs you into GNOME testing session\n"
"TryExec=/usr/bin/gnome-jhbuild-session\n"
"Exec=/usr/bin/gnome-jhbuild-session\n"
"Icon=\n"
"Type=Application"
msgstr ""
#: C/index.docbook:541(section/para)
msgid "Restart gdm ."
msgstr "Ponovno zaženite gdm ."
#: C/index.docbook:547(section/title)
msgid "Running GNOME from the display manager"
msgstr "Poganjanje GNOME z upravljalnika zaslona"
#: C/index.docbook:549(section/para)
msgid "To run the JHBuild GNOME, select the GNOME (JHBuild) session at the display manager before entering gnomedev login credentials. If successful, JHBuild GNOME will be displayed. If unsuccessful, check the log within the ~gnomedev/.xsession-errors file."
msgstr ""
#: C/index.docbook:560(section/title)
#, fuzzy
msgid "Buildbot Integration"
msgstr "vodnik strnjevanja"
#: C/index.docbook:562(section/para)
msgid "Coupled with the Buildbot project, JHBuild can also function as a continuous integration tool. The Buildbot configuration is used by the GNOME project at build.gnome.org ."
msgstr ""
#: C/index.docbook:568(section/title)
msgid "Configuring a Buildbot Slave"
msgstr "Prilagajanje podrejenega strežnika buildbot"
#: C/index.docbook:570(section/para)
msgid "A Buildbot slave is a variation of a normal JHBuild installation that serves the requests of a Buildbot master. It is recommended to set up JHBuild and complete a build with most modules building successfully before adding the Buildbot customizations."
msgstr ""
#: C/index.docbook:575(section/para)
msgid "Buildbot commands are options to the bot command. To download and install the extra required software, run the following command:"
msgstr ""
#: C/index.docbook:579(section/screen)
#, no-wrap
msgid "$ jhbuild bot --setup "
msgstr "$ jhbuild bot --setup "
#: C/index.docbook:581(section/para)
msgid "Once this step has completed successfully, three new configuration variables are required in ~/.jhbuildrc ."
msgstr ""
#: C/index.docbook:585(note/para)
msgid "It is not possible to use an alternate configuration file, the --file will not get desired effects."
msgstr ""
#: C/index.docbook:590(section/programlisting)
#, no-wrap
msgid ""
"\n"
"jhbuildbot_master = 'build.gnome.org:9070'\n"
"jhbuildbot_slavename = 'slavename'\n"
"jhbuildbot_password = 'password'\n"
msgstr ""
#: C/index.docbook:596(section/para)
msgid "jhbuildbot_master is a string specifying the Buildbot master server; it defaults to 'build.gnome.org:9070' . jhbuildbot_slavename and jhbuildbot_password identify the slave on the master server. Contact the Buildbot master administrators to obtain the slave name and password."
msgstr ""
#: C/index.docbook:605(note/para)
msgid "The administrators of build.gnome.org can be reached on the Build Brigade mailing list ."
msgstr "Skrbnike build.gnome.org lahko poiščete na dopisnem seznamu Build Brigade ."
#: C/index.docbook:620(section/title)
#, fuzzy
msgid "Command Reference"
msgstr "_API referenca"
#: C/index.docbook:622(section/para)
msgid "JHBuild uses a command line syntax similar to tools like CVS:"
msgstr "JHBuild uporablja skladnjo ukazne vrstice, podobno kot orodje CVS:"
#: C/index.docbook:624(section/cmdsynopsis)
msgid "jhbuild global-options command command-arguments -f , --file config "
msgstr "-f , --file prilagoditev "
#: C/index.docbook:639(listitem/simpara)
msgid "Use an alternative configuration file instead of the default ~/.jhbuildrc ."
msgstr ""
#: C/index.docbook:644(varlistentry/term)
msgid "-m , --moduleset moduleset "
msgstr "-m , --moduleset nabormodulov "
#: C/index.docbook:649(listitem/simpara)
msgid "Use a module set other than the module set listed in the configuration file. This option can be a relative path if the module set is located in the JHBuild moduleset folder, or an absolute path if located elsewhere."
msgstr ""
#: C/index.docbook:656(varlistentry/term)
msgid "--no-interact "
msgstr "--no-interact "
#: C/index.docbook:660(listitem/simpara)
msgid "Do not prompt the user for any input. This option is useful if leaving a build unattended, in order to ensure the build is not interrupted."
msgstr ""
#: C/index.docbook:667(section/para)
msgid "Command specific options are listed below."
msgstr ""
#: C/index.docbook:670(section/title)
msgid "autobuild"
msgstr ""
#: C/index.docbook:672(section/para)
msgid "The autobuild command automatically builds the modules as specified in the configuration file, and then upload the results to JhAutobuild."
msgstr ""
#: C/index.docbook:676(section/cmdsynopsis)
msgid "jhbuild autobuild --autogen --clean --distcheck --skip=module --start-at=module --report-url=reporturl --verbose "
msgstr ""
#: C/index.docbook:686(section/para)
msgid "The --autogen , --clean , --distcheck , --skip and --start-at options are processed as per the build command."
msgstr ""
#: C/index.docbook:694(varlistentry/term)
msgid "--report-url=reporturl , -r reporturl "
msgstr ""
#: C/index.docbook:699(listitem/simpara)
#, fuzzy
msgid "This option specifies the JhAutobuild URL to report to."
msgstr "Ta možnost določa JhAutoBuild URL, kateremu naj se poroča."
#: C/index.docbook:704(varlistentry/term)
msgid "--verbose , -v "
msgstr "--verbose , -v "
#: C/index.docbook:708(listitem/simpara)
msgid "If specified, JHBuild's output will be more verbose."
msgstr "Če je določeno, bo izhod JHBuild bolj opisen."
#: C/index.docbook:716(section/title)
msgid "bootstrap"
msgstr ""
#: C/index.docbook:718(section/para)
msgid "The bootstrap command installs a set of build utilities. The build utilities include autoconf , automake and similar utilities. The recommended method to install the build utilities is via your distribution's package management system. The bootstrap should only be used if the build utilities are not provided by your distribution's package management system, for example on Mac OS ."
msgstr ""
#: C/index.docbook:727(section/cmdsynopsis)
msgid "jhbuild bootstrap "
msgstr "jhbuild bootstrap "
#: C/index.docbook:730(section/para)
msgid "The bootstrap command builds modules using the same method as the build command, but uses the bootstrap.modules moduleset."
msgstr ""
#: C/index.docbook:734(section/para)
msgid "See the build command documentation for available options."
msgstr ""
#: C/index.docbook:740(section/title)
#, fuzzy
msgid "build"
msgstr "izgradi"
#: C/index.docbook:742(section/para)
msgid "The build command builds one or more packages, including their dependencies."
msgstr "Ukaz build izgradi enega ali več paketov, vključno z odvisnimi paketi."
#: C/index.docbook:745(section/cmdsynopsis)
msgid "jhbuild build --autogen --clean --check --dist --distcheck --ignore-suggests --no-network --skip=module --start-at=module --tags=tags -D date --no-xvfb --try-checkout --no-poison --force --build-optional-modules --min-age=time --nodeps module "
msgstr ""
#: C/index.docbook:767(section/para)
#: C/index.docbook:1031(section/para)
#: C/index.docbook:1055(section/para)
#: C/index.docbook:1137(section/para)
msgid "If no module names are provided on the command line, the -c , --clean "
msgstr "-c , --clean "
#: C/index.docbook:777(listitem/simpara)
msgid "Run make clean before building modules."
msgstr "Pred izgradnjo modulov zaženite make clean ."
#: C/index.docbook:782(varlistentry/term)
msgid "--check "
msgstr "--check "
#: C/index.docbook:786(listitem/simpara)
msgid "Run make check after building modules."
msgstr "Po izgradnji modulov zaženite make check ."
#: C/index.docbook:791(varlistentry/term)
msgid "-d , --dist "
msgstr "-d , --dist "
#: C/index.docbook:795(listitem/simpara)
msgid "Run make dist after building modules."
msgstr "Po izgradnji modulov zaženite make dist ."
#: C/index.docbook:800(varlistentry/term)
msgid "--distcheck "
msgstr "--distcheck "
#: C/index.docbook:804(listitem/simpara)
msgid "Run make distcheck after building modules."
msgstr "Po izgradnji modulov zaženite make distcheck ."
#: C/index.docbook:809(varlistentry/term)
msgid "--ignore-suggests "
msgstr "--ignore-suggests "
#: C/index.docbook:813(listitem/simpara)
msgid "Do not build soft dependencies."
msgstr ""
#: C/index.docbook:817(varlistentry/term)
msgid "-n , --no-network "
msgstr "-n , --no-network "
#: C/index.docbook:821(listitem/simpara)
msgid "Do not access the network when building modules. This will skip download or update stages in a build. If a module can't be built without network access, the module build will fail."
msgstr ""
#: C/index.docbook:828(varlistentry/term)
msgid "-s , --skip =module,... "
msgstr ""
#: C/index.docbook:833(listitem/simpara)
msgid "Do not build the listed modules. Used to skip the building of specified dependencies."
msgstr ""
#: C/index.docbook:838(varlistentry/term)
msgid "--tags =tag,... "
msgstr ""
#: C/index.docbook:842(listitem/simpara)
msgid "Ignore modules that do not match tag . Modules are automatically attributed a tag matching the name of the module's module set."
msgstr ""
#: C/index.docbook:849(varlistentry/term)
msgid "-t , --start-at =module "
msgstr "-t , --start-at =modul "
#: C/index.docbook:854(listitem/simpara)
msgid "Start at the named module rather than at the beginning of the list. This option is useful if the build was interrupted."
msgstr ""
#: C/index.docbook:860(varlistentry/term)
msgid "-D date "
msgstr "-D datum "
#: C/index.docbook:864(listitem/simpara)
msgid "If supported by the underlying version control system, update the source tree to the specified date before building. An ISO date format is required, e.g. \"2009-09-18 02:32Z\" ."
msgstr ""
#: C/index.docbook:871(varlistentry/term)
msgid "-x , --no-xvfb "
msgstr "-x , --no-xvfb "
#: C/index.docbook:875(listitem/simpara)
msgid "Run graphical tests on the actual X server rather than in a simulated Xvfb."
msgstr ""
#: C/index.docbook:880(varlistentry/term)
msgid "-C , --try-checkout "
msgstr "-C , --try-checkout "
#: C/index.docbook:884(listitem/simpara)
msgid "If the build fails, and if supported by the version control system, force a checkout and run autogen.sh before retrying the build."
msgstr ""
#: C/index.docbook:890(varlistentry/term)
msgid "-N , --no-poison "
msgstr "-N , --no-poison "
#: C/index.docbook:894(listitem/simpara)
msgid "If one or more of a module's dependencies failed, this option forces JHBuild to try to build the module anyway."
msgstr ""
#: C/index.docbook:899(varlistentry/term)
msgid "-f , --force "
msgstr "-f , --force "
#: C/index.docbook:903(listitem/simpara)
msgid "Build the modules even if policy states it is not required."
msgstr ""
#: C/index.docbook:908(varlistentry/term)
msgid "--build-optional-modules "
msgstr "--build-optional-modules "
#: C/index.docbook:912(listitem/simpara)
msgid "Modules listed as optional dependencies, may not be required to build the module. This option forces JHBuild to build optional dependencies."
msgstr ""
#: C/index.docbook:918(varlistentry/term)
msgid "--min-age =time "
msgstr "--min-age =čas "
#: C/index.docbook:922(listitem/simpara)
msgid "Skip modules installed more recently than the specified relative time. The time string format is a number followed by a unit. The following units are supported: seconds (s), minutes (m), hours (h) and days (d). For example, --min-age=2h will skip modules built less than two hours ago."
msgstr ""
#: C/index.docbook:931(varlistentry/term)
#| msgid "--direct "
msgid "--nodeps "
msgstr "--nodeps "
#: C/index.docbook:935(listitem/simpara)
msgid "Ignore missing system dependencies."
msgstr ""
#: C/index.docbook:942(section/title)
#, fuzzy
msgid "make"
msgstr "Izvedba"
#: C/index.docbook:944(section/para)
msgid "The make command is for actively developing on a particular module. It requires the current directory be a source checkout, and does the equivalent of buildone -nf $(basename $(pwd)) ."
msgstr ""
#: C/index.docbook:949(section/cmdsynopsis)
msgid "jhbuild make --clean --check --distcheck --quiet "
msgstr ""
#: C/index.docbook:956(section/para)
msgid "The options are the same as those available for the buildone command."
msgstr ""
#: C/index.docbook:963(section/title)
msgid "buildone"
msgstr ""
#: C/index.docbook:965(section/para)
msgid "The buildone command is similar to build , but it does not build the dependent modules. It is useful for rebuilding one or more modules."
msgstr ""
#: C/index.docbook:969(section/cmdsynopsis)
msgid "jhbuild buildone --clean --check --distcheck --no-network -D date --no-xvfb --force --min-age=time --nodeps module "
msgstr ""
#: C/index.docbook:982(section/para)
msgid "The --check , --clean , -d , --distcheck , --no-network , -D , -x and --nodeps options are processed as per the build command."
msgstr ""
#: C/index.docbook:989(section/para)
#: C/index.docbook:1469(section/para)
msgid "At least one module must be listed on the command line."
msgstr ""
#: C/index.docbook:993(section/title)
msgid "checkbranches"
msgstr ""
#: C/index.docbook:995(section/para)
msgid "The checkbranches checks the module's branches are defined correctly within the version control system and the branches are consistent with the module set."
msgstr ""
#: C/index.docbook:999(section/cmdsynopsis)
msgid "jhbuild checkbranches --branch=branch "
msgstr ""
#: C/index.docbook:1005(varlistentry/term)
msgid "--branch =branch , -b branch "
msgstr "--branch =veja , -b veja "
#: C/index.docbook:1010(listitem/simpara)
#, fuzzy
msgid "The branch to check."
msgstr "Preklop na vejo:"
#: C/index.docbook:1015(section/screen)
#, no-wrap
msgid ""
"$ jhbuild -m gnome-2.20 checkbranches \n"
"libgnomecanvas is missing branch definition for gnome-2-20\n"
"$ "
msgstr ""
#: C/index.docbook:1021(section/title)
#, fuzzy
msgid "clean"
msgstr "_Počisti"
#: C/index.docbook:1023(section/para)
msgid "The clean command cleans the build directories of one or more modules."
msgstr ""
#: C/index.docbook:1026(section/cmdsynopsis)
msgid "jhbuild clean --skip=module --start-at=module "
msgstr ""
#: C/index.docbook:1035(section/para)
msgid "See the build command documentation for a description of available options."
msgstr ""
#: C/index.docbook:1041(section/title)
#, fuzzy
msgid "dot"
msgstr "pika"
#: C/index.docbook:1043(section/para)
msgid "The dot command generates a file describing the directed graph formed by the dependencies between a set of modules. This file can then be processed using the GraphViz software to produce a diagram."
msgstr ""
#: C/index.docbook:1049(section/cmdsynopsis)
msgid "jhbuild dot --soft-deps --clusters module "
msgstr ""
#: C/index.docbook:1059(section/para)
msgid "The --soft-deps option adds dotted lines from the modules to the soft dependencies. The --clusters option groups modules from $ jhbuild dot modules | dot -Tps > dependencies.ps "
msgstr ""
#: C/index.docbook:1070(section/para)
msgid "Or a PNG image:"
msgstr "Ali slikovno datoteko PNG:"
#: C/index.docbook:1072(section/screen)
#, no-wrap
msgid "$ jhbuild dot modules | dot -Tpng > dependencies.png "
msgstr ""
#: C/index.docbook:1075(figure/title)
#, fuzzy
msgid "Sample JHBuild dot output"
msgstr "Primer izhoda programa, skripte"
#: C/index.docbook:1087(section/title)
#, fuzzy
msgid "gui"
msgstr "Grafični uporabniški vmesnik"
#: C/index.docbook:1089(section/para)
msgid "The gui command starts a graphical interface to JHBuild which can be used to select modules to build and change some options."
msgstr ""
#: C/index.docbook:1093(section/cmdsynopsis)
msgid "jhbuild gui "
msgstr "jhbuild gui "
#: C/index.docbook:1096(section/para)
msgid "The graphical interface is rendered using GTK, so extra support libraries are required."
msgstr "Grafični vmesnik je upodobljen z GTK, tako da so potrebne posebne podporne knjižnice."
#: C/index.docbook:1101(section/title)
#, fuzzy
msgid "info"
msgstr "INFO"
#: C/index.docbook:1103(section/para)
msgid "The info command displays information about one or more modules."
msgstr ""
#: C/index.docbook:1106(section/cmdsynopsis)
msgid "jhbuild info module "
msgstr ""
#: C/index.docbook:1110(section/para)
msgid "The command displays the module name, type, dependencies, dependent packages, the source directory, and the time it was last installed with JHBuild. If available, information specific to the module type such as the CVS repository or download URL will also be displayed."
msgstr ""
#: C/index.docbook:1116(section/para)
msgid "If there is no module specified the command will display information about all the modules defined in the module set."
msgstr ""
#: C/index.docbook:1121(section/title)
#, fuzzy
msgid "list"
msgstr "seznam"
#: C/index.docbook:1123(section/para)
msgid "The list command displays the expanded list of modules the build command would build."
msgstr ""
#: C/index.docbook:1126(section/cmdsynopsis)
msgid "jhbuild list -a -r -s --start-at=module --tags=tags --ignore-suggests --list-optional-modules module "
msgstr ""
#: C/index.docbook:1141(section/para)
msgid "The --skip , --start-at , --tags , and --ignore-suggests options are processed as per the build command."
msgstr ""
#: C/index.docbook:1149(varlistentry/term)
msgid "-a , --all-modules "
msgstr "-a , --all-modules "
#: C/index.docbook:1153(listitem/simpara)
msgid "List all the modules from the module set regardless of the build dependencies."
msgstr ""
#: C/index.docbook:1158(varlistentry/term)
msgid "-r , --show-revision "
msgstr "-r , --show-revision "
#: C/index.docbook:1162(listitem/simpara)
msgid "If a module is set to a branch, show the branch name with the module name."
msgstr ""
#: C/index.docbook:1167(varlistentry/term)
msgid "--list-optional-modules "
msgstr "--list-optional-modules "
#: C/index.docbook:1171(listitem/simpara)
msgid "This option forces JHBuild to list optional dependencies."
msgstr ""
#: C/index.docbook:1179(section/title)
msgid "rdepends"
msgstr ""
#: C/index.docbook:1181(section/para)
msgid "The rdepends command displays the reverse dependencies of a module."
msgstr ""
#: C/index.docbook:1184(section/cmdsynopsis)
msgid "jhbuild rdepends module "
msgstr "jhbuild rdepends modul "
#: C/index.docbook:1190(varlistentry/term)
msgid "--dependencies "
msgstr "--dependencies "
#: C/index.docbook:1194(listitem/simpara)
msgid "Show dependency path next to modules."
msgstr "Pokaži pot odvisnosti ob modulu."
#: C/index.docbook:1198(varlistentry/term)
msgid "--direct "
msgstr "--direct "
#: C/index.docbook:1202(listitem/simpara)
msgid "Limit display to modules directly depending on specified module."
msgstr "Omeji prikazovanje modulov odvisno od podanega modula."
#: C/index.docbook:1210(section/title)
#, fuzzy
msgid "run"
msgstr "tek"
#: C/index.docbook:1212(section/para)
msgid "The run command runs the specified command using the same environment that JHBuild uses when building modules."
msgstr ""
#: C/index.docbook:1216(section/cmdsynopsis)
msgid "jhbuild run --in-builddir --in-checkoutdir program argument jhbuild run --in-builddir --in-checkoutdir program argument --in-builddir =module "
msgstr "--in-builddir =modul "
#: C/index.docbook:1232(listitem/simpara)
msgid "Run the command in the build directory of the specified module."
msgstr "Zaženi ukaz v mapi za izgradnjo podanega modula."
#: C/index.docbook:1240(varlistentry/term)
msgid "--in-checkoutdir =module "
msgstr "--in-checkoutdir =modul "
#: C/index.docbook:1244(listitem/simpara)
#, fuzzy
msgid "Run the command in the source directory of the specified module."
msgstr "Poženi ukaz v mapi izvorne kode navedenega modula."
#: C/index.docbook:1252(section/title)
msgid "sanitycheck"
msgstr ""
#: C/index.docbook:1254(section/para)
msgid "The sanitycheck command performs a number of checks to verify the build environment is okay."
msgstr ""
#: C/index.docbook:1257(section/cmdsynopsis)
msgid "jhbuild sanitycheck "
msgstr "jhbuild sanitycheck "
#: C/index.docbook:1260(section/para)
#, fuzzy
msgid "Some of the checks include:"
msgstr "Vključi izbrana sporočila"
#: C/index.docbook:1264(listitem/simpara)
msgid "The checkout and install prefixes are writable."
msgstr ""
#: C/index.docbook:1267(listitem/simpara)
msgid "The required build tools are installed."
msgstr "Zahtevana orodja za gradnjo so nameščena."
#: C/index.docbook:1270(listitem/simpara)
msgid "Some commonly used macros are available in the search paths of the aclocal commands associated with the various versions of automake ."
msgstr ""
#: C/index.docbook:1275(listitem/simpara)
msgid "The XML catalog contains the DocBook DTD and stylesheets."
msgstr "Katalog XML vsebuje DTD DocBook in slogovne predloge."
#: C/index.docbook:1282(section/title)
#, fuzzy
msgid "shell"
msgstr "Lupina"
#: C/index.docbook:1284(section/para)
msgid "The shell command starts the user's shell with the same environment as JHBuild uses when building modules."
msgstr ""
#: C/index.docbook:1287(section/cmdsynopsis)
msgid "jhbuild shell "
msgstr "jhbuild shell "
#: C/index.docbook:1290(section/para)
msgid "This command is equivalent to the following:"
msgstr "Ukaz je ekvivalenten naslednjemu:"
#: C/index.docbook:1292(section/screen)
#, no-wrap
msgid "$ jhbuild run $SHELL "
msgstr ""
#: C/index.docbook:1294(section/para)
msgid "The UNDER_JHBUILD environment variable will be set to \"true\" when this shell is active. You can use the presence of that variable to customize your shell's prompt to indicate that you indeed are under a jhbuild-controlled shell. For example, you may want to put this in your .bashrc :"
msgstr ""
#: C/index.docbook:1300(section/screen)
#, no-wrap
msgid ""
"\n"
"\tif [ -n \"$UNDER_JHBUILD\" ]; then\n"
"\t PS1=\"[jhbuild] $PS1\"\n"
"\tfi\n"
" "
msgstr ""
#: C/index.docbook:1306(section/para)
msgid "This will make your bash shell display [jhbuild] before your normal prompt, making it easier to see which shells are under a jhbuild environment."
msgstr ""
#: C/index.docbook:1312(section/title)
msgid "sysdeps"
msgstr ""
#: C/index.docbook:1314(section/para)
#| msgid "sysdeps example"
msgid "The sysdeps command displays:"
msgstr "Ukaz sysdeps izpiše:"
#: C/index.docbook:1318(listitem/simpara)
msgid "a list of installed system packages which will be used during the build. JHBuild will not build these modules and opt to use the system package instead."
msgstr ""
#: C/index.docbook:1323(listitem/simpara)
msgid "a list of required packages. To begin a build the packages must be provided by your system."
msgstr ""
#: C/index.docbook:1327(listitem/simpara)
msgid "a list of optional packages. The corresponding system package was not found or too old. JHBuild will build the module. Optional packages will not be displayed if partial_build is False ."
msgstr ""
#: C/index.docbook:1335(section/cmdsynopsis)
msgid "jhbuild sysdeps --install "
msgstr "jhbuild sysdeps --install "
#: C/index.docbook:1341(varlistentry/term)
msgid "--install "
msgstr "--install "
#: C/index.docbook:1345(listitem/simpara)
msgid "This option installs system packages which are dependencies of the moduleset. The system packages are installed using PackageKit ."
msgstr ""
#: C/index.docbook:1353(example/title)
msgid "sysdeps example"
msgstr "sysdeps example"
#: C/index.docbook:1354(example/screen)
#, no-wrap
msgid ""
"$ jhbuild sysdeps \n"
"System installed packages which are new enough:\n"
" speex (required=1.2rc1, installed=1.2rc1)\n"
" libdiscid (required=0.2.2, installed=0.2.2)\n"
" telepathy-farsight (required=0.0.14, installed=0.0.16)\n"
" lcms2 (required=2.2, installed=2.2)\n"
"...\n"
"Required packages:\n"
" System installed packages which are too old:\n"
" (none)\n"
" No matching system package installed:\n"
" zlib (required=1.2)\n"
"Optional packages: (JHBuild will build the missing packages)\n"
" System installed packages which are too old:\n"
" webkitgtk-3.0 (required=1.5.1, installed=1.4.0)\n"
" ...\n"
" No matching system package installed:\n"
" libvala-0.14 (required=0.13.1)\n"
" ..."
msgstr ""
#: C/index.docbook:1377(section/title)
msgid "tinderbox"
msgstr ""
#: C/index.docbook:1379(section/para)
msgid "The tinderbox command is similar to build , but writes all terminal output to HTML files suitable for publishing on a website. It can be used to set up systems similar to Mozilla's Tinderbox, or Debian's Buildd."
msgstr ""
#: C/index.docbook:1384(section/cmdsynopsis)
msgid "jhbuild tinderbox --clean --no-network --output=directory --skip=module --start-at=module -D date -C -N -f --nodeps module "
msgstr ""
#: C/index.docbook:1398(section/para)
msgid "The --clean , --no-network , --skip , --start-at , -D , -C , -N , -f and --nodeps options are processed as per the build command."
msgstr ""
#: C/index.docbook:1408(varlistentry/term)
msgid "-o , --output =directory "
msgstr "-o , --output =mapa "
#: C/index.docbook:1413(listitem/simpara)
msgid "The directory to write the HTML files."
msgstr "Mapa za pisanje datotek HTML."
#: C/index.docbook:1420(section/title)
#, fuzzy
msgid "uninstall"
msgstr "_Odstrani ..."
#: C/index.docbook:1422(section/para)
msgid "The uninstall command uninstalls one or more modules."
msgstr "Ukaz uninstall odstrani enega ali več modulov."
#: C/index.docbook:1425(section/cmdsynopsis)
msgid "jhbuild uninstall module "
msgstr ""
#: C/index.docbook:1431(section/title)
#, fuzzy
msgid "update"
msgstr "_Posodobi"
#: C/index.docbook:1433(section/para)
msgid "The update command is similar to build , but only performs the download or update stage for modules without building them."
msgstr ""
#: C/index.docbook:1437(section/cmdsynopsis)
msgid "jhbuild update --skip=module --start-at=module --tags=tags --ignore-suggests -D date module "
msgstr ""
#: C/index.docbook:1446(section/para)
msgid "The --skip , --start-at , --tags , --ignore-suggests and -D options are processed as per the build command."
msgstr ""
#: C/index.docbook:1454(section/title)
msgid "updateone"
msgstr ""
#: C/index.docbook:1456(section/para)
msgid "The updateone command is similar to update , but it does not update the dependent modules. It is useful for updating one or more modules."
msgstr ""
#: C/index.docbook:1460(section/cmdsynopsis)
msgid "jhbuild updateone -D date module "
msgstr ""
#: C/index.docbook:1465(section/para)
msgid "The -D option is processed as per the build command."
msgstr ""
#: C/index.docbook:1474(section/title)
#, fuzzy
msgid "Configuration File Reference"
msgstr "Slabo oblikovana namestitvena datoteka"
#: C/index.docbook:1476(section/para)
msgid "The ~/.jhbuildrc file uses standard Python syntax. The file is run, and the resulting variables defined in the namespace are used to control how JHBuild acts. A set of default values are inserted into the namespace before running the user's configuration file."
msgstr ""
#: C/index.docbook:1482(section/para)
msgid "Boolean configuration variables are set using syntax as demonstrated in the following example:"
msgstr ""
#: C/index.docbook:1485(section/programlisting)
#, fuzzy, no-wrap
msgid "use_local_modulesets = True"
msgstr "use_local_modulesets = True"
#: C/index.docbook:1487(section/para)
msgid "String configuration variables are set using syntax as demonstrated in the following example:"
msgstr ""
#: C/index.docbook:1490(section/programlisting)
#, no-wrap
msgid "autogenargs = '--disable-static --disable-gtk-doc'"
msgstr "autogenargs = '--disable-static --disable-gtk-doc'"
#: C/index.docbook:1492(section/para)
msgid "List configuration variables are set using syntax as demonstrated in the following example:"
msgstr ""
#: C/index.docbook:1495(section/programlisting)
#, no-wrap
msgid "skip = ['mozilla', 'pulseaudio']"
msgstr "use_local_modulesets = True"
#: C/index.docbook:1497(section/para)
msgid "Dictionary configuration variables are set using syntax as demonstrated in the following example:"
msgstr ""
#: C/index.docbook:1500(section/programlisting)
#: C/index.docbook:2039(listitem/programlisting)
#, no-wrap
msgid "repos['git.gnome.org'] = 'ssh://username@git.gnome.org/git/'"
msgstr "repos['git.gnome.org'] = 'ssh://uporabniškoime@git.gnome.org/git/'"
#: C/index.docbook:1503(section/title)
#, fuzzy
msgid "Configuration Variables"
msgstr "Okoljske spremenljivke:"
#: C/index.docbook:1508(varlistentry/term)
msgid "autogenargs "
msgstr ""
#: C/index.docbook:1512(listitem/simpara)
msgid "A string containing arguments passed to the autogen.sh script of all modules. Can be overridden for particular modules using the module_autogenargs dictionary."
msgstr ""
#: C/index.docbook:1519(varlistentry/term)
msgid "branches "
msgstr ""
#: C/index.docbook:1523(listitem/simpara)
msgid "A dictionary specifying which branch to use for specific modules. This is useful if you are making some changes on a branch of a module and want JHBuild to build that branch instead of the one listed in the module set."
msgstr ""
#: C/index.docbook:1528(listitem/simpara)
msgid "The definition of branches depends on the module VCS:"
msgstr ""
#: C/index.docbook:1533(listitem/simpara)
msgid "CVS: revision. E.g. 'BRANCH-PROJECT-0_8' "
msgstr ""
#: C/index.docbook:1537(listitem/simpara)
msgid "Bazaar: URI of module branch. E.g. 'http://bzr.example.net/project/gnome-2-28' "
msgstr ""
#: C/index.docbook:1542(listitem/simpara)
msgid "Git: tuple, with first part being an optional repository (or the None value) and the second part the name of the branch. E.g. ('git://git.example.net/project', 'gnome-2-28') "
msgstr ""
#: C/index.docbook:1548(example/title)
msgid "Simple example"
msgstr "Enostaven primer"
#: C/index.docbook:1549(example/programlisting)
#, no-wrap
msgid "branches['modulename'] = (None, 'branchname')"
msgstr ""
#: C/index.docbook:1553(listitem/simpara)
msgid "Subversion: URI of module branch E.g. 'svn://svn.example.net/project/gnome-2-28' "
msgstr ""
#: C/index.docbook:1561(varlistentry/term)
msgid "builddir_pattern "
msgstr "builddir_pattern "
#: C/index.docbook:1565(listitem/simpara)
msgid "A printf style formatting pattern used to generate build directory names. This is only used when using separate source and build trees. The %s in the format string will be replaced with checkoutdir . Defaults to '%s' ."
msgstr ""
#: C/index.docbook:1574(varlistentry/term)
msgid "buildroot "
msgstr ""
#: C/index.docbook:1578(listitem/simpara)
msgid "A string specifying the parent directory to place build trees. Defaults to None , which causes builds to be performed within the source trees."
msgstr ""
#: C/index.docbook:1584(varlistentry/term)
msgid "buildscript "
msgstr ""
#: C/index.docbook:1588(listitem/simpara)
msgid "A string specifying which buildscript to use. The recommended setting is the default, terminal . In particular, do not set to gtk ."
msgstr ""
#: C/index.docbook:1594(varlistentry/term)
msgid "build_policy "
msgstr ""
#: C/index.docbook:1598(listitem/simpara)
msgid "A string specifying which modules to build. The three possible options are all , to build all modules requested, updated to build only modules which have changed, or updated-deps to build modules which have changed or which have dependencies which have changed. Defaults to updated-deps ."
msgstr ""
#: C/index.docbook:1607(varlistentry/term)
msgid "checkoutroot "
msgstr ""
#: C/index.docbook:1611(listitem/simpara)
msgid "A string specifying the directory to unpack source trees to. Unless buildroot is set, builds will occur in this directory too. Defaults to ~/checkout/gnome ."
msgstr ""
#: C/index.docbook:1618(varlistentry/term)
msgid "checkout_mode "
msgstr ""
#: C/index.docbook:1622(listitem/simpara)
msgid "A string specifying how the checkout is performed for directories in version control. Defaults to update . This can be set per module using module_checkout_mode . Possible values are update (update checkout directory), clobber (wipe out directory before checking out the sources), export (wipe out directory then create an unversioned copy of the sources) and copy (checkout in a directory different from the one it will build)."
msgstr ""
#: C/index.docbook:1635(varlistentry/term)
msgid "copy_dir "
msgstr ""
#: C/index.docbook:1639(listitem/simpara)
msgid "A string specifying the directory to copy to, if the copy checkout_mode is in use. Defaults to the checkout directory."
msgstr ""
#: C/index.docbook:1646(varlistentry/term)
msgid "cvs_program "
msgstr ""
#: C/index.docbook:1650(listitem/simpara)
msgid "A string specifying which program to use for CVS support. This can be git-cvsimport , or cvs . Defaults to cvs ."
msgstr ""
#: C/index.docbook:1657(varlistentry/term)
msgid "dvcs_mirror_dir "
msgstr ""
#: C/index.docbook:1661(listitem/simpara)
msgid "A string specifying a local mirror directory. JHBuild will create local mirrors of repositories at the specified directory. The mirrors can be shared by multiple repository groups, saving space and time because hard-links will be used for local clones. The commands update and updateone will create the mirrors and fetch new commits from the online repositories. This option is only supported by Git and Bazaar repositories."
msgstr ""
#: C/index.docbook:1672(varlistentry/term)
msgid "installprog "
msgstr ""
#: C/index.docbook:1676(listitem/simpara)
msgid "A string specifying a program to use as replacement for /usr/bin/install . If available, defaults to the install-check wrapper provided by JHBuild. The install-check wrapper optimizes header installation to reduce the time taken for rebuilds."
msgstr ""
#: C/index.docbook:1684(varlistentry/term)
msgid "ignore_suggests "
msgstr "ignore_suggests "
#: C/index.docbook:1688(listitem/simpara)
msgid "A boolean value specifying whether to ignore soft dependencies when calculating the dependency tree. Defaults to False ."
msgstr ""
#: C/index.docbook:1694(varlistentry/term)
msgid "interact "
msgstr ""
#: C/index.docbook:1698(listitem/simpara)
msgid "A boolean value specifying whether to interact with the user. Setting this value to False is equivalent to passing the --no-interact option. Defaults to True ."
msgstr ""
#: C/index.docbook:1705(varlistentry/term)
msgid "makeargs "
msgstr ""
#: C/index.docbook:1715(varlistentry/term)
msgid "makecheck "
msgstr ""
#: C/index.docbook:1719(listitem/simpara)
msgid "A boolean value specifying whether to run make check after make . Defaults to False ."
msgstr ""
#: C/index.docbook:1725(varlistentry/term)
msgid "makecheck_advisory "
msgstr ""
#: C/index.docbook:1729(listitem/simpara)
msgid "A boolean value specifying whether failures when running make check should be advisory only and not cause a build failure. Defaults to False ."
msgstr ""
#: C/index.docbook:1736(varlistentry/term)
msgid "makeclean "
msgstr ""
#: C/index.docbook:1740(listitem/simpara)
msgid "A boolean value specifying whether to run make clean before make . Defaults to False ."
msgstr ""
#: C/index.docbook:1746(varlistentry/term)
msgid "makedist "
msgstr ""
#: C/index.docbook:1750(listitem/simpara)
msgid "A boolean value specifying whether to run make dist after make . Defaults to False . This setting is equivalent to passing the --dist option."
msgstr ""
#: C/index.docbook:1757(varlistentry/term)
msgid "makedistcheck "
msgstr ""
#: C/index.docbook:1761(listitem/simpara)
msgid "A boolean value specifying whether to run make distcheck after make . Defaults to False . This setting is equivalent to passing the --distcheck option."
msgstr ""
#: C/index.docbook:1768(varlistentry/term)
msgid "module_autogenargs "
msgstr "module_autogenargs "
#: C/index.docbook:1772(listitem/simpara)
msgid "A dictionary mapping module names to strings specifying the arguments to be passed to autogen.sh . The setting in module_autogenargs is used instead of the global autogenargs setting. If a particular module isn't listed in the dictionary, the global autogenargs will be used."
msgstr ""
#: C/index.docbook:1781(varlistentry/term)
msgid "module_checkout_mode "
msgstr "module_checkout_mode "
#: C/index.docbook:1785(listitem/simpara)
msgid "A dictionary specifying which checkout mode to use for modules. This overrides the global checkout_mode setting."
msgstr ""
#: C/index.docbook:1791(varlistentry/term)
msgid "module_makeargs "
msgstr "module_makeargs "
#: C/index.docbook:1795(listitem/simpara)
msgid "A dictionary mapping module names to strings specifying the arguments to pass to make . The setting in module_makeargs replaces the value of makeargs . If a particular module isn't listed in the dictionary, the global makeargs will be used."
msgstr ""
#: C/index.docbook:1804(varlistentry/term)
msgid "module_makecheck "
msgstr "module_makecheck "
#: C/index.docbook:1808(listitem/simpara)
msgid "A dictionary mapping module names to boolean values specifying whether to run make check after make . The setting in module_makecheck replaces the value of makecheck . If a particular module isn't listed in the dictionary, the global makecheck will be used."
msgstr ""
#: C/index.docbook:1818(varlistentry/term)
msgid "module_nopoison "
msgstr "module_nopoison "
#: C/index.docbook:1822(listitem/simpara)
msgid "A dictionary mapping module names to boolean values. If a module is set to True , JHBuild will attempt to build dependent modules even if the specified module failed. The setting in module_nopoison replaces the value of nopoison . If a particular module isn't listed in the dictionary, the global nopoison will be used."
msgstr ""
#: C/index.docbook:1832(varlistentry/term)
msgid "module_extra_env "
msgstr "module_extra_env "
#: C/index.docbook:1836(listitem/simpara)
msgid "A dictionary mapping module names to dictionaries with extra environment variables to pass when executing commands for the module."
msgstr ""
#: C/index.docbook:1842(varlistentry/term)
msgid "modules "
msgstr ""
#: C/index.docbook:1855(varlistentry/term)
msgid "moduleset "
msgstr ""
#: C/index.docbook:1870(varlistentry/term)
msgid "modulesets_dir "
msgstr ""
#: C/index.docbook:1874(listitem/simpara)
msgid "A string specifying the directory containing the modulesets to use. Defaults to the modulesets/ directory in JHBuild sources."
msgstr ""
#: C/index.docbook:1881(varlistentry/term)
msgid "nice_build "
msgstr ""
#: C/index.docbook:1885(listitem/simpara)
msgid "Run builds under the SCHED_IDLE priority on Linux, nice on other Unix. This can dramatically improve desktop interactivity for parallel builds while having only a negligible impact on build throughput."
msgstr ""
#: C/index.docbook:1893(varlistentry/term)
msgid "nobuild "
msgstr ""
#: C/index.docbook:1897(listitem/simpara)
msgid "A boolean value, if set to True JHBuild will not build modules, but just download and unpack the sources. The default vale is False ."
msgstr ""
#: C/index.docbook:1903(varlistentry/term)
msgid "nonetwork "
msgstr ""
#: C/index.docbook:1907(listitem/simpara)
msgid "A boolean value specifying whether to access the network. This affects checking out or updating CVS modules, downloading tarballs and updating module sets. Setting this to True is equivalent to passing the --no-network option. Defaults to False ."
msgstr ""
#: C/index.docbook:1916(varlistentry/term)
msgid "nonotify "
msgstr ""
#: C/index.docbook:1920(listitem/simpara)
msgid "A boolean value specifying whether to emit notifications using the notification daemon. If set to False , notifications are emitted. Defaults to True ."
msgstr ""
#: C/index.docbook:1927(varlistentry/term)
msgid "nopoison "
msgstr ""
#: C/index.docbook:1931(listitem/simpara)
msgid "A boolean value, if set to True JHBuild attempts to build modules even if one or more of the module's dependencies failed to build. This option is equivalent to the --no-poison argument. The default value is False ."
msgstr ""
#: C/index.docbook:1939(varlistentry/term)
msgid "notrayicon "
msgstr ""
#: C/index.docbook:1943(listitem/simpara)
msgid "A boolean value specifying whether to show an icon in the system tray using Zenity. If set to False , notifications are emitted. Defaults to True ."
msgstr ""
#: C/index.docbook:1950(varlistentry/term)
msgid "noxvfb "
msgstr ""
#: C/index.docbook:1954(listitem/simpara)
msgid "A boolean value, if set to True JHBuild will run any graphical tests on the real X server, rather than using Xvfb . This option is equivalent to passing --no-xvfb . The default value is False "
msgstr ""
#: C/index.docbook:1962(varlistentry/term)
msgid "partial_build "
msgstr ""
#: C/index.docbook:1966(listitem/simpara)
msgid "A boolean value, if set to True JHBuild will not build dependency modules if corresponding system packages are installed and sufficient version. Defaults to True ."
msgstr ""
#: C/index.docbook:1973(varlistentry/term)
msgid "prefix "
msgstr ""
#: C/index.docbook:1984(varlistentry/term)
msgid "pretty_print "
msgstr ""
#: C/index.docbook:1988(listitem/simpara)
msgid "A boolean value specifying whether to pretty format the subprocess output. Only CVS output supports pretty printing. Disable if the pretty printing causes problems. Defaults to True ."
msgstr ""
#: C/index.docbook:1995(varlistentry/term)
msgid "print_command_pattern "
msgstr ""
#: C/index.docbook:1999(listitem/simpara)
msgid "A string displayed before JHBuild executes a command. %(command)s in the string will be replaced with the command about to be executed. %(cwd)s in the string will be replaced with the current working directory. Defaults to '%(command)s' ."
msgstr ""
#: C/index.docbook:2007(varlistentry/term)
msgid "progress_bar "
msgstr ""
#: C/index.docbook:2011(listitem/simpara)
msgid "A boolean value specifying whether to display a progress bar during True ."
msgstr ""
#: C/index.docbook:2017(varlistentry/term)
msgid "quiet_mode "
msgstr ""
#: C/index.docbook:2021(listitem/simpara)
msgid "A boolean value, if set to True disables the output of running commands. Defaults to False ."
msgstr ""
#: C/index.docbook:2027(varlistentry/term)
msgid "repos "
msgstr ""
#: C/index.docbook:2031(listitem/simpara)
msgid "A dictionary specifying an alternative repository location for a particular repository. This configuration variable is useful to a module developer. By default, JHBuild will check out code from repositories using an anonymous repository location. The dictionary keys are short repository names and the values are the alternative repository location strings. For example:"
msgstr ""
#: C/index.docbook:2043(varlistentry/term)
msgid "skip "
msgstr ""
#: C/index.docbook:2047(listitem/simpara)
msgid "A list of modules to skip. This --skip command line option extends the list. This list is empty by default."
msgstr ""
#: C/index.docbook:2053(varlistentry/term)
msgid "sticky_date "
msgstr ""
#: C/index.docbook:2057(listitem/simpara)
msgid "A string if set, and if supported by the underlying version control system, JHBuild will update the source tree to the specified date before building. An ISO date format is required, e.g. 'yyyy -mm -dd ' . Defaults to None ."
msgstr ""
#: C/index.docbook:2066(varlistentry/term)
msgid "svn_program "
msgstr ""
#: C/index.docbook:2070(listitem/simpara)
msgid "A string specifying which program to use for subversion support. This can be svn , git-svn or bzr . Defaults to svn ."
msgstr ""
#: C/index.docbook:2077(varlistentry/term)
msgid "tarballdir "
msgstr ""
#: C/index.docbook:2081(listitem/simpara)
msgid "A string if set, tarballs will be downloaded to the specified directory instead of checkoutroot . This is useful if you have multiple JHBuild environments or regularly clear out checkoutroot and want to reduce bandwidth usage."
msgstr ""
#: C/index.docbook:2089(varlistentry/term)
msgid "tinderbox_outputdir "
msgstr ""
#: C/index.docbook:2093(listitem/simpara)
msgid "A string specifying the directory to store jhbuild tinderbox output. This string can be overridden by the --output option. Defaults to None , so either the command line option must be used or this variable must be set in the configuration file."
msgstr ""
#: C/index.docbook:2102(varlistentry/term)
msgid "trycheckout "
msgstr ""
#: C/index.docbook:2106(listitem/simpara)
msgid "A boolean value, if set to True JHBuild will automatically try to solve failures by 1) running autogen.sh again, and 2) checking out a newer version of a module from version control. This setting is equivalent to passing the --try-checkout option."
msgstr ""
#: C/index.docbook:2115(varlistentry/term)
msgid "use_lib64 "
msgstr ""
#: C/index.docbook:2119(listitem/simpara)
msgid "A boolean value that specifies whether to install libraries to lib64 directories. If set, --libdir=\\${exec_prefix}/lib64 will be passed to configure. Defaults to True if running on x86_64 , ppc64 or s390x Linux, and False on other systems."
msgstr ""
#: C/index.docbook:2129(varlistentry/term)
msgid "use_local_modulesets "
msgstr "use_local_modulesets "
#: C/index.docbook:2133(listitem/simpara)
msgid "A boolean value that specifies to use modulesets that were checked out along the JHBuild source code; instead of downloading them on-the-fly from GNOME version control system. Defaults to False ."
msgstr ""
#: C/index.docbook:2140(varlistentry/term)
msgid "xvfbargs "
msgstr ""
#: C/index.docbook:2144(listitem/simpara)
msgid "A string listing arguments to pass to Xvfb if running graphical tests."
msgstr ""
#: C/index.docbook:2152(section/title)
#, fuzzy
msgid "Other Configuration File Structures"
msgstr "ni mogoče prebrati nastavitvene datoteke"
#: C/index.docbook:2154(section/para)
msgid "In addition to the above variables, there are other settings that can be set in the configuration file:"
msgstr ""
#: C/index.docbook:2159(varlistentry/term)
msgid "os.environ "
msgstr ""
#: C/index.docbook:2163(listitem/para)
msgid "A dictionary representing the environment. This environment is passed to processes that JHBuild spawns."
msgstr ""
#: C/index.docbook:2166(listitem/para)
msgid "Some influential environment variables include CPPFLAGS , CFLAGS , INSTALL and LDFLAGS . For example:"
msgstr ""
#: C/index.docbook:2171(listitem/programlisting)
#, no-wrap
msgid "os.environ['CFLAGS'] = '-O0 -g'"
msgstr "os.environ['CFLAGS'] = '-O0 -g'"
#: C/index.docbook:2175(varlistentry/term)
msgid "addpath (envvar , pathname )"
msgstr ""
#: C/index.docbook:2180(listitem/para)
msgid "This will add a directory to the PATH environment variable. addpath will correctly handle the case when the environment variable is initially empty (having a stray colon at the beginning or end of an environment variable can have unexpected consequences)."
msgstr ""
#: C/index.docbook:2186(listitem/para)
msgid "addpath has special handling for the ACLOCAL_FLAGS environment variable, which expects paths to be listed in the form -I pathname ."
msgstr ""
#: C/index.docbook:2193(varlistentry/term)
msgid "prependpath (envvar , pathname )"
msgstr ""
#: C/index.docbook:2198(listitem/para)
msgid "After processing the configuration file, JHBuild will alter some paths based on variables such as prefix (e.g. adding $prefix/bin to the start of PATH )."
msgstr ""
#: C/index.docbook:2203(listitem/para)
msgid "The prependpath function works like addpath , except that the environment variable is modified after JHBuild has made its changes to the environment."
msgstr ""
#: C/index.docbook:2214(section/title)
#, fuzzy
msgid "Module Set File Syntax"
msgstr "Določitev možnosti za filtriranje datotek"
#: C/index.docbook:2216(section/para)
msgid "JHBuild uses XML files to describe the dependencies between modules. A RELAX-NG schema and Document Type Definition are included with JHBuild in the modulesets/ directory. The RELAX-NG schema can be used to edit module set files using nxml-mode in Emacs."
msgstr ""
#: C/index.docbook:2222(section/para)
msgid "The top-level element in a module set file is moduleset element. No XML namespace is used. The elements below the top-level come in three types: module sources, include statements and module definitions."
msgstr ""
#: C/index.docbook:2228(section/title)
#: C/index.docbook:2957(section/title)
msgid "Module Sources"
msgstr "Viri modulov"
#: C/index.docbook:2230(section/para)
msgid "Rather than listing the full location of every module, a number of \"module sources\" are listed in the module set, and then referenced by name in the module definitions. As well as reducing the amount of redundant information in the module set, it makes it easy for a user to specify an alternative source for those modules (for CVS and Subversion, it is common for developers and users to use different repository access methods)."
msgstr ""
#: C/index.docbook:2238(section/para)
msgid "The repository element is used to describe all types of repository. The branch element is used inside module definition to specify additional settings."
msgstr ""
#: C/index.docbook:2243(section/programlisting)
#, no-wrap
msgid ""
"\n"
"<repository name=\"name \"\n"
" type=\"type \"\n"
" [ default=\"default \" ]\n"
" [ password=\"password \" ]\n"
" [ cvsroot=\"cvsroot \" ]\n"
" [ archive=\"archive \" ]\n"
" [ href=\"href \" ]\n"
" [ server=\"server \" ]\n"
" [ database=\"database \" ]\n"
" [ defbranch=\"defbranch \" ]\n"
" [ trunk-template=\"trunk-template \" ]\n"
" [ branches-template=\"branches-template \" ]\n"
" [ tags-template=\"tags-template \" ]\n"
" [ developer-href-example=\"developer-href-example \" ] />\n"
msgstr ""
#: C/index.docbook:2260(section/para)
msgid "The name attribute is a unique identifier for the repository."
msgstr ""
#: C/index.docbook:2263(section/para)
msgid "The default attribute specifies whether this repository is the default source for this module set."
msgstr ""
#: C/index.docbook:2267(section/para)
msgid "The type attribute specifies the type of repository. It can be one of: bzr , cvs , darcs , fossil , git , hg , mnt , svn , tarball . Other attributes depend on the type , as well as the branch used inside module definitions. Those are described below in the repository type sub-sections."
msgstr ""
#: C/index.docbook:2279(section/para)
msgid "The developer-href-example attribute is used to specify the format of the URL for the repository used by developers. This is informational only."
msgstr ""
#: C/index.docbook:2283(section/para)
msgid "The branch element is used inside module definitions."
msgstr ""
#: C/index.docbook:2286(section/programlisting)
#, no-wrap
msgid ""
"\n"
"<branch\n"
" [ repo=\"repository \" ]\n"
" [ module=\"module name \" ]\n"
" [ checkoutdir=\"checkoutdir \" ]\n"
" [ revision=\"revision \" ]\n"
" [ tag=\"tag \" ]\n"
" [ update-new-dirs=\"update-new-dirs \" ]\n"
" [ override-checkoutdir=\"override-checkoutdir \" ]\n"
" [ subdir=\"subdir \" ]\n"
" [ branch=\"branch \" ]\n"
" [ version=\"version \" ]\n"
" [ size=\"size \" ]\n"
" [ source-subdir=\"source-subdir \" ]\n"
" [ hash=\"hash \" ]/>\n"
msgstr ""
#: C/index.docbook:2303(section/para)
msgid "All atributes have sensible defaults and depend on the module and repository definitions. Common attributes are described here."
msgstr ""
#: C/index.docbook:2306(section/para)
msgid "The repo attribute is used to specify non-default repository name."
msgstr ""
#: C/index.docbook:2309(section/para)
msgid "The module attribute is used to specify module name to checkout from the repository. Defaults to module id."
msgstr ""
#: C/index.docbook:2313(section/para)
msgid "The checkoutdir attribute is used to specify the checkout directory name. Defaults to module id."
msgstr ""
#: C/index.docbook:2317(section/para)
msgid "Other attributes are described below"
msgstr "Drugi atributi so opisani spodaj"
#: C/index.docbook:2320(section/title)
msgid "Bazaar"
msgstr "Bazaar"
#: C/index.docbook:2322(section/para)
msgid "This repository type is used to define a Bazaar repository. It is recommended to have Bazaar 1.16 or higher."
msgstr ""
#: C/index.docbook:2325(section/programlisting)
#, no-wrap
#| msgid ""
#| "\n"
#| "<repository type=\"bzr\" name=\"launchpad.net\"\n"
#| " href=\"http://bazaar.launchpad.net/\"/>\n"
msgid ""
"\n"
"<repository type=\"bzr\" name=\"launchpad.net\"\n"
" href=\"lp:\"/>\n"
" "
msgstr ""
"\n"
"<repository type=\"bzr\" name=\"launchpad.net\"\n"
" href=\"lp:\"/>\n"
" "
#: C/index.docbook:2330(section/para)
msgid "Additional attributes are: trunk-template (defaults to \"%(module)s\" ) and branches-template (defaults to \"%(module)s/%(branch)s \"). These attributes are used to specify templates for constructing URL. A branch element in the module definitions can specify branch and user attributes. These values will be substitued in the templates. If either of those are defined branches-template is used, otherwise trunk-template is used. This way you can ovveride repository to build modules from your personal branch or build many modules fron a repository with non-standard layout."
msgstr ""
#: C/index.docbook:2346(section/para)
msgid "An addition branch element accepts revspec attibute to anchor on a particular revision. Any valid bzr revspec is accepted, for example date:yesterday, -5, tag:0.1 to get first revision since yesterday, 5 commits behind the tip or tag \"0.1\". See bzr help revisionspec for all possible values."
msgstr ""
#: C/index.docbook:2354(section/para)
msgid "For example repository with template attributes defined:"
msgstr ""
#: C/index.docbook:2358(section/programlisting)
#, no-wrap
#| msgid ""
#| "\n"
#| "<repository type=\"bzr\" name=\"launchpad.net\"\n"
#| " href=\"http://bazaar.launchpad.net/\"/>\n"
msgid ""
"\n"
"<repository type=\"bzr\" name=\"launchpad.net\"\n"
" href=\"lp:\"\n"
" trunk-template=\"~bzr-pqm/%(module)s/bzr.dev\"\n"
" branches-template=\"~bzr-pqm/%(module)s/%(branch)s\"/>\n"
" "
msgstr ""
"\n"
"<repository type=\"bzr\" name=\"launchpad.net\"\n"
" href=\"lp:\"\n"
" trunk-template=\"~bzr-pqm/%(module)s/bzr.dev\"\n"
" branches-template=\"~bzr-pqm/%(module)s/%(branch)s\"/>\n"
" "
#: C/index.docbook:2365(section/para)
msgid "Example branch elements for the above repository:"
msgstr ""
#: C/index.docbook:2368(section/programlisting)
#, no-wrap
#| msgid ""
#| "\n"
#| "<branch repo=\"hg.gtk-vnc\" module=\"outgoing.hg\" checkoutdir=\"gtk-vnc\"/>\n"
msgid ""
"\n"
"<branch repo=\"launchpad.net\"\n"
" module=\"bzr\"\n"
" checkoutdir=\"bzr-next\"/>\n"
" "
msgstr ""
"\n"
"<branch repo=\"launchpad.net\"\n"
" module=\"bzr\"\n"
" checkoutdir=\"bzr-next\"/>\n"
" "
#: C/index.docbook:2374(section/programlisting)
#, no-wrap
msgid ""
"\n"
"<branch repo=\"launchpad.net\"\n"
" module=\"bzr\"\n"
" branch=\"2.2\"\n"
" checkoutdir=\"bzr-beta\"/>\n"
" "
msgstr ""
"\n"
"<branch repo=\"launchpad.net\"\n"
" module=\"bzr\"\n"
" branch=\"2.2\"\n"
" checkoutdir=\"bzr-beta\"/>\n"
" "
#: C/index.docbook:2383(section/title)
msgid "CVS"
msgstr "CVS"
#: C/index.docbook:2385(section/para)
msgid "This repository type is used to define a CVS repository."
msgstr ""
#: C/index.docbook:2387(section/para)
msgid "The password attribute is used to specify the password to the repository."
msgstr ""
#: C/index.docbook:2390(section/para)
msgid "The cvsroot attribute is used to specify the root of the repository."
msgstr ""
#: C/index.docbook:2393(section/programlisting)
#, no-wrap
#| msgid ""
#| "\n"
#| "<repository type=\"cvs\" name=\"tango.freedesktop.org\"\n"
#| " cvsroot=\":pserver:anoncvs@anoncvs.freedesktop.org:/cvs/tango\"\n"
#| " password=\"\"/>\n"
msgid ""
"\n"
"<repository type=\"cvs\" name=\"tango.freedesktop.org\"\n"
" cvsroot=\":pserver:anoncvs@anoncvs.freedesktop.org:/cvs/tango\"\n"
" password=\"\"/>\n"
" "
msgstr ""
"\n"
"<repository type=\"cvs\" name=\"tango.freedesktop.org\"\n"
" cvsroot=\":pserver:anoncvs@anoncvs.freedesktop.org:/cvs/tango\"\n"
" password=\"\"/>\n"
" "
#: C/index.docbook:2401(section/para)
msgid "Additional attributes are: revision , update-new-dirs and override-checkoutdir ."
msgstr ""
#: C/index.docbook:2408(section/title)
msgid "Darcs"
msgstr "DArcs arhiv:"
#: C/index.docbook:2410(section/para)
msgid "This repository type is used to define a Darcs repository."
msgstr ""
#: C/index.docbook:2413(section/programlisting)
#, no-wrap
msgid ""
"\n"
"<repository type=\"darcs\" name=\"telepathy.freedesktop.org\"\n"
" href=\"http://projects.collabora.co.uk/darcs/telepathy/\"/>\n"
msgstr ""
"\n"
"<repository type=\"darcs\" name=\"telepathy.freedesktop.org\"\n"
" href=\"http://projects.collabora.co.uk/darcs/telepathy/\"/>\n"
#: C/index.docbook:2420(section/title)
msgid "Git"
msgstr "Git"
#: C/index.docbook:2422(section/para)
msgid "This repository type is used to define a Git repository."
msgstr ""
#: C/index.docbook:2424(section/programlisting)
#, no-wrap
#| msgid ""
#| "\n"
#| "<repository type=\"git\" name=\"git.freedesktop.org\"\n"
#| " href=\"git://anongit.freedesktop.org/git/\"/>\n"
msgid ""
"\n"
"<repository type=\"git\" name=\"git.freedesktop.org\"\n"
" href=\"git://anongit.freedesktop.org/git/\"/>\n"
" "
msgstr ""
"\n"
"<repository type=\"git\" name=\"git.freedesktop.org\"\n"
" href=\"git://anongit.freedesktop.org/git/\"/>\n"
" "
#: C/index.docbook:2429(section/para)
#: C/index.docbook:2551(section/para)
msgid "It allows the following attributes on the branch element:"
msgstr ""
#: C/index.docbook:2433(section/para)
msgid "The revision attribute is used to specify a local or remote-tracking branch to switch to in the update phase. It defaults to 'master'. It is possible to override this attribute with the branches configuration variable. The switch will only be performed, if the current branch is tracking a remote branch, to not disturb your own work."
msgstr ""
#: C/index.docbook:2440(section/para)
msgid "The tag attribute is used to specify a revision to unconditionally check out in the update phase. It overrides the revision attribute."
msgstr ""
#: C/index.docbook:2450(section/programlisting)
#, no-wrap
msgid ""
"\n"
"<branch repo=\"git.freedesktop.org\" module=\"swfdec/swfdec\"\n"
" checkoutdir=\"swfdec\"\n"
" revision=\"local-or-remote-branch \"\n"
" tag=\"tree-ish \"/>\n"
" "
msgstr ""
#: C/index.docbook:2459(section/title)
msgid "Mercurial"
msgstr ""
#: C/index.docbook:2461(section/para)
msgid "This repository type is used to define a Mercurial repository."
msgstr ""
#: C/index.docbook:2464(section/programlisting)
#, no-wrap
msgid ""
"\n"
"<repository type=\"hg\" name=\"hg.gtk-vnc\"\n"
" href=\"http://gtk-vnc.codemonkey.ws/hg/\" />\n"
msgstr ""
"\n"
"<repository type=\"hg\" name=\"hg.gtk-vnc\"\n"
" href=\"http://gtk-vnc.codemonkey.ws/hg/\" />\n"
#: C/index.docbook:2469(section/programlisting)
#, no-wrap
msgid ""
"\n"
"<branch repo=\"hg.gtk-vnc\" module=\"outgoing.hg\" checkoutdir=\"gtk-vnc\"/>\n"
msgstr ""
"\n"
"<branch repo=\"hg.gtk-vnc\" module=\"outgoing.hg\" checkoutdir=\"gtk-vnc\"/>\n"
#: C/index.docbook:2475(section/title)
msgid "Monotone"
msgstr ""
#: C/index.docbook:2477(section/para)
msgid "This repository type is used to define a Monotone repository."
msgstr ""
#: C/index.docbook:2480(section/para)
msgid "The server attribute is used to specify the repository server."
msgstr ""
#: C/index.docbook:2483(section/para)
msgid "The database attribute is used to specify the database to use for the repository."
msgstr ""
#: C/index.docbook:2486(section/para)
msgid "The defbranch attribute is used specify the branch of the repository to use."
msgstr ""
#: C/index.docbook:2489(section/programlisting)
#, no-wrap
msgid ""
"\n"
"<repository type=\"mtn\" name=\"pidgin.im\"\n"
" server=\"pidgin.im\" database=\"pidgin.im.mtn\"\n"
" defbranch=\"im.pidgin.pidgin\"/>\n"
msgstr ""
#: C/index.docbook:2497(section/title)
msgid "Subversion"
msgstr "Subversion"
#: C/index.docbook:2499(section/para)
msgid "This repository type is used to define a Subversion repository."
msgstr ""
#: C/index.docbook:2502(section/programlisting)
#, no-wrap
#| msgid ""
#| "\n"
#| "<repository type=\"hg\" name=\"hg.gtk-vnc\"\n"
#| " href=\"http://gtk-vnc.codemonkey.ws/hg/\" />\n"
msgid ""
"\n"
"<repository type=\"svn\" name=\"svn.gnome.org\" default=\"yes\"\n"
" href=\"http://svn.gnome.org/svn/\"/>\n"
" "
msgstr ""
"\n"
"<repository type=\"svn\" name=\"svn.gnome.org\" default=\"yes\"\n"
" href=\"http://svn.gnome.org/svn/\"/>\n"
" "
#: C/index.docbook:2509(section/para)
msgid "It allows a revision on the branch element. This attribute defines the branch to checkout or, if it is a number, a specific revision to checkout."
msgstr ""
#: C/index.docbook:2514(section/programlisting)
#, no-wrap
msgid ""
"\n"
"<branch revision=\"gnome-2-20\"/>\n"
" "
msgstr ""
"\n"
"<branch revision=\"gnome-2-20\"/>\n"
" "
#: C/index.docbook:2518(section/para)
msgid "It is possible to specify custom svn layout using trunk-template (defaults to \"%(module)s/trunk\"), branches-template (defaults to \"%(module)s/branches/%(branch)s\") and tags-template (defaults to \"%(module)s/tags/%(tag)s\")"
msgstr ""
#: C/index.docbook:2528(section/title)
msgid "System"
msgstr ""
#: C/index.docbook:2530(section/para)
msgid "This repository type is used to define a fake system repository. A system repository is required to create systemmodules ."
msgstr ""
#: C/index.docbook:2535(section/programlisting)
#, no-wrap
#| msgid ""
#| "\n"
#| "<repository type=\"bzr\" name=\"launchpad.net\"\n"
#| " href=\"http://bazaar.launchpad.net/\"/>\n"
msgid ""
"\n"
"<repository type=\"system\" name=\"system\"/>\n"
msgstr ""
"\n"
"<repository type=\"system\" name=\"system\"/>\n"
#: C/index.docbook:2541(section/title)
msgid "Tarballs"
msgstr ""
#: C/index.docbook:2543(section/para)
msgid "This repository type is used to define a tarball repository."
msgstr ""
#: C/index.docbook:2546(section/programlisting)
#, no-wrap
msgid ""
"\n"
"<repository type=\"tarball\" name=\"dbus/dbus-python\"\n"
" href=\"http://dbus.freedesktop.org/releases/dbus-python/\"/>\n"
msgstr ""
#: C/index.docbook:2555(section/para)
msgid "The module attribute specifies the file to download and compile, the version attribute specifies the module version."
msgstr ""
#: C/index.docbook:2561(section/para)
msgid "The size and hash , as well as the obsolete md5sum , attributes are optional. If these attributes are present, they are used to check that the source package was downloaded correctly."
msgstr ""
#: C/index.docbook:2567(section/para)
msgid "Any number of patch elements may be nested inside the branch element. These patches are applied, in order, to the source tree after unpacking. The file attribute gives the patch filename, and the strip attribute says how many levels of directories to prune when applying the patch."
msgstr ""
#: C/index.docbook:2575(section/para)
#: C/index.docbook:3089(section/para)
msgid "For module sets shipped with JHBuild, the patch files are looked up in the jhbuild/patches/ directory; for module sets referred by URI, the patch files are looked for in the same directory as the moduleset file, or in its patches/ subdirectory. It is also possible for the file attribute to specify a URI, in which case it will be downloaded from that location."
msgstr ""
#: C/index.docbook:2583(section/programlisting)
#, no-wrap
msgid ""
"\n"
"<branch module=\"dbus-python-0.80.2.tar.gz\" version=\"0.80.2\"\n"
" repo=\"dbus/dbus-python\"\n"
" hash=\"md5:2807bc85215c995bd595e01edd9d2077\" size=\"453499\">\n"
" <patch file=\"dbus-glib-build.patch\" strip=\"1\" />\n"
"</branch>\n"
msgstr ""
#: C/index.docbook:2591(section/para)
msgid "A tarball branch element may also contain quilt elements which specify nested branch to import."
msgstr ""
#: C/index.docbook:2599(section/title)
msgid "Including Other Module Sets"
msgstr ""
#: C/index.docbook:2601(section/para)
msgid "JHBuild allows one module set to include the contents of another by reference using the include element."
msgstr ""
#: C/index.docbook:2605(section/programlisting)
#, no-wrap
msgid ""
"\n"
"<include href=\"uri \"/>\n"
msgstr ""
#: C/index.docbook:2609(section/para)
msgid "The href is a URI reference to the module set to be included, relative to the file containing the include element."
msgstr ""
#: C/index.docbook:2613(section/para)
msgid "Only module definitions are imported from the referenced module set - module sources are not. Multiple levels of includes are allowed, but include loops are not (there isn't any code to handle loops at the moment)."
msgstr ""
#: C/index.docbook:2620(section/title)
msgid "Module Definitions"
msgstr "Definicije modulov"
#: C/index.docbook:2622(section/para)
msgid "There are various types of module definitions that can be used in a module set file, and the list can easily be extended. Only the most common ones will be mentioned here."
msgstr ""
#: C/index.docbook:2626(section/para)
msgid "They are all basically composed of a branch element describing how to get the module and dependencies , suggests and after elements to declare the dependencies of the module."
msgstr ""
#: C/index.docbook:2633(section/para)
msgid "Any modules listed in the dependencies element will be added to the module list for jhbuild build if it isn't already included, and make sure the dependent modules are built first."
msgstr ""
#: C/index.docbook:2638(section/para)
msgid "After generating the modules list, the modules listed in the suggests element will be used to further sort the modules list (although it will not pull any additional modules). This is intended for cases where a module has an optional dependency on another module."
msgstr ""
#: C/index.docbook:2645(section/title)
msgid "autotools"
msgstr "autotools"
#: C/index.docbook:2647(section/para)
msgid "The autotools element is used to define a module which is compiled using the GNU Autotools build system."
msgstr ""
#: C/index.docbook:2651(section/programlisting)
#, no-wrap
msgid ""
"\n"
"<autotools id=\"id \"\n"
"\t [ autogenargs=\"autogenargs \" ]\n"
"\t [ makeargs=\"makeargs \" ]\n"
"\t [ makeinstallargs=\"makeinstallargs \" ]\n"
"\t [ autogen-sh=\"autogen-sh \" ]\n"
"\t [ makefile=\"makefile \" ]\n"
"\t [ skip-autogen=\"skip-autogen \" ]\n"
"\t [ autogen-template=\"autogen-template \" ]\n"
"\t [ check-target=\"check-target \" ]\n"
"\t [ supports-non-srcdir-builds=\"supports-non-srcdir-builds \" ]>\n"
"\n"
" <branch [ ... ] >\n"
" [...]\n"
" </branch>\n"
"\n"
" <dependencies>\n"
" <dep package=\"modulename \"/>\n"
" ...\n"
" </dependencies>\n"
" <after>\n"
" <dep package=\"modulename \"/>\n"
" ...\n"
" </after>\n"
"\n"
"</autotools>\n"
msgstr ""
#: C/index.docbook:2679(section/para)
msgid "The autogenargs and makeargs and makeinstallargs attributes are used to specify additional arguments to pass to autogen.sh , make and make install respectively."
msgstr ""
#: C/index.docbook:2686(section/para)
msgid "The autogen-sh attribute specifies the name of the autogen.sh script to run. The value autoreconf can be used if your module has no autogen.sh script equivalent. In that case, JHBuild will run autoreconf -i , followed by the proper configure . skip-autogen chooses whether or not to run autogen.sh, it is a boolean with an extra never value to tell JHBuild to never skip running autogen.sh . makefile specifies the filename of the makefile to use."
msgstr ""
#: C/index.docbook:2699(section/para)
msgid "The supports-non-srcdir-builds attribute is used to mark modules that can't be cleanly built using a separate source directory."
msgstr ""
#: C/index.docbook:2704(section/para)
msgid "The autogen-template attribute can be used if you need finer control over the autogen command line. It is a python format string, which will be substituted with the following variables: srcdir , autogen-sh , prefix , libdir , and autogenargs . For example, here is the default autogen-template:"
msgstr ""
#: C/index.docbook:2712(section/programlisting)
#, no-wrap
msgid ""
"\n"
"%(srcdir)s/%(autogen-sh)s --prefix %(prefix)s --libdir %(libdir)s %(autogenargs)s\n"
msgstr ""
"\n"
"%(srcdir)s/%(autogen-sh)s --prefix %(prefix)s --libdir %(libdir)s %(autogenargs)s\n"
#: C/index.docbook:2716(section/para)
msgid "The check-target attribute must be specified (with false as value) for modules that do not have a make check target."
msgstr ""
#: C/index.docbook:2722(section/title)
msgid "cmake"
msgstr "cmake"
#: C/index.docbook:2724(section/para)
msgid "The cmake element is used to define a module which is built using the CMake build system."
msgstr ""
#: C/index.docbook:2727(section/programlisting)
#, no-wrap
msgid ""
"\n"
"<cmake id=\"modulename \">\n"
" <branch [ ... ] >\n"
" [...]\n"
" </branch>\n"
"\n"
" <dependencies>\n"
" <dep package=\"modulename \"/>\n"
" ...\n"
" </dependencies>\n"
" <after>\n"
" <dep package=\"modulename \"/>\n"
" ...\n"
" </after>\n"
"</cmake>\n"
msgstr ""
"\n"
"<cmake id=\"imemodula \">\n"
" <branch [ ... ] >\n"
" [...]\n"
" </branch>\n"
"\n"
" <dependencies>\n"
" <dep package=\"imemodula \"/>\n"
" ...\n"
" </dependencies>\n"
" <after>\n"
" <dep package=\"imemodula \"/>\n"
" ...\n"
" </after>\n"
"</cmake>\n"
#: C/index.docbook:2746(section/title)
msgid "distutils"
msgstr ""
#: C/index.docbook:2748(section/para)
msgid "The distutils element is used to define a module which is built using python's distutils"
msgstr ""
#: C/index.docbook:2751(section/programlisting)
#, no-wrap
msgid ""
"\n"
"<distutils id=\"modulename \"\n"
" [ supports-non-srcdir-builds=\"yes|no \" ]>\n"
" <branch [ ... ] >\n"
" [...]\n"
" </branch>\n"
"\n"
" <dependencies>\n"
" <dep package=\"modulename \"/>\n"
" ...\n"
" </dependencies>\n"
" <after>\n"
" <dep package=\"modulename \"/>\n"
" ...\n"
" </after>\n"
"</distutils>\n"
msgstr ""
"\n"
"<distutils id=\"imemodula \"\n"
" [ supports-non-srcdir-builds=\"yes|no \" ]>\n"
" <branch [ ... ] >\n"
" [...]\n"
" </branch>\n"
"\n"
" <dependencies>\n"
" <dep package=\"imemodula \"/>\n"
" ...\n"
" </dependencies>\n"
" <after>\n"
" <dep package=\"imemodula \"/>\n"
" ...\n"
" </after>\n"
"</distutils>\n"
#: C/index.docbook:2771(section/title)
msgid "linux"
msgstr "linux"
#: C/index.docbook:2773(section/para)
msgid "The linux element defines a module used to build a linux kernel. In addition, a separate kernel configuration can be chosen using the kconfig subelement."
msgstr ""
#: C/index.docbook:2778(section/programlisting)
#, no-wrap
msgid ""
"\n"
"<linux id=\"id \"\n"
"\t [ makeargs=\"makeargs \" ]>\n"
"\n"
" <branch [ ... ] >\n"
" [...]\n"
" </branch>\n"
"\n"
" <dependencies>\n"
" <dep package=\"modulename \"/>\n"
" ...\n"
" </dependencies>\n"
" <after>\n"
" <dep package=\"modulename \"/>\n"
" ...\n"
" </after>\n"
"\n"
" <kconfig [ repo=\"repo \" ]\n"
"\t version=\"version \"\n"
"\t [ module=\"module \" ]\n"
"\t [ config=\"config \" ] />\n"
"\n"
"</linux>\n"
msgstr ""
#: C/index.docbook:2805(section/title)
msgid "perl"
msgstr "perl"
#: C/index.docbook:2807(section/para)
msgid "The perl element is used to build perl modules."
msgstr "Element perl se uporablja za izgradnjo modulov perl."
#: C/index.docbook:2810(section/para)
msgid "The makeargs attribute is used to specify additional arguments to pass to make ."
msgstr ""
#: C/index.docbook:2814(section/programlisting)
#, no-wrap
msgid ""
"\n"
"<perl id=\"modulename \"\n"
"\t [ makeargs=\"makeargs \" ]>\n"
"\n"
" <branch [ ... ] >\n"
" [...]\n"
" </branch>\n"
"\n"
" <dependencies>\n"
" <dep package=\"modulename \"/>\n"
" ...\n"
" </dependencies>\n"
" <after>\n"
" <dep package=\"modulename \"/>\n"
" ...\n"
" </after>\n"
"\n"
"</perl>\n"
msgstr ""
#: C/index.docbook:2836(section/title)
#, fuzzy
msgid "systemmodule"
msgstr "modul"
#: C/index.docbook:2838(section/para)
msgid "The systemmodule element is used to specify modules that must be provided by the system. The module should be installed by your distributions package management system."
msgstr ""
#: C/index.docbook:2843(section/programlisting)
#, no-wrap
msgid ""
"\n"
"<systemmodule id=\"modulename \">\n"
" <pkg-config>pkg-config .pc</pkg-config>\n"
"\n"
" <branch repo=\"pkg-config \" version=\"version \" [ ... ] >\n"
" [...]\n"
" </branch>\n"
"</systemmodule>\n"
msgstr ""
#: C/index.docbook:2855(section/title)
msgid "waf"
msgstr ""
#: C/index.docbook:2857(section/para)
msgid "The waf element is used to define a module which is built using the Waf build system."
msgstr ""
#: C/index.docbook:2860(section/para)
msgid "The waf-command attribute is used to specify the waf command script to use; it defaults to waf ."
msgstr ""
#: C/index.docbook:2864(section/programlisting)
#, no-wrap
msgid ""
"\n"
"<waf id=\"modulename \">\n"
"\t [ waf-command=\"waf-command \" ]>\n"
" <branch [ ... ] >\n"
" [...]\n"
" </branch>\n"
"\n"
" <dependencies>\n"
" <dep package=\"modulename \"/>\n"
" ...\n"
" </dependencies>\n"
" <after>\n"
" <dep package=\"modulename \"/>\n"
" ...\n"
" </after>\n"
"</waf>\n"
msgstr ""
#: C/index.docbook:2884(section/title)
msgid "testmodule"
msgstr ""
#: C/index.docbook:2886(section/para)
msgid "The testmodule element is used to create a module which runs a suite of tests using LDTP or Dogtail."
msgstr ""
#: C/index.docbook:2890(section/programlisting)
#, no-wrap
msgid ""
"\n"
"<testmodule id=\"id \"\n"
"\t type=\"type \">\n"
"\n"
" <branch [ ... ] >\n"
" [...]\n"
" </branch>\n"
"\n"
" <dependencies>\n"
" <dep package=\"modulename \"/>\n"
" ...\n"
" </dependencies>\n"
" <after>\n"
" <dep package=\"modulename \"/>\n"
" ...\n"
" </after>\n"
"\n"
" <testedmodules>\n"
" <tested package=\"package \" />\n"
" </testedmodules>\n"
"\n"
"</testmodule>\n"
msgstr ""
#: C/index.docbook:2914(section/para)
msgid "The type attribute gives the type of tests to be run in the module. 'dogtail' uses python to invoke all .py files. 'ldtp' invokes 'ldtprunner run.xml'."
msgstr ""
#: C/index.docbook:2918(section/para)
msgid "Unless the noxvfb configuration option is set, an Xvfb server is started to run the tests in"
msgstr ""
#: C/index.docbook:2923(section/title)
msgid "metamodule"
msgstr ""
#: C/index.docbook:2925(section/para)
msgid "The metamodule element defines a module that doesn't actually do anything. The only purpose of a module of this type is its dependencies."
msgstr ""
#: C/index.docbook:2929(section/para)
msgid "For example, meta-gnome-desktop depends on all the key components of the GNOME desktop, therefore telling JHBuild to install it actually installs the full desktop."
msgstr ""
#: C/index.docbook:2933(section/programlisting)
#, no-wrap
msgid ""
"\n"
"<metamodule id=\"modulename \">\n"
" <dependencies>\n"
" <dep package=\"modulename \"/>\n"
" ...\n"
" </dependencies>\n"
" <suggests>\n"
" <dep package=\"modulename \"/>\n"
" ...\n"
" </suggests>\n"
"</metamodule>\n"
msgstr ""
#: C/index.docbook:2946(section/para)
msgid "The id attribute gives the name of the module. The child elements are handled as for autotools ."
msgstr ""
#: C/index.docbook:2954(section/title)
#, fuzzy
msgid "Deprecated Elements"
msgstr "Elementi razreda"
#: C/index.docbook:2960(section/title)
msgid "cvsroot"
msgstr "cvsroot"
#: C/index.docbook:2962(section/para)
msgid "The cvsroot element is now deprecated - the repository element should be used instead."
msgstr ""
#: C/index.docbook:2966(section/para)
msgid "The cvsroot element is used to describe a CVS repository."
msgstr ""
#: C/index.docbook:2969(section/programlisting)
#, no-wrap
msgid ""
"\n"
" <cvsroot name=\"rootname \"\n"
" [ default=\"yes|no \" ]\n"
" root=\"anon-cvsroot \"\n"
" password=\"anon-password \"/>\n"
msgstr ""
#: C/index.docbook:2976(section/para)
msgid "The name attribute should be a unique identifier for the CVS repository."
msgstr ""
#: C/index.docbook:2979(section/para)
msgid "The default attribute says whether this is the default module source for this module set file."
msgstr ""
#: C/index.docbook:2983(section/para)
msgid "The root attribute lists the CVS root used for anonymous access to this repository, and the password attribute gives the password used for anonymous access."
msgstr ""
#: C/index.docbook:2990(section/title)
msgid "svnroot"
msgstr ""
#: C/index.docbook:2992(section/para)
msgid "The svnroot element is now deprecated - the repository element should be used instead."
msgstr ""
#: C/index.docbook:2996(section/para)
msgid "The svnroot element is used to describe a Subversion repository."
msgstr ""
#: C/index.docbook:2999(section/programlisting)
#, no-wrap
msgid ""
"\n"
" <svnroot name=\"rootname \"\n"
" [ default=\"yes|no \" ]\n"
" href=\"anon-svnroot \"/>\n"
msgstr ""
#: C/index.docbook:3005(section/para)
msgid "The name attribute should be a unique identifier for the Subversion repository."
msgstr ""
#: C/index.docbook:3008(section/para)
msgid "If default attribute says whether this is the default module source for this module set file."
msgstr ""
#: C/index.docbook:3012(section/para)
msgid "The href attribute lists the base URL for the repository. This will probably be either a http , https or svn URL."
msgstr ""
#: C/index.docbook:3022(section/title)
#, fuzzy
msgid "Deprecated Module Types"
msgstr "Prednostne vrste večpredstavnostnih datotek"
#: C/index.docbook:3025(warning/para)
msgid "This section describes deprecated elements, they may still be used in existing module sets but it is advised not to use them anymore."
msgstr ""
#: C/index.docbook:3031(section/title)
#, fuzzy
msgid "tarball"
msgstr "Izgradi _Tar paket"
#: C/index.docbook:3034(important/para)
msgid "This deprecated element is just a thin wrapper around both autotools module type and tarball repository type."
msgstr ""
#: C/index.docbook:3039(section/para)
msgid "The tarball element is used to define a module that is to be built from a tarball."
msgstr ""
#: C/index.docbook:3042(section/programlisting)
#, no-wrap
msgid ""
"\n"
" <tarball id=\"modulename \"\n"
" [ version=\"version \" ]\n"
" [ checkourdir=\"checkoutdir \" ]\n"
" [ autogenargs=\"autogenargs \" ]\n"
" [ makeargs=\"makeargs \" ]\n"
" [ autogen-sh=\"autogen-sh \" ]\n"
" [ supports-non-srcdir-builds=\"yes|no \" ]>\n"
" <source href=\"source-url \"\n"
" [ size=\"source-size \" ]\n"
" [ hash=\"source-algo:source-hash \" ]\n"
" [ md5sum=\"source-md5sum \" ]/>\n"
" <patches>\n"
" <patch file=\"filename \" strip=\"level \"/>\n"
" ...\n"
" </patches>\n"
" <dependencies>\n"
" <dep package=\"modulename \"/>\n"
" ...\n"
" </dependencies>\n"
" <suggests>\n"
" <dep package=\"modulename \"/>\n"
" ...\n"
" </suggests>\n"
" </tarball>\n"
msgstr ""
#: C/index.docbook:3069(section/para)
msgid "The id and version attributes are used to identify the module."
msgstr ""
#: C/index.docbook:3073(section/para)
msgid "The source element specifies the file to download and compile. The href attribute is mandatory, while the size and hash , as well as the obsolete md5sum , attributes are optional. If these last two attributes are present, they are used to check that the source package was downloaded correctly."
msgstr ""
#: C/index.docbook:3082(section/para)
msgid "The patches element is used to specify one or more patches to apply to the source tree after unpacking, the file attribute gives the patch filename, and the strip attribute says how many levels of directories to prune when applying the patch."
msgstr ""
#: C/index.docbook:3097(section/para)
msgid "The other attributes and the dependencies , suggests and after elements are processed as for
Manual de JHBuild
James Henstridge C.J. Adams-Collier Frederic Peters David Turner
2004, 2008 James Henstridge
Manual de JHBuild v0.5 Enero 2008 Manual de JHBuild v0.1 Agosto 2007
JHBuild es una herramienta que se usa para construir completamente el escritorio GNOME desde el sistema de control de veriones. Sin embargo, se puede usar para construir otros proyectos creando para ello un conjunto de módulos.
Daniel Mustieles
daniel.mustieles@gmail.com
2008-2012.
Daniel Mustieles
Introducción
JHBuild es una herramienta diseñada para construir fácilmente colecciones de paquetes fuente (también conocidos como módulos
). JHBuild Usa archivos de conjuntos de módulos
para describir los módulos disponibles para construir. El conjuntos de módulos
incluye información de las dependencias que permite a JHBuild averigüar qué módulos debe construir y en qué orden.
Originalmente JHBuild se escribió para construir GNOME , pero se ha extendido para hacerlo usable con otros proyectos. Se puede almacenar un conjunto de módulos
en un servidor web, para permitir reglas de construcción independientes de JHBuild.
JHBuild puede construir módulos desde varias fuentes, incluyendo los repositorios de CVS , Subversion , Bazaar , Darcs , Git y Mercurial , así como archivos Zip y Tar almacenados en una web o un sitio FTP. JHBuild puede construir módulos usando varios sistemas de construcción, incluyendo Autotools, CMake, WAF, Python Distutils y Perl Makefiles.
JHBuild no está pensado para sustituir al sistema de mantenimiento de paquetes de la distribución. En cambio, facilita la construcción de software con un prefijo de instalación diferente, sin interferir con el resto del sistema.
Inicio
JHBuild requiere unos pocos pasos para configurarlo antes de construir software. JHBuild requiere algunos prerrequisitos software, y es necesario instalar las herramientas de prerrequisitos necesarias para obtener y construir los módulos de software.
Instalar JHBuild
JHBuild requiere una rutina de Python. Verifique que Python >= 2.3 está instalado.
La forma recomendada de descargar JHBuild es a través del sistema de control de versiones, git . Esto puede hacerlo con el siguiente comando. Se recomienda ejecutarlo en una carpeta nueva donde se instalará todo el código fuente, por ejemplo, ~/checkout/gnome .
$ git clone git://git.gnome.org/jhbuild
...
$ Esto descargará JHBuild en una nueva carpeta llamada jhbuild en la carpeta actual. Ahora, para construir e instalar JBuild:
$ cd jhbuild
$ ./autogen.sh
...
$ make
...
$ make install
...
$ Si gnome-common , yelp-tools y autotools está disponibles, autogen.sh configurará JHBuild para instalarlos mediante autotools . Si gnome-common , yelp-tools y autotools no está disponibles, autogen.sh configurará JHBuild para instalarlos mediante un Makefile. Para usar siempre el método del Makefile, pase --simple-install a autogen.sh .
Si estos pasos se completan correctamente se instalará una pequeña línea de comandos en ~/.local/bin para iniciar JHBuild. Añada ~/.local/bin a la variable PATH :
$ PATH=$PATH:~/.local/bin
$ Para añadir permanentemente ~/.local/bin a la variable PATH , ejecute el siguiente comando:
$ echo PATH=$PATH:~/.local/bin >> ~/.bashrc
$
Antes de ejecutar JHBuild, es necesario crear un archivo de configuración, ubicado en ~/.jhbuildrc .
Prerrequisitos para la construcción
Antes de poder construir cualquier módulo es necesario tener ciertas herramientas de construcción instaladas. Las herramientas habituales incluyen las GNU Autotools (autoconf , automake , libtool y gettext ), Las GNU Toolchain (binutils , gcc , g++ ), make, pkg-config y Python, dependiendo de qué módulos se construirán.
JHBuild puede comprobarlas herramientas están instaladas usando el comando sanitycheck :
$ jhbuild sanitycheck Si este comando devuelve algún mensaje, puede solucionar los errores de dos formas:
Instale el paquete requerido desde el repositorio de su distribución. El wiki de GNOME mantiene una lista de nombres de paquetes para diferentes distribuciones. Ejecute otra vez el comando sanitycheck para asegurarse de que las herramientas necesarias están instaladas.
Ejecute el comando bootstrap para descargar, construir e instalar los prerrequisitos de construcción.
$ jhbuild bootstrap Cuando termine, ejecute el comando sanitycheck para verificar que tiene las herramientas necesarias.
El comando bootstrap no construye todas las dependencias requeridas de los paquetes por esas herramientas. Si su distribución no proporciona esos paquetes, deberán construirse fuera del entorno de JHBuild.
Las dependencias de las herramientas de construcción incluyen m4 , perl y un compilador de a C (por ejemplo, gcc ).
Usar JHBuild
Después de que todo esté configurado, se puede usar JHBuild para construir software. Para construir los todos módulos seleccionados en el archivo ~/.jhbuildrc , ejecute el siguiente comando:
$ jhbuild build JHBuild descargará, configurará, compilará e instalará cada uno de los módulos. Si ocurre un error en cualquier fase, JHBuild mostrará un menú preguntando qué hacer. Estas opciones incluyen salir a una consola para reparar el error, volver a ejecutar la construcción desde varias fases, abandonar el módulo, o ignorar el error y continuar.
Desistir de cargar un módulo causará que todos los módulos que dependan de él fallen.
Debajo hay un ejemplo con el menú mostrado:
[1] Volver a ejecutar la fase de construcción
[2] Ignorar error y continuar la instalación
[3] Desistir de cargar el módulo
[4] Iniciar consola
[5] Recargar configuración
[6] Ir a la fase «limpiar carpeta y empezar»
[7] Ir a la fase «configurar»
[8] Ir a la fase «limpiar»
[9] Ir a la fase «distclean»
choice:
También es posible construir un conjunto de módulos diferentes y sus dependencias pasando los nombres de módulos como argumentos al comando build . Por ejemplo, para construir gtk+:
$ jhbuild build gtk+ Si por cualquier razón sale de JHBuild a mitad de una construcción, es posible recuperar la construcción en un momento particular utilizando la opción --start-at :
$ jhbuild build --start-at=pango Para construir uno o más módulos, ignorando sus dependencias, JHbuild proporciona el comando buildone . Para que el comando buildone funcione correctamente, previamente debe construir e instalar todas las dependencias, manualmente o desde los paquetes de la distribución.
$ jhbuild buildone gtk+ Cuando desarrolla activamente un módulo, generalmente está en una carpeta de trabajo. El comando make invocará al sistema de construcción e instalará el módulo. Esto será una parte clave de su ciclo de edición-compilación-instalación-pruebas.
$ jhbuild make Si por cualquier razón sale de JHBuild a mitad de una construcción, es posible recuperar la construcción en un momento particular utilizando la opción --start-at :
Para obtener una lista de los módulos y las dependencias que JHBuild construirá, y el orden en que se construirán, use el comando list :
$ jhbuild list Para obtener información acerca de un módulo en particular, use el comando info :
$ jhbuild info gtk+ Para descargar o actualizar todas las fuentes de software sin construir use el comando update . El comando update ofrece la oportunidad de modificar las fuentes antes de construir y puede ser útil si el ancho de banda de Internet varía.
$ jhbuild update Posteriormente JHBuild puede construir todo sin descargar ni actualizar los fuentes:
$ jhbuild build --no-network Para ejecutar un comando concreto con el mismo entorno que usa JHBuild, use el comando run :
$ jhbuild run programa Para iniciar una consola con el mismo entorno usado por JHBuild use el comando shell :
$ jhbuild shell
JHBuild y GNOME
Esta sección proporciona directrices para construir, instalar y ejecutar GNOME.
Construir GNOME
Para construir GNOME se requieren algunos paquetes de desarrollo. Esto incluye:
DocBook XML DTD y hojas de estilo XSLT. Deben registrarse en el catálogo XML (/etc/xml/catalog ).
Bibliotecas de las X
libsmbclient de Samba (usado para examinar redes Windows).
libbz2 de bzip2.
libpng , libjpeg y libtiff (usada para cargar imágenes).
Si está instalando paquetes de su distribución, y si es aplicable a ésta, instale los paquetes dev
o devel
correspondientes. En el wiki de GNOME se mantiene una lista de nombres de paquetes para las distintas distribuciones.
Ejecutar una única aplicación de GNOME
Esta sección detalla como ejecutar una única aplicación de GNOME. La aplicación se ejecutará dentro del actual entorno de escritorio. Para ejecutar la aplicación dentro de GNOME JHBuild completo consulte la
Lanzar una consola de JHBuild. La consola de JHBuild tiene configuradas todas las variables de entorno necesarias.
$ jhbuild shell Verificar que se ejecutará la aplicación correcta. Por ejemplo:
$ which gedit
/opt/gnome/bin/geditEjecutar la aplicación:
$ gedit & Alternativamente, ejecute la aplicación usando el comando run :
$ jhbuild run gedit
Ejecutar el entorno de escritorio GNOME
Crear una cuenta de usuario nueva para ejecutar JHBuild GNOME. Se recomienda ejecutar JHBuild GNOME con un usuario diferente para evitar problemas causados por configuraciones de usuario guardadas en la carpeta del usuario. Este manual se refiere a la cuenta nueva como gnomedev .
Configure JHBuild en la cuenta gnomedev nueva. Copie o cree un enlace simbólico de ~/.jhbuildrc y ~/.local/bin/jhbuild a la carpeta del usuario gnomedev .
Abrir una terminal como usuario gnomedev . Para añadir permanentemente ~/.local/bin a la variable PATH , ejecute el siguiente comando:
$ echo PATH=$PATH:~/.local/bin >> ~/.bashrc Probar si JHBuild funciona:
$ jhbuild run pkg-config gtk+-2.0 --modversion
2.20.1
Configurar GNOME para ejecutarse desde el gestor de ventanas
Construir e instalar JHBuild GNOME
Activar servicios del sistema. JHBuild GNOME usará el demonio D-Bus del sistema /usr/bin y los servicios del sistema con /usr/share/dbus-1/system-services/ . JHBuild GNOME usará el demonio de sesión D-Bus de JHBuild y los servicios con /opt/gnome /share/dbus-1/services//opt/gnome con el prefix de instalación de GNOME en el siguiente comando:
$ rm -rf /opt/gnome /var/run/dbus
$ ln -s /var/run/dbus /opt/gnome /var/run/dbus
$ rm -rf /opt/gnome /var/lib/dbus/machine-id
$ ln -s /var/lib/dbus/machine-id /opt/gnome /var/lib/dbus/machine-id Cree un script de inicio de GNOME en /usr/bin/gnome-jhbuild-session con el siguiente contenido, sustituyendo /opt/gnome por el prefix de instalación de GNOME :
#!/bin/sh
GNOME=/opt/gnome
GDK_USE_XFT=1
XDG_DATA_DIRS=$XDG_DATA_DIRS:$GNOME/share
XDG_CONFIG_DIRS=$XDG_CONFIG_DIRS:$GNOME/etc/xdg
jhbuild run gnome-session
Haga ejecutable el archivo /usr/bin/gnome-jhbuild-session :
$ chmod a+x /usr/bin/gnome-jhbuild-session Para añadir una entrada de sesión nueva en el gestor de sesiones, cree /usr/share/xsessions/gnome-jhbuild.desktop e introduzca:
[Desktop Entry]
Name=GNOME (JHBuild)
Comment=Esta sesión inicia la sesión de pruebas de GNOME
TryExec=/usr/bin/gnome-jhbuild-session
Exec=/usr/bin/gnome-jhbuild-session
Icon=
Type=Application
Reiniciar gdm .
Ejecutar GNOME desde el gestor de ventanas
Para ejecutar JHBuild GNOME seleccione la sesión GNOME (JHBuild) en el gestor de ventanas antes de introducir las credenciales de inicio de sesión de gnomedev . Si es correcto, se mostrará JHBuild GNOME. Si es incorrecto, compruebe el archivo de registro ~gnomedev/.xsession-errors .
Integración con buildbot
Junto al proyecto Buildbot , JHBuild puede funcionar también como una herramienta de integración. El proyecto GNOME usa la configuración de Buildbot en build.gnome.org .
Configurar un Buildbot esclavo
Un Buildbot esclavo es una variación de una instalación normal de JHBuild que sirve las peticiones a un Buildbot maestro. Se recomienda configurar JHBuild y completar una ejecución con la mayoría de los módulos construyéndose bien antes de añadir las configuraciones personalizadas de Buildbot.
Los comandos de Buildbot son opciones del comando bot . Para descargar e instalar el software adicional requerido ejecute el siguiente comando:
$ jhbuild bot --setup Una vez que este paso ha terminado correctamente, hay tres nuevas variables de configuración para definir en ~/.jhbuildrc .
No se puede usar un archivo alternativo de configuración. La opción --file no tendrá los efectos deseados.
jhbuildbot_master = 'build.gnome.org:9070'
jhbuildbot_slavename = 'nombredelesclavo'
jhbuildbot_password = 'contraseña'
jhbuildbot_master es una cadena que especifica el servidor Buildbot maestro; el predeterminado es 'build.gnome.org:9070' . jhbuildbot_slavename y jhbuildbot_password identifican al esclavo en el servidor maestro; contacte con los administradores del servidor Buildbot maestro para obtenerlos.
Se puede contactar con los administradores de build.gnome.org en la lista de correo de Build Brigade .
Referencia de comandos
JHBuild usa una sintaxis de línea de comandos similar a la de herramientas como CVS:
jhbuild opciones globales comando argumentos del comando Las opciones globales de JHBuild son:
-f , --file configuración
Use un archivo de configuración alternativo, en lugar del predeterminado, ~/.jhbuildrc .
-m , --moduleset conjunto de módulos
Usar un conjunto de módulos diferente del que aparece listado en el archivo de configuración. Esta opción puede ser una ruta relativa si el conjunto de módulos está ubicado en la carpeta de módulos de JHBuild, o una ruta absoluta si está ubicado en otro sitio.
--no-interact
No solicitar al usuario ninguna entrada. Esta opción es útil cuando se deja una construcción sin atender, para asegurarse de que no se interrumpe.
A continuación se listan las opciones específicas de los comandos.
autobuild
El comando autobuild construye automáticamente los módulos tal y como se especifica en el archivo de configuración, y sube los resultados a JhAutobuild.
jhbuild autobuild --autogen --clean --distcheck --skip=módulo --start-at=módulo --report-url=URL --verbose Las opciones --autogen , --clean , --distcheck , --skip y --start-at se procesan de la misma manera que para el comando build .
--report-url=reporturl , -r reporturl
Esta opción especifica el URL de JhAutobuild a la que se debe informar
--verbose , -v
Si está especificado, la salida de JHBuild será más detallada.
bootstrap
El comando bootstrap instala un conjunto de utilidades de construcción requeridas para construir la mayoría de módulos (ej. autoconf , automake , etc).
jhbuild bootstrap El comando, bootstrap construye módulos usando el mismo método que el comando build , pero usa el conjunto de módulos bootstrap.modules .
Consulte la documentación del comando build para ver las opciones disponibles.
build
El comando build construye uno o más paquetes, incluyendo sus dependencias.
jhbuild build --autogen --clean --check --dist --distcheck --ignore-suggests --no-network --skip=módulo --start-at=módulo --tags=etiquetas -D fecha --no-xvfb --try-checkout --no-poison --force --build-optional-modules --min-age=tiempo módulo Si no se indican nombres de módulos en la línea de comandos, se usará la lista de
-c , --clean
Ejecute make clean antes de construir los módulos.
--check
Ejecute make check después de construir los módulos.
-d , --dist
Ejecute make dist después de construir los módulos.
--distcheck
Ejecute make distcheck después de construir los módulos.
--ignore-suggests
No construir las dependencias suaves
-n , --no-network
No acceda a la red mientras esté construyendo módulos. Esto omitiría la descarga o etapas de la actualización en una construcción. Si no se puede construir un módulo sin acceso a la red, dará un error.
-s , --skip =módulo,...
No construir los módulos listados. Usado para omitir la construcción de determinadas dependencias.
--tags =etiqueta,...
Ignorar los módulos que no coinciden con etiqueta . Los módulos se asignan automáticamente a una etiqueta que coincide con el nombre del conjunto de módulos del módulo.
-t , --start-at =módulo
Comenzar en el módulo nombrado en lugar de por el principio de la lista. Esto es útil si se interrumpió la construcción por algún motivo.
-D fecha
Si la versión del sistema de control de versiones subyacente lo soporta, actualice el árbol de repositorios a su estado en la fecha dada antes de la construcción. La fecha debe estar en formato ISO, ej «2009-09-18 02:32Z» .
-x , --no-xvfb
Ejecutar comprobaciones gráficas en el servidor X actual en lugar de en un Xvfb simulado.
-C , --try-checkout
Si falla la construcción, y el sistema de control de versiones lo soporta, fuerce una descarga y ejecute autogen.sh antes de reintentar la construcción.
-N , --no-poison
Si falla una o más dependencias de un conjunto de módulos, esta opción fuerza a JHBuild a intentar construir el módulo de todas formas.
-f , --force
Construir los módulos aunque la política diga que no es necesario.
--build-optional-modules
Los módulos, listados como dependencias opcionales, pueden no ser necesarios para construir el módulo. Esta opción fuerza a JHBuild a construir las dependencias opcionales.
--min-age =tiempo
Omitir módulos instalados más recientemente que la fecha relativa dada; el formato de la cadena time es un número seguido de una unidad. Se soportan las siguientes unidades: segundos (s), minutos (m), horas (h) y días (d). Por ejemplo, --min-time=2h omitirá los módulos construidos hace menos de dos horas.
make
El make es para desarrollar activamente en un módulo en particular. Requiere que la carpeta actual sea una descargar de fuentes y es equivalente a buildone -nf $(basename $(pwd)) .
jhbuild make --clean --check --distcheck --quiet Las opciones son las mismas que las disponibles para el comando buildone .
buildone
El comando buildone es similar a build , pero no construye los módulos dependientes. Es útil para reconstruir uno o más módulos.
jhbuild buildone --clean --check --distcheck --no-network -D fecha --no-xvfb --force --min-age=tiempo módulo Las opciones --check , --clean , -d , --distcheck , --no-network , -D y -x se procesan de la misma manera que para el comando build .
Se debe listar al menos un módulo en la línea de comandos.
checkbranches
El comando checkbranches comprueba que las ramas de módulos están definidas correctamente en sistema de control de versiones, y que las ramas son consistentes con el conjunto de módulos.
jhbuild checkbranches --branch=rama
--branch =rama , -b rama
La rama para comprobar.
$ jhbuild -m gnome-2.20 checkbranches
libgnomecanvas es una definición de rama desconocida para gnome-2-20
$
clean
El comando clean limpia las carpetas de construcción de uno o más módulos.
jhbuild clean --skip=módulo --start-at=módulo Si no se indican nombres de módulos en la línea de comandos, se usará la lista de
Consulte la documentación del comando build para obtener una descripción de las opciones disponibles.
dot
El comando dot genera un archivo que describe el grafo dirigido formado por las dependencias entre un conjunto de módulos. Se puede procesar este archivo usando el software GraphViz para generar un diagrama.
jhbuild dot --soft-deps --clusters módulo Si no se indican nombres de módulos en la línea de comandos, se usará la lista de
La opción --soft-deps añadirá líneas de puntos desde los módulos hasta sus dependencias débiles. La opción --clusters agrupará los módulos de los
La salida del comando «dot» se puede redirigir a la utilidad «dot» para generar un archivo PostScript:
$ jhbuild dot módulos | dot -Tps > dependencies.ps O una imagen PNG:
$ jhbuild dot módulos | dot -Tpng > dependencies.png
Ejemplo de salida de JHBuild dot
gui
El comando gui inicia una interfaz gráfica de JHBuild que se puede usar para seleccionar los módulos que construir y cambiar algunas opciones.
jhbuild gui La interfaz gŕafica se renderiza usando GTK, por lo que se necesitarán algunas bibliotecas de soporte adicionales.
info
El comando info muestra información de uno o más módulos.
jhbuild info módulo El comando muestra el nombre del módulo, el tipo, sus dependencias, paquetes dependientes, la carpeta origen y la hora en que fue instalado con JHBuild. Si está disponible, también mostrará información específica del tipo de módulo, tal como el repositorio CVS o el URL de descarga.
Si no se especifica ningún módulo el comando mostrará información acerca de todos los módulos definidos en el conjunto de módulos.
list
El comando list se usa para mostrar una lista expandida de los módulos que el comando build construiría.
jhbuild list -a -r -s --start-at=módulo --tags=etiquetas --ignore-suggests --list-optional-modules módulo Si no se indican nombres de módulos en la línea de comandos, se usará la lista de
Las opciones --skip , --start-at , --tags , --ignore-suggests y -D se procesan de la misma manera que para el comando build .
-a , --all-modules
Listar todos los módulos del conjunto de módulos sin importar sus dependencias de construcción.
-r , --show-revision
Si se asigna un módulo a una rama, mostrar el nombre de la rama con el nombre del módulo.
--list-optional-modules
Esta opción fuerza a JHBuild a listar dependencias opcionales
rdepends
El comando rdepends muestra las dependencias inversas de un módulo.
jhbuild rdepends módulo
--dependencies
Mostrar las dependencias junto a los módulos.
--direct
Limitar la muestra a los módulos directamente dependientes del módulo dado.
run
El comando run ejecuta un comando especificado usando el mismo entorno que usa JHBuild cuando construye los módulos.
jhbuild run --in-builddir --in-checkoutdir programa argumento Si usa JHBuild para construir GNOME este comando puede ser útil en los scripts de inicio de las X.
--in-builddir =módulo
Ejecute el comando en la carpeta de construcción del módulo especificado.
--in-checkoutdir =módulo
Ejecute el comando en la carpeta de fuentes del módulo especificado.
sanitycheck
El comando sanitycheck lleva a cabo una serie de comprobaciones para ver si el entorno de construcción es correcto.
jhbuild sanitycheck Algunas de las comprobaciones incluyen:
Los prefijos de descarga e instalación son escribibles.
Las herramientas de construcción requeridas están instaladas.
Algunas macros usadas habitualmente están disponibles en la rutas de búsqueda de los comandos de aclocal , asociados con varias versiones de automake .
El catálogo XML contiene la DTD de DocBook y hojas de estilos.
shell
El comando shell inicia una consola de usuario con el mismo entorno que usa JHBuild cuando construye los módulos.
jhbuild shell Este comando es equivalente al siguiente:
$ jhbuild run $SHELL La variable de entorno UNDER_JHBUILD se establecerá a «true» cuando esta consola esté activa. Puede usar la presencia de esta variable para personalizar el «prompt» de su consola para indicar que, efectivamente, se encuentra en una consola controlada por jhbuild. Por ejemplo, puede querer incluir esto en su .bashrc :
if [ -n "$UNDER_JHBUILD" ]; then
PS1="[jhbuild] $PS1"
fi
Esto hará que su consola bash muestre [jhbuild] antes de su «prompt» normal, haciendo más fácil ver que consolas están bajo un entorno jhbuild.
sysdeps
El comando sysdeps muestra una lista de dependencias de módulos proporcionados por paquetes del sistema instalados. JHBuild no construirá los módulos desde las fuentes si el valor de la variable de configuración partial_build es True .
El comando sysdeps también muestra una lista de dependencias de módulos en la que los paquetes del sistema instalados son demasiado antiguos. JHBuild construirá los módulos más nuevos desde las fuentes.
El comando sysdeps también muestra una lista de dependencias de módulos que no coinciden con paquetes del sistema instalados.
jhbuild sysdeps --install
--install
Esta opción instala paquetes del sistema que son dependencias del conjunto de módulos. Los paquetes del sistema se instalan usando PackageKit .
ejemplo de <command>sysdeps</command>
$ jhbuild sysdeps
Paquetes del sistema instalados suficientemente nuevos:
speex (required=1.2rc1, instalado=1.2rc1)
libdiscid (requerido=0.2.2, instalado=0.2.2)
telepathy-farsight (requerido=0.0.14, instalado=0.0.16)
lcms2 (requerido=2.2, instalado=2.2)
...
Paquetes del sistema instalados demasiado antiguos:
webkitgtk-3.0 (requerido=1.5.1, instalado=1.4.0)
...
No coincide con ningún paquete del sistema instalado:
libvala-0.14 (requerido=0.13.1)
...
tinderbox
El comando tinderbox es parecido a build , pero guarda toda la salida del terminal en archivos HTML aptos para publicarlos en un sitio web. Se puede usar para configurar sistemas parecidos a Tinderbox de Mozilla o o Buildd de Debian.
jhbuild tinderbox --clean --no-network --output=carpeta --skip=módulo --start-at=módulo -D fecha -C -N -f módulo Las opciones --clean , --no-network , --skip , --start-at , -D , -C , -N y -f se procesan de la misma manera que para el comando build .
-o , --output =carpeta
La carpeta donde guardar los archivos HTML.
uninstall
El comando uninstall desinstala uno o más módulos.
jhbuild uninstall módulo
update
El comando update es similar a build , pero sólo realiza la fase de descarga o actualización de los módulos sin construirlos.
jhbuild update --skip=módulo --start-at=módulo --tags=etiquetas --ignore-suggests -D fecha módulo Las opciones --skip , --start-at , --tags , --ignore-suggests y -D se procesan de la misma manera que para el comando build .
updateone
El comando updateone es similar a update , pero no actualiza los módulos dependientes. Es útil para actualizar uno o varios módulos.
jhbuild updateone -D date module La opción -D se procesa de la misma manera que para el comando build .
Se debe listar al menos un módulo en la línea de comandos.
Referencia del archivo de configuración
El archivo ~/.jhbuildrc usa la sintaxis estándar de Python. Se ejecuta el archivo, y las variables resultantes, definidas en el espacio de nombres, se usan para controlar como actúa JHBuild. Se inserta un conjunto de valores predeterminados en el espacio de nombres antes de ejecutar el archivo de configuración del usuario.
Las variables de configuración booleanas se establecen usando una sintaxis como se demuestra en el siguiente ejemplo:
use_local_modulesets = True
Las variables de configuración de tipo cadena se establecen usando una sintaxis como se demuestra en el siguiente ejemplo:
autogenargs = '--disable-static --disable-gtk-doc'
Las variables de configuración de tipo lista se establecen usando una sintaxis como se demuestra en el siguiente ejemplo:
skip = ['mozilla', 'pulseaudio']
Las variables de configuración de tipo diccionario se establecen usando una sintaxis como se demuestra en el siguiente ejemplo:
repos['git.gnome.org'] = 'ssh://username@git.gnome.org/git/'
Variables de configuración
autogenargs
Una cadena que contiene los argumentos pasados al script autogen.sh de todos los módulos. Se pueden omitir para algunos módulos concretos usando el diccionario module_autogenargs .
branches
Un diccionario que especifica qué rama usar para módulos concretos. Esto es útil si hace algunos cambios en la rama de un módulo y quiere que JHBuild construya esa rama en lugar de la listada en el conjunto de módulos.
La definición de ramas depende del módulo VCS:
CV: revisión. Ej. «RAMA-PROYECTO-0_8»
Bazaar: URI de la rama del módulo. Ej. 'http://bzr.example.net/project/gnome-2-28'
Git: tupla, siendo la primera parte un repositorio opcional (o el valor Ninguno) y la segunda parte el nombre de la rama. Ej. ('git://git.example.net/project', 'gnome-2-28')
Ejemplo sencillo
branches['nombremodulo'] = (None, 'nombrerama')
Subversion: URI de la rama del módulo. Ej. 'svn://svn.example.net/project/gnome-2-28'
builddir_pattern
Un patrón de formateo al estilo de printf usado para generar nombres de carpetas de construcción. Esto se usa solamente cuando se usan repositorios y árboles de construcción por separado. En la cadena de formato, el %s se reemplazará con checkoutdir . De manera predeterminada es «%s» .
buildroot
Una cadena que especifica la carpeta padre donde colocar los árboles de construcción. El predeterminado es None , que hace que las construcciones se ejecuten dentro de los árboles de fuentes
buildscript
Una cadena que especifica el script de construcción que usar. El valor recomendado es el predeterminado, terminal . En particular, no lo configure como gtk .
build_policy
Una cadena que especifica los módulos que construir. Las tres opciones son all , para construir todos los módulos solicitados, updated , para construir solamente los módulos que han cambiado, o updated-deps para construir los módulos que han cambiado o que tienen dependencias que han cambiado. El valor predeterminado es updated-deps .
checkoutroot
Una cadena que especifica la carpeta donde descomprimir los árboles de fuentes. A menos que buildroot esté configurado, las construcciones se harán también en esta carpeta. El valor predeterminado es ~/checkout/gnome .
checkout_mode
Una cadena que especifica cómo se realiza la descarga de carpetas en el control de versiones. El predeterminado es update . Esto se puede configurar para cada módulo usando module_checkout_mode . Los valores posibles son update (actualizar carpeta de descarga), clobber (vaciar la carpeta antes de descargar las fuentes), export (vaciar la carpeta y crear una copia no versionada de las fuentes) y copy (descargar en una carpeta diferente de en la que se construirá).
copy_dir
Una cadena que especifica la carpeta que copiar, si el modo de copia checkout_mode está en uso. El predeterminado es la carpeta de descarga.
cvs_program
Una cadena que especifica qué programa usar para soporte de CVS. Éste puede ser git-cvsimport o cvs . El predeterminado es cvs .
dvcs_mirror_dir
Una cadena que especifica la carpeta espejo local. JHBuild creará carpetas espejo locales para los repositorios en la carpeta especificada. Los espejos se pueden compartir por varios grupos de repositorios, ahorrando espacio y tiempo ya que los enlaces duros se usarán para clones locales. Los comandos update y updateone crearán los espejos y recuperarán los nuevos commits de los repositorios en línea. Esta opción sólo está soportada por los repositorios Git y Bazaar.
installprog
Una cadena que especifica qué programa se usará como reemplazo de /usr/bin/install ; si está disponible, se utilizará install-check como predeterminado, proporcionado por JHBuild. install-check optimiza la instalación de cabeceras, para reducir el tiempo de las reconstrucciones.
ignore_suggests
Valor booleano que indica si se ignorarán las dependencias suaves cuando se calcule el árbol de dependencias. Su valor predeterminado es False .
interact
Un valor booleano que especifica si se interactúa con el usuario. Establecer este valor a False es equivalente a pasar la opción --no-interact . El valor predeterminado es True .
makeargs
Una cadena que lisa argumentos adicionales para pasarlos a make . De forma predeterminada es True .
makecheck
Valor booleano que indica si se ejecuta make check antes de make . De forma predeterminada está a False .
makecheck_advisory
Un valor booleano que especifica si los fallos producidos al ejecutar make check deben ser sólo informativos y no provocar un fallo de la construcción. El valor predeterminado es False .
makeclean
Valor booleano que indica si se ejecuta make clean después de make . De forma predeterminada está a False .
makedist
Un valor booleano que especifica si se ejecutará make dist antes de make . El valor predeterminado es False . Esta configuración es equivalente a pasar la opción --dist .
makedistcheck
Un valor booleano que especifica si se ejecutará make distcheck antes de make . El valor predeterminado es False . Esta configuración es equivalente a pasar la opción --distcheck .
module_autogenargs
Un diccionario que mapea nombres de módulos en cadenas que contienen argumentos para pasárselos a autogen.sh . La configuración de module_autogenargs se usa en lugar de la configuración global de autogenargs . Si un módulo en particular no está listado en el diccionario, se usará la variable global autogenargs .
module_checkout_mode
Un diccionario que especifica el modo de descarga a usar para los módulos. Ésto omite la configuración global checkout_mode .
module_makeargs
Un diccionario que mapea nombres de módulos en cadenas que contienen argumentos para pasárselos a make . El valor de module_makeargs reemplaza el valor de makeargs . Si un módulo en particular no está listado en el diccionario, se usará la variable global makeargs .
module_makecheck
Un diccionario que mapea nombres de módulos en valores booleanos especificando si se ejecutará make check después de make . El valor de module_makecheck reemplaza el valor de makecheck . Si un módulo en particular no está listado en el diccionario, se usará la variable global makecheck .
module_nopoison
Un diccionario que mapea nombres de módulos en valores booleanos. Si un módulo está establecido a True , JHBuild intentará construir los módulos dependientes aunque falle el módulo especificado. La configuración de module_nopoison reemplaza el valor de nopoison . Si un módulo en particular no está listado en el diccionario, se usará la variable global nopoison .
Un diccionario que mapea nombres de módulos a diccionarios con variables de entorno adicionales para pasar cuando se ejecutan comandos del módulo.
modules
Una lista de cadenas especificando los módulos que construir. La lista de los módulos actualmente construidos se expandirá recursivamente para incluir todas las dependencias, salvo que se use el comando buildone . Su valor predeterminado es ['meta-gnome-desktop'] .
moduleset
Una cadena o una lista de cadenas que contiene los nombres de los conjuntos de módulos que se usarán. También puede ser el nombre de archivo de un conjunto de módulos incluido en JHBuild (excluyendo la ruta y la extensión), o un URL completo a un conjunto de módulos administrado externamente. Los URL se almacenan localmente en la caché. si un módulo con el mismo nombre aparece en más de un conjunto de módulos, tendrá prioridad la última lista configurada. Los conjuntos de módulos proporcionados con JHBuild se actualizan para que coincididan con la versión liberada de desarrollo de GNOME.
modulesets_dir
Una cadena que especifica la carpeta que contiene el conjunto de módulos que usar. La predeterminada es la carpeta modulesets/ en las fuentes de JHBuild.
nice_build
Ejecutar la construcción bajo la prioridad SCHED_IDLE en Linux, o con nice en otros Unix. Esto puede mejorar drásticamente la interactividad de escritorio para construcciones en paralelo, mientras que sólo tiene un impacto insignificante en el rendimiento de la construcción.
nobuild
Un valor booleano que, si está establecido a True , hace que JHBuild no construya los módulos, sino que sólo descargue y descomprima las fuentes. El valor predeterminado es False .
nonetwork
Un valor booleano que especifica si se accede a la red o no. Esto afecta a la descarga o actualización de módulos del CVS, descargando archivos tar y actualizando los conjuntos de módulos. Establecerlo a True es equivalente a pasar la opción --no-network . El valor predeterminado es False .
nonotify
Un valor booleano que especifica si se deben emitir notificaciones usando el demonio de notificaciones. Si está establecido a False , las notificaciones se emiten. El valor predeterminado es True .
nopoison
Un valor booleano que, si está establecido a True , hace que JHBuild intente construir módulos aunque fallen una o más dependencias del módulo. Esta opción es equivalente al argumento --no-poison . Su valor predeterminado es False .
notrayicon
Un valor booleano que especifica si se debe mostrar un icono en la bandeja del sistema usando Zeinity. Si está establecido a False , las notificaciones se emiten. El valor predeterminado es True .
noxvfb
Un valor booleano que, si está establecido a True , hace que JHBuild ejecute comprobaciones gráficas en un servidor X real, en lugar de usar Xvfb . Esta opción es equivalente a pasar --no-xvfb . El valor predeterminado es False .
partial_build
Un valor booleano que, si está establecido a True , hace que JHBuild no construya las dependencias de los módulos si los correspondientes paquetes del sistema están instalados y su versión es suficiente. El valor predeterminado es True .
prefix
Una cadena que indica el prefijo donde instalar módulos.prefix debe ser una ruta absoluta. Esta carpeta debe ser escribible. La carpeta predeterminada es «/opt/gnome» .
pretty_print
Un valor booleano que especifica si activar el formateado de la salida de los subprocesos. Sólo hay soporte para la salida de CVS. Desactívelo si el formateado causa problemas. El valor predeterminado es True .
print_command_pattern
Se muestra una cadena antes de que JHBuild ejecute un comando. %(command)s se reemplazará en la cadena por el comando que ejecutar. %(cwd)s se reemplazará en la cadena por la carpeta de trabajo actual. La predeterminada es «%(command)s» .
progress_bar
Un valor booleano que especifica dónde mostrar una barra de progreso durante el True .
quiet_mode
Un valor booleano que si vale True desactiva la salida de los comandos en ejecución. Su valor predeterminado es False .
repos
Un diccionario que especifica la ubicación de un repositorio alternativo para uno en particular. Esta variable de configuración es útil para un desarrollador de módulos. De manera predeterminada, JHBuild descargará código de los repositorios usando una ubicación de repositorio anónima. Las claves del diccionario son nombres cortos de repositorios y los valores son las cadenas de ubicación de los repositorios alternativos. Por ejemplo:
repos['git.gnome.org'] = 'ssh://username@git.gnome.org/git/'
skip
Una lista de módulos que se omitirán La opción--skip de línea de comando extiende la lista. De manera predeterminada, esta lista está vacía.
sticky_date
Una cadena que si está establecida y está soportado por el sistema de control de versiones subyaciente, JHBuild actualizará el árbol de fuentes a la fecha indicada antes de la construcción. La fecha debe darse en formato ISO, ej «yyyy -mm -dd » . El valor predeterminado es None .
svn_program
Una cadena que especifica qué programa usar para soporte de subversion. Éste puede ser svn o git-svn . El predeterminado es svn .
tarballdir
Si está establecido, los archivos tar se descargarán en la carpeta especificada en lugar de en checkoutroot . Esto es útil si tiene múltiples entornos JHBuild o borra habitualmente su checkoutroot y quiere reducir el uso del ancho de banda.
tinderbox_outputdir
Una cadena que contiene la carpeta para guardar la salida de jhbuild tinderbox . Esta cadena se puede omitir con la opción --output . Su valor predeterminado es None , por lo que se debe usar la opción de la línea de comandos o se debe configurar esta variable en el archivo de configuración.
trycheckout
Un valor booleano que si está establecido a True hace que JHBuild intente automáticamente resolver problemas 1) ejecutando autogen.sh de nuevo, y 2) comprobando en el control de versiones si hay una nueva versión del módulo. Esta opción es equivalente a pasarle --try-checkout .
use_lib64
Un valor booleano que especifica si se instalarán bibliotecas en las carpetas lib64 . Si está establecido, se pasará --libdir=\${exec_prefix}/lib64 para configurarlo. El valor predeterminado es True si se ejecuta en Linux x86_64 , ppc64 o s390x , y False en otros sistemas.
use_local_modulesets
Un valor booleano que especifica que se usen los conjuntos de módulos que se descargaron junto al código fuente de JHBuild, en lugar de descargarlos manualmente del sistema de control de versiones de GNOME. Su valor predeterminado es False .
xvfbargs
Una cadena que lista los argumentos que pasar a Xvfb si se ejecutan comprobaciones gráficas.
Otras estructuras de los archivos de configuración
Aparte de las variables anteriores, hay algunas otras cosas que se pueden configurar en el archivo de configuración.
os.environ
Un diccionario que representa el entorno. Este entorno se le pasa a los procesos que JHBuild crea.
Algunas variables de entorno influyentes incluyen CPPFLAGS , CFLAGS , INSTALL y LDFLAGS . Por ejemplo:
os.environ['CFLAGS'] = '-O0'
addpath (envvar , pathname )
Esto añadirá una carpeta a la variable de entorno PATH . addpath manejará correctamente el caso en que la variable de entorno está vacía inicialmente (tener una comilla al principio o al final de una variable de entorno puede tener consecuencias inesperadas).
addpath gestiona de forma especial la variable de entorno ACLOCAL_FLAGS , que espera que se listen rutas en el formulario -I nombre-de--la-ruta .
prependpath (envvar , pathname )
Después de procesar el archivo de configuración, JHBuild alterará algunas rutas basadas en variables, tales como prefix (ej. añadiendo $prefix/bin al principio de PATH ).
La función prependpath trabaja igual que addpath , excepto que la variable de entorno se modifica después de que JHBuild haya hecho sus cambios al entorno.
Archivo de sintaxis del conjunto de módulos
JHBuild usa archivos XML para describir las dependencias entre módulos. En JHBuild se incluyen esquemas RELAX-NG y Definición de Tipo de Documento en la carpeta modulesets/ . El esquema RELAX-NG se puede usar para editar los archivos del conjunto de módulos usando nxml-mode en Emacs.
El elemento superior del archivo de un conjunto de módulos es el elemento moduleset . No se usa ningún nombre de espacio XML. El elemento a continuación del superior tiene tres tipos: fuentes de módulos, sentencias «include» y definiciones de módulos.
Repositorios de módulos
En lugar de listar la ubicación completa de todos los módulos, se muestra un número de «fuentes del módulo» en el conjunto de módulos, y se referencian por nombre en las definiciones de módulos. Aparte de reducir la cantidad de información redundante en el conjunto de módulos, hace más fácil para el usuario el especificar una fuente alternativa para esos módulos (para CVS y Subversion, es frecuente que desarrolladores y usuarios usen diferentes métodos de acceso al repositorio).
El elemento repositorio se usa para describir todos los tipos de repositorios. El elemento rama se usa dentro de la definición del módulo para indicar configuraciones adicionales.
<repository name="nombre "
type="tipo "
[ default="predeterminado " ]
[ password="contraseña " ]
[ cvsroot="cvsroot " ]
[ archive="archivo " ]
[ href="href " ]
[ server="servidor " ]
[ database="base de datos " ]
[ defbranch="rama predeterminada " ]
[ trunk-template="principal-plantilla " ]
[ branches-template="ramas-plantilla " ]
[ tags-template="etiquetas-plantilla " ]
[ developer-href-example="ejemplo-href-desarrollador " ] />
El atributo nombre es un identificador único del repositorio.
El atributo predeterminado especifica si este repositorio es el predeterminado para este conjunto de módulos.
El atributo type especifica el tipo de repositorio. Puede ser uno de estos: bzr , cvs , darcs , fossil , git , hg , mnt , svn , tarball . Otros atributos dependen de type , así como de branch usados dentro de las definiciones de los módulos. Se describen a continuación en las subsecciones de tipo de repositorios.
El atributo developer-href-example se usa para especificar el formato del URL del repositorio usado por los desarrolladores. Esto es sólo informativo.
El elemento rama se usa dentro de las definiciones del módulo.
<branch
[ repo="repositorio " ]
[ module="nombre del módulo " ]
[ checkoutdir="carpeta de descarga " ]
[ revision="revisión " ]
[ tag="etiqueta " ]
[ update-new-dirs="actualizar carpetas nuevas " ]
[ override-checkoutdir="omitir carpeta de descarga " ]
[ subdir="subcarpeta " ]
[ branch="rama " ]
[ version="versión " ]
[ size="tamaño " ]
[ source-subdir="subcarpeta de fuentes " ]
[ hash="hash " ]/>
Todos los atributos tienen valores predeterminados correctos y dependen del módulo y de las definiciones del repositorio. Aquí se describen los atributos comunes.
El atributo repo se usa para especificar un nombre de repositorio no predeterminado.
El atributo module se usa para especificar el nombre del módulo que descargar del repositorio. Su valor predeterminado es el identificador del módulo.
El atributo checkoutdir se usa para especificar la carpeta de descarga que usar. Su valor predeterminado es el identificador del módulo.
A continuación se describen otros atributos
Bazaar
El tipo de repositorio se usa para definir un repositorio Bazaar. Se recomienda tener Bazaar 1.16 o superior.
<repository type="bzr" name="launchpad.net"
href="lp:"/>
Los atributos adicionales son trunk-template (el predeterminado es «%(module)s» ») y branches-template (el predeterminado es «%(module)s/%(branch)s» ). Estos atributos se usan para especificar plantillas para construir URL. El elemento branch en la definición del módulo puede especificar los atributos branch y user . Estos valores se sustituirán en las plantillas. Si algún otro está definido se usa branches-template , de lo contrario se usa trunk-template . De este modo puede omitir el repositorio para construir módulos de su rama personal o construir varios módulos desde un repositorio con una disposición no estándar.
Además de un elemento branch acepta atributos revspec para anclarse en una revisión en particular. Se acepta cualquier bzr revspec válido, por ejemplo, date:yesterday, -5, tag:0.1 para obtener la primera revisión desde ayer, 5 commits después de la etiqueta «0.1». Consulte bzr help revisionspec para ver todos los valores posibles.
Ejemplo de repositorio con los atributos template definidos:
<repository type="bzr" name="launchpad.net"
href="lp:"
trunk-template="~bzr-pqm/%(module)s/bzr.dev"
branches-template="~bzr-pqm/%(module)s/%(branch)s"/>
Ejemplo de elementos de la branch para el anterior repositorio:
<branch repo="launchpad.net"
module="bzr"
checkoutdir="bzr-next"/>
<branch repo="launchpad.net"
module="bzr"
branch="2.2"
checkoutdir="bzr-beta"/>
CVS
El tipo de repositorio se usa para definir un repositorio CVS.
El atributo password se usa para especificar la contraseña del repositorio.
El atributo cvsroot se usa para especificar la raíz del repositorio.
<repository type="cvs" name="tango.freedesktop.org"
cvsroot=":pserver:anoncvs@anoncvs.freedesktop.org:/cvs/tango"
password=""/>
Los atributos adicionales son: revision , update-new-dirs y override-checkoutdir .
Darcs
El tipo de repositorio se usa para definir un repositorio Darcs.
<repository type="darcs" name="telepathy.freedesktop.org"
href="http://projects.collabora.co.uk/darcs/telepathy/"/>
Git
El tipo de repositorio se usa para definir un repositorio Git.
<repository type="git" name="git.freedesktop.org"
href="git://anongit.freedesktop.org/git/"/>
Permite los siguientes atributos en el elemento branch :
El atributo revision se usa para especificar una rama de control local o remota a la que cambiar en la fase de actualización. La predeterminada es «master». Es posible anular este atributo con la variable de configuración branches . El cambio sólo se realizará si la rama actual está controlando una rama remota, para no interferir en su trabajo.
El atributo tag se usa para especificar una revisión que descargar siempre en la fase de actualización. Omite el atributo revision .
<branch repo="git.freedesktop.org" module="swfdec/swfdec"
checkoutdir="swfdec"
revision="rama-local-o-remota "
tag="árbol "/>
Mercurial
El tipo de repositorio se usa para definir un repositorio Mercurial.
<repository type="hg" name="hg.gtk-vnc"
href="http://gtk-vnc.codemonkey.ws/hg/" />
<branch repo="hg.gtk-vnc" module="outgoing.hg" checkoutdir="gtk-vnc"/>
Monotone
El tipo de repositorio se usa para definir un repositorio Monotone.
El atributo server se usa para especificar el servidor del repositorio.
El atributo database se usa para especificar la base de datos que usar por el repositorio.
El atributo defbranch se usa para especificar la rama del repositorio que usar.
<repository type="mtn" name="pidgin.im"
server="pidgin.im" database="pidgin.im.mtn"
defbranch="im.pidgin.pidgin"/>
Subversion
El tipo de repositorio se usa para definir un repositorio Subversion.
<repository type="svn" name="svn.gnome.org" default="yes"
href="http://svn.gnome.org/svn/"/>
Permite una revision en el elemento branch . Este atributo define la rama que se descargará o, si es un número, una revisión específica para descargar.
<branch revision="gnome-2-20"/>
Es posible especificar una disposición de svn personalizada usando trunk-template (el predeterminado es «%(module)s/trunk»), branches-template (el predeterminado es «%(module)s/branches/%(branch)s») y tags-template (el predeterminado es «%(module)s/tags/%(tag)s»)
Archivos tar
El tipo de repositorio se usa para definir un repositorio de archivos tar.
<repository type="tarball" name="dbus/dbus-python"
href="http://dbus.freedesktop.org/releases/dbus-python/"/>
Permite los siguientes atributos en el elemento branch :
El atributo module especifica el archivo que se descargará y compilará; el atributo version especifica la versión del módulo.
Los atributos size y hash , al igual que el obsoleto md5sum , son opcionales. Si estos atributos están presentes, se usan para comprobar que el paquete fuente se ha descargado correctamente.
Se puede anidar cualquier número de elementos patch dentro del elemento branch . Estos parches se aplican, en orden, al árbol de fuentes después de descomprimirlo. El atributo file proporciona el nombre de archivo del parche, y el atributo strip dice a cuántos niveles de carpetas se descenderá al aplicar el parche.
Para conjuntos de módulos empaquetados con JHBuild, los archivos de parches se buscan en la carpeta jhbuild/patches/ ; para conjuntos de módulos referidos por el URI, los archivos de parches se buscan en la misma carpeta que el archivo del conjunto de módulos, o en su subcarpeta patches/ . También es posible que el atributo file especifique un URI, en cuyo caso se descargará de esa ubicación.
<branch module="dbus-python-0.80.2.tar.gz" version="0.80.2"
repo="dbus/dbus-python"
hash="md5:2807bc85215c995bd595e01edd9d2077" size="453499">
<patch file="dbus-glib-build.patch" strip="1" />
</branch>
Un archivo tar del elemento branch puede contener también elementos quilt que especifiquen elementos branch que importar.
Incluir otros conjuntos de módulos
JHBuild permite un conjunto de módulos para incluir los contenidos referidos por otro usando el elemento include .
<include href="uri "/>
El atributo href es una referencia al URI del conjunto de módulos que se incluirá, relativa al archivo que contiene el elemento include .
Desde el conjunto de módulos referenciado sólo se importan definiciones de módulos; no fuentes de módulos. Se permiten múltiples niveles de inclusión, pero no bucles (en este momento no hay ningún código para manejar bucles).
Definiciones de módulos
Hay varios tipos de definiciones de módulos que se pueden usar en un archivo de conjunto de módulos, y la lista se puede extender fácilmente. Aquí sólo se mencionan los más comunes.
Todos ellos están compuestos básicamente de un elemento branch que describe cómo obtener el módulo y unos elementos dependencies , suggests y after para declarar las dependencias del módulo.
jhbuild build añadirá a la lista de módulos todos los módulos listados en el elemento dependencies , si no están ya incluidos, y se asegurará que los módulos dependientes se construyen primero.Después de generar la lista de módulos, los módulos listados en el elemento suggests se usarán para ordenar la futura lista de módulos (aunque no añadirá módulos adicionales). Esto se hace para casos en que un módulo tiene dependencias opcionales en otro módulo.
cmake
El elemento cmake se usa para definir un módulo que se construirá usando el sistema de construcción CMake.
<cmake id="nombre del módulo ">
<branch [ ... ] >
[...]
</branch>
<dependencies>
<dep package="nombre del módulo "/>
...
</dependencies>
<after>
<dep package="nombre del módulo "/>
...
</after>
</cmake>
distutils
El elemento distutils se usa para definir un módulo que se construirá usando las distutils de python.
<distutils id="nombre del módulo "
[ supports-non-srcdir-builds="sí|no " ]>
<branch [ ... ] >
[...]
</branch>
<dependencies>
<dep package="nombre del módulo "/>
...
</dependencies>
<after>
<dep package="nombre del módulo "/>
...
</after>
</distutils>
linux
El elemento linux define un módulo usado para construir un kernel linux. Además, se puede seleccionar una configuración del kernel aparte usando el subelemento kconfig .
<linux id="id "
[ makeargs="argumentos de make " ]>
<branch [ ... ] >
[...]
</branch>
<dependencies>
<dep package="nombre del módulo "/>
...
</dependencies>
<after>
<dep package="nombre del módulo "/>
...
</after>
<kconfig [ repo="repositorio " ]
version="versión "
[ module="módulo " ]
[ config="configuración " ] />
</linux>
perl
El elemento perl se usa para construir módulos perl.
El atributo makeargs se usa para especificar argumentos adicionales para pasárselos a make .
<perl id="nombre del módulo "
[ makeargs="makeargs " ]>
<branch [ ... ] >
[...]
</branch>
<dependencies>
<dep package="nombre del módulo "/>
...
</dependencies>
<after>
<dep package="nombre del módulo "/>
...
</after>
</perl>
waf
El elemento waf se usa para definir un módulo que se construirá con el sistema de construcción Waf.
El atributo waf-command se usa para especificar el script del comando waf a usar; el predeterminado es waf .
<waf id="nombre del módulo ">
[ waf-command="waf-command " ]>
<branch [ ... ] >
[...]
</branch>
<dependencies>
<dep package="nombre del módulo "/>
...
</dependencies>
<after>
<dep package="nombre del módulo "/>
...
</after>
</waf>
testmodule
El elemento testmodule se usa para crear un módulo que ejecute un conjunto de pruebas usado LDTP o Dogtail.
<testmodule id="id "
type="tipo ">
<branch [ ... ] >
[...]
</branch>
<dependencies>
<dep package="nombre del módulo "/>
...
</dependencies>
<after>
<dep package="nombre del módulo "/>
...
</after>
<testedmodules>
<tested package="paquete " />
</testedmodules>
</testmodule>
El atributo type contiene el tipo de pruebas que ejecutar en el módulo. «dogtail» usa Python para invocar a todos los archivos .py. «ldtp» invoca «ldtprunner run.xml».
A menos que la opción de configuración «noxvfb» esté establecida, se inicia un servidor Xvfb para ejecutar las pruebas en él
Elementos obsotelos
Repositorios de módulos
cvsroot
El elemento cvsroot está obsoleto; en su lugar, se debe usar el elemento repository .
El elemento cvsroot se usa para describir un repositorio CVS.
<cvsroot name="nombre del raíz "
[ default="sí|no " ]
root="cvsroot-anónimo "
password="contraseña-anónima "/>
El atributo name debe ser un identificador único para el repositorio CVS.
El atributo default indica si es el repositorio de módulos predeterminados para ese archivo de conjuntos de módulos.
El atributo root lista la raíz de CVS usada para acceso anónimo a este repositorio, y el atributo password da la contraseña usada para el acceso anónimo.
svnroot
El elemento svnroot está obsoleto; en su lugar se debe usar el elemento repository .
El elemento svnroot se usa para describir un repositorio de Subversion.
<svnroot name="nombre del raíz "
[ default="sí|no " ]
href="svnroot-anónimo "/>
El atributo name debe ser un identificador único para el repositorio de Subversion.
Si el atributo default indica si si este repositorio es el predeterminado para este conjunto de módulos.
El atributo href lista el URL base del repositorio. Probablemente será un URL http , https o svn .
Tipos de módulos obsoletos
Esta sección describe elementos obsoletos, aún se deben usar en conjuntos de módulos existentes, pero se recomienda que no se usen más.
archivo tar
El elemento obsoleto es sólo una fina envoltura alrededor del tipo de módulo autotools y del tipo de repositorio tarball .
El elemento tarball se usa para definir un módulo que se construirá a partir de un archivo tar.
<tarball id="nombre del módulo "
[ version="versión " ]
[ checkourdir="carpeta de descarga " ]
[ autogenargs="argumentos de autogen " ]
[ makeargs="argumentos de make " ]
[ autogen-sh="autogen-sh " ]
[ supports-non-srcdir-builds="sí|no " ]>
<source href="url fuente "
[ size="tamaño fuente " ]
[ hash="algoritmo-del-fuente:hash-del-fuente " ]
[ md5sum="suma md5 del fuente " ]/>
<patches>
<patch file="nombre del archivo " strip="nivel "/>
...
</patches>
<dependencies>
<dep package="nombre del módulo "/>
...
</dependencies>
<suggests>
<dep package="nombre del módulo "/>
...
</suggests>
</tarball>
Los atributos id y version se usan para identificar el módulo.
El elemento source especifica el archivo que se descargará y compilará. El atributo href es obligatorio mientras que los atributos size y hash , al igual que el obsoleto md5sum , son opcionales. Si los dos últimos están presentes, se usan para comprobar que el paquete fuente se ha descargado correctamente.
El elemento patches se utiliza para especificar uno o más parches para aplicarlos al árbol de fuentes después de descomprimirlo. El atributo file contiene el nombre el nombre de archivo del parche y el atributo strip dice a cuántos niveles de carpetas se descenderá al aplicar el parche.
Para conjuntos de módulos empaquetados con JHBuild, los archivos de parches se buscan en la carpeta jhbuild/patches/ ; para conjuntos de módulos referidos por el URI, los archivos de parches se buscan en la misma carpeta que el archivo del conjunto de módulos, o en su subcarpeta patches/ . También es posible que el atributo file especifique un URI, en cuyo caso se descargará de esa ubicación.
Los otros atributos y los elementos dependencies , suggests y after se procesan de la misma manera que para el comando
jhbuild-3.5.91/doc/es/es.stamp 0000644 0001750 0001750 00000000000 11743103645 015777 0 ustar 00fred fred 0000000 0000000 jhbuild-3.5.91/doc/es/es.po 0000644 0001750 0001750 00001000314 12017472601 015276 0 ustar 00fred fred 0000000 0000000 # translation of jhbuild-help.master.po to Español
#
# Jorge González , 2008, 2009, 2010.
# Daniel Mustieles , 2008, 2009, 2010, 2011, 2012.
#
msgid ""
msgstr ""
"Project-Id-Version: jhbuild-help.master\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2012-08-27 12:37+0000\n"
"PO-Revision-Date: 2012-08-27 17:39+0200\n"
"Last-Translator: Daniel Mustieles \n"
"Language-Team: Español \n"
"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=2; plural=(n!=1);\n"
"X-Generator: Gtranslator 2.91.5\n"
#. Put one translator per line, in the form NAME , YEAR1, YEAR2
msgctxt "_"
msgid "translator-credits"
msgstr "Daniel Mustieles , 2008-2012"
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#.
#. This is a reference to an external file such as an image or video. When
#. the file changes, the md5 hash will change to let you know you need to
#. update your localized copy. The msgstr is not used at all. Set it to
#. whatever you like once you have updated your copy of the file.
#: C/index.docbook:1102(imagedata)
msgctxt "_"
msgid ""
"external ref='figures/jhbuild_sample_dot_output.png' "
"md5='af9fe7edb29fcaefeadfb2f5987aa6e4'"
msgstr ""
"external ref='figures/jhbuild_sample_dot_output.png' "
"md5='af9fe7edb29fcaefeadfb2f5987aa6e4'"
#: C/index.docbook:7(articleinfo/title)
msgid "JHBuild Manual"
msgstr "Manual de JHBuild"
#: C/index.docbook:9(authorgroup/author)
msgid "James Henstridge "
msgstr "James Henstridge "
#: C/index.docbook:13(authorgroup/author)
msgid "C.J. Adams-Collier "
msgstr "C.J. Adams-Collier "
#: C/index.docbook:17(authorgroup/author)
msgid "Frederic Peters "
msgstr "Frederic Peters "
#: C/index.docbook:21(authorgroup/author)
msgid "David Turner "
msgstr "David Turner "
#: C/index.docbook:26(articleinfo/copyright)
msgid "2004, 2008 James Henstridge "
msgstr "2004, 2008 James Henstridge "
#: C/index.docbook:31(revhistory/revision)
msgid "JHBuild Manual v0.5 January 2008 "
msgstr "Manual de JHBuild v0.5 Enero 2008 "
#: C/index.docbook:35(revhistory/revision)
msgid "JHBuild Manual v0.1 August 2007 "
msgstr "Manual de JHBuild v0.1 Agosto 2007 "
#: C/index.docbook:41(abstract/para)
msgid ""
"JHBuild is a tool used to build the whole GNOME desktop from the version "
"control system. JHBuild can also be customized to build other projects too."
msgstr ""
"JHBuild es una herramienta que se usa para construir completamente el "
"escritorio GNOME desde el sistema de control de veriones. Sin embargo, se "
"puede usar para construir otros proyectos creando para ello un conjunto de "
"módulos."
#: C/index.docbook:48(section/title)
msgid "Introduction"
msgstr "Introducción"
#: C/index.docbook:50(section/para)
msgid ""
"JHBuild is a tool designed to ease building collections of source packages, "
"called modules
. JHBuild uses module set
files "
"to describe the modules available to build. The module set
"
"files include dependency information that allows JHBuild to discover what "
"modules need to be built and in what order."
msgstr ""
"JHBuild es una herramienta diseñada para construir fácilmente colecciones de "
"paquetes fuente (también conocidos como módulos
). JHBuild Usa "
"archivos de conjuntos de módulos
para describir los módulos "
"disponibles para construir. El conjuntos de módulos
incluye "
"información de las dependencias que permite a JHBuild averigüar qué módulos "
"debe construir y en qué orden."
#: C/index.docbook:57(section/para)
msgid ""
"JHBuild was originally written for building GNOME , but has since been extended to be usable with other "
"projects. A module set
file can be hosted on a web server, "
"allowing for build rules independent of the JHBuild project."
msgstr ""
"Originalmente JHBuild se escribió para construir GNOME , pero se ha extendido para hacerlo usable con "
"otros proyectos. Se puede almacenar un conjunto de módulos
en "
"un servidor web, para permitir reglas de construcción independientes de "
"JHBuild."
#: C/index.docbook:63(section/para)
msgid ""
"JHBuild can build modules from a variety of sources, including CVS , Subversion , Bazaar , Darcs , Git and Mercurial repositories, as well as Tar and Zip "
"archives hosted on web or FTP sites. JHBuild can build modules using a "
"variety of build systems, including Autotools, CMake, WAF, Python Distutils "
"and Perl Makefiles."
msgstr ""
"JHBuild puede construir módulos desde varias fuentes, incluyendo los "
"repositorios de CVS , Subversion , Bazaar , Darcs , Git y Mercurial , así como archivos "
"Zip y Tar almacenados en una web o un sitio FTP. JHBuild puede construir "
"módulos usando varios sistemas de construcción, incluyendo Autotools, CMake, "
"WAF, Python Distutils y Perl Makefiles."
#: C/index.docbook:74(section/para)
msgid ""
"JHBuild is not intended as a replacement for the distribution's package "
"management system. Instead, it makes it easy to build software into a "
"separate install prefix without interfering with the rest of the system."
msgstr ""
"JHBuild no está pensado para sustituir al sistema de mantenimiento de "
"paquetes de la distribución. En cambio, facilita la construcción de software "
"con un prefijo de instalación diferente, sin interferir con el resto del "
"sistema."
#: C/index.docbook:81(section/title)
msgid "Getting Started"
msgstr "Inicio"
#: C/index.docbook:83(section/para)
msgid ""
"JHBuild requires a few set up steps to be run before building software. "
"JHBuild requires some prerequisite software, and it is necessary to install "
"prerequisite tools needed to obtain and build the software modules."
msgstr ""
"JHBuild requiere unos pocos pasos para configurarlo antes de construir "
"software. JHBuild requiere algunos prerrequisitos software, y es necesario "
"instalar las herramientas de prerrequisitos necesarias para obtener y "
"construir los módulos de software."
#: C/index.docbook:89(section/title)
msgid "Installing JHBuild"
msgstr "Instalar JHBuild"
#: C/index.docbook:91(section/para)
msgid ""
"JHBuild requires a Python runtime. Verify Python >= 2.3 is installed."
msgstr ""
"JHBuild requiere una rutina de Python. Verifique que Python >= 2.3 está "
"instalado."
#: C/index.docbook:94(section/para)
msgid ""
"The recommended way to download JHBuild is via the version control system, "
"git . This can be achieved with the following command. It "
"is recommended to run the command from a new directory where all source code "
"will be installed, for example, ~/checkout/gnome ."
msgstr ""
"La forma recomendada de descargar JHBuild es a través del sistema de control "
"de versiones, git . Esto puede hacerlo con el siguiente "
"comando. Se recomienda ejecutarlo en una carpeta nueva donde se instalará "
"todo el código fuente, por ejemplo, ~/checkout/gnome ."
#: C/index.docbook:100(section/screen)
#, no-wrap
msgid ""
"$ git clone git://git.gnome.org/jhbuild \n"
"... \n"
"$ "
msgstr ""
"$ git clone git://git.gnome.org/jhbuild \n"
"... \n"
"$ "
#: C/index.docbook:104(section/para)
msgid ""
"This will download JHBuild into a new folder named jhbuild under the current directory. Now to build and install JHBuild:"
msgstr ""
"Esto descargará JHBuild en una nueva carpeta llamada jhbuild en la carpeta actual. Ahora, para construir e instalar JBuild:"
#: C/index.docbook:108(section/screen)
#, no-wrap
msgid ""
"$ cd jhbuild \n"
"$ ./autogen.sh \n"
"... \n"
"$ make \n"
"... \n"
"$ make install \n"
"... \n"
"$ "
msgstr ""
"$ cd jhbuild \n"
"$ ./autogen.sh \n"
"... \n"
"$ make \n"
"... \n"
"$ make install \n"
"... \n"
"$ "
#: C/index.docbook:117(section/para)
msgid ""
"If gnome-common , yelp-tools and autotools are available, "
"autogen.sh will configure JHBuild to install via "
"autotools . If gnome-common, yelp-tools and "
"autotools are not available, autogen."
"sh will configure JHBuild to install via a plain Makefile. To "
"always use the plain Makefile method pass --simple-install "
"to autogen.sh ."
msgstr ""
"Si gnome-common , yelp-tools y autotools está disponibles, "
"autogen.sh configurará JHBuild para instalarlos "
"mediante autotools . Si gnome-common, yelp-tools y "
"autotools no está disponibles, autogen."
"sh configurará JHBuild para instalarlos mediante un Makefile. "
"Para usar siempre el método del Makefile, pase --simple-install a autogen.sh ."
#: C/index.docbook:130(section/para)
msgid ""
"If the above steps complete successfully, a small shell script will be "
"installed in ~/.local/bin to start JHBuild. Add "
"~/.local/bin to the PATH :"
msgstr ""
"Si estos pasos se completan correctamente se instalará una pequeña línea de "
"comandos en ~/.local/bin para iniciar JHBuild. Añada "
"~/.local/bin a la variable PATH :"
#: C/index.docbook:134(section/screen)
#, no-wrap
msgid ""
"$ PATH=$PATH:~/.local/bin \n"
"$ "
msgstr ""
"$ PATH=$PATH:~/.local/bin \n"
"$ "
#: C/index.docbook:137(section/para)
msgid ""
"To permanently add ~/.local/bin to the PATH variable, run the following command:"
msgstr ""
"Para añadir permanentemente ~/.local/bin a la variable "
"PATH , ejecute el siguiente comando:"
#: C/index.docbook:140(section/screen)
#, no-wrap
msgid ""
"\n"
"$ echo PATH=$PATH:~/.local/bin >> ~/.bashrc \n"
"$ "
msgstr ""
"\n"
"$ echo PATH=$PATH:~/.local/bin >> ~/.bashrc \n"
"$ "
#: C/index.docbook:146(section/title)
msgid "Configuring JHBuild"
msgstr "Configurar JHBuild"
#: C/index.docbook:148(section/para)
msgid ""
"JHBuild can be configured via a configuration file. The default location is "
"~/.config/jhbuildrc . If a configuration file does not "
"exist, the defaults are used. The configuration file uses Python syntax. An "
"example is provided, see examples/sample.jhbuildrc . "
"Copy examples/sample.jhbuildrc to ~/.config/"
"jhbuildrc and customize as required."
msgstr ""
"Se puede configurar JHBuild mediante el archivo de configuración. su "
"ubicación predeterminada es ~/.config/jhbuildrc . Si no "
"existe un archivo de configuración, se usarán los valores predeterminados. "
"El archivo de configuración usa la sintaxis de Python. Se proporciona un "
"ejemplo en examples/sample.jhbuildrc . Copie "
"examples/sample.jhbuildrc a ~/.config/"
"jhbuildrc y personalícelo como necesite."
#: C/index.docbook:157(section/para)
msgid ""
"The sample configuration will make JHBuild build the meta-gnome-"
"core and meta-gnome-apps-tested "
"modules and dependencies from the gnome-apps module "
"set. JHBuild will unpack source trees to ~/checkout/gnome and install all files to subdirectories of /opt/gnome. The two directories must be writable."
msgstr ""
"La configuración de ejemplo hará que JHBuild construya los módulos "
"meta-gnome-core y meta-gnome-apps-"
"tested y sus dependencias desde el conjunto de módulos "
"gnome-apps . JHBuild descomprimirá los árboles de "
"fuentes en ~/checkout/gnome e instalará todos los "
"archivos en subcarpetas de /opt/gnome . Las dos carpetas "
"deben ser escribibles."
#: C/index.docbook:166(section/para)
msgid ""
"Configuration variables are documented in . The most commonly used variables are:"
msgstr ""
"Las variables de configuración están documentadas en repos "
msgstr "repos "
#: C/index.docbook:177(listitem/simpara)
msgid ""
"A dictionary that can be used to specify an alternative repository location "
"for a particular repository. This configuration variable is useful to a "
"module developer. By default, JHBuild will check out code from repositories "
"using an anonymous repository location. The dictionary keys are short "
"repository names and the values are alternative repository location strings. "
"For example:"
msgstr ""
"Un diccionario que puede usarse para especificar la ubicación de un "
"repositorio alternativo para uno en particular. Esta variable de "
"configuración es útil para un desarrollador de módulos. De manera "
"predeterminada, JHBuild descargará código de los repositorios usando una "
"ubicación de repositorio anónima. Las claves del diccionario son nombres "
"cortos de repositorios y los valores son las cadenas de ubicación de los "
"repositorios alternativos. Por ejemplo:"
#: C/index.docbook:185(listitem/programlisting)
#, no-wrap
msgid "repos['git.gnome.org'] = 'ssh://username @git.gnome.org/git/'"
msgstr "repos['git.gnome.org'] = 'ssh://nombre_de_usuario @git.gnome.org/git/'"
#: C/index.docbook:189(varlistentry/term)
msgid "moduleset "
msgstr "moduleset "
#: C/index.docbook:193(listitem/simpara)
#: C/index.docbook:1884(listitem/simpara)
msgid ""
"A string or list of strings specifying the name(s) of the module set(s) to "
"use. This can either be the filename of a moduleset included with JHBuild "
"(excluding the path and extension), or a full HTTP URL to an externally "
"managed moduleset. HTTP URL modulesets are cached locally. If a module with "
"the same name is present in more than one moduleset, the last set listed "
"takes priority. Modulesets provided with JHBuild are updated to match the "
"current GNOME development release."
msgstr ""
"Una cadena o una lista de cadenas que contiene los nombres de los conjuntos "
"de módulos que se usarán. También puede ser el nombre de archivo de un "
"conjunto de módulos incluido en JHBuild (excluyendo la ruta y la extensión), "
"o un URL completo a un conjunto de módulos administrado externamente. Los "
"URL se almacenan localmente en la caché. si un módulo con el mismo nombre "
"aparece en más de un conjunto de módulos, tendrá prioridad la última lista "
"configurada. Los conjuntos de módulos proporcionados con JHBuild se "
"actualizan para que coincididan con la versión liberada de desarrollo de "
"GNOME."
#: C/index.docbook:204(varlistentry/term)
msgid "modules "
msgstr "modules "
#: C/index.docbook:208(listitem/simpara)
#: C/index.docbook:1871(listitem/simpara)
msgid ""
"A list of strings specifying the modules to build. The list of modules "
"actually built will be recursively expanded to include all the dependencies "
"unless the buildone command is used. Defaults to ['meta-gnome-desktop']"
" ."
msgstr ""
"Una lista de cadenas especificando los módulos que construir. La lista de "
"los módulos actualmente construidos se expandirá recursivamente para incluir "
"todas las dependencias, salvo que se use el comando buildone . Su valor "
"predeterminado es ['meta-gnome-desktop'] ."
#: C/index.docbook:217(varlistentry/term)
msgid ""
"checkoutroot "
msgstr ""
"checkoutroot "
#: C/index.docbook:221(listitem/simpara)
msgid ""
"A string specifying the directory to unpack source trees to. Unless buildroot is set, "
"builds will occur in this directory too. Defaults to ~/checkout/"
"gnome ."
msgstr ""
"Una cadena que especifica la carpeta donde descomprimir los árboles de "
"fuentes. A menos que buildroot esté configurado, las construcciones se harán también en "
"esta carpeta. La predeterminada es ~/checkout/gnome ."
#: C/index.docbook:229(varlistentry/term)
msgid "prefix "
msgstr "prefix "
#: C/index.docbook:233(listitem/simpara)
#: C/index.docbook:2002(listitem/simpara)
msgid ""
"A string specifying the prefix to install modules to. prefix must be an absolute path. This directory must be writable. Defaults "
"to '/opt/gnome' ."
msgstr ""
"Una cadena que indica el prefijo donde instalar módulos.prefix debe ser una ruta absoluta. Esta carpeta debe ser escribible. La "
"carpeta predeterminada es «/opt/gnome» ."
#: C/index.docbook:240(varlistentry/term)
msgid "autogenargs "
msgstr ""
"autogenargs "
#: C/index.docbook:244(listitem/simpara)
msgid ""
"A string containing arguments passed to the autogen.sh "
"script of all modules. Can be overridden for particular modules using the "
"module_autogenargs dictionary."
msgstr ""
"Una cadena que contiene los argumentos pasados al script autogen."
"sh de todos los módulos. Se pueden omitir para algunos módulos "
"concretos usando el diccionario module_autogenargs ."
#: C/index.docbook:252(varlistentry/term)
msgid "makeargs "
msgstr "makeargs "
#: C/index.docbook:256(listitem/simpara)
#: C/index.docbook:1733(listitem/simpara)
#| msgid ""
#| "A string listing additional arguments to be passed to make. Defaults to '' ."
msgid ""
"A string listing additional arguments to be passed to make. JHBuild will automatically append the parallel execution option "
"(-j ) based upon available CPU cores. Defaults to "
"'' ."
msgstr ""
"Una cadena que lista argumentos adicionales para pasarlos a make. JHBuild añadirá automáticamente la opción de ejecución en paralelo "
"(-j ) basándose en la disponibilidad de los núcleos de la "
"CPU. Lo predeterminado es '' ."
#: C/index.docbook:266(section/title)
msgid "Build Prerequisites"
msgstr "Prerrequisitos para la construcción"
#: C/index.docbook:268(section/para)
msgid ""
"Before any modules can be built, it is necessary to have certain build tools "
"installed. Common build tools include the GNU Autotools "
"(autoconf , automake , "
"libtool and gettext ), "
"The GNU Toolchain (binutils , gcc, g++ ), make, pkg-config and Python, "
"depending on which modules will be built."
msgstr ""
"Antes de poder construir cualquier módulo es necesario tener ciertas "
"herramientas de construcción instaladas. Las herramientas habituales "
"incluyen las GNU Autotools (autoconf , "
"automake , libtool y "
"gettext ), Las GNU Toolchain "
"(binutils , gcc , "
"g++ ), make, pkg-config y Python, dependiendo de "
"qué módulos se construirán."
#: C/index.docbook:277(section/para)
msgid ""
"JHBuild can check the tools are installed using the sanitycheck command:"
msgstr ""
"JHBuild puede comprobarlas herramientas están instaladas usando el comando "
"sanitycheck :"
#: C/index.docbook:280(section/screen)
#, no-wrap
msgid "$ jhbuild sanitycheck "
msgstr "$ jhbuild sanitycheck "
#: C/index.docbook:282(section/para)
msgid ""
"If this command displays any messages, please install the required package "
"from your distribution's repository. A list of package names for different "
"distributions is maintained on the GNOME wiki. Run the sanitycheck command again after installing the distribution's packages to "
"ensure the required tools are present."
msgstr ""
"Si el comando muestra algún mensaje, instale el paquete requerido del "
"repositorio de su distribución. El wiki de GNOME mantiene una lista de "
"nombres de "
"paquetes para diferentes distribuciones. Ejecute otra vez el comando "
"sanitycheck depsués de instalar los paquetes para "
"asegurarse de que las herramientas necesarias están instaladas."
#: C/index.docbook:292(section/title)
msgid "Using JHBuild"
msgstr "Usar JHBuild"
#: C/index.docbook:294(section/para)
msgid ""
"After set up is complete, JHBuild can be used to build software. To build "
"all the modules selected in the ~/.config/jhbuildrc "
"file, run the following command:"
msgstr ""
"Después de que todo esté configurado, se puede usar JHBuild para construir "
"software. Para construir los todos módulos seleccionados en el archivo "
"~/.config/jhbuildrc ., ejecute el siguiente comando:"
#: C/index.docbook:299(section/screen)
#, no-wrap
msgid "$ jhbuild build "
msgstr "$ jhbuild build "
#: C/index.docbook:301(section/para)
msgid ""
"JHBuild will download, configure, compile and install each of the modules. "
"If an error occurs at any stage, JHBuild will present a menu asking what to "
"do. The choices include dropping to a shell to fix the error, rerunning the "
"build from various stages, giving up on the module, or ignore the error and "
"continue."
msgstr ""
"JHBuild descargará, configurará, compilará e instalará cada uno de los "
"módulos. Si ocurre un error en cualquier fase, JHBuild mostrará un menú "
"preguntando qué hacer. Estas opciones incluyen salir a una consola para "
"reparar el error, volver a ejecutar la construcción desde varias fases, "
"abandonar el módulo, o ignorar el error y continuar."
#: C/index.docbook:308(note/simpara)
msgid ""
"Giving up on a module will cause any modules depending on the module to fail."
msgstr ""
"Desistir de cargar un módulo causará que todos los módulos que dependan de "
"él fallen."
#: C/index.docbook:312(section/para)
msgid "Below is an example of the menu displayed:"
msgstr "Debajo hay un ejemplo con el menú mostrado:"
#: C/index.docbook:314(section/screen)
#, no-wrap
msgid ""
" [1] Rerun phase build\n"
" [2] Ignore error and continue to install\n"
" [3] Give up on module\n"
" [4] Start shell\n"
" [5] Reload configuration\n"
" [6] Go to phase \"wipe directory and start over\"\n"
" [7] Go to phase \"configure\"\n"
" [8] Go to phase \"clean\"\n"
" [9] Go to phase \"distclean\"\n"
"choice: "
msgstr ""
" [1] Volver a ejecutar la fase de construcción\n"
" [2] Ignorar error y continuar la instalación\n"
" [3] Desistir de cargar el módulo\n"
" [4] Iniciar consola\n"
" [5] Recargar configuración\n"
" [6] Ir a la fase «limpiar carpeta y empezar»\n"
" [7] Ir a la fase «configurar»\n"
" [8] Ir a la fase «limpiar»\n"
" [9] Ir a la fase «distclean»\n"
"choice: "
#: C/index.docbook:325(section/para)
msgid ""
"It is also possible to build a different set of modules and their "
"dependencies by passing the module names as arguments to the build command. For example, to build gtk+:"
msgstr ""
"También es posible construir un conjunto de módulos diferentes y sus "
"dependencias pasando los nombres de módulos como argumentos al comando "
"build . Por ejemplo, para construir gtk+:"
#: C/index.docbook:329(section/screen)
#, no-wrap
msgid "$ jhbuild build gtk+ "
msgstr "$ jhbuild build gtk+ "
#: C/index.docbook:331(section/para) C/index.docbook:352(section/para)
msgid ""
"If JHBuild is cancelled part way through a build, it is possible to resume "
"the build at a particular module using the --start-at "
"option:"
msgstr ""
"Si por cualquier razón sale de JHBuild a mitad de una construcción, es "
"posible recuperar la construcción en un momento particular utilizando la "
"opción --start-at :"
#: C/index.docbook:335(section/screen)
#, no-wrap
msgid "$ jhbuild build --start-at=pango "
msgstr "$ jhbuild build --start-at=pango "
#: C/index.docbook:337(section/para)
msgid ""
"To build one or more modules, ignoring their dependencies, JHBuild provides "
"the buildone command. For the buildone "
"command to complete successfully, all dependencies must be previously built "
"and installed or provided by distribution packages."
msgstr ""
"Para construir uno o más módulos, ignorando sus dependencias, JHbuild "
"proporciona el comando buildone . Para que el comando "
"buildone funcione correctamente, previamente debe "
"construir e instalar todas las dependencias, manualmente o desde los "
"paquetes de la distribución."
#: C/index.docbook:343(section/screen)
#, no-wrap
msgid "$ jhbuild buildone gtk+ "
msgstr "$ jhbuild buildone gtk+ "
#: C/index.docbook:345(section/para)
msgid ""
"When actively developing a module, you are likely in a source working "
"directory. The make will invoke the build system and "
"install the module. This will be a key part of your edit-compile-install-"
"test cycle."
msgstr ""
"Cuando desarrolla activamente un módulo, generalmente está en una carpeta de "
"trabajo. El comando make invocará al sistema de "
"construcción e instalará el módulo. Esto será una parte clave de su ciclo de "
"edición-compilación-instalación-pruebas."
#: C/index.docbook:350(section/screen)
#, no-wrap
msgid "$ jhbuild make "
msgstr "$ jhbuild make "
#: C/index.docbook:356(section/para)
msgid ""
"To get a list of the modules and dependencies JHBuild will build, and the "
"order they will be built, use the list command:"
msgstr ""
"Para obtener una lista de los módulos y las dependencias que JHBuild "
"construirá, y el orden en que se construirán, use el comando list:"
#: C/index.docbook:360(section/screen)
#, no-wrap
msgid "$ jhbuild list "
msgstr "$ jhbuild list "
#: C/index.docbook:362(section/para)
msgid ""
"To get information about a particular module, use the info command:"
msgstr ""
"Para obtener información acerca de un módulo en particular, use el comando "
"info :"
#: C/index.docbook:365(section/screen)
#, no-wrap
msgid "$ jhbuild info gtk+ "
msgstr "$ jhbuild info gtk+ "
#: C/index.docbook:367(section/para)
msgid ""
"To download or update all the software sources without building, use the "
"update command. The update command "
"provides an opportunity to modify the sources before building and can be "
"useful if internet bandwidth varies."
msgstr ""
"Para descargar o actualizar todas las fuentes de software sin construir use "
"el comando update . El comando update "
"ofrece la oportunidad de modificar las fuentes antes de construir y puede "
"ser útil si el ancho de banda de Internet varía."
#: C/index.docbook:372(section/screen)
#, no-wrap
msgid "$ jhbuild update "
msgstr "$ jhbuild update "
#: C/index.docbook:374(section/para)
msgid ""
"Later, JHBuild can build everything without downloading or updating the "
"sources:"
msgstr ""
"Posteriormente JHBuild puede construir todo sin descargar ni actualizar los "
"fuentes:"
#: C/index.docbook:377(section/screen)
#, no-wrap
msgid "$ jhbuild build --no-network "
msgstr "$ jhbuild build --no-network "
#: C/index.docbook:379(section/para)
msgid ""
"To run a particular command with the same environment used by JHBuild, use "
"the run command:"
msgstr ""
"Para ejecutar un comando concreto con el mismo entorno que usa JHBuild, use "
"el comando run :"
#: C/index.docbook:382(section/screen)
#, no-wrap
msgid "$ jhbuild run program "
msgstr "$ jhbuild run programa "
#: C/index.docbook:384(section/para)
msgid ""
"To start a shell with the same environment used by JHBuild, use the "
"shell command:"
msgstr ""
"Para iniciar una consola con el mismo entorno usado por JHBuild use el "
"comando shell :"
#: C/index.docbook:387(section/screen)
#, no-wrap
msgid "$ jhbuild shell "
msgstr "$ jhbuild shell "
#: C/index.docbook:392(section/title)
msgid "JHBuild and GNOME"
msgstr "JHBuild y GNOME"
#: C/index.docbook:394(section/para)
msgid ""
"This section provides guidance on building, installing and running GNOME."
msgstr ""
"Esta sección proporciona directrices para construir, instalar y ejecutar "
"GNOME."
#: C/index.docbook:398(section/title)
msgid "Building GNOME"
msgstr "Construir GNOME"
#: C/index.docbook:400(section/para)
msgid "To build GNOME some development packages are required. This includes:"
msgstr ""
"Para construir GNOME se requieren algunos paquetes de desarrollo. Esto "
"incluye:"
#: C/index.docbook:405(listitem/simpara)
msgid ""
"DocBook XML DTD and XSLT stylesheets. These need to be registered in the XML "
"catalog (/etc/xml/catalog )."
msgstr ""
"DocBook XML DTD y hojas de estilo XSLT. Deben registrarse en el catálogo XML "
"(/etc/xml/catalog )."
#: C/index.docbook:410(listitem/simpara)
msgid "X libraries"
msgstr "Bibliotecas de las X"
#: C/index.docbook:413(listitem/simpara)
msgid ""
"libsmbclient from Samba (used for browsing Windows "
"networks)."
msgstr ""
"libsmbclient de Samba (usado para examinar redes "
"Windows)."
#: C/index.docbook:417(listitem/simpara)
msgid "libbz2 from bzip2."
msgstr "libbz2 de bzip2."
#: C/index.docbook:420(listitem/simpara)
msgid ""
"libpng , libjpeg and "
"libtiff (used for image loading)."
msgstr ""
"libpng , libjpeg y "
"libtiff (usada para cargar imágenes)."
#: C/index.docbook:425(section/para)
msgid ""
"If installing distribution packages, and if applicable for your "
"distribution, install the corresponding dev
or devel packages. A list of package names for different distributions is "
"maintained on the GNOME wiki."
msgstr ""
"Si está instalando paquetes de su distribución, y si es aplicable a ésta, "
"instale los paquetes dev
o devel
"
"correspondientes. En el wiki de GNOME se mantiene una lista de nombres de paquetes "
"para las distintas distribuciones."
#: C/index.docbook:434(section/title)
msgid "Running a Single GNOME Application"
msgstr "Ejecutar una única aplicación de GNOME"
#: C/index.docbook:436(section/para)
msgid ""
"This section details how to run a single GNOME application. The application "
"will run within the current desktop environment. To run the application "
"within the complete JHBuild GNOME see ."
msgstr ""
"Esta sección detalla como ejecutar una única aplicación de GNOME. La "
"aplicación se ejecutará dentro del actual entorno de escritorio. Para "
"ejecutar la aplicación dentro de GNOME JHBuild completo consulte la ."
#: C/index.docbook:441(section/para)
msgid ""
"Launch a JHBuild shell. The JHBuild shell has all the necessary environment "
"variables set."
msgstr ""
"Lanzar una consola de JHBuild. La consola de JHBuild tiene configuradas "
"todas las variables de entorno necesarias."
#: C/index.docbook:444(section/screen)
#, no-wrap
msgid "$ jhbuild shell "
msgstr "$ jhbuild shell "
#: C/index.docbook:446(section/para)
msgid "Verify the correct application will be run. For example:"
msgstr "Verificar que se ejecutará la aplicación correcta. Por ejemplo:"
#: C/index.docbook:448(section/screen)
#, no-wrap
msgid ""
"$ which gedit \n"
"/opt/gnome/bin/gedit"
msgstr ""
"$ which gedit \n"
"/opt/gnome/bin/gedit"
#: C/index.docbook:451(section/para)
msgid "Run the application:"
msgstr "Ejecutar la aplicación:"
#: C/index.docbook:453(section/screen)
#, no-wrap
msgid "$ gedit & "
msgstr "$ gedit & "
#: C/index.docbook:455(section/para)
msgid ""
"Alternatively, run the application using the run command:"
msgstr ""
"Alternativamente, ejecute la aplicación usando el comando run:"
#: C/index.docbook:458(section/screen)
#, no-wrap
msgid "$ jhbuild run gedit "
msgstr "$ jhbuild run gedit "
#: C/index.docbook:462(section/title)
msgid "Running the GNOME Desktop Environment"
msgstr "Ejecutar el entorno de escritorio GNOME"
#: C/index.docbook:464(section/para)
msgid ""
"Create a new user account to run the JHBuild GNOME. Running JHBuild GNOME "
"using different user account is recommended to avoid problems caused by user "
"settings stored in the home directory. This manual refers to the new account "
"as gnomedev ."
msgstr ""
"Crear una cuenta de usuario nueva para ejecutar JHBuild GNOME. Se recomienda "
"ejecutar JHBuild GNOME con un usuario diferente para evitar problemas "
"causados por configuraciones de usuario guardadas en la carpeta del usuario. "
"Este manual se refiere a la cuenta nueva como gnomedev ."
#: C/index.docbook:470(section/para)
msgid ""
"Setup JHBuild on the new gnomedev account. Copy or soft-link ~/.config/jhbuildrc and ~/.local/bin/jhbuild to gnomedev home directory."
msgstr ""
"Configure JHBuild en la cuenta gnomedev nueva. Copie o cree un enlace simbólico de ~/.config/"
"jhbuildrc y ~/.local/bin/jhbuild a la "
"carpeta del usuario gnomedev ."
#: C/index.docbook:477(section/para)
msgid ""
"Open a terminal as the user gnomedev. Permanently add ~/.local/bin to the "
"PATH variable, run the following command:"
msgstr ""
"Abrir una terminal como usuario gnomedev. Para añadir permanentemente ~/.local/bin a "
"la variable PATH , ejecute el siguiente comando:"
#: C/index.docbook:482(section/screen)
#, no-wrap
msgid "$ echo PATH=$PATH:~/.local/bin >> ~/.bashrc "
msgstr "$ echo PATH=$PATH:~/.local/bin >> ~/.bashrc "
#: C/index.docbook:484(section/para)
msgid "Test JHBuild works:"
msgstr "Probar si JHBuild funciona:"
#: C/index.docbook:486(section/screen)
#, no-wrap
msgid ""
"$ jhbuild run pkg-config gtk+-2.0 --modversion \n"
"2.20.1"
msgstr ""
"$ jhbuild run pkg-config gtk+-2.0 --modversion \n"
"2.20.1"
#: C/index.docbook:490(section/title)
msgid "Setup GNOME to run from the display manager"
msgstr "Configurar GNOME para ejecutarse desde el gestor de ventanas"
#: C/index.docbook:492(section/para)
msgid "Build and install JHBuild GNOME."
msgstr "Construir e instalar JHBuild GNOME"
#: C/index.docbook:494(section/para)
msgid ""
"Enable system services. JHBuild GNOME will use the /usr/bin system D-Bus daemon and the system "
"services within /usr/share/dbus-1/system-services/ . "
"JHBuild GNOME will use the JHBuild session D-Bus "
"daemon and the services within /opt/gnome/share/dbus-1/services/ /opt/"
"gnome with GNOME install prefix in the command "
"below:"
msgstr ""
"Activar servicios del sistema. JHBuild GNOME usará el demonio D-"
"Bus del sistema /usr/bin y los servicios "
"del sistema con /usr/share/dbus-1/system-services/ . "
"JHBuild GNOME usará el demonio de sesión D-Bus de "
"JHBuild y los servicios con /opt/gnome /"
"share/dbus-1/services//opt/gnome "
"con el prefix de instalación de GNOME en el siguiente "
"comando:"
#: C/index.docbook:504(section/screen)
#, no-wrap
msgid ""
"$ rm -rf /opt/gnome /var/run/dbus \n"
"$ ln -s /var/run/dbus /opt/gnome /var/run/dbus \n"
"$ rm -rf /opt/gnome /var/lib/dbus/machine-id \n"
"$ ln -s /var/lib/dbus/machine-id /opt/gnome /var/lib/dbus/machine-id "
msgstr ""
"$ rm -rf /opt/gnome /var/run/dbus \n"
"$ ln -s /var/run/dbus /opt/gnome /var/run/dbus \n"
"$ rm -rf /opt/gnome /var/lib/dbus/machine-id \n"
"$ ln -s /var/lib/dbus/machine-id /opt/gnome /var/lib/dbus/machine-id "
#: C/index.docbook:509(section/para)
msgid ""
"Create a GNOME startup script at /usr/bin/gnome-jhbuild-session with the following, replacing /opt/gnome with "
"GNOME install prefix :"
msgstr ""
"Cree un script de inicio de GNOME en /usr/bin/gnome-jhbuild-"
"session con el siguiente contenido, sustituyendo /opt/"
"gnome por el prefix de instalación de GNOME :"
#: C/index.docbook:514(section/programlisting)
#, no-wrap
msgid ""
"#!/bin/sh\n"
"\n"
"GNOME=/opt/gnome \n"
" \n"
"GDK_USE_XFT=1\n"
"XDG_DATA_DIRS=$XDG_DATA_DIRS:$GNOME/share\n"
"XDG_CONFIG_DIRS=$XDG_CONFIG_DIRS:$GNOME/etc/xdg\n"
"\n"
"jhbuild run gnome-session\n"
msgstr ""
"#!/bin/sh\n"
"\n"
"GNOME=/opt/gnome \n"
" \n"
"GDK_USE_XFT=1\n"
"XDG_DATA_DIRS=$XDG_DATA_DIRS:$GNOME/share\n"
"XDG_CONFIG_DIRS=$XDG_CONFIG_DIRS:$GNOME/etc/xdg\n"
"\n"
"jhbuild run gnome-session\n"
#: C/index.docbook:525(section/para)
msgid ""
"Make the file /usr/bin/gnome-jhbuild-session executable:"
msgstr ""
"Haga ejecutable el archivo /usr/bin/gnome-jhbuild-session:"
#: C/index.docbook:528(section/screen)
#, no-wrap
msgid "$ chmod a+x /usr/bin/gnome-jhbuild-session "
msgstr "$ chmod a+x /usr/bin/gnome-jhbuild-session "
#: C/index.docbook:530(section/para)
msgid ""
"To add a new session entry in the display manager, create /usr/"
"share/xsessions/gnome-jhbuild.desktop and enter:"
msgstr ""
"Para añadir una entrada de sesión nueva en el gestor de sesiones, cree "
"/usr/share/xsessions/gnome-jhbuild.desktop e introduzca:"
#: C/index.docbook:534(section/programlisting)
#, no-wrap
msgid ""
"[Desktop Entry]\n"
"Name=GNOME (JHBuild)\n"
"Comment=This session logs you into GNOME testing session\n"
"TryExec=/usr/bin/gnome-jhbuild-session\n"
"Exec=/usr/bin/gnome-jhbuild-session\n"
"Icon=\n"
"Type=Application"
msgstr ""
"[Desktop Entry]\n"
"Name=GNOME (JHBuild)\n"
"Comment=Esta sesión inicia la sesión de pruebas de GNOME\n"
"TryExec=/usr/bin/gnome-jhbuild-session\n"
"Exec=/usr/bin/gnome-jhbuild-session\n"
"Icon=\n"
"Type=Application"
#: C/index.docbook:542(section/para)
msgid "Restart gdm ."
msgstr "Reiniciar gdm ."
#: C/index.docbook:548(section/title)
msgid "Running GNOME from the display manager"
msgstr "Ejecutar GNOME desde el gestor de ventanas"
#: C/index.docbook:550(section/para)
msgid ""
"To run the JHBuild GNOME, select the GNOME (JHBuild) session at the display "
"manager before entering gnomedev "
"login credentials. If successful, JHBuild GNOME will be displayed. If "
"unsuccessful, check the log file. The log file will be located at "
"~gnomedev/.cache/gdm/session.log or "
"~gnomedev/.xsession-errors ."
msgstr ""
"Para ejecutar JHBuild GNOME seleccione la sesión GNOME (JHBuild) en el "
"gestor de ventanas antes de introducir las credenciales de inicio de sesión "
"de gnomedev . Si es correcto, se "
"mostrará JHBuild GNOME. Si es incorrecto, compruebe el archivo de registro "
"que se encuentra en ~gnomedev/.cache/gdm/session.log o "
"en ~gnomedev/.xsession-errors ."
#: C/index.docbook:562(section/title)
msgid "Buildbot Integration"
msgstr "Integración con buildbot"
#: C/index.docbook:564(section/para)
msgid ""
"Coupled with the Buildbot "
"project, JHBuild can also function as a continuous integration tool. The "
"Buildbot configuration is used by the GNOME project at build.gnome.org ."
msgstr ""
"Junto al proyecto Buildbot , "
"JHBuild puede funcionar también como una herramienta de integración. El "
"proyecto GNOME usa la configuración de Buildbot en build.gnome.org ."
#: C/index.docbook:570(section/title)
msgid "Configuring a Buildbot Slave"
msgstr "Configurar un Buildbot esclavo"
#: C/index.docbook:572(section/para)
msgid ""
"A Buildbot slave is a variation of a normal JHBuild installation that serves "
"the requests of a Buildbot master. It is recommended to set up JHBuild and "
"complete a build with most modules building successfully before adding the "
"Buildbot customizations."
msgstr ""
"Un Buildbot esclavo es una variación de una instalación normal de JHBuild "
"que sirve las peticiones a un Buildbot maestro. Se recomienda configurar "
"JHBuild y completar una ejecución con la mayoría de los módulos "
"construyéndose bien antes de añadir las configuraciones personalizadas de "
"Buildbot."
#: C/index.docbook:577(section/para)
msgid ""
"Buildbot commands are options to the bot command. To "
"download and install the extra required software, run the following command:"
msgstr ""
"Los comandos de Buildbot son opciones del comando bot . "
"Para descargar e instalar el software adicional requerido ejecute el "
"siguiente comando:"
#: C/index.docbook:581(section/screen)
#, no-wrap
msgid "$ jhbuild bot --setup "
msgstr "$ jhbuild bot --setup "
#: C/index.docbook:583(section/para)
msgid ""
"Once this step has completed successfully, three new configuration variables "
"are required in ~/.config/jhbuildrc ."
msgstr ""
"Una vez que este paso ha terminado correctamente, hay tres nuevas variables "
"de configuración para definir en ~/.config/jhbuildrc ."
#: C/index.docbook:588(note/para)
msgid ""
"It is not possible to use an alternate configuration file, the --file will not get desired effects."
msgstr ""
"No se puede usar un archivo alternativo de configuración. La opción --file no tendrá los efectos "
"deseados."
#: C/index.docbook:593(section/programlisting)
#, no-wrap
msgid ""
"\n"
"jhbuildbot_master = 'build.gnome.org:9070'\n"
"jhbuildbot_slavename = 'slavename'\n"
"jhbuildbot_password = 'password'\n"
msgstr ""
"\n"
"jhbuildbot_master = 'build.gnome.org:9070'\n"
"jhbuildbot_slavename = 'nombredelesclavo'\n"
"jhbuildbot_password = 'contraseña'\n"
#: C/index.docbook:599(section/para)
msgid ""
"jhbuildbot_master is a string specifying the Buildbot "
"master server; it defaults to 'build.gnome.org:9070' . "
"jhbuildbot_slavename and jhbuildbot_password identify the slave on the master server. Contact the Buildbot "
"master administrators to obtain the slave name and password."
msgstr ""
"jhbuildbot_master es una cadena que especifica el "
"servidor Buildbot maestro; el predeterminado es 'build.gnome."
"org:9070' . jhbuildbot_slavename y "
"jhbuildbot_password identifican al esclavo en el servidor "
"maestro; contacte con los administradores del servidor Buildbot maestro para "
"obtenerlos."
#: C/index.docbook:608(note/para)
msgid ""
"The administrators of build.gnome.org can be reached on the Build Brigade mailing list ."
msgstr ""
"Se puede contactar con los administradores de build.gnome.org en la lista de correo de Build Brigade ."
#: C/index.docbook:623(section/title)
msgid "Command Reference"
msgstr "Referencia de comandos"
#: C/index.docbook:625(section/para)
msgid "JHBuild uses a command line syntax similar to tools like CVS:"
msgstr ""
"JHBuild usa una sintaxis de línea de comandos similar a la de herramientas "
"como CVS:"
#: C/index.docbook:627(section/cmdsynopsis)
msgid ""
"jhbuild global-options command command-arguments jhbuild opciones globales comando argumentos del comando -f , --file config"
msgstr ""
"-f , --file configuración"
#: C/index.docbook:642(listitem/simpara)
msgid ""
"Use an alternative configuration file instead of the default ~/."
"config/jhbuildrc ."
msgstr ""
"Use un archivo de configuración alternativo, en lugar del predeterminado, "
"~/.config/jhbuildrc ."
#: C/index.docbook:647(varlistentry/term)
msgid ""
"-m , --moduleset moduleset"
msgstr ""
"-m , --moduleset conjunto de "
"módulos "
#: C/index.docbook:652(listitem/simpara)
msgid ""
"Use a module set other than the module set listed in the configuration file. "
"This option can be a relative path if the module set is located in the "
"JHBuild moduleset folder, or an absolute path if located elsewhere."
msgstr ""
"Usar un conjunto de módulos diferente del que aparece listado en el archivo "
"de configuración. Esta opción puede ser una ruta relativa si el conjunto de "
"módulos está ubicado en la carpeta de módulos de JHBuild, o una ruta "
"absoluta si está ubicado en otro sitio."
#: C/index.docbook:659(varlistentry/term)
msgid "--no-interact "
msgstr "--no-interact "
#: C/index.docbook:663(listitem/simpara)
msgid ""
"Do not prompt the user for any input. This option is useful if leaving a "
"build unattended, in order to ensure the build is not interrupted."
msgstr ""
"No solicitar al usuario ninguna entrada. Esta opción es útil cuando se deja "
"una construcción sin atender, para asegurarse de que no se interrumpe."
#: C/index.docbook:670(section/para)
msgid "Command specific options are listed below."
msgstr "A continuación se listan las opciones específicas de los comandos."
#: C/index.docbook:673(section/title)
msgid "autobuild"
msgstr "autobuild"
#: C/index.docbook:675(section/para)
msgid ""
"The autobuild command automatically builds the modules as "
"specified in the configuration file, and then upload the results to "
"JhAutobuild."
msgstr ""
"El comando autobuild construye automáticamente los "
"módulos tal y como se especifica en el archivo de configuración, y sube los "
"resultados a JhAutobuild."
#: C/index.docbook:679(section/cmdsynopsis)
msgid ""
"jhbuild autobuild --autogen --clean "
"--distcheck --skip=module --start-at=module "
"--report-url=reporturl --verbose"
msgstr ""
"jhbuild autobuild --autogen --clean "
"--distcheck --skip=