[maemo-developers] Optional build dependencies (e.g. for fremantle)
From: Till Harbaum / Lists lists at harbaum.orgDate: Wed Mar 18 14:50:00 EET 2009
- Previous message: Optional build dependencies (e.g. for fremantle)
- Next message: Optional build dependencies (e.g. for fremantle)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi, Am Dienstag 17 März 2009 schrieb Till Harbaum / Lists: > > Build-Depends: would-like-to-have-pkg1|harmless-pkg2, > > would-like-to-have-pkg2|harmless-pkg2, ... > I'll give it a try. Ok, first try yesterday was Build-Depends: maemo-version-dev, tablet-browser-interface-dev|maemo-version-dev, ... This did not install tablet-browser-interface-dev. There seems to be some optimization somewhere that makes such a shortcut impossible. So i just tried: Build-Depends: maemo-version-dev, tablet-browser-interface-dev|devscripts, ... Which works fine and pulls tablet-browser-interface-dev in. What about the package to use for this? Such a packet has some limitations: - It must not be a dependency of anything else the build depends upon. E.g. things like libpng-dev will likely always be loaded due to dependencies from the gui libs. - It must always be present - It must be something an application will normally never need to build successfully (it should never become a real dependency) This seems to be true for devscripts. Any other suggestion? Anyway, the osm2go package can now be built by chinook, diablo and fremantle autobuilders :-) Now it's time to add some "#if MAEMO_VERSION_MAJOR == 5" into the source code to adapt to the new dialog layout. Till
- Previous message: Optional build dependencies (e.g. for fremantle)
- Next message: Optional build dependencies (e.g. for fremantle)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]