Xorg / Glamo ?
rod at whitby.id.au
Wed Feb 4 02:11:40 CET 2009
Thomas has one opinion about MokoMakefile. It is not the only opinion
held by various Openmoko and third-party developers.
It is true that the delta between the normal OE build process, and the
Openmoko build process is progressively getting smaller.
However, there are many people who find the normal OE setup instructions
too complex, and seem to happily use the nslu2-linux Makefile, the FSO
Makefile, or the SHR Makefile to build OE distributions.
In my opinion, build setup instructions need to be executable, otherwise
they are always out of date. When a Makefile is not up to date with the
intentions of the Openmoko developers, the delta is clear and can be
fixed once in a central place for many people. When there are multiple
wiki pages all saying slightly different things, changes to the build
process are much harder to deploy.
Juan Alberto Aranda Alvarez wrote:
> Then, it should be wiped out completely from the wiki. I guess it was
> created as a way to "protect" new developers. But it totally confused me.
> The toolchain is a good idea to show newcomers the phone and get them
> excited with it. But it isn't maintained either, so you have a lot of
> new comers wanting to port their application and would only get
> Thomas Gstädtner wrote:
>> On Wed, Feb 4, 2009 at 12:57 AM, Juan Alberto Aranda Alvarez
>> <jaranda at openmoko.com> wrote:
>>> So basically MokoMakefile is broken?
>> It not only is broken, it also is unmaintained. I suggest you to use
>> plain Openembedded, makes everything much easier.
> Yes it does
>> devel mailing list
>> devel at lists.openmoko.org
> devel mailing list
> devel at lists.openmoko.org
More information about the devel