Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Zhang, Jessica" <jessica.zhang@intel.com>
Cc: "Sywula, Krzysztof M" <krzysztof.m.sywula@intel.com>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: Yocto toolchain for Windows
Date: Wed, 14 Aug 2013 10:27:21 +0100	[thread overview]
Message-ID: <1376472441.22952.3.camel@ted> (raw)
In-Reply-To: <C6510F6D410BB64A8C15398EDC6B847C73C69E71@ORSMSX103.amr.corp.intel.com>

On Wed, 2013-08-14 at 00:00 +0000, Zhang, Jessica wrote:
> Hi Richard,
> 
> I've tried the sdk on windows and here're the issues that I've run into:
> 
> 1. in our sysroot all the libraries have .so we need to change them to .dll

Which sysroot? The one for the target system should be using .so's since
we're targeting a Linux system.

> 2. seems the cross compiler i586-poky-linux-gcc.exe relies on
> libiconv-2.dll, so I manually installed that dll.

No surprise since the dynamic linking detection doesn't work for
windows. We can add a manual dependency to resolve that.

> 3. Now when I run i586-poky-linux-gcc.exe, I'm getting "the application was
> unable to start correctly (0xc000007b). Click OK  to close the application."
> By doing some initial search on the error, it seems relate to 32/64 bit dll
> mismatch.  You mentioned that 32bit windows binaries are generated, so can
> we generate a 64bit for me to try since my windows box is a 64bit.

I was confused, they are supposed to be windows 64 bit binaries (and
file under Linux says they are) so something other than what I
originally thought is wrong.

Cheers,

Richard



      reply	other threads:[~2013-08-14  9:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <6741EAAB26B57F4995668065CB62D86B33933627@IRSMSX102.ger.corp.intel.com>
     [not found] ` <CAFpw0gKhTFiKC8BwPhtULqmtkuzgYV3MVPOCLn64ibgGYjuaGA@mail.gmail.com>
     [not found]   ` <6741EAAB26B57F4995668065CB62D86B33933DFC@IRSMSX102.ger.corp.intel.com>
     [not found]     ` <CAFpw0gKiRwXD8gJhG+7XDSHSGEvZY3YBR5MxBZieVMYPd_sL1g@mail.gmail.com>
     [not found]       ` <6741EAAB26B57F4995668065CB62D86B33934034@IRSMSX102.ger.corp.intel.com>
2013-08-12 13:34         ` Yocto toolchain for Windows Francois Retief
2013-08-13 16:17           ` Khem Raj
2013-08-13 20:11             ` Richard Purdie
2013-08-13 20:21               ` Khem Raj
2013-08-14  0:00               ` Zhang, Jessica
2013-08-14  9:27                 ` Richard Purdie [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=1376472441.22952.3.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=jessica.zhang@intel.com \
    --cc=krzysztof.m.sywula@intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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