public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/105719] RFE: fixincludes should handle Frameworks
Date: Tue, 24 May 2022 19:21:22 +0000	[thread overview]
Message-ID: <bug-105719-4-X8o0Gir36W@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105719-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105719

Iain Sandoe <iains at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |iains at gcc dot gnu.org

--- Comment #3 from Iain Sandoe <iains at gcc dot gnu.org> ---
(In reply to Eric Gallager from comment #0)
> This is split off from bug 93082. Basically, if there is a header that needs
> to be fixincluded in /Systems/Library/Frameworks or /Library/Frameworks or
> ${SDKROOT}/Library/Frameworks, fixincludes currently won't find it. This
> should be fixed by adding another include tree (or trees) for fixincludes to
> search.

the way that header search works, you probably want to keep the sysroot (a.k.a
SDKROOT) distinct (you might want to look in gcc/config/darwin-c.cc for how the
eventual search paths are constructed, just for background).

Solving 37036 would also allow us to have multiple SDKs - which would be nice
since we can, in principle, target any version of Darwin with the same compiler
- the limitation preventing that is that the fixed includes (and SDK includes
used in some libraries) do not work over more than a few OS revisions ..
forcing us to need cross compilers for other OS versions in a rather artificial
way.  If we could implement the OS version as a multilib we could avoid that
and just have one compiler to target any version (or the same arch, of course).

[dreams of things we might do if time were available]

  parent reply	other threads:[~2022-05-24 19:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-24 14:41 [Bug target/105719] New: " egallager at gcc dot gnu.org
2022-05-24 14:42 ` [Bug target/105719] " egallager at gcc dot gnu.org
2022-05-24 14:49 ` egallager at gcc dot gnu.org
2022-05-24 19:21 ` iains at gcc dot gnu.org [this message]
2023-05-14 19:43 ` iains at gcc dot gnu.org
2023-05-15 18:10 ` bkorb at gnu dot org
2023-05-18 10:24 ` egallager at gcc dot gnu.org
2024-06-07 19:58 ` egallager at gcc dot gnu.org

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=bug-105719-4-X8o0Gir36W@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).