Re: [maemo-developers] Building Maemo from scratch
Ah, I understand... In my grep listing, all the packages there were marked RPROVIDES. I will try what Marc suggested and add a PROVIDES line in there. I'll let the list know in a week or so. rusty On 1/23/06, Florian Boor <[EMAIL PROTECTED]> wrote: > Hi, > > Russell Geldmacher wrote: > > I was under the impression that when OE sees a package that has > > (R)DEPENDS on another package, it will go find the one marked > > (R)PROVIDES for that functionality and build it. Is that wrong? > > more or less, yes - but RDEPENDS/RPROVIDES ends up in the package dependencies > only. So if an alternate package doesn't set PROVIDES you will run into build > time dependency trouble. > > Greetings > > Florian > > -- > The dream of yesterday Florian Boor > is the hope of todayTel: 0271-771091-14 > and the reality of tomorrow.Fax: 0271-771091-19 > [Robert Hutchings Goddard, 1904][EMAIL PROTECTED] > > 6C 44 30 4C 43 20 6B 61 16 07 0F AA E6 97 70 A8 > ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Building Maemo from scratch
Marc, Thanks for the suggestion, I will try that when I get back home (in a week). rusty On 1/21/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Hi, > > Am Freitag, 20. Januar 2006 22:22 schrieb Russell Geldmacher: > > Hi Florian, > > > > I was under the impression that when OE sees a package that has > > (R)DEPENDS on another package, it will go find the one marked > > (R)PROVIDES for that functionality and build it. Is that wrong? > > as far as I remember, I just added "linux-hotplug" to the DEPENDS line of > nokia770-init_1.0.bb. This worked many month ago, but since then, many things > have changed... > > Marc > > > > rusty > > > > > >On 1/20/06, Florian Boor <[EMAIL PROTECTED]> wrote: > > > Hi, > > > > > > Russell Geldmacher wrote: > > > > I'm getting fairly far in the OE build process (for Maemo-1.0 -- we'll > > > > talk about adding 1.1 later). It eventually will fail with the > > > > following message: > > > > > > > > ERROR: Nothing provides hotplug > > > > ERROR: dependency hotplug (for nokia770-init) not satisfied > > > > NOTE: no buildable providers for nokia770-init > > > > ERROR: dependency nokia770-init (for task-bootstrap) not satisfied > > > > NOTE: no buildable providers for task-bootstrap > > > > ERROR: dependency task-bootstrap (for maemo-image) not satisfied > > > > NOTE: no buildable providers for maemo-image > > > > > > > > It seems like this hotplug issue shouldn't be happening, since at > > > > least three packages are providing hotplug. I get this from my > > > > packages directory: > > > > > > Thats not really true, they don't provide this at build time. This is > > > RPROVIDES vs. PROVIDES. Someone must have removed the hotplug packages > > > from OE... it might be possible that you can simply use hotplug-ng > > > instead of this but i didn't try this before. But the missing hotplug > > > stuff might be worth a question to OE mailingist. If this didn't happen > > > by accident i don't call this a clever idea... > > > > > > > Is there any chance you can send me your local.conf? > > > > > > I could do this, but i don't think it will help - its rather old. > > > > > > Greetings > > > > > > Florian > > > > > > -- > > > The dream of yesterday Florian Boor > > > is the hope of todayTel: 0271-771091-14 > > > and the reality of tomorrow.Fax: 0271-771091-19 > > > [Robert Hutchings Goddard, 1904][EMAIL PROTECTED] > > > > > > 6C 44 30 4C 43 20 6B 61 16 07 0F AA E6 97 70 A8 > > > > ___ > > maemo-developers mailing list > > maemo-developers@maemo.org > > https://maemo.org/mailman/listinfo/maemo-developers > ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Building Maemo from scratch
Hi, Russell Geldmacher wrote: > I was under the impression that when OE sees a package that has > (R)DEPENDS on another package, it will go find the one marked > (R)PROVIDES for that functionality and build it. Is that wrong? more or less, yes - but RDEPENDS/RPROVIDES ends up in the package dependencies only. So if an alternate package doesn't set PROVIDES you will run into build time dependency trouble. Greetings Florian -- The dream of yesterday Florian Boor is the hope of todayTel: 0271-771091-14 and the reality of tomorrow.Fax: 0271-771091-19 [Robert Hutchings Goddard, 1904][EMAIL PROTECTED] 6C 44 30 4C 43 20 6B 61 16 07 0F AA E6 97 70 A8 ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Building Maemo from scratch
Hi, Am Freitag, 20. Januar 2006 22:22 schrieb Russell Geldmacher: > Hi Florian, > > I was under the impression that when OE sees a package that has > (R)DEPENDS on another package, it will go find the one marked > (R)PROVIDES for that functionality and build it. Is that wrong? as far as I remember, I just added "linux-hotplug" to the DEPENDS line of nokia770-init_1.0.bb. This worked many month ago, but since then, many things have changed... Marc > rusty > > >On 1/20/06, Florian Boor <[EMAIL PROTECTED]> wrote: > > Hi, > > > > Russell Geldmacher wrote: > > > I'm getting fairly far in the OE build process (for Maemo-1.0 -- we'll > > > talk about adding 1.1 later). It eventually will fail with the > > > following message: > > > > > > ERROR: Nothing provides hotplug > > > ERROR: dependency hotplug (for nokia770-init) not satisfied > > > NOTE: no buildable providers for nokia770-init > > > ERROR: dependency nokia770-init (for task-bootstrap) not satisfied > > > NOTE: no buildable providers for task-bootstrap > > > ERROR: dependency task-bootstrap (for maemo-image) not satisfied > > > NOTE: no buildable providers for maemo-image > > > > > > It seems like this hotplug issue shouldn't be happening, since at > > > least three packages are providing hotplug. I get this from my > > > packages directory: > > > > Thats not really true, they don't provide this at build time. This is > > RPROVIDES vs. PROVIDES. Someone must have removed the hotplug packages > > from OE... it might be possible that you can simply use hotplug-ng > > instead of this but i didn't try this before. But the missing hotplug > > stuff might be worth a question to OE mailingist. If this didn't happen > > by accident i don't call this a clever idea... > > > > > Is there any chance you can send me your local.conf? > > > > I could do this, but i don't think it will help - its rather old. > > > > Greetings > > > > Florian > > > > -- > > The dream of yesterday Florian Boor > > is the hope of todayTel: 0271-771091-14 > > and the reality of tomorrow.Fax: 0271-771091-19 > > [Robert Hutchings Goddard, 1904][EMAIL PROTECTED] > > > > 6C 44 30 4C 43 20 6B 61 16 07 0F AA E6 97 70 A8 > > ___ > maemo-developers mailing list > maemo-developers@maemo.org > https://maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Building Maemo from scratch
Hi Florian, I was under the impression that when OE sees a package that has (R)DEPENDS on another package, it will go find the one marked (R)PROVIDES for that functionality and build it. Is that wrong? rusty On 1/20/06, Florian Boor <[EMAIL PROTECTED]> wrote: > Hi, > > Russell Geldmacher wrote: > > I'm getting fairly far in the OE build process (for Maemo-1.0 -- we'll > > talk about adding 1.1 later). It eventually will fail with the > > following message: > > > > ERROR: Nothing provides hotplug > > ERROR: dependency hotplug (for nokia770-init) not satisfied > > NOTE: no buildable providers for nokia770-init > > ERROR: dependency nokia770-init (for task-bootstrap) not satisfied > > NOTE: no buildable providers for task-bootstrap > > ERROR: dependency task-bootstrap (for maemo-image) not satisfied > > NOTE: no buildable providers for maemo-image > > > > It seems like this hotplug issue shouldn't be happening, since at > > least three packages are providing hotplug. I get this from my > > packages directory: > > Thats not really true, they don't provide this at build time. This is > RPROVIDES > vs. PROVIDES. Someone must have removed the hotplug packages from OE... it > might > be possible that you can simply use hotplug-ng instead of this but i didn't > try > this before. But the missing hotplug stuff might be worth a question to OE > mailingist. If this didn't happen by accident i don't call this a clever > idea... > > > Is there any chance you can send me your local.conf? > > I could do this, but i don't think it will help - its rather old. > > Greetings > > Florian > > -- > The dream of yesterday Florian Boor > is the hope of todayTel: 0271-771091-14 > and the reality of tomorrow.Fax: 0271-771091-19 > [Robert Hutchings Goddard, 1904][EMAIL PROTECTED] > > 6C 44 30 4C 43 20 6B 61 16 07 0F AA E6 97 70 A8 > ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Building Maemo from scratch
Hi, Russell Geldmacher wrote: > I'm getting fairly far in the OE build process (for Maemo-1.0 -- we'll > talk about adding 1.1 later). It eventually will fail with the > following message: > > ERROR: Nothing provides hotplug > ERROR: dependency hotplug (for nokia770-init) not satisfied > NOTE: no buildable providers for nokia770-init > ERROR: dependency nokia770-init (for task-bootstrap) not satisfied > NOTE: no buildable providers for task-bootstrap > ERROR: dependency task-bootstrap (for maemo-image) not satisfied > NOTE: no buildable providers for maemo-image > > It seems like this hotplug issue shouldn't be happening, since at > least three packages are providing hotplug. I get this from my > packages directory: Thats not really true, they don't provide this at build time. This is RPROVIDES vs. PROVIDES. Someone must have removed the hotplug packages from OE... it might be possible that you can simply use hotplug-ng instead of this but i didn't try this before. But the missing hotplug stuff might be worth a question to OE mailingist. If this didn't happen by accident i don't call this a clever idea... > Is there any chance you can send me your local.conf? I could do this, but i don't think it will help - its rather old. Greetings Florian -- The dream of yesterday Florian Boor is the hope of todayTel: 0271-771091-14 and the reality of tomorrow.Fax: 0271-771091-19 [Robert Hutchings Goddard, 1904][EMAIL PROTECTED] 6C 44 30 4C 43 20 6B 61 16 07 0F AA E6 97 70 A8 ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Building Maemo from scratch
Hi all,
Just noticed my reply wasn't to the list. Here is where I'm at:
I'm getting fairly far in the OE build process (for Maemo-1.0 -- we'll
talk about adding 1.1 later). It eventually will fail with the
following message:
ERROR: Nothing provides hotplug
ERROR: dependency hotplug (for nokia770-init) not satisfied
NOTE: no buildable providers for nokia770-init
ERROR: dependency nokia770-init (for task-bootstrap) not satisfied
NOTE: no buildable providers for task-bootstrap
ERROR: dependency task-bootstrap (for maemo-image) not satisfied
NOTE: no buildable providers for maemo-image
It seems like this hotplug issue shouldn't be happening, since at
least three packages are providing hotplug. I get this from my
packages directory:
grep -r hotplug * | grep PROVIDES
hotplug-ng/hotplug-ng_001.bb:RPROVIDES = "hotplug"
linux-hotplug/linux-hotplug_20040329.bb:RPROVIDES_${PN} = "hotplug"
linux-hotplug/linux-hotplug_20040920.bb:RPROVIDES_${PN} = "hotplug"
Since more than one package provides hotplug, do I need to set a
preferred provider for it?
Is there any chance you can send me your local.conf?
If you or anyone else is interested, I can post my steps to getting at
least this far and hopefully someone else can look at it as well.
Thanks,
rusty
On 1/16/06, Florian Boor <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Russell Geldmacher wrote:
> > 1. Is Maemo going to be maintained in OE?
>
> lets say i hope so. I started to do some work into this direction, but my free
> time is a little bit limited at the moment. What we currently suffer from is
> the
> problem that OE doesn't have a mechanism to build the packages from the
> original
> sources directly without adding all the included patches to OE manually. I
> started to code such a bitbake class, but like mentioned before it takes some
> time. Having such a tool it becomes much easier maintaining the packages in
> OE.
>
> > 2. I've been working a little from the Maemo/OE document available at:
> > http://downloads.kernelconcepts.de/maemo-oe.txt -- is the author of
> > that document on this list, and available for me to ask some questions
> > to?
>
> Oh... that document is missing a name. I wrote that, and of course i'll try to
> answer questions as good and fast as possible. :-)
>
> Greetings
>
> Florian
>
> --
> The dream of yesterday Florian Boor
> is the hope of todayTel: 0271-771091-14
> and the reality of tomorrow.Fax: 0271-771091-19
> [Robert Hutchings Goddard, 1904][EMAIL PROTECTED]
>
> 6C 44 30 4C 43 20 6B 61 16 07 0F AA E6 97 70 A8
>
___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Building Maemo from scratch
Hi, Russell Geldmacher wrote: > 1. Is Maemo going to be maintained in OE? lets say i hope so. I started to do some work into this direction, but my free time is a little bit limited at the moment. What we currently suffer from is the problem that OE doesn't have a mechanism to build the packages from the original sources directly without adding all the included patches to OE manually. I started to code such a bitbake class, but like mentioned before it takes some time. Having such a tool it becomes much easier maintaining the packages in OE. > 2. I've been working a little from the Maemo/OE document available at: > http://downloads.kernelconcepts.de/maemo-oe.txt -- is the author of > that document on this list, and available for me to ask some questions > to? Oh... that document is missing a name. I wrote that, and of course i'll try to answer questions as good and fast as possible. :-) Greetings Florian -- The dream of yesterday Florian Boor is the hope of todayTel: 0271-771091-14 and the reality of tomorrow.Fax: 0271-771091-19 [Robert Hutchings Goddard, 1904][EMAIL PROTECTED] 6C 44 30 4C 43 20 6B 61 16 07 0F AA E6 97 70 A8 ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Building Maemo from scratch
Hi Devesh, For now I was starting with the OpenEmbedded build of Maemo, even though it seems like only Maemo 1.0 is available in OE. It seems to me that OE automates exactly what is needed to create a Maemo rootstrap. Once that rootstrap is created, porting the necessary pacakges to a new device should be straightforward: you modify the build under the OE working directory, create a new ipkg and a patch, and apply those changes to your recipe. Which brings me to two questions: 1. Is Maemo going to be maintained in OE? 2. I've been working a little from the Maemo/OE document available at: http://downloads.kernelconcepts.de/maemo-oe.txt -- is the author of that document on this list, and available for me to ask some questions to? Thanks, rusty On 1/12/06, Devesh Kothari <[EMAIL PROTECTED]> wrote: > ext Florian Boor wrote: > > >Helo, > > > >Russell Geldmacher wrote: > > > > > > > >>So, as I'd assume, there are package-specific patches for Maemo? These > >>apply to the pristine tarballs I'm guessing? Where can one get these > >>patches? (Is that a dumb question showing I know nothing about OE?) > >> > >> > > > >well... you have two sorts of patches: > >The maemo source packages are Debian-style sources which sometimes contain > >patches to be applied before building the source. In addition you sometimes > >need > >patches to apply additional fixes to build the sources with OE. These patches > >are managed in OE, but so far OE doesn't have a mechanism to handle the > >patches > >included in the source package. Of course you can extract these patches and > >add > >them to OE manually, but it makes maintainance of it much more complicated. > > > > > >Greetings > > > >Florian > > > > > > > Wouldnt it be just easier to do it the debian way inside SB. > > 1. get the list of packages right so the dependencies are met. > 2. If you need to modify or add some components then have them available > in a different local repo [building, packaging and resolving their > dependencies is a step that should be done seperately, possibly in > another SB maemo rootstrap] > 3. for nokia 770 add the magic packages from nokia binary distribution > > and you have your new rootfs for nokia 770. > > For other devices, to use maemo, you would have to provide device > specific stuff. Or even better to get the reverse dependencies on what > packages depend on packages provided by nokia, and approximate what in > functionality they would mean for the different device, and have > packages (dummy or providing similar functionality but for your device > like device state management, battery management, input methods and VKB etc) > > Then comes the desktop part etc, which is hildon, remove all af-desktop > related components from your build as hildon is quite n770 800x480 > resolution tied. See what could be used from e.g GPE etc package them as > debian [that could be quite a work] > > Also lot of device startup procedure would have to be streamlined > > would be quite lot of work but IMHO doable :) Just IN MY PERSONAL > OPINION, it would great to see option of 2 toolkits (GPE , Hildon), a > core base maemo platform + adaptation layers , and device specific > layer, and common set of development tools and environment [SB etc, with > different toolkits etc] > > Devesh > > > > > ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Building Maemo from scratch
ext Florian Boor wrote: >Helo, > >Russell Geldmacher wrote: > > > >>So, as I'd assume, there are package-specific patches for Maemo? These >>apply to the pristine tarballs I'm guessing? Where can one get these >>patches? (Is that a dumb question showing I know nothing about OE?) >> >> > >well... you have two sorts of patches: >The maemo source packages are Debian-style sources which sometimes contain >patches to be applied before building the source. In addition you sometimes >need >patches to apply additional fixes to build the sources with OE. These patches >are managed in OE, but so far OE doesn't have a mechanism to handle the patches >included in the source package. Of course you can extract these patches and add >them to OE manually, but it makes maintainance of it much more complicated. > > >Greetings > >Florian > > > Wouldnt it be just easier to do it the debian way inside SB. 1. get the list of packages right so the dependencies are met. 2. If you need to modify or add some components then have them available in a different local repo [building, packaging and resolving their dependencies is a step that should be done seperately, possibly in another SB maemo rootstrap] 3. for nokia 770 add the magic packages from nokia binary distribution and you have your new rootfs for nokia 770. For other devices, to use maemo, you would have to provide device specific stuff. Or even better to get the reverse dependencies on what packages depend on packages provided by nokia, and approximate what in functionality they would mean for the different device, and have packages (dummy or providing similar functionality but for your device like device state management, battery management, input methods and VKB etc) Then comes the desktop part etc, which is hildon, remove all af-desktop related components from your build as hildon is quite n770 800x480 resolution tied. See what could be used from e.g GPE etc package them as debian [that could be quite a work] Also lot of device startup procedure would have to be streamlined would be quite lot of work but IMHO doable :) Just IN MY PERSONAL OPINION, it would great to see option of 2 toolkits (GPE , Hildon), a core base maemo platform + adaptation layers , and device specific layer, and common set of development tools and environment [SB etc, with different toolkits etc] Devesh ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Building Maemo from scratch
Helo, Russell Geldmacher wrote: > So, as I'd assume, there are package-specific patches for Maemo? These > apply to the pristine tarballs I'm guessing? Where can one get these > patches? (Is that a dumb question showing I know nothing about OE?) well... you have two sorts of patches: The maemo source packages are Debian-style sources which sometimes contain patches to be applied before building the source. In addition you sometimes need patches to apply additional fixes to build the sources with OE. These patches are managed in OE, but so far OE doesn't have a mechanism to handle the patches included in the source package. Of course you can extract these patches and add them to OE manually, but it makes maintainance of it much more complicated. Greetings Florian -- The dream of yesterday Florian Boor is the hope of todayTel: 0271-771091-14 and the reality of tomorrow.Fax: 0271-771091-19 [Robert Hutchings Goddard, 1904][EMAIL PROTECTED] 6C 44 30 4C 43 20 6B 61 16 07 0F AA E6 97 70 A8 ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Building Maemo from scratch
On Fri, Dec 16, 2005 at 11:50:44AM -0500, Russell Geldmacher wrote: > The trick is going to be building the packages from source. Is there > something out there for the packages which is analogous to SRPM? I'm not sure if this is the sense you mean SRPM, but you can do 'apt-get source ' and apt will download the source from the repository, apply the distribution-specific diff and give you a source tree you can call dpkg-buildpackage on. Debian I think uses custom scripts to compile all new source uploads for all it's architectures, and in theory the SOURCE_DEPENDS line can tell such a tool everything it needs to do so. You might try something like that (or see if one of the debhelper toolsuites already does this) and, as you say, just build all the packages on the list. HTH, -r ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Building Maemo from scratch
Hello again, On 12/16/05, Florian Boor <[EMAIL PROTECTED]> wrote: > Hi, > > Russell Geldmacher wrote: > > I am interested in building Maemo from scratch in order to begin > > figuring out what it would take to port it to a new device. I would > > appreciate any information regarding this. > > sounds good... building it from the scratch isn't really easy, but you might > want to take a look at OpenEmbedded. > We have all relevant bits of maemo 1.0 in OE and it is pretty easy to add > support for a new device there. The current problem is that we need to update > the packages to the latest 1.1rc bits in order to make them work. > Some information about this can be found here: > http://www.kernelconcepts.de/~fuchs/oe/maemo-oe.txt OK! I am not so familiar with OpenEmbeddd, so I will read that doc and then do some reading about OE. > > I'm trying to create a class to make OE apply the patches included in the > maemo > source packages automatically because this would reduce the effort maintaining > updated maemo packages in OE extremely. Unfortunately my time to spend on this > is a little bit limited :-( So, as I'd assume, there are package-specific patches for Maemo? These apply to the pristine tarballs I'm guessing? Where can one get these patches? (Is that a dumb question showing I know nothing about OE?) > > Second, is there any documentation out there describing other efforts > > to port Maemo? > > Not that i'm aware of, but it would be a good idea to start do document every > efforts in the wiki. I remember some more people were interested in it too. Great, as soon as I get somethnig tangible done, I will document it in the Wiki :-) Thanks, rusty > Greetings > > Florian > > -- > The dream of yesterday Florian Boor > is the hope of todayTel: 0271-771091-14 > and the reality of tomorrow.Fax: 0271-771091-19 > [Robert Hutchings Goddard, 1904][EMAIL PROTECTED] > > 6C 44 30 4C 43 20 6B 61 16 07 0F AA E6 97 70 A8 > ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Building Maemo from scratch
> > First question: how do the developers create the binary distributions? > > If I can find information on how those are generated, perhaps I can > > adapt that to be configurable for new devices. > > > I suggest to take a look at our dev root FS howto: > http://maemo.org/platform/docs/howtos/howto_use_flasher_rootfs.html > You could perhaps get some ideas from it. Ah, OK I see what that's doing. I will need to rebuild all of the packages on the rootfs.packages list. So then, assuming I have all my packages rebuilt, I can probably generate a jffs2 for a device by modifying sources.list to point to a device-specific repository. The trick is going to be building the packages from source. Is there something out there for the packages which is analogous to SRPM? Thanks! rusty ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Building Maemo from scratch
Hi, Russell Geldmacher wrote: > I am interested in building Maemo from scratch in order to begin > figuring out what it would take to port it to a new device. I would > appreciate any information regarding this. sounds good... building it from the scratch isn't really easy, but you might want to take a look at OpenEmbedded. We have all relevant bits of maemo 1.0 in OE and it is pretty easy to add support for a new device there. The current problem is that we need to update the packages to the latest 1.1rc bits in order to make them work. Some information about this can be found here: http://www.kernelconcepts.de/~fuchs/oe/maemo-oe.txt I'm trying to create a class to make OE apply the patches included in the maemo source packages automatically because this would reduce the effort maintaining updated maemo packages in OE extremely. Unfortunately my time to spend on this is a little bit limited :-( > Second, is there any documentation out there describing other efforts > to port Maemo? Not that i'm aware of, but it would be a good idea to start do document every efforts in the wiki. I remember some more people were interested in it too. Greetings Florian -- The dream of yesterday Florian Boor is the hope of todayTel: 0271-771091-14 and the reality of tomorrow.Fax: 0271-771091-19 [Robert Hutchings Goddard, 1904][EMAIL PROTECTED] 6C 44 30 4C 43 20 6B 61 16 07 0F AA E6 97 70 A8 ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Building Maemo from scratch
ext Russell Geldmacher wrote: > I am interested in building Maemo from scratch in order to begin > figuring out what it would take to port it to a new device. I would > appreciate any information regarding this. > Building all the stuff from scratch would be tricky even for the Nokia 770. If you want to try it with other devices then I can imagine even more troubles. It could be easier to start with UI framework part. I vaguely recall that somebody have tried that already.. > First question: how do the developers create the binary distributions? > If I can find information on how those are generated, perhaps I can > adapt that to be configurable for new devices. > I suggest to take a look at our dev root FS howto: http://maemo.org/platform/docs/howtos/howto_use_flasher_rootfs.html You could perhaps get some ideas from it. > Second, is there any documentation out there describing other efforts > to port Maemo? > Not yet, but it would be great to start wiki pages on such efforts. > Thanks for your help! > rusty Please keep us posted and good luck! Regards, Ferenc ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] Building Maemo from scratch
Hi all, I am interested in building Maemo from scratch in order to begin figuring out what it would take to port it to a new device. I would appreciate any information regarding this. First question: how do the developers create the binary distributions? If I can find information on how those are generated, perhaps I can adapt that to be configurable for new devices. Second, is there any documentation out there describing other efforts to port Maemo? Thanks for your help! rusty ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
