1.is anyone working on making winegcc do dlls? 2.what is the "hard part" about making winegcc do dlls? and 3.is there something I can do (code-hacking wise) to help with winegcc dll support?
Le mar 15/07/2003 à 21:23, Jonathan Wilson a écrit :
1.is anyone working on making winegcc do dlls?
Dimitrie (well, if he isn't, then nobody).
2.what is the "hard part" about making winegcc do dlls?
Making sure all mingw's options map (or are discarded) to Unix gcc's.
and 3.is there something I can do (code-hacking wise) to help with winegcc dll support?
Ask Dimitrie. There's probably something, although if you don't mind looking in Makefiles, you can probably extract a method from dlls/Makefile* using regular gcc rather than winegcc. Vincent
--- Jonathan Wilson <jonwil(a)tpgi.com.au> wrote:
1.is anyone working on making winegcc do dlls? 2.what is the "hard part" about making winegcc do dlls? and 3.is there something I can do (code-hacking wise) to help with winegcc dll support?
Winegcc is supposed to act like mingw-gcc from what I understand. Building applications and dll using WINElib and Mingw32-gcc is interesting because there is no consistancy with anything. gcc has the options -mdll and -shared that can be used to build dlls on Mingw but also mingw-binutils has dllwrap/tool to link dlls so I dont know how he is planing on addressing this. Plus you have winebuild thrown in to the mix. People want to fix winebuild and wine libraries to support dlopen()ing them on *nix. Thanks Steven __________________________________ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com
On July 15, 2003 09:23 pm, Jonathan Wilson wrote:
1.is anyone working on making winegcc do dlls?
I was supposed to, but I've been away for over a month, and it takes time to get back into a working mode ... :)
2.what is the "hard part" about making winegcc do dlls?
It's not rocket science, it's just that we should try (hard) to make winegcc behave (as much as possible) as mingw-gcc.
and 3.is there something I can do (code-hacking wise) to help with winegcc dll support?
Help would be appreciated, as it seems this little thing holds up a lot of other stuff. What we need to do is support -shared. The dllwrap/dlltool stuff from binutil has been deprecated for the more standard -shared flag to gcc. So, what we need is: -- recognize the -shared flag in winegcc, and forward to winewrap (easy) -- instrument winewrap to do the winebuild invokation and all the other crap that is done in the Makefiles (not hard, we just need to study the Makefiles for the proper way to build a DLL in Wine). Ideally, we should end up with the same way of building a DLL in Wine as in Mingw. Unfortunately, I don't think that's feasible 100% now. The problem is that mingw-gcc supports __declspec(dllexport) and __declspec(dllimport) which allows it to build the DLL without a .def file. The Unix gcc does not support these, so we will need a .def file for the time being. Not a big problem for now, we can worry about it later. -- Dimi.
participants (4)
-
Dimitrie O. Paun -
Jonathan Wilson -
Steven Edwards -
Vincent Béron