what directory should one build in?

George Hartzell <[email protected]>
Newsgroups gmane.comp.handhelds.openzaurus.devel
Message-ID <[email protected]>
I've been using the instructions at:

  http://oe.handhels.org/cgi-bin/moin.cgi/GettingStarted

as I try to learn to build openzaurus.

The instructions refer to '/stuff/', which in my case is
/home/hartzell/openembedded.

In that directory I have my OE.db and an org.openembedded.oz354x
directory.  I update both as described on the wiki page.

I do my builds from /home/hartzell/openzaurus (aka "/stuff/"), which
creates a /home/hartzell/openzaurus/tmp directory full of build
related stuff.

I'd like to explore other branches/revisions, but I'm afraid that
they'll all try to write into /home/hartzell/openembedded/tmp and it
will get confused.

What's the proper way to develop with multiple branches?

In a related question, the wiki GettingStarted page suggests the
following command to update a repository's local database:

 monotone --db=/stuff/OE.db pull monotone.vanille.de org.openembedded.dev

If I'm tracking org.openembedded.oz354x, should I use

 monotone --db=/stuff/OE.db pull monotone.vanille.de org.openembedded.oz354x

and if I want to track both org.openembedded.{dev,oz354x} should I use

 monotone --db=/stuff/OE.db pull monotone.vanille.de 'org.openembedded.*'

or???

Does the example in the wiki page do the right thing?  In particular,
do the local database pickup up the org.openembedded.dreambox updates

Thanks!

g.


-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
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.