Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH dylan, master] Fix meta-toolchain-qte SDK build for x11-less DISTRO
Date: Wed, 05 Jun 2013 16:07:40 -0400	[thread overview]
Message-ID: <20130605200740.GF10298@denix.org> (raw)
In-Reply-To: <CAP9ODKqiVaF3njGCLXHhT7n03d-QyESQAdw3S+HF2-JNEazCMw@mail.gmail.com>

On Wed, Jun 05, 2013 at 02:43:07PM -0300, Otavio Salvador wrote:
> On Wed, Jun 5, 2013 at 2:23 PM, Nicolas Dechesne <
> nicolas.dechesne@linaro.org> wrote:
> 
> >
> >
> >
> > On Wed, Jun 5, 2013 at 7:19 PM, Saul Wold <sgw@linux.intel.com> wrote:
> >
> >> On 06/05/2013 10:12 AM, Otavio Salvador wrote:
> >>
> >>>
> >>>
> >>>
> >>> On Wed, Jun 5, 2013 at 1:58 PM, Saul Wold <sgw@linux.intel.com
> >>> <mailto:sgw@linux.intel.com>> wrote:
> >>>
> >>>     On 06/05/2013 09:32 AM, Nicolas Dechesne wrote:
> >>>
> >>>
> >>>         On Wed, Jun 5, 2013 at 6:30 PM, Saul Wold <sgw@linux.intel.com
> >>>         <mailto:sgw@linux.intel.com>
> >>>         <mailto:sgw@linux.intel.com <mailto:sgw@linux.intel.com>>>
> >>> wrote:
> >>>
> >>>              You could just directly put the nativesdk-libx11 in place
> >>>         of the
> >>>              variable, no need to have the variable there.
> >>>
> >>>
> >>>         yes, that's what I had initially, but found it was less easy to
> >>>         read...
> >>>         with X11DEPENDS it's more 'obvious' that there is something
> >>>         special..
> >>>         that said, i can make the change if that's really needed.
> >>>
> >>>     We do use the X11DEPENDS elsewhere when there are multiple
> >>>     dependencies, but I also found cases where we just include the
> >>>     dependency directly in the test. I was trying pick a direction:
> >>>     single entry no X11DEPENDS, multiple entries use X11DEPENDS.
> >>>
> >>>     Comments, flames, ...
> >>>
> >>>
> >>> Yes; I sent this patch in Febuary:
> >>> http://patchwork.openembedded.**org/patch/44759/<http://patchwork.openembedded.org/patch/44759/>
> >>>
> >>> Please use this one instead of the recent one.
> >>>
> >>>
> >> Well reading back on that, it looks like I was waiting for an
> >> EXTRA_OECONF or related change to the autoconf scripts.
> >>
> >> Sau!
> >
> >
> > hmm. ok, sorry Otavio, i missed the other patch. I will check on my side
> > too about EXTRA_OECONF.
> >
> 
> Nicolas, don't worry. It is normal to end redoing some stuff.
> 
> Last time I checked it had no support in Qt build system; I am not sure if
> it uses or not the host headers (in case they exist) but it needs testing
> to be sure.

I can confirm that it does not link against host X11 when built w/o that 
dependency and nativesdk has no x11 libs/headers. As I previously mentioned, 
we've been using this fix for over 6 months on several releases built on 
different machines w/o problems...

-- 
Denys


  reply	other threads:[~2013-06-05 20:07 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-05  7:24 [PATCH dylan, master] Fix meta-toolchain-qte SDK build for x11-less DISTRO Nicolas Dechesne
2013-06-05 16:30 ` Saul Wold
2013-06-05 16:32   ` Nicolas Dechesne
2013-06-05 16:58     ` Saul Wold
2013-06-05 17:12       ` Otavio Salvador
2013-06-05 17:19         ` Saul Wold
2013-06-05 17:23           ` Nicolas Dechesne
2013-06-05 17:43             ` Otavio Salvador
2013-06-05 20:07               ` Denys Dmytriyenko [this message]
2013-06-05 20:10                 ` Otavio Salvador
2013-06-05 20:53                   ` Saul Wold
2013-06-05 20:56                     ` Otavio Salvador
2013-06-05 20:58                       ` Denys Dmytriyenko
2013-06-06 15:46                         ` Richard Purdie
2013-06-06 16:28                           ` Otavio Salvador
2013-06-07 12:19                           ` Nicolas Dechesne
2013-06-05 16:40 ` Denys Dmytriyenko

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130605200740.GF10298@denix.org \
    --to=denis@denix.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio@ossystems.com.br \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox