On Wed, 2010-09-29 at 15:37 +0200, Rolf Offermanns wrote: > On 09/28/2010 02:34 PM, Anas Nashif wrote: > > Why do you want to rebuild everything? Just get the binary packages.. > > What if someone needs armv6 for example? Or anything else besides ia32 > and armv7?
This question looks to be put on MeeGO porting list. As par my understanding from MeeGo porting guide it is clear that we have to create account in MeeGO OBS & do the build by our own tool chain. Still below point is not clear - - What is the MeeGO base we have to take to build MeGoo for new Hw (Ex. ARM11 (armv6),Freescale i.MX ..) - Do we have to build kernel as well for different architecture or with some MeeGo base kernel, add patches accordingly. - Any document available about how to validate toolchain as par MeeGo build. (If i will take supporting toolchain from codeSourcey or build my own toolchain then it will be Ok for MeeGo build ) - What is the guideline available to separate out arch dependent or not dependent package for new Hw. - Currently i can see under http://repo.meego.com/MeeGo/releases/1.0 below folder tree present. Icon Name ________________________________________________________________________ [DIR] Parent Directory [DIR] core/ [DIR] extra/ [DIR] ivi/ [DIR] netbook/ [DIR] non-oss/ ________________________________________________________________________ What is the guide-line is available about how to differentiate package based on above folder tree. Fast response from MeeGo portng list wiil be appreciated, so that developer can start making MeeGo up for different HW. > > -Rolf > _______________________________________________ > MeeGo-packaging mailing list > [email protected] > http://lists.meego.com/listinfo/meego-packaging _______________________________________________ MeeGo-packaging mailing list [email protected] http://lists.meego.com/listinfo/meego-packaging
