|
From: Steven E. <Ste...@kn...> - 2001-11-13 01:07:37
|
I'm going to try to build a striped vim for reactos based off of vim 6.0 in the next week or so. Steven -----Original Message----- From: Craig Barkhouse To: ros...@re... Sent: 11/12/01 1:40 PM Subject: [ros-kernel] Re: Bug Report - VIM for Win32 There is no fundamental difference between a console app and a GUI app. The difference is mainly what the compiler inserts into your program as startup code. Once running, both types of apps have FULL access to the Win32 API. A console app can suddenly open up windows and dialog boxes; a GUI app can suddenly launch a console session. You get the idea. In addition to window-related functions, User32.dll also has lots of functions for messages, events, processes, and threads. Vim uses User32.dll for FindWindow() (an attempt to get the console window handle, for the purpose of changing the icon (see below)), MsgWaitForMultipleObjects() (for interprocess message passing), and possibly other stuff. Vim uses Shell32.dll for ExtractIcon() (it changes the icon of the console window while it is running) and possibly other stuff. I don't know why Vim needs Comctl32.dll. I wonder if this really was a console build rather than a GUI build. When I build console Vim, it doesn't appear to link with Comctl32.dll. Anyway, you *might* be able to strip Vim down enough so that it doesn't need these DLLs. A lot of these features are not strictly necessary. ----- Original Message ----- From: "Phillip Susi" <ps...@cf...> To: <ros...@re...> Sent: Sunday, November 11, 2001 3:54 PM Subject: [ros-kernel] Re: Bug Report - VIM for Win32 > Isn't vim console based? Then why the heck is it importing things from > user32, comctl32, and shell32? > > At 03:40 PM 11/11/2001 -0500, you wrote: > > >vim.exe crashes because it cant import GetSysColotPen which is a export of > >user32. This is what happens when i try to run vim.exe for win32 ==================================================== To remove yourself from this mailing list, go to = http://www.reactos.com/home/mailing.html =================================================== ########################################### This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange. For more information, connect to http://www.F-Secure.com/ |