> > PS. Should we create a Trac issue for this, to help remember we need to
> fix it in the future?
>
> I don’t need a ticket for it, the compiler is nagging every time I build
> LyX :)
It's fine by me. In case you wondered, some reasons I thought of creating
an issue:
- gives background, eg why
Am 08.07.2017 um 23:42 schrieb Christian Ridderström :
>
> On 8 July 2017 at 22:01, Stephan Witt wrote:
> I’m aware of these warnings. Recently I tried to replace the deprecated calls
> in os_unix.cpp. But that’s not easy.
> 1. The replacements have to be available at least with 10.7 or we have
On 8 July 2017 at 22:01, Stephan Witt wrote:
> I’m aware of these warnings. Recently I tried to replace the deprecated
> calls in os_unix.cpp. But that’s not easy.
> 1. The replacements have to be available at least with 10.7 or we have to
> de-support old systems.
> 2. The replacements have to b
Hi Christian,
I’m aware of these warnings. Recently I tried to replace the deprecated calls
in os_unix.cpp. But that’s not easy.
1. The replacements have to be available at least with 10.7 or we have to
de-support old systems.
2. The replacements have to be provide the same functionality as the
Hi,
While compiling on macOS Sierra, 10.12,5, I noticed warnings about
deprecated calls from an Objective C file. Below is a log excerpt, there
are probably more warnings.
What's the policy is here... should I e.g. create a Trac issue?
It's not obvious to me that we at this time would want to sw
