<div dir="ltr">Having had an inconvenient debugging session this morning with the help of you, ndec, and so forth on IRC, I would propose to get rid of this gtk doc stub, at least how it is now. It is completely breaking projects causing regressions compared to denzil. We are pretty much blocked by it altogether now. Here is the other thread for details: <a href="https://lists.yoctoproject.org/pipermail/poky/2013-August/009184.html">https://lists.yoctoproject.org/pipermail/poky/2013-August/009184.html</a><div>
<br></div><div>IMHO, there should be a way for end users to get rid of the blocker issue and regression. So, how about making this optional?</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Aug 21, 2013 at 11:04 AM, Burton, Ross <span dir="ltr"><<a href="mailto:ross.burton@intel.com" target="_blank">ross.burton@intel.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="im">On 21 August 2013 09:40, Jack Mitchell <span dir="ltr"><<a href="mailto:ml@communistcode.co.uk" target="_blank">ml@communistcode.co.uk</a>></span> wrote:<br>
</div><div class="gmail_extra"><div class="gmail_quote"><div class="im">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div><span style="color:rgb(34,34,34)">Here is the patch which kicks it all off:</span><br>
</div>
<br>
<a href="http://lists.linuxtogo.org/pipermail/openembedded-core/2012-July/026077.html" target="_blank">http://lists.linuxtogo.org/pipermail/openembedded-core/2012-July/026077.html</a><br>
<br>
So, make of this what you will. I've cc'd Ross in to see if he has a<br>
specific reason for re-enabling gkt-doc in some packages. Maybe we<br>
should turn it into an image feature...?<br></blockquote><div><br></div></div><div>tl;dr: it's a stub package, you're not building any gtk-doc, and you can't turn it on if you wanted to.<br></div><div><br></div>
<div>
There's some confusion in this thread, so I'll try and clear it up.</div><div><br></div><div>We need to build gtk-doc (or compatible) because it provides m4 autoconf fragments that are needed at configure time by any package that uses gtk-doc for documentation. Previously we were patching recipes one by one to disable the rules, but that's prone to failure. We integrated gtk-doc-stub (also used by gnome-os) which has the same external interfaces but is entirely stubs, for example:</div>
<div><br></div><div><a href="https://git.gnome.org/browse/gtk-doc-stub/tree/gtk-doc.m4" target="_blank">https://git.gnome.org/browse/gtk-doc-stub/tree/gtk-doc.m4</a><br></div><div><br></div><div>This way we can actually configure everything that uses gtk-doc without needing the full gtk-doc package.</div>
<div><br></div><div>There is a gtk-doc class which adds a dependency on gtk-doc-stub-native and then adds --disable-gtk-doc to EXTRA_OECONF. This is why the explicit --disable was removed from connman: it was redundant.</div>
<div><br></div><div>The other advantage of using a central gtk-doc class is that if someone did want to build gtk-doc, they would just need to package up the real gtk-doc and change the class.</div><span class="HOEnZb"><font color="#888888"><div>
<br></div><div>Ross</div>
</font></span></div></div></div>
<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.openembedded.org/mailman/listinfo/openembedded-core" target="_blank">http://lists.openembedded.org/mailman/listinfo/openembedded-core</a><br>
<br></blockquote></div><br></div>