Re: intention of stubs with arch flag, specially in msvcp*

2010-09-15 Thread André Hentschel
Am 15.09.2010 19:44, schrieb Alexandre Julliard: > André Hentschel writes: > >> The last one silently gets ignored, but the one with the arch flag causes >> winebuild >> to put some extra assembler code into the dll. >> >> So is this intented? > > No. Try something like this: > > diff --git a/

Re: intention of stubs with arch flag, specially in msvcp*

2010-09-15 Thread Alexandre Julliard
André Hentschel writes: > The last one silently gets ignored, but the one with the arch flag causes > winebuild > to put some extra assembler code into the dll. > > So is this intented? No. Try something like this: diff --git a/tools/winebuild/parser.c b/tools/winebuild/parser.c index bc483c9.

intention of stubs with arch flag, specially in msvcp*

2010-09-15 Thread André Hentschel
Hi all, I used to think the arch flag is only used to say "this function is only available on win32" or to say the same for win64. We do that e.g. in msvcp* dlls. So i am not sure why those stubs like @ stub -arch=win32 function differ so heavy from stubs like @ stub function The last