# Building LibreOffice on Windows with Cygwin and MSVC: Tips and Tricks

This page is a translated version of the page Development/BuildingOnWindows and the translation is 0% complete.

Other languages:
العربية • ‎Deutsch • ‎English • ‎español • ‎italiano • ‎日本語 • ‎한국어 • ‎português do Brasil • ‎русский

## Build dependencies

Before you can start hacking LibreOffice on Windows, you need to follow these instructions to set up a build environment. Do also read our generic building hints.

### Install Visual Studio

You need the Microsoft compiler/development suite Visual Studio, which can be obtained from here: https://visualstudio.microsoft.com/downloads/

There is an edition that is free of charge, the Community Edition, that includes everything needed to build all LibreOffice features: https://visualstudio.microsoft.com/vs/community/

Current master (since LibreOffice 7.0) requires Visual Studio 2019 (at least v16.4) (or the equivalent Visual Studio Build Tools).

Since VS 2017, a separate Build Tools package is available that includes compilers, and most toolchains and libraries without installing Visual Studio IDE: https://visualstudio.microsoft.com/downloads/#build-tools-for-visual-studio-2019

For older LibreOffice versions the required Visual Studio versions are:

• LibreOffice 4.4 requires Visual Studio 2012
• LibreOffice 5.0 requires Visual Studio 2013
• LibreOffice 5.4 requires Visual Studio 2015
• LibreOffice 6.2 requires Visual Studio 2017
• LibreOffice 6.3 can be built with either Visual Studio 2017 or 2019

Visual Studio 2019 can optionally install 2017 and 2015 compilers (VS 2015 / 2017 C++ Buildtools). The only thing missing are the older C++ Redistributable MSM packages, so older configure.ac scripts need a little patch to build MSI packages.

#### Visual Studio 2019

Visual Studio (and Visual Studio Build Tools) 2019 at least v16.4 work on current master. The easiest way is to install the "Desktop development with C++" workload with Visual Studio, that includes most of the following components required for build:

• MSVC v142 - VS 2019 C++ x64/x86 build tools (v14.2x)
• C++ core features
• Windows 10 SDK (10.0.xxxxx.x)
• Windows Universal C Runtime
• C++ ATL for v142 build tools (x86 & x64)
• .NET Framework 4.x.x SDK
• C++ 2019 Redistributable MSMs (only required to build MSI installer; not part of the "Desktop development with C++" workload)
• C++ Clang Compiler for Windows (9.0.0) (not part of the "Desktop development with C++" workload)

You can select these options in the VS 2019 installer.

The redistributable MSMs (only required to build MSI installer) are not part of the workload selection in 2019, but need to be picked from the individual component selection. For details, see the comments to the VS Developer Community questions Where MergeModules for 14.20.27404.0 and 14.20.27508? and Deprecation of CRT redist MSMs?.

 Note: Visual Studio command-line tools use system OEM codepage to output messages to console, when corresponding UI language is installed as part of Visual Studio installation. The OEM codepage on Windows depends on system locale defined using "Language for non-Unicode programs" in intl.cpl applet (description of the setting), and is often incompatible with encoding set in cygwin shell (typically UTF-8). This garbles the output from the tools in the build log. You might want to make sure that you only install English UI when installing Visual Studio to avoid that problem.

### Install Java

No matter what version of Visual Studio you're using, you need a

• Java Development Kit (JDK) Version 9 or later. Make sure to get a 32-bit SDK if you are building for 32-bit Windows, and a 64-bit SDK if you are building for 64-bit Windows (with --enable-64-bit). Grab it from adoptopenjdk.net or oracle.com (Oracle requires login to download).

Note that the Oracle JDK is 64-bit-only.

Note that the AdoptOpenJDK installer will not be detected out of the box: you need to manually enable the "JavaSoft (Oracle) registry keys" option for this.

### Install Cygwin and other dependencies

 Note: The Easiest way to perform the following is to use LODE , which automates all that is necessary, beyond installing Visual Studio and Java. If you want to do it the hard way, continue reading.

#### Install Cygwin Requirements

On Windows, you must install Cygwin from www.cygwin.com. Suggested version: 2.11 or later.

The easiest way to do so is to download Cygwin's setup-x86.exe (32-bit) or setup-x86_64.exe (64-bit).

• It is preferable to use 64-bit Cygwin if possible, because it is less likely to have problems with fork() (see Cygwin FAQ for details).

This instruction uses the 64-bit version as an example: Run cmd and navigate to the download dir (if you have trouble navigating, you can also drag setup-x86_64.exe from the file explorer into the cmd window) and copy and paste the command below to run setup-x86_64.exe with the list of required packages preselected.

  setup-x86_64.exe -P autoconf -P automake -P bison -P cabextract -P doxygen -P flex -P gcc-g++ ^
-P gettext-devel git -P gnupg -P gperf -P make -P mintty ^
-P nasm -P openssh -P openssl -P patch -P perl -P python -P python3 ^
-P pkg-config -P rsync -P unzip -P vim -P wget -P zip -P perl-Archive-Zip ^
-P perl-Font-TTF -P perl-IO-String


This launches the GUI and requires you to manually choose installation paths etc, but the packages passed via command line are pre-selected meaning you just need to accept the selection.

NOTE: installation path of Cygwin must not contain non-ASCII letters to avoid autogen.sh/configure problems (if it contains, move folder of the Cygwin installation to a new place and update its Windows shortcuts & Start Menu items).

Alternatively, run the setup-x86.exe or setup-x86_64.exe utility, switch the package view mode to 'Full' by pressing 'View' until 'Full' is displayed beside it, then manually select the packages listed in the above command for installation.

If you upgraded Cygwin, you might have to run the rebaseall command (not needed if you installed Cygwin for the first time):

Close all Cygwin consoles, run c:\cygwin\bin\dash.exe and in the terminal, launch /bin/rebaseall.

#### Other dependencies

After having installed Cygwin, open Cygwin command line by clicking on its desktop icon Cygwin64 Terminal, and perform next steps:

##### Install GNU make

A Win32 build of GNU make 4.0+ is made available (and required) for building LibreOffice.

It's easiest to put it in /opt/lo/bin, where configure will automatically find it; you can also use another location and set the MAKE variable. Either prepend /opt/lo/bin to PATH, or alternatively, when you build LibreOffice, always call "make" with the absolute path /opt/lo/bin/make (or wherever you put it). LibreOffice can not and should not use Cygwin's /usr/bin/make.

mkdir -p /opt/lo/bin
cd /opt/lo/bin
wget https://dev-www.libreoffice.org/bin/cygwin/make-4.2.1-msvc.exe
cp make-4.2.1-msvc.exe make
chmod +x make

##### Install ant and junit

You can extract them anywhere, they don't have to be installed. If you don't want to use Junit, it can be disabled with --without-junit in the autogen.sh command later.

  mkdir -p /cygdrive/c/sources
cd /cygdrive/c/sources
wget https://archive.apache.org/dist/ant/binaries/apache-ant-1.9.5-bin.tar.bz2
tar -xjvf apache-ant-1.9.5-bin.tar.bz2


Also works with the combination of junit 4.13,hamcrest 2.2 and Apache Ant 1.10.8

##### Clone the LibreOffice source code repositories

NOTE: sources should be in a relatively short path to avoid exceeding the file/pathname limit and the destination path cannot have any space in it.

  cd /cygdrive/c/sources
git clone https://gerrit.libreoffice.org/core libo-core

##### Optionally create build directory

You can build LibreOffice into another directory than your checkout. This helps keeping the source code tree clean and eases building multiple versions.

If you want to build into a separate directory, say /cygdrive/c/build, enter these commands:

  mkdir /cygdrive/c/build
cd /cygdrive/c/build


Otherwise change directory to the /cygdrive/c/sources/libo-core folder:

  cd /cygdrive/c/sources/libo-core

##### Configure and build the code

Now run autogen.sh to configure the build:

  /cygdrive/c/sources/libo-core/autogen.sh \
--with-external-tar=/cygdrive/c/sources/lo-externalsrc \
--with-junit=/cygdrive/c/sources/junit-4.10.jar \
--with-ant-home=/cygdrive/c/sources/apache-ant-1.9.5 \
--enable-pch --disable-ccache \
[additional switches, if you know what you are doing :-) ...]


Note that it's not recommended to use ccache on Windows. If you have it installed in your Cygwin environment, be safe and disable it with --disable-ccache (as in the command above).

If the autogen.sh script complains that it cannot find some header files, it is possible that it cannot locate the your Windows SDK or that it finds a corrupted one. This may happen if you installed multiple version of Visual Studio on your computer, especially if you installed a Beta version, and even if you uninstalled those. In this case, you may use the --with-windows-sdk=7.1A, possibly replacing 7.1A with another version of the SDK to select a specific uncorrupted version.

