[Mesa-dev] [OS]Mesa MinGW AppVeyor Repository

[Eric Engestrom]

On Monday, 2017-10-02 14:16:02 +0000, Trevor (CIMdata) wrote:
> Hello Emil,
> Yes, I did see the AppVeyor integraton for MSVC. It could be quite
> easy to add the MinGW scope to the metrix.
> 
> I don’t really know how to ‘upsteam’ the patches I use mostly because
> I am not the author. Do I just submit a PR? Anyway to help George with
> his patch – which fixes the MinGW build – I have done the CI script,
> AppVeyor.yml and set up AV repo. My source if free and w/o license.

Just FYI, it's a common misconception that "no license" means "license
to do anything", but what it really means is "whatever the default is in
the legislation of the country/state the author happens to have been in
when they wrote this", which is usually close to impossible to know for
everyone else.

If your point is to distribute your code freely, consider the MIT
license, or look at https://choosealicense.com


> Please feel free to use it if you wish. Many thanks!
> 
> Cheers,
> 
> Trevor SANDY
> +33 682 100 571
> 
> From: Emil Velikov
> Sent: 02 October 2017 16:04
> To: Trevor Sandy
> Cc: Kyriazis, George; mesa-dev at lists.freedesktop.org
> Subject: Re: [Mesa-dev] [OS]Mesa MinGW AppVeyor Repository
> 
> Hi Trevor,
> 
> On 2 October 2017 at 13:48, Trevor Sandy <trevor.sandy at gmail.com> wrote:
> > Hi George,
> >
> > You might be interested to know I have set up a CI env on AppVeyor for MinGW
> > builds.
> >
> > Here is the GitHub repo: https://github.com/trevorsandy/osmesa_mingw_av.
> > Follow the badge in the README to the AppVeyor instance.
> >
> > You can demo your patches quite easily - see the README.md on how to extract
> > source that can be used by my build script. Or change set the version to
> > download and build its source bundle. Perhaps later on I'll add the ability
> > to get build content (tag, branch, commit etc...) directly from Mesa's git
> > repo.
> >
> The upstream Mesa repository has AppVeyor integration, admittedly it
> builds only with MSVC.
> 
> If you want for things to work, I strongly recommend upstreaming your patches.
> Otherwise it will be in a perpetual state of brokenness and you'll
> have to dedicate even more resources as time goes by.
> 
> Thanks
> Emil
>