Loading ...
Sorry, an error occurred while loading the content.

RE: Win32 gVim NSIS2 installer

Expand Messages
  • Bram Moolenaar
    ... If the size increase is this small, I think it s a good idea to include the console versions. Allow the user to select whether he wants to install the
    Message 1 of 26 , Mar 1, 2004
    • 0 Attachment
      Alejandro Lopez-Valencia wrote:

      > >> Would it be possible to add a selection of console versions to
      > >> the installers too? (Letting the user choose which one to
      > >> install, that is) Or would this make the package
      > >> tooooooooooooooo big?
      > >
      > > I think it would not be a bad idea to include _one_ console version.
      > > However, there is no console version that runs well on both Win
      > > 95/98/ME
      > > and on NT/2000/XP. Thus we would have to include both versions and
      > > decide between the two when installing.
      > >
      > > I wonder how much the package grows when adding the two vim.exe files.
      >
      > I have an answer. Using LZMA compression:
      >
      > Installer including gvim, with the compiler/cpp flags mentioned before.
      >
      > EXE header size: 36352 / 35328 bytes
      > Install code: (60721 bytes)
      > Install data: (9500528 bytes)
      > Uninstall code+data: (5007 bytes)
      > Compressed data: 2480940 / 9566256 bytes
      > CRC (0xAA3664F9): 4 / 4 bytes
      >
      > Total size: 2517296 / 9601588 bytes (26.2%)
      >
      > Installer including 32-bit console vim and gvim.
      >
      > EXE header size: 36352 / 35328 bytes
      > Install code: (60749 bytes)
      > Install data: (10588532 bytes)
      > Uninstall code+data: (5007 bytes)
      > Compressed data: 2635370 / 10654288 bytes
      > CRC (0x170725C8): 4 / 4 bytes
      >
      > Total size: 2671726 / 10689620 bytes (25.0%)
      >
      >
      > I was *way* off in my size increase guess. It seems this installer does
      > a binary xdelta!

      If the size increase is this small, I think it's a good idea to include
      the console versions. Allow the user to select whether he wants to
      install the console vim or not. Then install the Win 98 or Win XP
      version, depending on the current system.

      I assume the LZMA decompression doesn't require the user to install
      something, right?

      --
      GUARD #1: What -- a swallow carrying a coconut?
      ARTHUR: It could grip it by the husk!
      GUARD #1: It's not a question of where he grips it! It's a simple question
      of weight ratios! A five ounce bird could not carry a 1 pound
      coconut.
      The Quest for the Holy Grail (Monty Python)

      /// Bram Moolenaar -- Bram@... -- http://www.Moolenaar.net \\\
      /// Sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
      \\\ Project leader for A-A-P -- http://www.A-A-P.org ///
      \\\ Buy at Amazon and help AIDS victims -- http://ICCF.nl/click1.html ///
    • Alejandro Lopez-Valencia
      On Sunday, February 29, 2004 1:20 PM, Giuseppe Bilotta broke the silence ... Ahh yes! I think your request is reasonable. I d be happy with English and
      Message 2 of 26 , Mar 1, 2004
      • 0 Attachment
        On Sunday, February 29, 2004 1:20 PM, Giuseppe Bilotta broke the silence
        of shunyata and uttered:

        > On Sunday, February 29, 2004 Alejandro Lopez-Valencia wrote:
        >> You are right. I've reading further into the manual and it is
        >> completely possible to create extra installers that look for the
        >> location of the main package before letting themselves be dump to
        >> the disk. Hmmm... Now that I think of it, that's how Winamp
        >> extensions work when using NSIS installers.
        >
        > That would be an excellent idea.
        >
        > And about localization: would it be possible to choose which
        > localization to install? I don't want to install 65 Gigabytes
        > of data when I'm going to use only 3 Kbs ;)
        >
        > (Seriously, I wouldn't need anything but English and Italian,
        > for example ...)

        Ahh yes! I think your request is reasonable. I'd be happy with English
        and Spanish, and the latter mostly to impress chicks at parties telling
        them I am the translator. ;-)

        Hmm.. I think the implementation is mostly sweat. I don't promise
        anything, but I'll take a stab at it and deliver a first draft
        installer. First I need to reacquaint myself with the source code
        distribution tarballs. (I have used the CVS repository for so long, the
        splits are non-existent in my mind.)
      • Matthias Mohr
        ... No, it s just one of the possible compression methods from NSIS. I also vote for integration of the console executables. But the help files and language
        Message 3 of 26 , Mar 1, 2004
        • 0 Attachment
          > > Installer including 32-bit console vim and gvim.
          > >
          > > EXE header size: 36352 / 35328 bytes
          > > Install code: (60749 bytes)
          > > Install data: (10588532 bytes)
          > > Uninstall code+data: (5007 bytes)
          > > Compressed data: 2635370 / 10654288 bytes
          > > CRC (0x170725C8): 4 / 4 bytes
          > >
          > > Total size: 2671726 / 10689620 bytes (25.0%)
          > >
          > >
          > > I was *way* off in my size increase guess. It seems this installer does
          > > a binary xdelta!
          >
          > If the size increase is this small, I think it's a good idea to include
          > the console versions. Allow the user to select whether he wants to
          > install the console vim or not. Then install the Win 98 or Win XP
          > version, depending on the current system.
          >
          > I assume the LZMA decompression doesn't require the user to install
          > something, right?
          No, it's just one of the possible compression methods from NSIS.
          I also vote for integration of the console executables.
          But the help files and language dependend things should be made in different "extension" installers!

          I installed NSIS v2 on my computer and did some small changes to the gvim.nsis to make the v2 NSIS happy.
          And I also included the console executables - but my knowledge about NSIS is very small, so I included them hardcoded.

          BTW, I also tried to examine the version information from the build executable gvim.exe (including patchlevel)
          A NSIS-function for that purpose is really easy, but I have no idea how I execute that function at the very first beginning of NSIS
          compilation process.

          So finally I ended up with defines again :-(

          Is there anybody with good knowledge about NSIS who can help?

          with regards,
          Matthias

          SysDesign - The Solution Behind IT.

          Ihr Spezialist für Systemtechnik sowie Hard- und Softwareentwicklung für alle technischen Anwendungsbereiche.
          --------------------------------------------------------------------------
          Your specialist for systems engineering as well as hard and software engineering for all technical fields of application.
        • Alejandro Lopez-Valencia
          On Monday, March 01, 2004 7:52 AM, Matthias Mohr broke the silence of ... I am not particuarly knowledgeable, but I am writing a prototype.
          Message 4 of 26 , Mar 1, 2004
          • 0 Attachment
            On Monday, March 01, 2004 7:52 AM, Matthias Mohr broke the silence of
            shunyata and uttered:

            >
            > Is there anybody with good knowledge about NSIS who can help?

            I am not particuarly knowledgeable, but I am writing a prototype.
          • Jonathan D Johnston
            ... Actually, Dos32 Vim (compiled with DJGPP) is recommended for Win9x console. From my experience, it works great for Win98se. ... Also, see the options at
            Message 5 of 26 , Mar 1, 2004
            • 0 Attachment
              On Sunday, February 29, 2004 Alejandro Lopez-Valencia wrote:
              > There is a problem though. The 32-bit console version doesn't work
              > well in Win9x. In those systems, the 16-bit console version works
              > better. Now we start talking about including three versions... Hmm...
              > You'll need OpenWatcom for perpetrating such a feat :-)

              Actually, Dos32 Vim (compiled with DJGPP) is recommended for Win9x
              console. From my experience, it works great for Win98se.

              :h dos16
              :h dos32
              Also, see the options at http://www.vim.org/download.php#pc

              Regards,
              Jonathan D Johnston

              ________________________________________________________________
              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!
            • Alejandro Lopez-Valencia
              On Monday, March 01, 2004 10:44 AM, Jonathan D Johnston broke the ... Are you sure? I think you mean this: Dos16 version Can be used on any MS-DOS system,
              Message 6 of 26 , Mar 1, 2004
              • 0 Attachment
                On Monday, March 01, 2004 10:44 AM, Jonathan D Johnston broke the
                silence of shunyata and uttered:

                > On Sunday, February 29, 2004 Alejandro Lopez-Valencia wrote:
                >> There is a problem though. The 32-bit console version doesn't work
                >> well in Win9x. In those systems, the 16-bit console version works
                >> better. Now we start talking about including three versions... Hmm...
                >> You'll need OpenWatcom for perpetrating such a feat :-)
                >
                > Actually, Dos32 Vim (compiled with DJGPP) is recommended for Win9x
                > console. From my experience, it works great for Win98se.
                >
                > :h dos16
                > :h dos32
                > Also, see the options at http://www.vim.org/download.php#pc

                Are you sure? I think you mean this:

                """
                Dos16 version Can be used on any MS-DOS system, only uses up to 640
                Kbyte of
                memory. Also runs on OS/2, Windows 95, and NT. Excludes some
                Vim-specific features (autocommands, syntax highlighting,
                etc.). Recommended for use on pre-386 machines.
                *dos32*
                Dos32 version Requires 386 processor and a |DPMI| driver, uses all
                available memory. Supports long file names and the Windows
                clipboard, but NOT on Windows NT. Recommended for MS-DOS,
                Windows 3.1 and Windows 95.

                There are also two versions that run under Windows:
                Win32 version Requires Windows 95 or Windows NT, uses all available
                memory, supports long file names, etc. Has some problems on
                Windows 95. Recommended for Windows NT. See |os_win32.txt|
                Win32 GUI Requirements like the Win32 version, but runs in its own
                window, instead of a console. Has scrollbars, menu, etc.
                Recommended for Windows 95 and Windows NT. See |gui-w32|.
                """

                I am not particularly privy to using a DPMI driver is I can help it. It
                has always being unstable for me.
              • Alejandro Lopez-Valencia
                On Monday, March 01, 2004 12:04 PM, Alejandro Lopez-Valencia broke the ... OK. Now I know why I shuold not type without looking directly to the screen: I am
                Message 7 of 26 , Mar 1, 2004
                • 0 Attachment
                  On Monday, March 01, 2004 12:04 PM, Alejandro Lopez-Valencia broke the
                  silence of shunyata and uttered:


                  > I am not particularly privy to using a DPMI driver is I can help it.
                  > It
                  > has always being unstable for me.

                  OK. Now I know why I shuold not type without looking directly to the
                  screen: "I am not particularly privy to using a DPMI driver if I can
                  help it. It has always been unstable for me." :-)
                • Jonathan D Johnston
                  ... I wrote ... [snipped quotation from doc/os_msdos.txt] Which is the same thing that I wrote. Look at the last sentence for ... Recommended for MS-DOS,
                  Message 8 of 26 , Mar 1, 2004
                  • 0 Attachment
                    Alejandro Lopez-Valencia wrote:
                    > There is a problem though. The 32-bit console version doesn't work
                    > well in Win9x. In those systems, the 16-bit console version works
                    > better. Now we start talking about including three versions... Hmm...
                    > You'll need OpenWatcom for perpetrating such a feat :-)

                    I wrote
                    > Actually, Dos32 Vim (compiled with DJGPP) is recommended for Win9x
                    > console. From my experience, it works great for Win98se.
                    >
                    > :h dos16
                    > :h dos32
                    > Also, see the options at http://www.vim.org/download.php#pc

                    Alejandro Lopez-Valencia wrote:
                    > Are you sure? I think you mean this:
                    [snipped quotation from doc/os_msdos.txt]

                    Which is the same thing that I wrote. Look at the last sentence for
                    :h dos32
                    "Recommended for MS-DOS, Windows 3.1 and Windows 95."

                    Also, from http://www.vim.org/download.php#pc :
                    32 bit DOS executable vim##d32.zip vim62d32.zip
                    The 32 bit DOS version works well on MS-Windows 95/98/ME. It
                    requires a DPMI manager, which needs to be installed on
                    MS-DOS. MS-Windows already has one. It supports long file
                    names, but NOT on MS-Windows NT/2000/XP. It is compiled
                    with "big" features

                    Alejandro Lopez-Valencia wrote:
                    [...]
                    > "I am not particularly privy to using a DPMI driver if I can
                    > help it. It has always been unstable for me." :-)

                    As noted at vim.org, DPMI is built into Win32, so no third-party driver
                    is needed unless you want to use Vim from MS-DOS. I have only
                    occasionally used the Dos32 Vim from MS-DOS. For DOS, I use the
                    CWSDPMI that is distributed in vim##d32.zip. No Vim DPMI problems, from
                    Windows or DOS, so far.

                    Console for Win9x, in summary & from my perspective:
                    Dos32/DJGPP Vim:
                    + 32-bit
                    + For years has been the recommended console version for Win9x
                    + Years of experience by Vim developers & users
                    - Some people don't like DPMI

                    A new 16-bit compilation or some "third-party" 16-bit port:
                    + No DPMI
                    - 16-bit
                    - No/little experience by Vim developers or users

                    Maybe your NSIS2 package needs to include *three* console versions. :-)

                    Regards,
                    Jonathan D Johnston

                    ________________________________________________________________
                    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!
                  • Alejandro Lopez-Valencia
                    On Monday, March 01, 2004 4:41 PM, Jonathan D Johnston broke the silence of shunyata and uttered: [snip] - Aha... So, No need for MSVC4.x but DJGPP 32 mode
                    Message 9 of 26 , Mar 1, 2004
                    • 0 Attachment
                      On Monday, March 01, 2004 4:41 PM, Jonathan D Johnston broke the silence
                      of shunyata and uttered:

                      [snip] -> Aha... So, No need for MSVC4.x but DJGPP 32 mode with DPMI
                      emulation, Hmm... That goes to show I haven't touched a win9x box in the
                      longest of times.

                      >
                      > Maybe your NSIS2 package needs to include *three* console versions.
                      > :-)

                      Ahhh! But you misread my intentions! I am creating prototype script that
                      might be used by others (maybe even Bram) to create theirs. I am not in
                      pursue of glory here. :-)

                      Of course, you are welcome to use it and publish binary installers with
                      the latest and greatest patches (and flog yourself in the process ;-).
                    Your message has been successfully submitted and would be delivered to recipients shortly.