Save a copy of the last used parameters in the file autogen.input. It will not be overridden by autogen.sh when using other parameters. If autogen.sh is called again without parameters, it will fetch its input from autogen.input if it is present.

Don't forget to specify --with-jdk-home when you use AdoptOpenJDK in zip format, because configure.ac detects JDK's paths from registry JDK's installer downloadable from Oracle sets. Other JDKs may need this option too(not tested).

Read the summary output from the autogen.sh command. If it did not report any errors or relevant warnings, then all that is left to do is to run the right version of make to build LibreOffice. Before you do this, make sure your anti-virus software will not cause any problems.

   /opt/lo/bin/make gb_COLOR=1  # gb_COLOR=1 enables colored output


If the build process fails at this point with the error error C3861: 'InetPtonW': identifier not found, this is because of a bug in the build process for Windows SDK 8. You may work around this by using the --with-windows-sdk=7.1A option.

##### Run LibreOffice

When the build has finished without errors, you can run your fresh build of LibreOffice using

   instdir/program/soffice.exe


## Microsoft Visual Studio Project Integration

The LibreOffice build system can generate project file for some IDEs including -- thanks to Honza Havlíček's excellent work -- Microsoft Visual Studio: (note that this does not allow a full build so you still need to use Cygwin to do full builds)

### Build a project file for Visual Studio

The IDE integration script is written in python3, which is not installed by default (using the lode method), please install it in cygwin before running the make command. After a complete build of LibreOffice was successful, execute the following command to generate a Visual Studio project for Visual Studio 2019:

  $/opt/lo/bin/make vs2019-ide-integration  For Visual Studio 2017 use: $ /opt/lo/bin/make vs2017-ide-integration


If the generation is successful, the resulting solution file LibreOffice.sln will be placed in the root directory of the build and can be opened with Microsoft Visual Studio.

Note that if you use --enable-mergelibs, the generated solution will for unclear reason contain less projects, and have problems finding many symbols. Until that is fixed, it's advisable to avoid --enable-mergelibs when using IDE integration.

### Why MSVC?

It is a frequently asked question, usually coming from free software purists, why we use proprietary compiler instead of a free one (i.e. gcc).

• ABI backwards-compatibility for compiled extensions. There is some resistance to breaking that.
• So far MSVC produces faster, smaller binaries.
• There are some features in the code that don't compile with MinGW. They use API that MinGW does not provide headers for etc.
• There are open questions around how we would run unit tests in a MinGW cross-compilation environment.
• There are open questions around how well gdb works on Windows; the MSVC C++ debugger is really quite good.

### Autogen options

Something like the following in the autogen.input file is known to produce a working build:

--disable-odk
--with-junit=/cygdrive/c/sources/junit-4.10.jar
--with-ant-home=/cygdrive/c/sources/apache-ant-1.9.5


Of course, change the information behind ='s to fit your needs; set the paths to what you have used when installing various prerequisites.

You also need to specify the path for ant with --with-ant-home=<cygwin path of ant>.

### 64-bit Visual Studio build

A port for 64-bit Windows is working on master with all supported compilers. To build it, use the --enable-64-bit flag to configure.

## Notes on older and non-default MS compilers

### Switching to non-default compiler

Specify which Visual Studio version to use in case several are installed.

If not specified, the order of preference is 2015, 2017 for libreoffice-6-1 (and older branches), 2019 is used for master.

--with-visual-studio=2019


To edit dialogs (.ui files), you need Glade. There is an old version for Windows but it doesn't support all properties that are needed for LibreOffice dialogs.

So you need to install Glade in Cygwin:

• Install Glade in Cygwin by running the Cygwin Setup, then install the following packages:
X11, X11 fonts, Gtk3, Glade, OpenGL
export GLADE_CATALOG_SEARCH_PATH=<path_to_core>/instdir/share/glade
• Open one Cygwin console and run:
X -multiwindow
• Open another Cygwin console and run:
DISPLAY=:0.0 glade.exe

That's it, you should now run Glade ≥ 3.18

## Known Problems

### Cygwin and git

The main problem is the cygwin-git is very slow.

The alternatives are:

Here are the times using the same computer and repo and not being the first call:

git status

git Version Time [sec]
cygwin 2.21.0 20
win 2.22.0 1
WSL 2.16.0 6

Git in WSL is slower than git-bash, but it has the advantage of working in a complete Linux environment with all other tools provided by the distribution. You should not mix tools from Cygwin and WSL (i.e. open separate terminals for Cygwin and for WSL).

