public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Costas Argyris <costas.argyris@gmail.com>
To: Jacek Caban <jacek@codeweavers.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: Enable UTF-8 code page in driver and compiler on 64-bit mingw host [PR108865]
Date: Tue, 7 Mar 2023 14:00:06 +0000	[thread overview]
Message-ID: <CAHyHGCkK8nkE6P27naxMaQ35rdG40VZCMGGcRDa_MGtPp7pHFw@mail.gmail.com> (raw)
In-Reply-To: <508051a3-0314-bb4a-1ce8-5772b1b8f5a6@codeweavers.com>

[-- Attachment #1: Type: text/plain, Size: 2352 bytes --]

Hi Jacek,

"Is there a reason to make it specific to x86_64? It seems to me that all
mingw hosts could use it."

Are you referring to the 32-bit host?    My concern here is that this
functionality (embedding the UTF-8
manifest file into the executable) is only truly supported in recent
versions of Windows.    From:

https://learn.microsoft.com/en-us/windows/apps/design/globalizing/use-utf8-code-page

It says that Windows Version 1903 (May 2019 Update) enables this, so we are
looking at the 64-bit
version of Windows.

I suppose you are referring to the scenario where one has a 32-bit gcc +
mingw running in a 64-bit
Windows that is recent enough to support this?    It is not clear to me
based on the above doc what
would happen encoding-wise in that situation, and I haven't tried it either
because I assumed that
most people would want the 64-bit version of gcc since they are probably
running a 64-bit OS.

If you think it is useful, I could look into that as a separate task to try
and keep this one simple, if
that makes sense.

"I think that .manifest file should also be a dependency here."

Why is that?    Windres takes only the .rc file as its input, as per its
own doc, and it successfully
compiles it into an object file.    The .manifest file is only referenced
by the .rc file, and it doesn't
get passed to windres, so I don't see why it has to be listed as a
prerequisite in the make rule.

Thanks,
Costas

On Tue, 7 Mar 2023 at 12:02, Jacek Caban <jacek@codeweavers.com> wrote:

> Hi Costas,
>
> On 3/7/23 01:52, Costas Argyris via Gcc-patches wrote:
>
> This is a proposal for addressing
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108865
>
> by integrating the UTF-8 manifest file into gcc's build process for the
> 64-bit mingw host.
>
>
> Is there a reason to make it specific to x86_64? It seems to me that all
> mingw hosts could use it.
>
>
>
> +# The resource .rc file references the utf8 .manifest file.
> +# Compile it into an object file using windres.
> +# The resulting .o file gets added to host_extra_gcc_objs in
> +# config.host for x86_64-*-mingw* host and gets linked into
> +# the driver as a .o file, so it's lack of symbols is OK.
> +utf8rc-mingw32.o : $(srcdir)/config/i386/utf8-mingw32.rc
> +	$(WINDRES) $< $@
>
>
> I think that .manifest file should also be a dependency here.
>
>
> Thanks,
>
> Jacek
>

  reply	other threads:[~2023-03-07 14:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-07  0:52 Costas Argyris
2023-03-07 12:01 ` Jacek Caban
2023-03-07 14:00   ` Costas Argyris [this message]
2023-03-07 14:17     ` Jacek Caban
2023-03-07 15:27       ` Costas Argyris
2023-03-08 10:52         ` Costas Argyris
2023-03-09 13:33           ` Costas Argyris
2023-03-09 15:03             ` Jonathan Yong
2023-03-27 17:17               ` Costas Argyris
2023-03-28  8:05                 ` Jonathan Yong
2023-03-28 10:43                   ` Costas Argyris
2023-03-28 12:03                     ` Jonathan Yong

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=CAHyHGCkK8nkE6P27naxMaQ35rdG40VZCMGGcRDa_MGtPp7pHFw@mail.gmail.com \
    --to=costas.argyris@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jacek@codeweavers.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).