<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
On 2011年11月23日 15:31, Koen Kooi wrote:
<blockquote
cite="mid:28E4D413-B6C4-46D4-8622-26CBA7255088@dominion.thruhere.net"
type="cite">
<pre wrap="">
Op 23 nov. 2011, om 07:47 heeft Xiaofeng Yan het volgende geschreven:
</pre>
<blockquote type="cite">
<pre wrap="">From: Xiaofeng Yan <a class="moz-txt-link-rfc2396E" href="mailto:xiaofeng.yan@windriver.com"><xiaofeng.yan@windriver.com></a>
Hi Richard & all,
I fixed some problems found at previous submitting and use PACKAGECONFIG to get mutual configuration between directfb and x11. I hope this submitting isn't a horrible mess :).
One previous problem about what happen when user want to have both directfb and x11 in DISTRO_FEATURES?
</pre>
</blockquote>
<pre wrap="">
That was the question I was going to ask
</pre>
<blockquote type="cite">
<pre wrap="">I think directfb and x11 can't be defined in DISTRO_FEATURES at the same time because directfb and x11 are the lowest level library for GUI with different mechanism.
</pre>
</blockquote>
<pre wrap="">
I don't understand what the above means, but I've been building both directfb and x11 for some years now and they don't clash.
</pre>
</blockquote>
Hi koen,<br>
<br>
Thanks for your comment.<br>
I want to build an image only including directfb and gtk without
x11. There are no any stuff related to x11 in this image. You know,
directfb often is used in many embedded device because directfb is
enough for their requirement. Perhaps they feel more familiar <span></span><span></span>with
directfb or gtk+ rather than x11. The purpose of building this image
is for some people who want to use yocto to develop their
production getting an image based on directfb anf gtk+ very
easily. So it need an mechanism making an mutual operation between
directfb and x11 when compiling core-image-gtk-directfb for getting
directfb image without x11. Of course, you can add directfb to
DISTRO_FEATURES with x11, if you want to have both of them. But if
you want to get an image without x11, then I think you can only
remove x11 from DISTRO_FEATURES at current status because x11 is the
default configuration.<br>
<blockquote
cite="mid:28E4D413-B6C4-46D4-8622-26CBA7255088@dominion.thruhere.net"
type="cite">
<pre wrap=""></pre>
<blockquote type="cite">
<pre wrap="">x11 and directfb should be mutual in DISTRO_FEATURES. User may use file "meta-yocto/conf/local.conf.sample.extended" to select the mode they want to need.
but directfb can work in an image with x11. for example, "directfb" and "direcrfb-examples" can be added to task-core-x11-sato.bb. you can run df_andi, a demo based on directfb, on matchbox term running on core-image-sato with x11. So directfb and x11 can exist in the same image but not be defined in DISTRO_FEATURES at same time.
If you have any suggestion, I will fix them again.
</pre>
</blockquote>
<pre wrap="">
Last time I looked both gtk+ and pango had their backend modularized, so you can build both and install the right one in the rootfs. I think that would be a better way to go. Just look at debian with their gtk-directfb installer, they have gtk-X as well :)
</pre>
</blockquote>
I know what you mean. It could be a good method to have both in an
image. It may become a new task after completing this feature.<br>
<br>
Thanks<br>
Yan<br>
<blockquote
cite="mid:28E4D413-B6C4-46D4-8622-26CBA7255088@dominion.thruhere.net"
type="cite">
<pre wrap="">regards,
Koen</pre>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
Openembedded-core mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Openembedded-core@lists.openembedded.org">Openembedded-core@lists.openembedded.org</a>
<a class="moz-txt-link-freetext" href="http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core">http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core</a>
</pre>
</blockquote>
<br>
</body>
</html>