NOTE: A mix between different git tools is not always compatible, when you change you should renew (clone) the git repositories.

Best to configure "autocrlf" before cloning master, to avoid the problem (see below for how to set "autocrlf" to a sensible value)

### Cygwin Shell

You will use Cygwin Bash Shell for the whole build process. You must install all the build dependencies above before starting the shell to run autogen because autogen needs some environment variables to find the tools.

If you see an error similar to the following when running autogen.sh

   $'\r': command not found  This means that that windows style newline characters are creating issues with the Cygwin Shell. The good way to solve this is to configure git to clone with UNIX line ending. To do so, in git bash:  git config --global core.autocrlf input  #### Big List Of Dodgy Apps If you get mysterious build breaks, building is very slow or your systems hangs totally, check if you are running an application which interferes with Cygwin. For a list of known offenders, see this point in the Cygwin FAQ. ### Buildability of 'master' If you are building the Windows build for the first time, it is recommended that you check the current state of https://tinderbox.libreoffice.org/MASTER/status.html . If you see recent "green" builds, it is a good time to try - otherwise it might happen to you that you'll have to fix the build yourself. The buildability on Windows has improved recently with the introduction of the MinGW and more stable native Windows tinderboxes, but still there might be a day or two when 'master' is not buildable on Windows. The usual recommendation is to just pull and try again, and once you have a build, don't pull in the tree any more, but do your hacking in it. Clone a different tree and iterate pulling and building in that until it again works, then switch. Repeat. Alternatively, if you find a known good state (a green box) for Windows on the Tinderbox side back in history, you can do: git checkout -b my_workbranchname${last_good_commit}


to start working on a branch starting at the last good state.

### BitDefender / other Anti-Virus / security tools breaking the build

If your build fails with a FileNotFoundError: such as The system cannot find the file specified: '../../../dist/out/bin\\example.exe', there's a good chance your Anti-Virus is quarantining or deleting important files.

Another potential source of problems are the sample documents (those labeled CVE) that check for known vulnerabilities to ensure they don't reappear again. In the source they are stored encrypted to avoid triggering the warnings, but when the corresponding test is run, the original is created in the temp directory and tools such as BitDefender can flag it.

If you want to run these tests, disable monitoring of the temporary build-directories <root of repo>\*\pass and C:\cygwin\tmp in your Anti-Virus tool. For Windows 8 and 10 you will need to disable Windows Defender launch - search for and launch 'defender' from the shell.

You can also use the --disable-cve-tests autogen flag to skip the tests that are known to cause trouble.

Also note that Anti-Virus tools can slow down your build quite a bit, if you want to build fast you should disable real time monitoring of the source tree and the temporary files directory C:\cygwin\tmp.

### Norton Antivirus breaking the build

Norton Antivirus and Symantec Endpoint Protection complain about certain files that the build produces. It finds the following files (in a build without "--enable-dbgutil" )

Malware: Suspicious.Cloud
D:\bld\rel\workdir\UnpackedTarball\icu\source\bin\genrb.exe*
Malware: Suspicious.Cloud.5
D:\bld\rel\workdir\UnpackedTarball\nss\nss\lib\zlib\out\example.exe*
D:\bld\rel\workdir\UnpackedTarball\nss\dist\out\bin\example.exe*
D:\bld\rel\instdir\program\reg4allmsdoc.dll
D:\bld\rel\instdir\program\sdqsmsi.dll
D:\bld\rel\instdir\program\sellangmsi.dll


Files with * are needed for the build - exclude them from the virus scan!

The following files appear with varying names (????) in a release build, so you cannot exclude them from the scan.

D:\bld\rel\instdir\program\RCX????.tmp
D:\bld\rel\instdir\program\RCX????.tmp
D:\bld\rel\instdir\program\RCX????.tmp


Current workaround: Don't do release builds (unless you are allowed/willing to switch off the virus scanner).

### System PATH causing weird build breakage

If you experience weird build breakage that no one else seems to experience, check your PATH value and try cleaning it. Note that you need to open a new shell and re-run autogen.sh in order for the new system PATH value to take effect in your build. Some people have experienced a build failure in the shell module due to their system PATH including a path to an older OOo installation which had a DLL of the same name as the one that the build uses.

### Windows Update automatically reboot during compilation

Sometimes Microsoft Windows reboot during compilation. It happen because Windows Update updates operating system and reboot. To stop windows update from command line, you can enter following command in command box:

