[ https://issues.apache.org/jira/browse/FOP-2834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
simon steiner updated FOP-2834: ------------------------------- Summary: [PATCH] Support to launch fop command from the MSYS2/MINGW bash on Windows (was: Patch for support to launch fop command from the MSYS2/MINGW bash on Windows) > [PATCH] Support to launch fop command from the MSYS2/MINGW bash on Windows > -------------------------------------------------------------------------- > > Key: FOP-2834 > URL: https://issues.apache.org/jira/browse/FOP-2834 > Project: FOP > Issue Type: Improvement > Components: unqualified > Affects Versions: 2.3 > Environment: Windows 7/10 with MSYS2 (www.msys2.org) > Reporter: Gerrit Albrecht > Priority: Minor > Labels: FOP, MSYS > Attachments: fop-2.3-msys2.patch > > Original Estimate: 5m > Remaining Estimate: 5m > > When using the fop 2.3 binary download with a MSYS2 shell, the fop command in > the main directory fails because it does not know anything about MSYS2. Same > problem exists after running fop from a MINGW32/64 bash. The fop.bat worked > out of the box but would need cmd.exe. > The patch (for fop 1.0) is from here: > [https://gist.github.com/lammermann/1307565] > My patch enables MSYS2 too (MSYS2 uses different uname's for its shells) and > targets version 2.3. > To test it you need a JAVA_HOME env variable which leads to a JRE (tested > with jre1.8.0_192) and you have to add $JAVA_HOME/bin and fop-2.3/fop to the > PATH variable. -- This message was sent by Atlassian JIRA (v7.6.3#76005)