[Mesa-dev] [PATCH 0/2] Compilation fixes for mingw

Brian Paul brianp at vmware.com
Tue Mar 21 19:57:02 UTC 2017


> On Mar 19, 2017, at 4:37 PM, Emil Velikov <emil.l.velikov at gmail.com> wrote:
> 
> On 19 March 2017 at 22:16, Miklós Máté <mtmkls at gmail.com> wrote:
>> On 19/03/17 22:13, Emil Velikov wrote:
>>> 
>>> Hi Miklós,
>>> 
>>> On 19 March 2017 at 12:28, Miklós Máté <mtmkls at gmail.com> wrote:
>>>> 
>>>> After this series the build goes further, but eventually stops with:
>>>>  scons: Building targets ...
>>>>  Archiving build\windows-x86-debug\gallium\auxiliary\libgallium.a ...
>>>>  Installing build\windows-x86-debug\bin\u_atomic_test.exe ...
>>>>  Compiling src\gallium\tests\unit\u_format_compatible_test.c ...
>>>>  The command line is too long.
>>>>  scons: *** [build\windows-x86-debug\gallium\auxiliary\libgallium.a]
>>>> Error 1
>>>>  scons: building terminated because of errors.
>>>> 
>>>> To fix this error one would probably need to compile gallium/auxillary
>>>> into 2-3
>>>> smaller archives and then compose them into libgallium.a. Unfortunately,
>>>> my
>>>> buildsystem knowledge is too weak for this.
>>>> 
>>> Can you elaborate why/how you're building things on your end.
>>> 
>>> Appveyor (admittedly using MSVC) and local [Archlinux]
>>> cross-compilation via mingw-w64 works like a charm without any of
>>> these.
>>> Are you using the 'old' mingw aka mingw32 - it looks abandoned, so I'd
>>> suggest sticking with the "w64" one.
>> 
>> I have very limited knowledge about windows, I just wanted to help Federico
>> with his quest of running kotor with llvmpipe on windows. I saw in the mesa
>> documentation that I can use mingw to build it, I googled mingw, the first
>> result was mingw.org, the download link took me to sourceforge, and I
>> downloaded the installer from there. Now I see that there is also a
>> mingw-w64.org. Oh well.
>> 
> Right - we might as well correct documentation/build to explicitly
> state mingw-w64.
> 
> Jose considering the issues reported I'm assuming that you guys are
> using the w64 one, if any ?

Yeah, just w64.


> Any objections if we "deprecate" support for mingw-w32 ?

I think that’s OK.

-Brian


> 
>>> 
>>> Can I ask you to try and hookup mingw into our Appveyor builds - it
>>> should be possible to use it but I haven't tried.
>> 
>> I can try, but my experience in this area is very limited.
>> 
> Link Appveyor with your Github account (iirc you don't even need an
> account for the former) and experiment ;-)
> 
>> 
>>> 
>>>> Miklós Máté (2):
>>>>   c11: fix include with mingw
>>> 
>>> This one might be ok, need to check.
>>> 
>>>>   c11: comment out thrd_equal()
>>>> 
>>> But this one is not - if anything we need to fix the 'interesting'
>>> Windows code in MAPI to use it. I've got some work in the area, that I
>>> really should finish on of these days.
>> 
>> OK, nevermind then.
>> 
> It's an issue on our end, but thank you very much for pointing out it.
> If you'd can spot any references to mingw and update those to
> mingw-w64 [sending a patch or two] that will be greatly appreciated !
> 
> Thanks
> Emil
> _______________________________________________
> mesa-dev mailing list
> mesa-dev at lists.freedesktop.org
> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.freedesktop.org_mailman_listinfo_mesa-2Ddev&d=DwIGaQ&c=uilaK90D4TOVoH58JNXRgQ&r=Ie7_encNUsqxbSRbqbNgofw0ITcfE8JKfaUjIQhncGA&m=RJP1oYpsZQACs3N2lWWpMzncTxAYFyVTCsLsGyVYhhM&s=sj0L7qdKjjG339cDt6mc_0oC7Y9yqCYSvf-7OFJlaSs&e= 



More information about the mesa-dev mailing list