Lines Matching refs:with
25 2. Using MSYS2 with MinGW
29 6. Building with Python support
30 7. Building with Python3 support
31 8. Building with Racket or MzScheme support
32 9. Building with Lua support
33 10. Building with Perl support
34 11. Building with Ruby support
35 12. Building with Tcl support
36 13. Building with DirectX (DirectWrite) support
56 When installing "Visual Studio Community 2015 with Update 3" make sure to
64 Building with Visual Studio (VS2010, VS2012, VS2013, VS2015, VS2017 and VS2019)
67 To build Vim from the command line with MSVC, use Make_mvc.mak.
77 Make_mvc.mak allows a Vim to be built with various different features and
80 For compiling gVim with IME support on far-east Windows, add IME=yes
97 Vim with Make_mvc.mak.
100 Targeting Windows XP with MSVC 2012 and later *new-msvc-windows-xp*
103 Beginning with Visual C++ 2012, Microsoft changed the behavior of LINK.EXE
129 For x64 builds run this with the "x86_amd64" option:
138 …http://blogs.msdn.com/b/vcblog/archive/2012/10/08/windows-xp-targeting-with-c-in-visual-studio-201…
147 This depends on VS2017 with the optional ARM64 compiler and SDK
155 The minimal supported version is Windows XP. Building with older compilers
176 To compile and debug Vim with the VC2003 Toolkit, you will also need
183 The free Code::Blocks IDE works with the VC2003 Toolkit, as described at
198 Now you can build Vim with Make_mvc.mak.
245 |ms-platform-sdk|. You can build Vim with Make_mvc.mak.
261 Vim with Make_mvc.mak.
268 2. MSYS2 with MinGW
292 If pacman complains that `catgets` and `libcatgets` conflict with another
368 This is about how to produce a Win32 binary of gvim with MinGW from the normal
415 After churning for a while, you will end up with 'gvim.exe' in the 'vim\src'
435 ADDITION: NLS support with MinGW
446 Use Make_cyg.mak with Cygwin's GCC. See
451 running on Unix), while with Make_cyg.mak you get a Windows application (like
452 with the other makefiles).
475 6. Building with Python support
478 For building with MSVC the "Windows Installer" from www.python.org works fine.
491 When using MinGW and link with the official Python (as one line):
496 When using msys2 and link with Python2 bundled with msys2 (as one line):
506 (This is for 64-bit builds. For 32-bit builds, replace mingw64 with mingw32.)
513 Building with the mingw32 compiler, and the ActiveState ActivePython:
517 'libpython20.a' to link with:
524 cross-compiling on Linux with the mingw32 setup, you need to also convert all
532 You will end up with a Python-enabled, Win32 version. Enjoy!
535 7. Building with Python3 support
538 For building with MSVC the "Windows Installer" from www.python.org works fine.
552 When using MinGW and link with the official Python3 (as one line):
557 When using msys2 and link with Python3 bundled with msys2 (as one line):
567 (This is for 64-bit builds. For 32-bit builds, replace mingw64 with mingw32.)
572 8. Building with Racket or MzScheme support
575 1) Building with Racket support (newest)
577 MzScheme and PLT Scheme names have been rebranded as Racket. Vim with Racket
578 support can be built with either MSVC or MinGW (or Cygwin).
598 User can override this with the PLTCOLLECTS environment
623 Spaces should be escaped with '\'.
626 2) Building with MzScheme support (older)
630 Vim with MzScheme (http://www.plt-scheme.org/software/mzscheme) support can
631 be built with either MSVC, or MinGW, or Cygwin. Supported versions are 205 and
662 9. Building with Lua support
665 Vim with Lua support can be built with either MSVC or MinGW (or maybe Cygwin).
717 10. Building with Perl support
720 Vim with Perl support can be built with either MSVC or MinGW (or Cygwin).
743 11. Building with Ruby support
746 Vim with Ruby support can be built with either MSVC or MinGW (or Cygwin).
752 If you use MinGW you can easily build with RubyInstaller, but if you use MSVC
779 If you want to link with ruby, normally you must use the same compiler as
780 which was used to build the ruby binary. RubyInstaller is built with MinGW,
781 so normally you cannot use MSVC for building Vim if you want to link with
786 You can install RubyInstaller with the default options and directory.
829 For 64-bit version, replace RUBY=C:\Ruby24 with RUBY=C:\Ruby24-x64.
832 with Ruby 2.1 or later. (Default is 0x501.)
838 Using MinGW is easier than using MSVC when linking with RubyInstaller.
845 For 64-bit version, replace RUBY=C:/Ruby24 with RUBY=C:/Ruby24-x64.
846 If you set WINVER explicitly, it must be set to >=0x500, when building with
851 12. Building with Tcl support
854 Vim with Tcl support can be built with either MSVC or MinGW (or Cygwin).
866 For building with MSVC 2015 use version 8.6.6 or later.
874 Sometimes the Tcl dll name changes. E.g. ActiveTcl 8.6.4 comes with tcl86.dll,
875 but ActiveTcl 8.6.6 comes with tcl86t.dll. You can set the dll name by setting
890 13. Building with DirectX (DirectWrite) support
893 Vim with DirectX (DirectWrite) support can be built with either MSVC or MinGW.
894 This requires dwrite_2.h and some other header files which come with Windows
906 by default. However, you can use the header files from newer SDKs with older
970 To install the "Edit with Vim" popup menu, you need both 32-bit and 64-bit
1005 The DLLs in the "vim82" should be the same bitness with the (g)vim.exe.
1019 - You can tell it to write a "_vimrc" file with your preferences in the
1021 - It can also install an "Edit with Vim" entry in the Windows Explorer