[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-kimageshop
Subject:    Re: JPEG-XL and upgrading MinGW GCC
From:       Dmitry Kazakov <dimula73 () gmail ! com>
Date:       2022-02-25 7:11:33
Message-ID: CAEkBSfX+ZwD3nR+SEMTKF=rnmLzO28y-m4qZipGSa0JhpsCNrw () mail ! gmail ! com
[Download RAW message or body]

Hi, @Amyspark!

Our docker images are not updated yet, though everything is ready for that.
We only need to wait until sysadmins actually switch them on Jenkins.

For the MSYS, I was fine with switching to it after 5.0 release (which has
happened already). There are only two things we need to take into account:

1) MSYS is a rolling distribution. So we should host all the used packages
somewhere on files.kde.org to fix the versions. And update them manually
when we are ready.
2) Sysadmins were not happy with the switch, because of the installer-based
deployment of MSYS. Though we can try packaging the exact environment
needed for us into a .zip file. That will make the life of sysadmins easier.


On Thu, Feb 24, 2022 at 8:56 PM L. E. Segovia <amy@amyspark.me> wrote:

> Hi all,
>
> I've been tinkering the past couple of days with JPEG-XL, getting it in
> place within 3rdparty. I found that one of the dependencies of libjxl is
> Google's Highway library, which requires something newer than GCC 7.3
> due to:
>
> - support of AVX512 intrinsics
> - usage of the __STDC_FORMAT_MACROS
>
> Fixing the former is needed for our Windows CI, but it will still fail
> on the former item.
>
> Questions:
>
> - Do you know if the Docker image has been updated?
>
> - And what can we do with our Windows build itself, which uses MinGW GCC
> 7.3?  Obviously, switching to MSYS does the trick, but I think Dmitry's
> been reluctant in the past to just do the jump.
>
> Cheers,
>
> amyspark.
>
> --
> amyspark 🌸 https://www.amyspark.me
>


-- 
Dmitry Kazakov

[Attachment #3 (text/html)]

<div dir="ltr">Hi,  @Amyspark!<div><br></div><div>Our docker images are not updated \
yet, though everything is ready for that. We only need to wait until sysadmins \
actually switch them on Jenkins.</div><div><br></div><div>For the MSYS, I was fine \
with switching to it after  5.0 release (which has happened already). There are only \
two things we need to take into account:</div><div><br></div><div>1) MSYS is a \
rolling  distribution. So we should host all the used packages somewhere on <a \
href="http://files.kde.org">files.kde.org</a> to fix the versions. And update them \
manually when we are ready.</div><div>2) Sysadmins were not happy  with the switch, \
because of the installer-based deployment of MSYS. Though we can try packaging the \
exact environment needed for us into a .zip file. That will make the life of \
sysadmins easier.</div><div><br></div></div><br><div class="gmail_quote"><div \
dir="ltr" class="gmail_attr">On Thu, Feb 24, 2022 at 8:56 PM L. E. Segovia &lt;<a \
href="mailto:amy@amyspark.me">amy@amyspark.me</a>&gt; wrote:<br></div><blockquote \
class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex">Hi all,<br> <br>
I&#39;ve been tinkering the past couple of days with JPEG-XL, getting it in <br>
place within 3rdparty. I found that one of the dependencies of libjxl is <br>
Google&#39;s Highway library, which requires something newer than GCC 7.3 <br>
due to:<br>
<br>
- support of AVX512 intrinsics<br>
- usage of the __STDC_FORMAT_MACROS<br>
<br>
Fixing the former is needed for our Windows CI, but it will still fail <br>
on the former item.<br>
<br>
Questions:<br>
<br>
- Do you know if the Docker image has been updated?<br>
<br>
- And what can we do with our Windows build itself, which uses MinGW GCC <br>
7.3?   Obviously, switching to MSYS does the trick, but I think Dmitry&#39;s <br>
been reluctant in the past to just do the jump.<br>
<br>
Cheers,<br>
<br>
amyspark.<br>
<br>
-- <br>
amyspark 🌸 <a href="https://www.amyspark.me" rel="noreferrer" \
target="_blank">https://www.amyspark.me</a><br> </blockquote></div><br \
clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature">Dmitry \
Kazakov</div>



[prev in list] [next in list] [prev in thread] [next in thread]