public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "thilo.cestonaro@ts.fujitsu.com" <thilo.cestonaro@ts.fujitsu.com>
To: "ross.burton@intel.com" <ross.burton@intel.com>
Cc: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] added recipe for libdbus-c++
Date: Tue, 15 Nov 2016 15:27:05 +0000	[thread overview]
Message-ID: <1479223403.5380.6.camel@ts.fujitsu.com> (raw)
In-Reply-To: <CAJTo0LY0_hUiFhYJKA3B+qouLoBhXd4W_ab=3T-gYDMPFUj7tw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1366 bytes --]

Am Dienstag, den 15.11.2016, 14:23 +0000 schrieb Burton, Ross:
> 
> On 15 November 2016 at 13:46, Thilo Cestonaro <thilo.cestonaro@ts.fujitsu.com> wrote:
> > Signed-off-by: Thilo Cestonaro <thilo.cestonaro@ts.fujitsu.com>
> > 
> 
> As Alex said, please submit this to meta-oe as there's no strong rationale to keep it in oe-core, especially considering it's abandoned.
> 
> The remove_CXX_FOR_BUILD-stuff patch can be trimmed to just modify configure.ac and tools/Makefile.am, the other files will be regenerated at do_configure and patching them can cause conflicts if
> upstream ever makes a new release.
> 
> Also please explain clearly why that has to be removed in the patch header because usually we need to patch *in* the _FOR_BUILD macros: I was curious and ended up looking at the build to understand
> why. AFAICT it's because upstream if cross-compiling it refuses to build target tools and will only build host tools so the test suite can run, but disabling the tests and patching out CXX_FOR_BUILD
> we can build target tools.  The downside is that we have no test suite, which is useful (see the ptest class).

Perhaps I will add ptest in another patch later. Will need to look into it.
Thanks for your comments!

> 
> Thank you for being the first person in a long time to actually submit the recipe to the community!
> 
> Ross

[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 3847 bytes --]

      reply	other threads:[~2016-11-15 15:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-15 13:46 [PATCH] added recipe for libdbus-c++ Thilo Cestonaro
2016-11-15 14:05 ` Alexander Kanavin
2016-11-15 14:23 ` Burton, Ross
2016-11-15 15:27   ` thilo.cestonaro [this message]

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=1479223403.5380.6.camel@ts.fujitsu.com \
    --to=thilo.cestonaro@ts.fujitsu.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.com \
    /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