On Monday 09 Jan 2006 21:50, Rolf Kalbermatter wrote:
> Paul Millar wrote:
> > The problem above (at the beginning of this year) was with a
> > missing GUID in the compiler, which is now fixed.
>
> Could you tell me what GUID it was.
Certainly, it was IID_IHttpNegotiate2, as defined by:
DEFINE_GU
Paul Millar wrote:
> The problem above (at the beginning of this year) was with a
> missing GUID in the compiler, which is now fixed.
Could you tell me what GUID it was. I'm currently in the process of trying
to get compilation of DLLs working again with MSVC and the winapi tools and
noticed a
Hi Saulius,
On Friday 06 Jan 2006 15:15, Saulius Krasuckas wrote:
> * On Fri, 6 Jan 2006, Paul Millar wrote:
> > WRT builds winetest.exe anyway (in fact, all the DLLs and EXEs it can),
> > but the results are not registered, so no one sees them.
>
> I didn't got it - when do the results get not re
On Friday 06 Jan 2006 01:29, Saulius Krasuckas wrote:
> I may perfectly repeat someones else question, but why in the world
> winetest-200YmmDD1000-paul-mingw.exe files aren't being generated if the
> patches arrives too late during partical day?
>
> I think compiled EXEs should be released regardl
* On Fri, 6 Jan 2006, Paul Millar wrote:
> * On Friday 06 Jan 2006 01:29, Saulius Krasuckas wrote:
> >
> > I think compiled EXEs should be released regardless of their
> > generation date. No?
Excuse me for my typos and logical mistakes, but..
> Personally, I'd prefer building winetest.exe as p
I may perfectly repeat someones else question, but why in the world
winetest-200YmmDD1000-paul-mingw.exe files aren't being generated if the
patches arrives too late during partical day?
I think compiled EXEs should be released regardless of their generation
date. No?
