From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Steffen Sledz <sledz@dresearch-fe.de>,
"Burton, Ross" <ross.burton@intel.com>
Cc: openembedded-devel <openembedded-devel@lists.openembedded.org>,
openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: MS Windows machine?
Date: Thu, 04 Jan 2018 14:39:54 +0000 [thread overview]
Message-ID: <1515076794.5525.196.camel@linuxfoundation.org> (raw)
In-Reply-To: <9d1c1e79-5eab-941c-0d30-314f9df51de1@dresearch-fe.de>
On Thu, 2018-01-04 at 07:31 +0100, Steffen Sledz wrote:
> On 21.12.2017 14:00, Steffen Sledz wrote:
> >
> > On 21.12.2017 12:39, Burton, Ross wrote:
> > >
> > > If you want to build for a Windows target then that should be
> > > possible but
> > > nobody as far as I'm aware has made the work public. meta-mingw
> > > will
> > > contain most of the changes needed as that does build Windows
> > > binaries.
> > That's exactly what we like to to.
> >
> > So has anyone tried this before?
> >
> > What else would be needed to build e.g. for MACHINE=i686-mingw32?
> Is someone able to create a machine definition for this? I'm not
> really familiar with this job.
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.
You'd need need to look through the bbappends which are in meta-mingw
and add them to the appropriate pieces you need for target binaries
rather than sdk binaries.
I did once do this for darwin so it is possible, I've never tried it
for windows though.
Cheers,
Richard
next prev parent reply other threads:[~2018-01-04 14:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-21 6:40 MS Windows machine? Steffen Sledz
2017-12-21 9:08 ` Burton, Ross
2017-12-21 9:54 ` Steffen Sledz
2017-12-21 11:39 ` Burton, Ross
2017-12-21 13:00 ` Steffen Sledz
2018-01-04 6:31 ` Steffen Sledz
2018-01-04 14:39 ` Richard Purdie [this message]
2018-01-05 11:29 ` Steffen Sledz
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=1515076794.5525.196.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@lists.openembedded.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox