On Wed, May 18, 2011 at 10:26 AM, Leonardo Valeri Manera
<[email protected]> wrote:
> On 18 May 2011 03:02, Guopeng Wen <[email protected]> wrote:
>> I've uploaded release 0.9 of my patch for Vim NSIS installer to
>> github:
>> https://github.com/gpwen/vim-installer-mui2/wiki
[snip]
>
> Very nice. Pretty much the only that's missing, as far as I'm
> concerned, is an option to disable win95 compatibility.
>
> Those of us using the free SDKs to compile can't build the
> COMMAND.COM text version anyway, so its bogus in our custom-made
> installer packages, since the recent SDKs won't go below win2000
> or XP.
I suppose by "win95 compatibility", you mean Windows 95 console
version "vimd32.exe" is not easy to build, right? That's the only
file specific to Window 95/98/ME.
> Unless I missed the ability to do that. In which case I'd love to
> know how its done ...
What I did is including a bogus vimd32.exe like you said, generated
with something like:
touch vimd32.exe
I think this method should be good enough if you're not intended to
distribute the installer widely; Otherwise, it might be a good idea
to build a full fledged installer.
With that said, a more complex solution might be:
- Add a macro to determine whether "vimd32.exe" should be included
or not;
- If "vimd32.exe" has been excluded, and the installer determined
that the target platform is Window 95/98/ME, the "Vim console
program" component will be disabled.
In this way, the installer is still usable on Windows 95 (so, still
Windows 95 compatible), except some functionality is lost.
Any suggestion?
--
Guopeng
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
