Hi paul,<br><br> Iam not specialist in this. I am just following the steps mentioned here<br><br> <a href="http://icedtea.classpath.org/wiki/CrossCompileOECoreTutorial">http://icedtea.classpath.org/wiki/CrossCompileOECoreTutorial</a><br>
<br>I am building from this path vj@ubuntu:/host/coreembedded/oe-core/build$ and it contains pseudodone file.<br><br>and in vj@ubuntu:/host/coreembedded/oe-core/build/conf local.conf exits..<br><br>and the same is calling bitbake which is present in scripts..<br>
<br>Regards,<br>VJ<br><br><div class="gmail_quote">On Fri, Mar 16, 2012 at 4:26 PM, Paul Eggleton <span dir="ltr"><<a href="mailto:paul.eggleton@linux.intel.com">paul.eggleton@linux.intel.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Friday 16 March 2012 01:20:44 Andreas Oberritter wrote:<br>
> Sorry, I messed up some details. In fact, pseudo-native doesn't get<br>
> rebuilt, but bitbake pseudo-native still gets executed for every<br>
> machine, unless $BUILDDIR/pseudodone is present and contains<br>
> PSEUDOBINDIR. This just wastes time and confuses users who receive a<br>
> message saying "Pseudo is not present but is required, building this<br>
> first before the main build".<br>
<br>
It takes a small amount of time just once. However if this is really an issue<br>
perhaps we could address it directly rather than hacking around it?<br>
<br>
> >> BUILDDIR doesn't seem to have any other use than pointing to the<br>
> >> 'pseudodone' file. I don't understand why it's required to run bitbake<br>
> >> from there.<br>
> ><br>
> > Well, it's required that bitbake is run from the build directory and when<br>
> > you use the setup script as intended that's where BUILDDIR points to. I<br>
> > hadn't anticipated that anyone would be changing BUILDDIR to point to<br>
> > anything other than the build dir, however I don't really think it's a<br>
> > good idea to support that.<br>
><br>
> That's because BUILDDIR has no meaning outside oe-core's setup scripts.<br>
> In scripts/bitbake, BUILDDIR would better be called PSEUDODONEDIR or<br>
> similar, because that's what the variable really means in this context<br>
<br>
The naming is such that it should point to the build directory because that's<br>
where pseudodone is meant to be written. I think when it was introduced there<br>
was an idea that it might be useful in other contexts, thus the naming.<br>
<br>
> In order to verify that scripts/bitbake is called from the build<br>
> directory, you could as well just check whether $PWD/conf/local.conf exists.<br>
<br>
Unfortunately it's not that simple. bitbake.conf pulls in local.conf using<br>
"include" and not "require", thus it doesn't actually have to exist anywhere.<br>
<br>
> I'm not using oe-core's scripts, because they make assumptions about the<br>
> directory layout that don't fit my project's needs. I think they are<br>
> overly complex<br>
<br>
Could you perhaps elaborate on what needs those scripts are not fulfilling?<br>
<br>
> and they display texts that seem to suit yocto's needs but at least not<br>
> mine.<br>
<br>
We print these messages so that people know what to do and where to find<br>
further information. I don't think that's unreasonable. However if you have<br>
suggestions on how we might improve those messages or allow them to be<br>
customised if necessary, we could look at changing them.<br>
<br>
Cheers,<br>
Paul<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
<br>
Paul Eggleton<br>
Intel Open Source Technology Centre<br>
<br>
_______________________________________________<br>
Openembedded-core mailing list<br>
<a href="mailto:Openembedded-core@lists.openembedded.org">Openembedded-core@lists.openembedded.org</a><br>
<a href="http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core" target="_blank">http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core</a><br>
</font></span></blockquote></div><br>