All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Steffen Sledz <sledz@dresearch-fe.de>,
	"Burton, Ross" <ross.burton@intel.com>,
	Otavio Salvador <otavio.salvador@ossystems.com.br>
Cc: openembedded-devel <openembedded-devel@lists.openembedded.org>,
	openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] MS Windows machine?
Date: Fri, 05 Jan 2018 12:22:36 +0000	[thread overview]
Message-ID: <1515154956.30291.30.camel@linuxfoundation.org> (raw)
In-Reply-To: <cad1f9fe-e682-a5f6-72ab-71a7738ea46a@dresearch-fe.de>

On Fri, 2018-01-05 at 12:29 +0100, Steffen Sledz wrote:
> On 04.01.2018 15:39, Richard Purdie wrote:
> > 
> > In basic terms, you need a machine which:
> > 
> > * Sets TARGET_ARCH to the right thing (i686 or x86_64)
> > * Sets TARGET_OS to mingw32
> > 
> > and then some distro config which sets up the toolchain when mingw
> > is
> > the target os to the values like meta-mingw/conf/machine-sdk/i686-
> > mingw32.conf sets.
> Do you have a sample distro config which we can use as a template?

No, sorry. As I said, I've not tried this before. Its not a trivial
thing to do, equally it shouldn't be too bad given what we already
have...

Sadly I don't have the time available to play with something like that
either, much as I do quite enjoy it...

Cheers,

Richard


WARNING: multiple messages have this Message-ID (diff)
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Steffen Sledz <sledz@dresearch-fe.de>,
	"Burton, Ross" <ross.burton@intel.com>,
	Otavio Salvador <otavio.salvador@ossystems.com.br>
Cc: openembedded-devel <openembedded-devel@lists.openembedded.org>,
	openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: MS Windows machine?
Date: Fri, 05 Jan 2018 12:22:36 +0000	[thread overview]
Message-ID: <1515154956.30291.30.camel@linuxfoundation.org> (raw)
In-Reply-To: <cad1f9fe-e682-a5f6-72ab-71a7738ea46a@dresearch-fe.de>

On Fri, 2018-01-05 at 12:29 +0100, Steffen Sledz wrote:
> On 04.01.2018 15:39, Richard Purdie wrote:
> > 
> > In basic terms, you need a machine which:
> > 
> > * Sets TARGET_ARCH to the right thing (i686 or x86_64)
> > * Sets TARGET_OS to mingw32
> > 
> > and then some distro config which sets up the toolchain when mingw
> > is
> > the target os to the values like meta-mingw/conf/machine-sdk/i686-
> > mingw32.conf sets.
> Do you have a sample distro config which we can use as a template?

No, sorry. As I said, I've not tried this before. Its not a trivial
thing to do, equally it shouldn't be too bad given what we already
have...

Sadly I don't have the time available to play with something like that
either, much as I do quite enjoy it...

Cheers,

Richard


  reply	other threads:[~2018-01-05 12:22 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-21  6:40 MS Windows machine? Steffen Sledz
2017-12-21  9:08 ` [OE-core] " Burton, Ross
2017-12-21  9:08   ` Burton, Ross
2017-12-21  9:54   ` [OE-core] " Steffen Sledz
2017-12-21  9:54     ` Steffen Sledz
2017-12-21 11:39     ` [OE-core] " Burton, Ross
2017-12-21 11:39       ` Burton, Ross
2017-12-21 13:00       ` [OE-core] " Steffen Sledz
2017-12-21 13:00         ` Steffen Sledz
2018-01-04  6:31         ` [OE-core] " Steffen Sledz
2018-01-04  6:31           ` Steffen Sledz
2018-01-04 14:39           ` [OE-core] " Richard Purdie
2018-01-04 14:39             ` Richard Purdie
2018-01-05 11:29             ` [OE-core] " Steffen Sledz
2018-01-05 11:29               ` Steffen Sledz
2018-01-05 12:22               ` Richard Purdie [this message]
2018-01-05 12:22                 ` Richard Purdie

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=1515154956.30291.30.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=otavio.salvador@ossystems.com.br \
    --cc=ross.burton@intel.com \
    --cc=sledz@dresearch-fe.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.