[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH v2 0/4] New getprogname module
From: |
Pino Toscano |
Subject: |
Re: [PATCH v2 0/4] New getprogname module |
Date: |
Tue, 06 Sep 2016 15:49:36 +0200 |
User-agent: |
KMail/5.2.3 (Linux/4.6.6-300.fc24.x86_64; KDE/5.25.0; x86_64; ; ) |
Hi Jeremy,
On Tuesday, 6 September 2016 13:13:52 CEST T J wrote:
> Anyway, it appears that this has not been tested on Windows/MinGW as
> it currently does not work. Everything worked fine with the old
> progname module.
>
> A sample build log is here:
> https://ci.appveyor.com/project/fontforge/fontforge/build/1.0.32
I don't have a mingw toolchain myself, so sorry it broke. OTOH, I read
that mingw had the program_invocation_name and
program_invocation_short_name variables (specific to GNU libc)
implemented as well few years ago.
I guess this needs help from somebody with mingw experience.
--
Pino Toscano
signature.asc
Description: This is a digitally signed message part.
- Re: [PATCH v2 0/4] New getprogname module, Jim Meyering, 2016/09/03
- Re: [PATCH v2 0/4] New getprogname module, Pino Toscano, 2016/09/05
- Re: [PATCH v2 0/4] New getprogname module, Jim Meyering, 2016/09/05
- Re: [PATCH v2 0/4] New getprogname module, Jim Meyering, 2016/09/06
- Re: [PATCH v2 0/4] New getprogname module, Pino Toscano, 2016/09/06
- Re: [PATCH v2 0/4] New getprogname module, T J, 2016/09/06
- Re: [PATCH v2 0/4] New getprogname module,
Pino Toscano <=
- Re: [PATCH v2 0/4] New getprogname module, Jim Meyering, 2016/09/06
- Re: [PATCH v2 0/4] New getprogname module, Gisle Vanem, 2016/09/06
- Re: [PATCH v2 0/4] New getprogname module, Jim Meyering, 2016/09/06
- Re: [PATCH v2 0/4] New getprogname module, Jim Meyering, 2016/09/07
- Re: [PATCH v2 0/4] New getprogname module, Gisle Vanem, 2016/09/07
- Re: [PATCH v2 0/4] New getprogname module, Jim Meyering, 2016/09/07
- Re: [PATCH v2 0/4] New getprogname module, Jim Meyering, 2016/09/08