[
https://issues.apache.org/jira/browse/XALANC-788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roger Leigh resolved XALANC-788.
--------------------------------
Resolution: Fixed
> Drop Autoconf build
> -------------------
>
> Key: XALANC-788
> URL: https://issues.apache.org/jira/browse/XALANC-788
> Project: XalanC
> Issue Type: Bug
> Reporter: Roger Leigh
> Assignee: Roger Leigh
> Priority: Major
> Fix For: 1.12
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Like Xerces-C, Xalan-C currently provides an Autotools build and a CMake
> build. Unlike Xerces-C, the Autotools build is in a poor shape and is not
> particularly great for portability on modern platforms. The "runConfigure"
> and "Makefile.incl" scripts replace the proper use of Autoconf platform
> support, feature detection and option selection. These are entirely counter
> to the point behind using Autoconf in the first place. There's no use of
> Automake or Libtool, so the portability of the library creation is
> particularly limited.
> I don't personally have the time to dedicate to supporting this, including
> replacing the hardcoded logic with Automake/Libtool. Even these are poor
> nowadays when it comes to current C++ support.
> The CMake build can replace the Autoconf support entirely, is portable for
> all current platforms and compilers, and I would strongly suggest taking the
> course unless there is a compelling reason otherwise.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