C:> net stop wuauserv


It stops a Windows Update service process.

### Failing PDF signing tests

On Windows, it can happen, that PDF signing tests are failing:

[build CUT] xmlsecurity_pdfsigning
warn:sfx.appl:2956:6324:sfx2/source/appl/app.cxx:193: No DDE-Service possible. Error: 16399
warn:svl.crypto:2956:6324:svl/source/crypto/cryptosign.cxx:1415: CryptAcquireCertificatePrivateKey failed: Das Zertifikat und der private Schlüssel für die Entschlüsselung wurden nicht gefunden.
warn:vcl.filter:2956:6324:vcl/source/filter/ipdf/pdfdocument.cxx:846: PDFDocument::Sign: PDFWriter::Sign() failed


Solution: Remove expired Own Certificate: http://imgur.com/a/NdCxT

1. Start certmgr
2. proceed to Own Certificates
3. Remove expired certificate
4. Repeat the tests
5. Done

### Short filenames (8.3 filenames)

If you get an error like the following one:

configure: error: converted path "C:/PROG~1/Microsoft SDKs/Windows/v8.1A/bin/NETFX4~1.1TO/" still contains spaces. Short filenames (8.3 filenames) support was disabled on this system?
Error running configure at ./autogen.sh line 300.


Then ensure 8.3 name creation is enabled. Open the Command Prompt as administrator and run:

fsutil 8dot3name query c:


Also, check that the conflicting folder (in this case, "Microsoft SDKs") has a corresponding 8.3 filename. For example:

cd C:\Program Files (x86)\
dir /x M*


This will print a list of folders beginning with "M" and their associated 8.3 filenames. If "Microsoft SDKs" does not have a short filename, you can rename it to "tmp", then create a new folder "Microsoft SDKs", check that it has a short filename and move the contents of "tmp" to "Microsoft SDKs".

When choosing a directory in which to install LODE, please use the 8.3 rules. Windows does not correct environment variables, therefore e.g. LODE_HOME will be wrong and will cause problems. Therefore, always clone lode in a 8.3 path such as:

C:\source\LO\lode


autogen.sh might report that it cannot find mscvc.exe.

This is caused by the long filename problem as well, but the solution is a bit more work:

Shift+reset, go to the safe mode, do this:

fsutil 8dot3name set c: 0
fsutil file setshortname "Program Files (x86)" PROGS
fsutil file setshortname "Microsoft Visual Studio 12.0" msvc-12
fsutil file setshortname "Windows Kits" W~Kits


### Windows permission issues

If you receive the following error :

ALINK : error AL1078: Error signing assembly -- Access is denied.


Then right click and select "properties" of the folder "C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys" and under the "security" tab modify the permissions of the user and allow "Full control".

### Other known problems

• Paths that include /opt cause problems with some external modules; it is best to avoid having your source tree in /opt; or use --disable-orcus to overcome this.
• Asian locale builds sometimes fail due to encoding issues in the source code; in these cases, patches to fix those problems are appreciated. Alternatively, configure Windows for a US locale.

## Using a Windows program as your git editor

Paths under Cygwin are an endless source of nightmares. This section documents using Notepad++ as your git editor under Cygwin. It assumes you are using the 64-bit version of Notepad++ (adjust the path, if using the 32-bit version).

Below you will find a wrapper script written by Gene Pavlovsky (original gist in GitHub).

1. Save the script as cygrun.sh into the bin directory in Cygwin's root (so it is in the PATH). When saving the cygrun.sh using Notepad++, do this first to make sure it has Unix line endings: from the "Edit" menu, select "EOL Conversion" -> "UNIX (LF)".
2. In a Cygwin shell inside the bin directory, give this command to create a symbolic link:
ln -s cygrun.sh cygrun

3. Give this command in your home directory:
git config --global core.editor "cygrun -w 'C:/Program Files/Notepad++/notepad++.exe' --wait"

or alternatively edit your .gitconfig to contain this editor block:
editor = cygrun -w 'C:/Program Files/Notepad++/notepad++.exe' --wait

The --wait is important, as it forces git to wait until you close the file.

Bonus: if you want to define Notepad++ as the default editor of your shell and also access it through a handy "np" alias, add these to the .bashrc file in your home directory:

export EDITOR="'/cygdrive/c/Program Files/Notepad++/notepad++.exe'"


Remember to be very careful with the line endings, when creating new files and use the Edit -> EOL Conversion.

The cygrun script:

