Re: winebuild initialisation

[Eric Pouech]

Jon wrote:
> Hi,
>
> This patch adds initialisation code to apps that import msvcrt. This should be 
> expanded at some point to do the right things for dlls that do the same, but 
> at present, this only affects Winelib users who build their own dlls.
>
> Apps that don't import msvcrt won't see any changes.

any reason why not use DllMain instead of patching winebuild ?

winebuild initialisation

[Jon Griffiths]

Hi,

--- Eric Pouech  wrote:
> any reason why not use DllMain instead of patching winebuild ?

If you mean the DllMain of msvcrt, there is no way for the it to know
what type of app is calling it AFAICS. Only the generated main knows,
and should inform msvcrt when it starts. Also the handling of main()
is different for natively build apps linked with msvcrt: they should
eventually have a different loop than ExitProcess(main())

Some of these settings can be overriden and should be handled by the
.exe file. Wildcard expansion and the user math errors come to mind.
The patch doesn't allow for that yet, since i figured it would be
best to see if any developers actually _do_ override the default c
library initialisation in their win32 apps before supporting it under
Winelib.

Cheers,
Jon

=====
"Don't wait for the seas to part, or messiahs to come;
 Don't you sit around and waste this chance..." - Live

[e-mail]

__________________________________________________
Do you Yahoo!?
Yahoo! Web Hosting - establish your business online
http://webhosting.yahoo.com