[maemo-developers] Developing for all IT platforms
From: Santtu Lakkala inz at inz.fiDate: Sat Oct 20 20:12:41 EEST 2007
- Previous message: Developing for all IT platforms
- Next message: Developing for all IT platforms
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Marius Gedminas wrote: > On Thu, Oct 18, 2007 at 10:12:29PM +0100, Neil Jerram wrote: >> Is there a recommended procedure for setting up Scratchbox so that one >> can easily compile an application and build its package for all of the >> IT platforms (i.e. ideally: 770 with latest 2006 OS, 770 with HE, N800 >> with latest 2007 OS, and N810 with whatever its OS is). > > I had Maemo 2.1 and 3.0 targets side-by-side in my Scratchbox once. I > haven't tried installing 4.0, 3.2 and 2.2 yet (actually I haven't gotten > up to installing scratchbox on my new laptop yet, it's just too tedious. > I want 'apt-get install maemo-sdk-4.0 maemo-sdk-3.2 maemo-sdk-2.2'!) I have targets for mistral/2.0 (to support mistral, scirocco and gregale), bora/3.0 (to support bora 3.0, 3.1, 3.2) and now chinook-beta to support the upcoming N810. I then compile packages first on mistral and see if they work on bora -- if they don't, rebuild with bora... >> and/or providing .install >> files, so that an IT user will easily be able to get the version of >> the package that is right for them? > > The Extras repository will generate several .install files for you, > which is a bit silly, because you want only one that works for all OS > versions. Merging them into a single .install isn't too difficult, and > the format is pretty obvious. It is documented here: > > https://stage.maemo.org/svn/maemo/projects/haf/trunk/osso-application-installer/doc/repository.txt > > Hm, it only speaks of OS2006 (where .install files are not officially > supported, but work fine nevertheless) and OS2007. I didn't find documentation for chinook .install files, but reading the source, I got the following: - ----8<----8<----8<---- [install] package = <package to be installed> catalogues = <comma separated list of repositories for the package> [<repository1>] name = <repository name> uri = <base uri> dist = <dist name> components = <components> - ----8<----8<----8<---- Of course the .install file can still include the repo_name, repo_deb and repo_deb_3. For example, mh-shot-tool install file currently looks like this: - ----8<----8<----8<---- [install] repo_name = maemo-hackers catalogues = maemo-hackers-chinook repo_deb = deb http://maemo-hackers.org/apt mistral main repo_deb_3 = deb http://maemo-hackers.org/apt bora main package = mh-shot-tool [maemo-hackers-chinook] name=Maemo Hackers for chinook uri=http://maemo-hackers.org/apt dist=chinook components=main - ----8<----8<----8<---- - -- Santtu Lakkala -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQFHGho3X9Rc0+po4p0RAtFRAJ0QbwwI920qeM5SrgiirGH5/owdswCgqRdB +wowp0L0ng6DeyQFhmPjCFU= =/0Aa -----END PGP SIGNATURE-----
- Previous message: Developing for all IT platforms
- Next message: Developing for all IT platforms
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]