You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fop-dev@xmlgraphics.apache.org by "Chris Bowditch (JIRA)" <ji...@apache.org> on 2019/01/10 09:15:00 UTC
[jira] [Commented] (FOP-2834) Patch for support to launch fop
command from the MSYS2/MINGW bash on Windows
[ https://issues.apache.org/jira/browse/FOP-2834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16739228#comment-16739228 ]
Chris Bowditch commented on FOP-2834:
-------------------------------------
I've re-classified this as an improvement as it was never intended for FOP's scripts to support MSYS2 out of the box
> Patch for 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
> Fix For: 2.3
>
> 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)