public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: Mingw64 and Cygwin: header and libs layout
Date: Tue, 13 Mar 2012 13:37:00 -0000	[thread overview]
Message-ID: <20120313133621.GA32472@calimero.vinschen.de> (raw)
In-Reply-To: <CAEwic4aRc24XLsxz5NYhWN+z=KFX_qQ+hOWbzK6sdB5m-JCigw@mail.gmail.com>

Hi Kai,

On Mar 13 14:25, Kai Tietz wrote:
> Hi Corinna,
> 
> I suggest the approach to install for cygwin the platform-headers to a
> shared place.  I suggest that mingw-w64 adds to configure for headers
> and crt an option, which installs platform-headers/libraries to
> '/usr/shared/psdk_windows' location.  Means under this path are the
> folders lib/lib64/include containing only the platform-parts.

That sounds like an excellent idea to me!

> For the cygwin-based mingw-w64 cross-compiler we need to add here by
> spec (for headers in gcc and for libs in binutils or gcc).  IMHO this
> should be a special configuration option for gcc (and binutils), which
> adds the required parts to spec-files.

IMHO we should keep the "w32api" scheme.  The reason is that this
requires no changes at all to the gcc specs file.  Rather, the Cygwin
gcc package would simply create matching symlinks:

  ln -s /usr/share/windows_psdk/include /usr/include/w32api
  ln -s /usr/share/windows_psdk/lib     /usr/lib/w32api
  ln -s /usr/share/windows_psdk/lib64   /usr/lib64/w32api

> The CRT libraries and headers should stay IMHO in private places for
> toolchain.  There is no need to put them under different locations or
> to have them at shared-locations AFAICS., as cygwin-toolchain won't
> provide this '-mno-cygwin' approach.  So toolchains are regarding
> their CRT-headers isolated.

Absolutely.


Thanks,
Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

  reply	other threads:[~2012-03-13 13:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-13 10:11 Corinna Vinschen
2012-03-13 13:25 ` Kai Tietz
2012-03-13 13:37   ` Corinna Vinschen [this message]
2012-03-13 13:51     ` Christopher Faylor
2012-03-13 14:01       ` Corinna Vinschen
2012-03-13 22:48         ` JonY
2012-03-16 17:20         ` Charles Wilson
2012-03-24 18:12 ` Dave Korn
2012-03-24 19:20   ` Corinna Vinschen
2012-03-24 22:59     ` Dave Korn
2012-03-25 12:28       ` Corinna Vinschen
     [not found]         ` <CAEwic4aBE6fn57ZGt2nM5bxxF8EDcB4e4XT8kGrEN6v=m-QFJA@mail.gmail.com>
2012-03-26  9:55           ` Kai Tietz

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=20120313133621.GA32472@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --cc=cygwin-apps@cygwin.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).