On Thu, 6 Jun 2019, NightStrike wrote:
For the build bot I used to run, a full build of gcc and its test suite
would take several days for the cygwin target and host.
I mention that because in my experience, it's far more important to test
against the breakages due to compiler changes rather
On 6/5/19 9:42 PM, Martin Storsjö wrote:
On Wed, 5 Jun 2019, Francois Gouget wrote:
3. Build a few projects - to make sure they build.
Wine, Wine Gecko, VLC should give a good coverage.
That sounds like long running tasks so we will likely need new
hardware so the TestBot can run them for
On 6/5/19 8:21 AM, Francois Gouget wrote:
3. Build a few projects - to make sure they build.
Wine, Wine Gecko, VLC should give a good coverage.
That sounds like long running tasks so we will likely need new hardware
so the TestBot can run them for every patch that gets submitted: if
patches
Hi everyone,
I was very excited at first but sadly, it seems this discussion isn't
going anywhere.
I believe cooperation is always beneficial to both sides so I will try
to help moving the debate forward.
Jacek listed 5 discussion topics but I think for sake of clarity we
should create 5
On Mon, 3 Jun 2019, Jacek Caban wrote:
[...]
> Here is how I imagine TestBot could look do:
>
> 1. Accept mingw-w64 patches (like it currently does for Wine patches)
>
> 2. Build a compiler toolchain
>
> This is scripted in many places, so it shouldn't be too hard to automate. We
> could
As a user, and not a coder with "a name", i might just be contributing to noise
by this... Sorry if i am stepping on any toes here tho.
Since mingw-w64 is NOT a "wine project", and can be used for a lot of stuff
totally outside of wine, I think it will be completely wrong to rename it to
On Wed, Jun 5, 2019, 3:43 PM Martin Storsjö wrote:
> On Wed, 5 Jun 2019, Francois Gouget wrote:
>
> >> 3. Build a few projects - to make sure they build.
> >>
> >> Wine, Wine Gecko, VLC should give a good coverage.
> >
> > That sounds like long running tasks so we will likely need new hardware
>
On Wed, 5 Jun 2019, Francois Gouget wrote:
3. Build a few projects - to make sure they build.
Wine, Wine Gecko, VLC should give a good coverage.
That sounds like long running tasks so we will likely need new hardware
so the TestBot can run them for every patch that gets submitted: if
On 22/05/2019 21:45, Jacek Caban wrote:
- Testing
Wine has a TestBot and a number of test cases, which is a great tool
for developers to make sure their patches are right. mingw-w64 does
not have such thing and mostly depends on developers doing their own
testing and regression reports
On 22/05/2019 21:45, Jacek Caban wrote:
- Source code sharing
Technically, we could share much more code than we currently do.
Duplicating efforts is quite suboptimal for everyone. Right now
mingw-w64 imports a number of platform headers and widl tool from Wine
via wine-import.sh script.
On 22/05/2019 21:45, Jacek Caban wrote:
- mingw-w64 name
There have been talks about rebranding mingw-w64 for a long time
(longer than I am in joined the project). While it's a good name for a
branch, an established project that is no longer related to mingw.org
could have a better
How about TeaSDK, CoffeeSDK, or GrapeSDK? :p
Not entirely serious, but also not entirely kidding. Grape sounds like a
good candidate as a common umbrella for Wine and related projects, since
Wine is generated from Grape. Also grape is a simple English word that any
primary school student should
On 5/23/19 9:22 AM, Biswapriyo Nath wrote:
Thank you for this great idea. I agree with the cooperation. But I have
some questions and concerns.
1. What will happen to all the mails, patches, users contributions, issues,
releases etc.?
If we move ML, it would go to new ML. Same for issues.
On 5/23/19 11:52 AM, NightStrike wrote:
On Wed, May 22, 2019 at 3:44 PM Jacek Caban wrote:
Hi all,
[I'm addressing it to both mingw-w64-public and wine-devel]
As most of you know, Wine and mingw-w64 have a lot in common and
cooperate to some extend for quite a while. There have been talks
On Wed, May 22, 2019 at 3:44 PM Jacek Caban wrote:
>
> Hi all,
>
> [I'm addressing it to both mingw-w64-public and wine-devel]
>
> As most of you know, Wine and mingw-w64 have a lot in common and
> cooperate to some extend for quite a while. There have been talks about
> tightening this
Thank you for this great idea. I agree with the cooperation. But I have
some questions and concerns.
1. What will happen to all the mails, patches, users contributions, issues,
releases etc.?
2. Where should we now send the emails and patches? I would suggest for a
separate mailing list.
3. Will
Hi Ruben,
On 22/05/2019 22:17, Ruben Van Boxem wrote:
All this probably is a great idea :). I just have (entirely worthless) 2c
two share on one point you bring up:
Thanks for sharing the opinion, it's definitely not worthless ;)
Op wo 22 mei 2019 om 21:44 schreef Jacek Caban :
-
All this probably is a great idea :). I just have (entirely worthless) 2c
two share on one point you bring up:
Op wo 22 mei 2019 om 21:44 schreef Jacek Caban :
> - mingw-w64 name
>
> There have been talks about rebranding mingw-w64 for a long time (longer
> than I am in joined the project).
Hi all,
[I'm addressing it to both mingw-w64-public and wine-devel]
As most of you know, Wine and mingw-w64 have a lot in common and
cooperate to some extend for quite a while. There have been talks about
tightening this relationship for years. Recent Wine move to using PE
files for its
19 matches
Mail list logo
