OESF | ELSI | pdaXrom | OpenZaurus | Zaurus Themes | Community Links | Ibiblio

IPB

Welcome Guest ( Log In | Register )

 
Reply to this topicStart new topic
> OE build
Richjn
post Feb 11 2004, 04:28 AM
Post #1





Group: Members
Posts: 121
Joined: 21-October 03
Member No.: 696



Just alittle note to anyone thinking of having a go at compiling a few apps but have been put off in the past by the "mumbo jumbo" that seems to surround the issue.

I highly recomend giving the new OpenEmbedded build structure ago. For one thing most of the hard work has been done for you and by simply following the instructions here

http://openembedded.org/phpwiki/index.php/.../GettingStarted

You will be well on your way

Note: # autoconf-native_2.57.oe is now 2.59 and automake-native_1.7.7.oe is now 1.8.2


(mickeyl you might want to update the autoconf/automake versions in the instructions as although obvious when you look its always nice to have the instructions work with copy paste to build up your confidence when your starting out)

Although I'm a relative newbie I find the build structure a pleasure to work with and have already compiled my first few apps.

Well done OE team

Richard
Go to the top of the page
 
+Quote Post
Mickeyl
post Feb 11 2004, 08:20 AM
Post #2





Group: Members
Posts: 1,497
Joined: 12-November 03
From: Germany
Member No.: 907



Hi Richard,

thanks for your nice words. Glad you got started pretty quick. We made great progress on OE. I'll describe that in the 2nd OOO newsletter which is due soon. Ah and btw., openembedded.org/phpwiki is a WikiWiki - it's designed to support easy collaboration. If instructions become inaccurate, just edit the page and change them smile.gif
Go to the top of the page
 
+Quote Post
jh
post Feb 11 2004, 09:29 AM
Post #3





Group: Members
Posts: 115
Joined: 20-November 03
Member No.: 968



My sentiments exactly... the OE build system has been great to work with. I appreciate all the work that went into it.

jason
Go to the top of the page
 
+Quote Post
Richjn
post Feb 11 2004, 03:53 PM
Post #4





Group: Members
Posts: 121
Joined: 21-October 03
Member No.: 696



Didn't realise that I could make changes (I'm not signed up) 8)

Changes made to wiki so up to date for now.


Richard
Go to the top of the page
 
+Quote Post
lardman
post Feb 24 2004, 03:54 AM
Post #5





Group: Members
Posts: 4,515
Joined: 25-October 03
From: Bath, UK
Member No.: 464



I've started using OE and I agree it's nice to work with. I have a couple of questions though (they may be answered on the mailing list but the search function seems to only work sometimes for me).

I've compiled the base bits and pieces (the fact that qmake needs to be compiled ought to be added to the GettingStarted document imo), have had troubles with libjpeg (and have seen the fix for it on the mailing list).

Now I'd like to compile qpegps and qplot for starters. They complain (amongst other things) of not finding (the Qtopia) header files. Fair enough, is there another package I need to build to make these header files available or is this something I have to do by hand (setting QTDIR and QPEDIR for example to point to the headers wherever I choose to stick them)?

Where's the libopie package? I presume this is required by the Qt/Opie apps?

And a random question - will the build process eventually be able to automatically create its dependencies? I presume so, I also presume that if it annoys me enough I should just write my own - in other words this is not a complaint, just a thought.

Kernel development (currently) needs to use GCC 2.95.x, this ought to be spelled out on the GettingStarted page methinks, or perhaps there's a way for oe to check, I don't know.

Cheers,


Si
Go to the top of the page
 
+Quote Post
Mickeyl
post Feb 24 2004, 05:11 AM
Post #6





Group: Members
Posts: 1,497
Joined: 12-November 03
From: Germany
Member No.: 907



One important thing is to note the difference between oebuild and oemake. oebuild just builds the package you give it by name, whereas oemake builds a provider (e.g. oemake libqpe-opie-1.0.3) and automatically all dependencies. oemake makes building much easier, however the quirrel with oemake is that currently it builds _all_ providers of a given dependency, e.g. it will build you qt-2.3.6, qt-2.3.7, qt-2.3.8-snapshot, etc. which can be a bit annoying. Needs work.
Go to the top of the page
 
+Quote Post
lardman
post Feb 24 2004, 05:44 AM
Post #7





Group: Members
Posts: 4,515
Joined: 25-October 03
From: Bath, UK
Member No.: 464



Okay. I see that opie is in a nonworking directory in the OE system. What steps should I take to get a working system? Follow the opie.handhelds.org instructions (though I'm not sure how well that will work with OE)?

Cheers,


Si
Go to the top of the page
 
+Quote Post

Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:

 



RSS Lo-Fi Version Time is now: 28th May 2015 - 12:18 PM