Re: Opie and OpenEmbedded

Lorn Potter <[email protected]>
Newsgroups gmane.comp.handhelds.opie.devel
Message-ID <[email protected]>
Paul Sokolovsky wrote:
> Hello Michael,
> 
> Saturday, October 14, 2006, 1:43:11 PM, you wrote:
> 
> []
> 
>> I'd like to encourage someone of the active Opie developers
>> to take care about everything Opie (and consequently Qt/Embedded)
>> in OpenEmbedded.
> 
>   As promised, maintenance plan I would like to adhere to:
> 
> 1. Ensure that OPIE packages and rootfs builds correctly in OE.dev,
> including working on support for new/different versions of GCC,
> packaging peculiarities, etc.
> 
> 2. Work towards adding OPIE support in Angstrom.
> 
> 3. Working with port maintainers towards adding support for more
> machines to OPIE.
> 
> 4. Work on establishing guidelines for machine support. In
> particular, I'm not going to accept any patches blindly. Existing
> machines support needs cleanup, too. Of course, this includes making
> patches for libopie2 (at least), so I'm going to collaborate with OPIE
> maintainers on that.

see below.

> 
> 5. More higher-level and longer-term goal is getting rid of as much
> machine-dependent packages for OPIE as possible. This might include
> reworking means to support/configure different machines by means of
> declarative configs, instead of being hardcoded into the C++ code.

All of this is going to change with the upcoming qtopia 4 gpl release. 
Use the tag BEFORE_LJP_UPDATE because I plan on demolishing main.

In Qtopia 4 (soon to be Opie II - or whatever people call it), there is 
a devices/ directory which can contain device specific code that gets 
used in place of the default files in the tree. Configurable with 
-device example

like this:

in devices/example/

config.pri  configure  custom.cpp  custom.h  defaultbuttons.conf 
DESCRIPTION  mkspecs  README.txt  src

./mkspecs:
qws

./mkspecs/qws:
linux-example-g++

./mkspecs/qws/linux-example-g++:
qmake.conf  qplatformdefs.h

./src:
plugins  projects.pri  src.pro  tree_config.pri

./src/plugins:
plugins.pro  qtopiacore

./src/plugins/qtopiacore:
kbddrivers  mousedrivers  qtopiacore.pro

./src/plugins/qtopiacore/kbddrivers:
example  kbddrivers.pro

./src/plugins/qtopiacore/kbddrivers/example:
examplekbddriverplugin.cpp  examplekbddriverplugin.h 
examplekbdhandler.cpp  examplekbdhandler.h  example.pro

./src/plugins/qtopiacore/mousedrivers:
example  mousedrivers.pro

./src/plugins/qtopiacore/mousedrivers/example:
examplemousedriverplugin.cpp  examplemousedriverplugin.h 
examplemousehandler.cpp  examplemousehandler.h  example.pro


because every device is different. Its unnecessary to have every build 
have every device built in.




> 
> 6. Process bugreports/maillist traffic as standard part of maintenance
> work. This is of course the most "tough" part ;-), but I'm on the OPIE
> MLs/OE.dev bug notice ML for some time now, and that traffic does not
> seem to be high.
> 
> 
> 
> 


-- 
Lorn 'ljp' Potter
Trolltech Qtopia Community Manager
Opie Core Developer
http://qtopia.net
_______________________________________________

http://opie.handhelds.org/cgi-bin/moin.cgi/DeveloperWikiIndex

Opie-devel mailing list
[email protected]
https://handhelds.org/mailman/listinfo/opie-devel
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.