33782Re: Re: bundling of vim.exe with gvim distribution
- Oct 3, 2003
> As a general rule I agree that the wrapper doesn't make sense.If your system can run "vim32", why do you want "vim16"?
> OTOH, I do think that a package should be provided that
> includes all three versions (GUI, Vim-32, Vim-16); executables
> could be called gvim.exe, vim32.exe, vim16.exe (You could then
> make a wrapper vim.exe that chooses the appropriate version).
> Also, technicall speaking under DOS/Windows you can put moreThis is very easy. Assume that you've already built the DOS version of
> than one version in the same .exe; *most* of the time, the DOS
> part is just a stub that says "Hey man, you need Windows to run
> this program!", but nobody prevents you from using a
> "different" stub, like for example the 16-bit console version.
> So you could create a single vim.exe containing both the 16-bit
> and the 32-bit console version.
vim.exe, and renamed it "vim16.exe", and put it in your object file
directory. When you are linking "vim.exe" (the 32-bit Windows console
version), add "/STUB:vim16.exe" to the LINK command line and the linker
will do the rest. The only downside is that (obviously) the file would
be somewhat larger...
The best thing to hit the internet in years - Juno SpeedBand!
Surf the web up to FIVE TIMES FASTER!
Only $14.95/ month - visit www.juno.com to sign up today!
- << Previous post in topic Next post in topic >>