Tips for making packages for qplus
[email protected] Thu, 20 Feb 2003 13:17:30 +0900
| Newsgroups | gmane.linux.qplus.devel |
|---|---|
| Message-ID | <[email protected]> |
This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C2D896.FBC98FE0 Content-Type: text/plain; charset="euc-kr" The followings are some useful tips for making packages for qplus. 1) Test your QPD file in the command line. When you just a made a new QPD file, try to validate it on command line first. # cd <projdir> # . QPLUS.sh # make menuconfig --> if it emit erros on translating QPD -> cml, there will be syntax error on your QPD file. # buildpkgs.py <pkgname> --> this build specified package. eg) # buildpkgs.py busybox --> if you get errors, you should check SPEC section of QPD file of <pkgname> package. 2) Common cases of errors - package name must be [a-Z0-9]*. In other word you can't use special characters. Therefore a name like "pkg-devel" is invalid. instead you should concatenate it like "pkgdevel". Also, A value of 'Name' tag of SPEC section must be identical with one of %%package tag of QPD section. - You can not use rpm macros at the %%files tag of QPD section due to QPD tags are processed independently not knowing upper RPM section. p.s. Pybe, please CC to the qplus-devel list when you reply. Heechul - HeeChul Yun, Embedded S/W Team at ETRI phone: +82-42-860-1673 ------_=_NextPart_001_01C2D896.FBC98FE0 Content-Type: text/html; charset="euc-kr" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; = charset=3Deuc-kr"> <META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version = 5.5.2653.12"> <TITLE>Tips for making packages for qplus</TITLE> </HEAD> <BODY> <P><FONT SIZE=3D2>The followings are some useful tips for making = packages for qplus. </FONT> </P> <P><FONT SIZE=3D2>1) Test your QPD file in the command line. </FONT> <BR><FONT SIZE=3D2>When you just a made a new QPD file, try to validate = it on command line first. </FONT> </P> <P><FONT SIZE=3D2># cd <projdir> </FONT> <BR><FONT SIZE=3D2># . QPLUS.sh </FONT> <BR><FONT SIZE=3D2># make menuconfig </FONT> <BR> <FONT SIZE=3D2>--> if = it emit erros on translating QPD -> cml, there will be syntax error = on your QPD file. </FONT> <BR><FONT SIZE=3D2># buildpkgs.py <pkgname> = </FONT> <BR> <FONT SIZE=3D2>--> = this build specified package. eg) # buildpkgs.py busybox </FONT> <BR> <FONT SIZE=3D2>--> if = you get errors, you should check SPEC section of QPD file of = <pkgname> package. </FONT> </P> <P><FONT SIZE=3D2>2) Common cases of errors </FONT> <BR><FONT SIZE=3D2>- package name must be [a-Z0-9]*. In other word you = can't use special characters. Therefore </FONT> <BR><FONT SIZE=3D2>a name like "pkg-devel" is invalid. = instead you should concatenate it like "pkgdevel". </FONT> <BR><FONT SIZE=3D2>Also, A value of 'Name' tag of SPEC section must be = identical with one of %%package tag of QPD section. </FONT> </P> <P><FONT SIZE=3D2>- You can not use rpm macros at the %%files tag of = QPD section due to </FONT> <BR><FONT SIZE=3D2>QPD tags are processed independently not knowing = upper RPM section. </FONT> </P> <BR> <P><FONT SIZE=3D2>p.s. Pybe, please CC to the qplus-devel list when you = reply. </FONT> </P> <P><FONT SIZE=3D2>Heechul</FONT> </P> <P><FONT SIZE=3D2>-</FONT> <BR><FONT SIZE=3D2>HeeChul = Yun, </FONT> <BR><FONT SIZE=3D2>Embedded S/W Team at ETRI</FONT> <BR><FONT SIZE=3D2>phone: +82-42-860-1673</FONT> </P> </BODY> </HTML> ------_=_NextPart_001_01C2D896.FBC98FE0-- ------------------------------------------------------- This SF.net email is sponsored by: SlickEdit Inc. Develop an edge. The most comprehensive and flexible code editor you can use. Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial. www.slickedit.com/sourceforge