rigacci.org

User Tools

Site Tools

Trace: • Cross compile per OpenMoko
doc:appunti:prog:openmoko_compile

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
doc:appunti:prog:openmoko_compile [2009/12/16 16:38] – niccolodoc:appunti:prog:openmoko_compile [2009/12/17 12:20] (current) – niccolo
Line 125: Line 125:
 In the example above we used some **''./configure''** options, among them: In the example above we used some **''./configure''** options, among them:
  
-**''--with-saxon=saxon-xslt''**\\ This is because we have the Debian libsaxon-java package, where the executable is called ''saxon-xslt'' instead of ''saxon''.+**''%%--with-saxon=saxon-xslt%%''**\\ This is because we have the Debian libsaxon-java package, where the executable is called ''saxon-xslt'' instead of ''saxon''.
  
-**''--enable-svg2png-scaling=16,32,48,96''**\\ For each .svg icon, render a png image of the specified size. Images will be named **''icon_XX_YY.png''**.+**''%%--enable-svg2png-scaling=16,32,48,96%%''**\\ For each .svg icon, render a png image of the specified size. Images will be named **''icon_XX_YY.png''**.
  
-**''--enable-svg2png-scaling-flag=32,48''**\\ Same as above, but only for country flag icons.+**''%%--enable-svg2png-scaling-flag=32,48%%''**\\ Same as above, but only for country flag icons.
  
  
Line 152: Line 152:
 The control file is described [[http://wiki.openmoko.org/wiki/Toolchain#Packaging_your_application|here]]. The control file is described [[http://wiki.openmoko.org/wiki/Toolchain#Packaging_your_application|here]].
  
-If you need more control files (e.g. a ''postinst'' or alike) you have to tweak with the ''om-make-ipkg'' script.  Here it is the script I use, it looks for the control files int an **''opkg''** directory, so you have to pass just the directory name containing the source tree.+If you need more control files (e.g. a ''postinst'' or alike) you have to tweak with the ''om-make-ipkg'' script.  Here it is the script I use, it looks for the control files into an **''opkg''** directory, so you have to pass just the directory name containing the source tree.
  
 <code bash> <code bash>
Line 164: Line 164:
 test x${OMTOOL_DIR} = x && . /usr/local/openmoko/arm/setup-env test x${OMTOOL_DIR} = x && . /usr/local/openmoko/arm/setup-env
 . ${OMTOOL_DIR}/arm/scripts/functions . ${OMTOOL_DIR}/arm/scripts/functions
- 
 S=${1} S=${1}
 (test x${S} = x || test ! -d ${S}) && error_exit (test x${S} = x || test ! -d ${S}) && error_exit
- 
 appname=$(basename ${S}) appname=$(basename ${S})
 tmpdir=/tmp/${appname}-ipkg-tmp tmpdir=/tmp/${appname}-ipkg-tmp
 test -e "${tmpdir}" && echo Cannot use ${tmpdir} because it already exists. && exit 1 test -e "${tmpdir}" && echo Cannot use ${tmpdir} because it already exists. && exit 1
- 
 make -C ${S} install DESTDIR="${tmpdir}" make -C ${S} install DESTDIR="${tmpdir}"
- 
 # Copy control files to destination directory. # Copy control files to destination directory.
 cp -pr opkg/* ${tmpdir} cp -pr opkg/* ${tmpdir}
- 
 ipkg-build -o 0 -g 0 ${tmpdir} ipkg-build -o 0 -g 0 ${tmpdir}
 rm -rf ${tmpdir} rm -rf ${tmpdir}
doc/appunti/prog/openmoko_compile.1260977929.txt.gz · Last modified: by niccolo