Changes between Initial Version and Version 1 of OpenEmbedded


Ignore:
Timestamp:
Jul 19, 2008, 4:59:25 AM (16 years ago)
Author:
kiozen
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • OpenEmbedded

    v1 v1  
     1The latest OpenEmbedded distribution (July 2008) ships with a very outdated *bb file for GDAL (1.3.2). The usual approach of simply re-naming the file to a more up-to-date version will fail as GDAL's compilation process has been standardized to the common compilation rules. Thus all the workarounds of the old *bb file are finally void.
     2
     3For a very minimalistic compilation of GDAL for mobile devices you can use this *bb file (gdal_1.5.2.bb):
     4
     5{{{
     6DESCRIPTION = "GDAL is a translator library for raster geospatial data formats"
     7HOMEPAGE = "http://www.gdal.org/"
     8LICENSE = "MIT"
     9DEPENDS = "zlib"
     10
     11SRC_URI = "http://www.gdal.org/dl/${P}.tar.gz"
     12
     13inherit autotools pkgconfig binconfig
     14
     15#PARALLEL_MAKE = ""
     16
     17EXTRA_OECONF = "--without-perl \
     18                --without-python \
     19                --without-php \
     20                --without-ruby \
     21                --without-curl \
     22                --with-libz=internal \
     23                --with-png=internal \
     24                --with-jpeg=internal \
     25                --with-libtiff=internal \
     26                --without-expat \
     27                "
     28FILES_${PN} = "\
     29${bindir}/ \
     30${libdir}/ \
     31${datadir}/ \
     32"
     33
     34do_stage() {
     35        autotools_stage_all
     36}
     37}}}
     38
     39The file has to go into "./org.openembedded.dev/packages/gdal".  To compile GDAL you do a
     40{{{
     41bitbake gdal
     42}}}
     43
     44in your local build path.
     45
     46The very same *bb file has been reported as fix to the OpenEmbedded bug tracking system. However bug processing is slow for OpenEmbedded and geo-spatial toolkits aren't on the top priority list. Thus best practice is to check first if the changes are applied already.
     47
     48
     49
     50