All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Francois Retief <fgretief@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: GCC search paths in MinGW SDK
Date: Wed, 04 Sep 2013 14:00:45 +0100	[thread overview]
Message-ID: <1378299645.1059.236.camel@ted> (raw)
In-Reply-To: <CAFpw0gLn_s_SYaj9mMtYJvBfc1dqYEzYcXFn04J9+Xm1UroLeA@mail.gmail.com>

On Tue, 2013-09-03 at 23:13 +0200, Francois Retief wrote:
> Thanks to Richard's recent improvements in the oe-core tree, I finally
> got my first MinGW build to compile through and generate a SDK
> tarball.
>
> Next issue is that on windows GCC is unable to find the crt1.o, crti.o
> and crtbegin.o files. when compiling a small hello world app (see gist
> [1] for gcc verbose output). I verified that the files are indeed in
> the SDK folders and was correctly unpacked. 

Make sure you specify --sysroot=xxxx where xxxx is the location of
target sysroot you want to compile against.

> ps. I have noticed that there is a relocate_sdk.py file in the root of
> the SDK folder. What is it's purpose and can it have anything to do
> with the GCC search paths?

It is used on Linux to help with these kinds of issues, it will be
completely useless on windows and we shouldn't ship it there.

I've shared the result of my tweaks as
http://git.yoctoproject.org/cgit.cgi/meta-mingw/ btw. I flattened the
history as I had a ton of now meaningless commits and tests so it made
sense for a clean start IMO.

Cheers,

Richard




  parent reply	other threads:[~2013-09-04 13:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-03 21:13 GCC search paths in MinGW SDK Francois Retief
2013-09-04  1:45 ` Mark Hatle
2013-09-04 13:03   ` Richard Purdie
2013-09-13  5:54   ` Khem Raj
2013-09-13  7:04     ` Francois Retief
2013-09-04 13:00 ` Richard Purdie [this message]
2013-09-04 15:40   ` Otavio Salvador

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=1378299645.1059.236.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=fgretief@gmail.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 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.