#!/bin/bash
#
# Run a program, converting UNIX and Windows format path arguments.
#
# Install in Cygwin's bin dir or elsewhere in your path.
# Create a symlink for convenience: ln -s cygrun.sh cygrun.
#
# Use cygrun -w windows-program unix-path ... to run Windows programs (e.g. from UNIX software).
# E.g., in my .gitconfig core.editor is set to cygrun -w 'C:/Program Files/Notepad2/Notepad2.exe'.
#
# Use cygrun [-u] unix-program windows-path ... to run Cygwin programs (e.g. from Windows software).
# Usually not needed since Cygwin translates Windows paths automatically (e.g. ls 'C:\Windows' works).
# Still it can be useful in case a Windows program might produce paths that mix backslashes and forward slashes,
# e.g. in Apache Ant ${dist.dir}/file evaluates to C:\path\to\project\dist/file, which Cygwin won't # translate automatically. So, to deploy the file, I use cygrun -u scp${dist.dir}/file ${deploy.url}. # # Use the -b option to detach from tty, run the process in background, and return immediately. # # There is currently a limitation on passing non-path arguments to a program. Since there is no way # to automatically distinguish path arguments from non-path arguments, all of the arguments are passed # to cygpath. As long as non-path arguments don't contain / or \ characters, and -a or -C # options are not used, cygpath will return the arguments unmodified - no problem. # Due to this, the -a and -C options are disabled at the moment. # TODO: Add an option allowing to specify index positions of path arguments (comma-separated, support ranges). # # Most of the options are passed as is to cygpath, which is used for path conversion. set -e -o pipefail usage() { local code=${1:-2}
test $code -ne 0 && exec >&2 echo "Usage:$(basename "$0" .sh) [options] program [argument]..." echo echo 'Run a program, converting UNIX and Windows format path arguments.' echo echo 'Output type options:' echo echo ' -d, --dos print DOS (short) form of NAMEs (C:\PROGRA~1\)' echo ' -m, --mixed like --windows, but with regular slashes (C:/WINNT)' echo ' -u, --unix (default) print Unix form of NAMEs (/cygdrive/c/winnt)' echo ' -w, --windows print Windows form of NAMEs (C:\WINNT)' echo echo 'Path conversion options:' echo echo ' -U, --proc-cygdrive Emit /proc/cygdrive path instead of cygdrive prefix' echo ' when converting Windows path to UNIX path.' echo ' -c, --codepage CP print DOS, Windows, or mixed pathname in Windows' echo ' codepage CP. CP can be a numeric codepage identifier,' echo ' or one of the reserved words ANSI, OEM, or UTF8.' echo ' If this option is missing, cygrun defaults to the' echo ' character set defined by the current locale.' echo echo "Other 'cygpath' options:" echo echo ' -f, --file FILE read FILE for input; use - to read from STDIN' echo " -o, --option read 'cygpath' options from FILE as well (for use with --file)" echo ' -h, --help output usage information and exit' echo echo 'Run options:' echo echo ' -b, --background run in a new session' echo ' -n, --dry-run print the command that would be executed, and exit' exit$code
}

run() {
local -n _run_args=$2 if test "$dry_run"; then
test "$chdir" && printf 'cd %s\n' "$chdir"
printf '%s\n' "$1${_run_args[*]}"
else
test "$chdir" && cd -- "$chdir"
if test "$background"; then setsid "$1" "${_run_args[@]}" </dev/null &>/dev/null & else exec "$1" "${_run_args[@]}" fi fi } declare opts fileopts chdir background dry_run while test$# -gt 0; do
case $1 in -d|--dos|-u|--unix|-m|--mixed|-w|--windows|-U|--proc-cygdrive|-o|--option) opts="${opts} $1" ;; -C|--codepage|-f|--file) opts="${opts} $1$2"
shift
;;
-f|--file)
fileopts=1
opts="${opts} -i$1 $2" shift ;; -b|--background) background=1 ;; -n|--dry-run) dry_run=1 ;; -h|--help) usage 0 ;; --) shift break ;; -*) script="$(basename "$0" .sh)" echo "$script: Unknown option: $1" >&2 echo "Try '$script --help' for more information." >&2
exit 2
;;
*)
break
;;
esac
shift
done
test "$chdir" && opts="$opts -a"

program=$1 test "$program" || usage
shift

declare -a args
test $# -gt 0 -o "$fileopts" && mapfile -t args < <(cygpath $opts -- "$@" || exit 1)
run "\$program" args