[jira] [Assigned] (XALANC-808) Remove XalanMsgLib
[ https://issues.apache.org/jira/browse/XALANC-808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Leigh reassigned XALANC-808: -- Assignee: Gary D. Gregory (was: Roger Leigh) > Remove XalanMsgLib > -- > > Key: XALANC-808 > URL: https://issues.apache.org/jira/browse/XALANC-808 > Project: XalanC > Issue Type: Bug > Components: XalanC >Affects Versions: 1.13 >Reporter: Roger Leigh >Assignee: Gary D. Gregory >Priority: Major > Fix For: 1.13 > > Original Estimate: 24h > Remaining Estimate: 24h > > XalanMsgLib adds quite a bit of complexity to the build and to the > implementation. It's also completely unused: there is only a single > supported language: en_US. There hasn't been another language added in the > entire history of the project. The demand for and likelihood of getting any > translations is near zero. > As a result, this issue is a proposal for dropping the XalanMsgLib library. > If it's unused, why pay the costs for having it? > Unless there are any objections, I would suggest we drop it entirely for 1.13. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Assigned] (XALANC-796) Autogenerate version information in Windows resource files
[ https://issues.apache.org/jira/browse/XALANC-796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Leigh reassigned XALANC-796: -- Assignee: Gary D. Gregory (was: Roger Leigh) > Autogenerate version information in Windows resource files > -- > > Key: XALANC-796 > URL: https://issues.apache.org/jira/browse/XALANC-796 > Project: XalanC > Issue Type: Bug > Components: XalanC >Affects Versions: 1.11 >Reporter: Roger Leigh >Assignee: Gary D. Gregory >Priority: Major > Fix For: 1.13 > > > Autogenerate embedded version numbers. Since it can include headers, the > information could be sourced directly from the XalanVersion.hpp. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Assigned] (XALANC-811) Support in-source build
[ https://issues.apache.org/jira/browse/XALANC-811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Leigh reassigned XALANC-811: -- Assignee: Gary D. Gregory (was: Roger Leigh) > Support in-source build > --- > > Key: XALANC-811 > URL: https://issues.apache.org/jira/browse/XALANC-811 > Project: XalanC > Issue Type: Bug > Components: XalanC >Affects Versions: 1.12 >Reporter: Roger Leigh >Assignee: Gary D. Gregory >Priority: Major > Fix For: 1.13 > > > Sample and/or Test executables have the same name as the subdirectory. They > are stored one level up and so causes naming conflicts on Unix where there is > no executable suffix. > Move the executables into the subdirectories. > Update documentation to point to new locations. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Assigned] (XALANC-802) Static builds are broken on Windows
[ https://issues.apache.org/jira/browse/XALANC-802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Leigh reassigned XALANC-802: -- Assignee: Gary D. Gregory (was: Roger Leigh) > Static builds are broken on Windows > --- > > Key: XALANC-802 > URL: https://issues.apache.org/jira/browse/XALANC-802 > Project: XalanC > Issue Type: Bug > Components: XalanC >Affects Versions: 1.11, 1.12 > Environment: MSVC >Reporter: Roger Leigh >Assignee: Gary D. Gregory >Priority: Major > Fix For: 1.13 > > Original Estimate: 24h > Remaining Estimate: 24h > > The DLL import/export macros are used unconditionally, breaking linking when > using a static library. > Use a suitable _EXPORT define when building; see CMake GenerateExportHeader > for one way to do this which could be easily enabled. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Assigned] (XALANC-803) MinGW build is broken
[ https://issues.apache.org/jira/browse/XALANC-803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Leigh reassigned XALANC-803: -- Assignee: Gary D. Gregory (was: Roger Leigh) > MinGW build is broken > - > > Key: XALANC-803 > URL: https://issues.apache.org/jira/browse/XALANC-803 > Project: XalanC > Issue Type: Bug > Components: XalanC >Affects Versions: 1.12 >Reporter: Roger Leigh >Assignee: Gary D. Gregory >Priority: Major > Fix For: 1.13 > > Original Estimate: 48h > Remaining Estimate: 48h > > HANDLE and other macros not defined. Likely need to check if it should be > using the Unix or Windows includes and types, and adjust to make MinGW work. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Commented] (XALANC-815) Compilation failing in Linux
[ https://issues.apache.org/jira/browse/XALANC-815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17551406#comment-17551406 ] Roger Leigh commented on XALANC-815: To clarify, are you saying that adding ICU::data corrects the problem, or does the error still occur with this change? > Compilation failing in Linux > > > Key: XALANC-815 > URL: https://issues.apache.org/jira/browse/XALANC-815 > Project: XalanC > Issue Type: Bug > Components: XalanC >Affects Versions: 1.12 > Environment: Ubuntu, Fedora >Reporter: Minhaajuddin Ahmad Khan >Assignee: Gary D. Gregory >Priority: Major > > Hello, > I am trying to build xalan-c (version 1.12) with icu in Ubuntu but it fails. > Could anyone help me with this. > Steps to reproduce : > 1. Clone xalan-c > 2. cmake -G "Unix Makefiles" -DCMAKE_PREFIX_PATH="path to vcpkg installed > libraries" -DCMAKE_INSTALL_PREFIX=./install/Xalan-c -DCMAKE_BUILD_TYPE=Debug > -Dtranscoder=icu "path to source" > 3. make > Error > [ 95%] Linking C executable SimpleXPathCAPI > /usr/bin/ld: > /home/minhaaj/app/vcpkg/installed/x64-linux/lib/libicuuc.a(rbbistbl.ao): > undefined reference to symbol > '_ZTVN10__cxxabiv121__vmi_class_type_infoE@@CXXABI_1.3' > /usr/bin/ld: /lib/x86_64-linux-gnu/libstdc++.so.6: error adding symbols: DSO > missing from command line > collect2: error: ld returned 1 exit status > make[2]: *** [samples/CMakeFiles/SimpleXPathCAPI.dir/build.make:90: > samples/SimpleXPathCAPI] Error 1 > make[1]: *** [CMakeFiles/Makefile2:842: > samples/CMakeFiles/SimpleXPathCAPI.dir/all] Error 2 > make: *** [Makefile:141: all] Error 2 > Please note I have applied a patch for configuration error as below in > src/xalanc/Utils/MsgCreator/CMakeLists.txt > target_link_libraries(MsgCreator ICU::uc ICU::i18n) > changed to > target_link_libraries(MsgCreator ICU::uc ICU::i18n ICU::data) -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Commented] (XALANC-803) MinGW build is broken
[ https://issues.apache.org/jira/browse/XALANC-803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17419864#comment-17419864 ] Roger Leigh commented on XALANC-803: Apologies, I've lost track of that due to lots of other commitments. If everyone is happy with this, then I don't see any blocker to merging it. I'll just re-run the CI to double-check the cygwin build is OK (though it might not be--AppVeyor broke it for Xerces and I'm not sure about Xalan). > MinGW build is broken > - > > Key: XALANC-803 > URL: https://issues.apache.org/jira/browse/XALANC-803 > Project: XalanC > Issue Type: Bug > Components: XalanC >Affects Versions: 1.12 >Reporter: Roger Leigh >Assignee: Roger Leigh >Priority: Major > Fix For: 1.13 > > Original Estimate: 48h > Remaining Estimate: 48h > > HANDLE and other macros not defined. Likely need to check if it should be > using the Unix or Windows includes and types, and adjust to make MinGW work. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Commented] (XALANC-803) MinGW build is broken
[ https://issues.apache.org/jira/browse/XALANC-803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17419676#comment-17419676 ] Roger Leigh commented on XALANC-803: If you want to put this change into a patch or github PR, that would be most appreciated. > MinGW build is broken > - > > Key: XALANC-803 > URL: https://issues.apache.org/jira/browse/XALANC-803 > Project: XalanC > Issue Type: Bug > Components: XalanC >Affects Versions: 1.12 >Reporter: Roger Leigh >Assignee: Roger Leigh >Priority: Major > Fix For: 1.13 > > Original Estimate: 48h > Remaining Estimate: 48h > > HANDLE and other macros not defined. Likely need to check if it should be > using the Unix or Windows includes and types, and adjust to make MinGW work. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Commented] (XALANC-813) Can we build xalan-c(1.12) on rhel 8.2 ?
[ https://issues.apache.org/jira/browse/XALANC-813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17209758#comment-17209758 ] Roger Leigh commented on XALANC-813: This is a known issue: https://issues.apache.org/jira/browse/XALANC-811 I'll get this fixed in the next point release. As a workaround, please build using a separate build directory, and it will work correctly. This is recommended practice anyway, so I would suggest doing this in any case. Kind regards, Roger > Can we build xalan-c(1.12) on rhel 8.2 ? > > > Key: XALANC-813 > URL: https://issues.apache.org/jira/browse/XALANC-813 > Project: XalanC > Issue Type: Bug > Components: XalanC >Affects Versions: 1.12 >Reporter: Krunal Ghute >Assignee: Gary D. Gregory >Priority: Major > Fix For: 1.11 > > > Not able to build xalan-c rpms on rhel 8.2 using spec file. can we build > xalan-c (1.12) on rhel 8.2? if yes then can you please tell me the procedure. > beacuse while building xalan-c rpm we faced many compilation issues , PSB. > -Wformat-nonliteral] > theCharsWritten = sprintf(theBuffer, *thePrintfString, theValue); > ^ > [ 7%] Building CXX object > src/xalanc/CMakeFiles/xalan-c.dir/PlatformSupport/DOMStringPrintWriter.cpp.o > [ 7%] Building CXX object > src/xalanc/CMakeFiles/xalan-c.dir/PlatformSupport/DoubleSupport.cpp.o > [ 7%] Building CXX object > src/xalanc/CMakeFiles/xalan-c.dir/PlatformSupport/ExecutionContext.cpp.o > In file included from > /home/pmx/rpmbuild/BUILD/amdocs-xalan-c-1.12/src/xalanc/PlatformSupport/ExecutionContext.hpp:32, > from > /home/pmx/rpmbuild/BUILD/amdocs-xalan-c-1.12/src/xalanc/PlatformSupport/ExecutionContext.cpp:19: > /home/pmx/rpmbuild/BUILD/amdocs-xalan-c-1.12/src/xalanc/PlatformSupport/ProblemListenerBase.hpp:28:10: > fatal error: LocalMsgIndex.hpp: No such file or directory > #include "LocalMsgIndex.hpp" > ^~~ > compilation terminated. > make[2]: *** [src/xalanc/CMakeFiles/xalan-c.dir/build.make:427: > src/xalanc/CMakeFiles/xalan-c.dir/PlatformSupport/ExecutionContext.cpp.o] > Error 1 > make[1]: *** [CMakeFiles/Makefile2:250: > src/xalanc/CMakeFiles/xalan-c.dir/all] Error 2 > make: *** [Makefile:141: all] Error 2 > error: Bad exit status from /var/tmp/rpm-tmp.zf5qy4 (%build) > please help to resolve this isses. > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Commented] (XALANC-813) Can we build xalan-c(1.12) on rhel 8.2 ?
[ https://issues.apache.org/jira/browse/XALANC-813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17208405#comment-17208405 ] Roger Leigh commented on XALANC-813: LocalMsgIndex is generated during the build automatically. Which message loader did you configure? Note: see the comments in *src/xalanc/Utils/CMakeLists.txt*. Some of the message loaders (e.g. ICU) are known to be broken and need someone to fix them. If in doubt, use the "inmemory" loader. > Can we build xalan-c(1.12) on rhel 8.2 ? > > > Key: XALANC-813 > URL: https://issues.apache.org/jira/browse/XALANC-813 > Project: XalanC > Issue Type: Bug > Components: XalanC >Affects Versions: 1.12 >Reporter: Krunal Ghute >Assignee: Gary D. Gregory >Priority: Major > Fix For: 1.11 > > > Not able to build xalan-c rpms on rhel 8.2 using spec file. can we build > xalan-c (1.12) on rhel 8.2? if yes then can you please tell me the procedure. > beacuse while building xalan-c rpm we faced many compilation issues , PSB. > -Wformat-nonliteral] > theCharsWritten = sprintf(theBuffer, *thePrintfString, theValue); > ^ > [ 7%] Building CXX object > src/xalanc/CMakeFiles/xalan-c.dir/PlatformSupport/DOMStringPrintWriter.cpp.o > [ 7%] Building CXX object > src/xalanc/CMakeFiles/xalan-c.dir/PlatformSupport/DoubleSupport.cpp.o > [ 7%] Building CXX object > src/xalanc/CMakeFiles/xalan-c.dir/PlatformSupport/ExecutionContext.cpp.o > In file included from > /home/pmx/rpmbuild/BUILD/amdocs-xalan-c-1.12/src/xalanc/PlatformSupport/ExecutionContext.hpp:32, > from > /home/pmx/rpmbuild/BUILD/amdocs-xalan-c-1.12/src/xalanc/PlatformSupport/ExecutionContext.cpp:19: > /home/pmx/rpmbuild/BUILD/amdocs-xalan-c-1.12/src/xalanc/PlatformSupport/ProblemListenerBase.hpp:28:10: > fatal error: LocalMsgIndex.hpp: No such file or directory > #include "LocalMsgIndex.hpp" > ^~~ > compilation terminated. > make[2]: *** [src/xalanc/CMakeFiles/xalan-c.dir/build.make:427: > src/xalanc/CMakeFiles/xalan-c.dir/PlatformSupport/ExecutionContext.cpp.o] > Error 1 > make[1]: *** [CMakeFiles/Makefile2:250: > src/xalanc/CMakeFiles/xalan-c.dir/all] Error 2 > make: *** [Makefile:141: all] Error 2 > error: Bad exit status from /var/tmp/rpm-tmp.zf5qy4 (%build) > please help to resolve this isses. > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Resolved] (XALANC-812) Remove NDEBUG/_DEBUG check
[ https://issues.apache.org/jira/browse/XALANC-812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Leigh resolved XALANC-812. Resolution: Fixed > Remove NDEBUG/_DEBUG check > -- > > Key: XALANC-812 > URL: https://issues.apache.org/jira/browse/XALANC-812 > Project: XalanC > Issue Type: Bug > Components: XalanC >Affects Versions: 1.12 >Reporter: Roger Leigh >Assignee: Roger Leigh >Priority: Major > Fix For: 1.13 > > > Unclear why this check exists, and it has been reported to cause problems. > Remove the check entirely from PlatformDefinitions.hpp.in. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Created] (XALANC-812) Remove NDEBUG/_DEBUG check
Roger Leigh created XALANC-812: -- Summary: Remove NDEBUG/_DEBUG check Key: XALANC-812 URL: https://issues.apache.org/jira/browse/XALANC-812 Project: XalanC Issue Type: Bug Components: XalanC Affects Versions: 1.12 Reporter: Roger Leigh Assignee: Roger Leigh Fix For: 1.13 Unclear why this check exists, and it has been reported to cause problems. Remove the check entirely from PlatformDefinitions.hpp.in. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Created] (XALANC-811) Support in-source build
Roger Leigh created XALANC-811: -- Summary: Support in-source build Key: XALANC-811 URL: https://issues.apache.org/jira/browse/XALANC-811 Project: XalanC Issue Type: Bug Components: XalanC Affects Versions: 1.12 Reporter: Roger Leigh Assignee: Roger Leigh Fix For: 1.13 Sample and/or Test executables have the same name as the subdirectory. They are stored one level up and so causes naming conflicts on Unix where there is no executable suffix. Move the executables into the subdirectories. Update documentation to point to new locations. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Commented] (XALANC-808) Remove XalanMsgLib
[ https://issues.apache.org/jira/browse/XALANC-808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17132666#comment-17132666 ] Roger Leigh commented on XALANC-808: For reference, XERCESC-2204 is the same issue in Xerces-C. > Remove XalanMsgLib > -- > > Key: XALANC-808 > URL: https://issues.apache.org/jira/browse/XALANC-808 > Project: XalanC > Issue Type: Bug > Components: XalanC >Affects Versions: 1.13 >Reporter: Roger Leigh >Assignee: Gary D. Gregory >Priority: Major > Fix For: 1.13 > > Original Estimate: 24h > Remaining Estimate: 24h > > XalanMsgLib adds quite a bit of complexity to the build and to the > implementation. It's also completely unused: there is only a single > supported language: en_US. There hasn't been another language added in the > entire history of the project. The demand for and likelihood of getting any > translations is near zero. > As a result, this issue is a proposal for dropping the XalanMsgLib library. > If it's unused, why pay the costs for having it? > Unless there are any objections, I would suggest we drop it entirely for 1.13. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Assigned] (XALANC-808) Remove XalanMsgLib
[ https://issues.apache.org/jira/browse/XALANC-808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Leigh reassigned XALANC-808: -- Assignee: Roger Leigh (was: Gary D. Gregory) > Remove XalanMsgLib > -- > > Key: XALANC-808 > URL: https://issues.apache.org/jira/browse/XALANC-808 > Project: XalanC > Issue Type: Bug > Components: XalanC >Affects Versions: 1.13 >Reporter: Roger Leigh >Assignee: Roger Leigh >Priority: Major > Fix For: 1.13 > > Original Estimate: 24h > Remaining Estimate: 24h > > XalanMsgLib adds quite a bit of complexity to the build and to the > implementation. It's also completely unused: there is only a single > supported language: en_US. There hasn't been another language added in the > entire history of the project. The demand for and likelihood of getting any > translations is near zero. > As a result, this issue is a proposal for dropping the XalanMsgLib library. > If it's unused, why pay the costs for having it? > Unless there are any objections, I would suggest we drop it entirely for 1.13. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Resolved] (XALANC-809) XalanTransformer/XalanCAPI.h
[
https://issues.apache.org/jira/browse/XALANC-809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roger Leigh resolved XALANC-809.
Resolution: Fixed
> XalanTransformer/XalanCAPI.h
>
>
> Key: XALANC-809
> URL: https://issues.apache.org/jira/browse/XALANC-809
> Project: XalanC
> Issue Type: Bug
> Components: XalanC
>Affects Versions: 1.12
> Environment: FreeBSD 12
>Reporter: Roger Leigh
>Assignee: Roger Leigh
>Priority: Major
> Fix For: 1.13
>
>
> Noticed while packaging 1.12 for the FreeBSD ports, this header is present
> but not installed. Patch is trivial:
> {noformat}
> diff --git a/src/xalanc/CMakeLists.txt b/src/xalanc/CMakeLists.txt
> index eee478e03..a5d9131c4 100644
> --- a/src/xalanc/CMakeLists.txt
> +++ b/src/xalanc/CMakeLists.txt
> @@ -832,6 +832,7 @@ set(xalantransformer_sources
>XalanTransformer/XercesDOMWrapperParsedSource.cpp)
> set(xalantransformer_headers
> + XalanTransformer/XalanCAPI.h
>XalanTransformer/XalanCompiledStylesheetDefault.hpp
>XalanTransformer/XalanCompiledStylesheet.hpp
>XalanTransformer/XalanDefaultDocumentBuilder.hpp
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org
For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Assigned] (XALANC-809) XalanTransformer/XalanCAPI.h
[
https://issues.apache.org/jira/browse/XALANC-809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roger Leigh reassigned XALANC-809:
--
Assignee: Roger Leigh (was: Gary D. Gregory)
> XalanTransformer/XalanCAPI.h
>
>
> Key: XALANC-809
> URL: https://issues.apache.org/jira/browse/XALANC-809
> Project: XalanC
> Issue Type: Bug
> Components: XalanC
>Affects Versions: 1.12
> Environment: FreeBSD 12
>Reporter: Roger Leigh
>Assignee: Roger Leigh
>Priority: Major
> Fix For: 1.13
>
>
> Noticed while packaging 1.12 for the FreeBSD ports, this header is present
> but not installed. Patch is trivial:
> {noformat}
> diff --git a/src/xalanc/CMakeLists.txt b/src/xalanc/CMakeLists.txt
> index eee478e03..a5d9131c4 100644
> --- a/src/xalanc/CMakeLists.txt
> +++ b/src/xalanc/CMakeLists.txt
> @@ -832,6 +832,7 @@ set(xalantransformer_sources
>XalanTransformer/XercesDOMWrapperParsedSource.cpp)
> set(xalantransformer_headers
> + XalanTransformer/XalanCAPI.h
>XalanTransformer/XalanCompiledStylesheetDefault.hpp
>XalanTransformer/XalanCompiledStylesheet.hpp
>XalanTransformer/XalanDefaultDocumentBuilder.hpp
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org
For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Created] (XALANC-809) XalanTransformer/XalanCAPI.h
Roger Leigh created XALANC-809:
--
Summary: XalanTransformer/XalanCAPI.h
Key: XALANC-809
URL: https://issues.apache.org/jira/browse/XALANC-809
Project: XalanC
Issue Type: Bug
Components: XalanC
Affects Versions: 1.12
Environment: FreeBSD 12
Reporter: Roger Leigh
Assignee: Gary D. Gregory
Fix For: 1.13
Noticed while packaging 1.12 for the FreeBSD ports, this header is present but
not installed. Patch is trivial:
{noformat}
diff --git a/src/xalanc/CMakeLists.txt b/src/xalanc/CMakeLists.txt
index eee478e03..a5d9131c4 100644
--- a/src/xalanc/CMakeLists.txt
+++ b/src/xalanc/CMakeLists.txt
@@ -832,6 +832,7 @@ set(xalantransformer_sources
XalanTransformer/XercesDOMWrapperParsedSource.cpp)
set(xalantransformer_headers
+ XalanTransformer/XalanCAPI.h
XalanTransformer/XalanCompiledStylesheetDefault.hpp
XalanTransformer/XalanCompiledStylesheet.hpp
XalanTransformer/XalanDefaultDocumentBuilder.hpp
{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org
For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Assigned] (XALANC-803) MinGW build is broken
[ https://issues.apache.org/jira/browse/XALANC-803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Leigh reassigned XALANC-803: -- Assignee: Roger Leigh (was: Gary D. Gregory) > MinGW build is broken > - > > Key: XALANC-803 > URL: https://issues.apache.org/jira/browse/XALANC-803 > Project: XalanC > Issue Type: Bug > Components: XalanC >Affects Versions: 1.12 >Reporter: Roger Leigh >Assignee: Roger Leigh >Priority: Major > Fix For: 1.13 > > Original Estimate: 48h > Remaining Estimate: 48h > > HANDLE and other macros not defined. Likely need to check if it should be > using the Unix or Windows includes and types, and adjust to make MinGW work. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Updated] (XALANC-802) Static builds are broken on Windows
[ https://issues.apache.org/jira/browse/XALANC-802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Leigh updated XALANC-802: --- Affects Version/s: 1.12 > Static builds are broken on Windows > --- > > Key: XALANC-802 > URL: https://issues.apache.org/jira/browse/XALANC-802 > Project: XalanC > Issue Type: Bug > Components: XalanC >Affects Versions: 1.11, 1.12 > Environment: MSVC >Reporter: Roger Leigh >Assignee: Roger Leigh >Priority: Major > Fix For: 1.13 > > Original Estimate: 24h > Remaining Estimate: 24h > > The DLL import/export macros are used unconditionally, breaking linking when > using a static library. > Use a suitable _EXPORT define when building; see CMake GenerateExportHeader > for one way to do this which could be easily enabled. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Assigned] (XALANC-802) Static builds are broken on Windows
[ https://issues.apache.org/jira/browse/XALANC-802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Leigh reassigned XALANC-802: -- Assignee: Roger Leigh (was: Gary D. Gregory) > Static builds are broken on Windows > --- > > Key: XALANC-802 > URL: https://issues.apache.org/jira/browse/XALANC-802 > Project: XalanC > Issue Type: Bug > Components: XalanC >Affects Versions: 1.11 > Environment: MSVC >Reporter: Roger Leigh >Assignee: Roger Leigh >Priority: Major > Fix For: 1.13 > > Original Estimate: 24h > Remaining Estimate: 24h > > The DLL import/export macros are used unconditionally, breaking linking when > using a static library. > Use a suitable _EXPORT define when building; see CMake GenerateExportHeader > for one way to do this which could be easily enabled. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Resolved] (XALANC-807) CMake build unconditionally adds debug postfix with MSVC
[ https://issues.apache.org/jira/browse/XALANC-807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Leigh resolved XALANC-807. Resolution: Fixed > CMake build unconditionally adds debug postfix with MSVC > > > Key: XALANC-807 > URL: https://issues.apache.org/jira/browse/XALANC-807 > Project: XalanC > Issue Type: Bug > Components: XalanC >Affects Versions: 1.12 > Environment: Microsoft Visual C++ >Reporter: Roger Leigh >Assignee: Roger Leigh >Priority: Major > Labels: cmake > Fix For: 1.12 > > Original Estimate: 24h > Remaining Estimate: 24h > > CMAKE_DEBUG_POSTFIX is unconditionally added to the library name when > building with MSVC. This issue is carried over from the Xerces-C CMake > logic, where the bug was already fixed. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Updated] (XALANC-807) CMake build unconditionally adds debug postfix with MSVC
[ https://issues.apache.org/jira/browse/XALANC-807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Leigh updated XALANC-807: --- Summary: CMake build unconditionally adds debug postfix with MSVC (was: CMake builds unconditionally adds debug postfix with MSVC) > CMake build unconditionally adds debug postfix with MSVC > > > Key: XALANC-807 > URL: https://issues.apache.org/jira/browse/XALANC-807 > Project: XalanC > Issue Type: Bug > Components: XalanC >Affects Versions: 1.12 > Environment: Microsoft Visual C++ >Reporter: Roger Leigh >Assignee: Roger Leigh >Priority: Major > Labels: cmake > Fix For: 1.12 > > Original Estimate: 24h > Remaining Estimate: 24h > > CMAKE_DEBUG_POSTFIX is unconditionally added to the library name when > building with MSVC. This issue is carried over from the Xerces-C CMake > logic, where the bug was already fixed. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Created] (XALANC-807) CMake builds unconditionally adds debug postfix with MSVC
Roger Leigh created XALANC-807: -- Summary: CMake builds unconditionally adds debug postfix with MSVC Key: XALANC-807 URL: https://issues.apache.org/jira/browse/XALANC-807 Project: XalanC Issue Type: Bug Components: XalanC Affects Versions: 1.12 Environment: Microsoft Visual C++ Reporter: Roger Leigh Assignee: Roger Leigh Fix For: 1.12 CMAKE_DEBUG_POSTFIX is unconditionally added to the library name when building with MSVC. This issue is carried over from the Xerces-C CMake logic, where the bug was already fixed. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Resolved] (XALANC-801) Enable AppVeyor CI for Windows
[ https://issues.apache.org/jira/browse/XALANC-801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Leigh resolved XALANC-801. Resolution: Fixed Passing with caveats (no MinGW, no Cygwin, and no static library support), so currently just DLL with VS2017. > Enable AppVeyor CI for Windows > -- > > Key: XALANC-801 > URL: https://issues.apache.org/jira/browse/XALANC-801 > Project: XalanC > Issue Type: Bug >Affects Versions: 1.12 >Reporter: Roger Leigh >Assignee: Roger Leigh >Priority: Major > Fix For: 1.12 > > > To complement the Travis CI, add AppVeyor for testing MSVC, MinGW and Cygwin. > XALANC-799 and XALANC-800 are prerequisites for MinGW. > Cygwin might require an update to FindXercesC.cmake in CMake (it uses a > slightly different library naming convention). So Cygwin support might > require deferring. > MSVC can use vcpkg to obtain the build dependencies. > Note Xerces-C++ AppVeyor support can be used as the basis for this. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Resolved] (XALANC-780) Use xalanc namespace unconditionally
[ https://issues.apache.org/jira/browse/XALANC-780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Leigh resolved XALANC-780. Fix Version/s: 1.12 Assignee: Roger Leigh (was: Steven J. Hathaway) Resolution: Fixed Fixed in https://github.com/apache/xalan-c/pull/3 > Use xalanc namespace unconditionally > > > Key: XALANC-780 > URL: https://issues.apache.org/jira/browse/XALANC-780 > Project: XalanC > Issue Type: Improvement > Components: XalanC >Affects Versions: 1.11 >Reporter: Roger Leigh >Assignee: Roger Leigh >Priority: Major > Fix For: 1.12 > > Attachments: 0001-Remove-XALAN_CPP_NAMESPACE_BEGIN-and-_END.patch, > 0002-Drop-use-of-XALAN_CPP_NAMESPACE_USE.patch, > 0003-Remove-XALAN_USING_XALAN_CLASS-and-_STRUCT.patch, > 0004-Remove-XALAN_USING_XALAN-macro.patch, > 0005-Remove-XALAN_DECLARE_CLASS-and-_STRUCT-macros.patch, > 0006-Remove-XALAN_USING_STD-macro.patch, 0007-Remove-XALAN_USING-macro.patch, > 0008-Remove-XALAN_STD_QUALIFIER.patch, > 0009-Remove-XALAN_NO_STD_NAMESPACE-and-workarounds.patch, > 0010-Remove-XALAN_HAS_CPP_NAMESPACE-and-workarounds.patch > > > Related to XALANC-779. > > All currently supported platforms can cope with namespaces. This patchset > removes all the special case workarounds and macros used to handle > non-namespace-capable compilers. The aim being to simplify the code for > ongoing maintenance and drop unnecessary logic from the platform-specific > headers (with the intention being to replace them entirely by feature tests). > But there's little point adding feature tests for features which have been > supported for decades; we may as well drop the special-casing at this point. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Resolved] (XALANC-777) Remove redundant XALAN_SGI_BASED_STL macro
[ https://issues.apache.org/jira/browse/XALANC-777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Leigh resolved XALANC-777. Fix Version/s: 1.12 Resolution: Fixed Fixed in https://github.com/apache/xalan-c/pull/3 > Remove redundant XALAN_SGI_BASED_STL macro > -- > > Key: XALANC-777 > URL: https://issues.apache.org/jira/browse/XALANC-777 > Project: XalanC > Issue Type: Improvement > Components: XalanC >Affects Versions: 1.11 >Reporter: Roger Leigh >Assignee: Steven J. Hathaway >Priority: Major > Labels: build, patch > Fix For: 1.12 > > Attachments: > 0001-Remove-unused-compatibility-macro-XALAN_SGI_BASED_ST.patch > > > Removes unused redundant logic from the headers (to simplify adding feature > macros for autoconf and cmake). No impact on portability or compatibility > since the removed conditional logic was unused. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Resolved] (XALANC-806) C++98 and C++11 support
[ https://issues.apache.org/jira/browse/XALANC-806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Leigh resolved XALANC-806. Resolution: Fixed Fixed in [https://github.com/apache/xalan-c/pull/3|https://github.com/apache/xalan-c/pull/3/files] and https://github.com/apache/xalan-c/pull/4 > C++98 and C++11 support > --- > > Key: XALANC-806 > URL: https://issues.apache.org/jira/browse/XALANC-806 > Project: XalanC > Issue Type: Bug > Components: XalanC >Affects Versions: 1.11 >Reporter: Roger Leigh >Assignee: Roger Leigh >Priority: Major > Fix For: 1.12 > > Original Estimate: 336h > Remaining Estimate: 336h > > * Make C++98 the minimum supported version, removing compatibility macros for > pre-Standard compilers > * Make C++11 supported; requires removal of use of std::unary_function and > std::binary_function (which is backward-compatible) > The intent of these changes is to allow Xalan-C++ to compile with all > contemporary compilers up to at least C++17, while still retaining support > for older platforms as much as possible. Only thoroughly obsolete platforms > will be left out. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Resolved] (XALANC-773) Build failure with Xerces-C++ 3.2.0 and VS2015
[ https://issues.apache.org/jira/browse/XALANC-773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Leigh resolved XALANC-773. Fix Version/s: 1.12 Assignee: Roger Leigh (was: Steven J. Hathaway) Resolution: Fixed Fixed in https://github.com/apache/xalan-c/pull/3/files > Build failure with Xerces-C++ 3.2.0 and VS2015 > -- > > Key: XALANC-773 > URL: https://issues.apache.org/jira/browse/XALANC-773 > Project: XalanC > Issue Type: Bug > Components: XalanC >Affects Versions: 1.11 > Environment: Windows with VS2015 >Reporter: Roger Leigh >Assignee: Roger Leigh >Priority: Major > Labels: PlatformSupport, build > Fix For: 1.12 > > Attachments: xerces-char16_t.diff > > > Xerces-C++ 3.2.0 will allow XMLChar to be char16_t instead of wchar_t on a > compiler with C++11 support such as VS2015. The attached patch is required > to fix a few places in the Xalan-C sources where implicit wchar_t to > XalanDOMChar* conversions were used without casts. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Resolved] (XALANC-776) Add CMake build system
[ https://issues.apache.org/jira/browse/XALANC-776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Leigh resolved XALANC-776. Resolution: Fixed Fixed in https://github.com/apache/xalan-c/pull/5 > Add CMake build system > -- > > Key: XALANC-776 > URL: https://issues.apache.org/jira/browse/XALANC-776 > Project: XalanC > Issue Type: Improvement > Components: XalanC >Affects Versions: 1.11 >Reporter: Roger Leigh >Assignee: Roger Leigh >Priority: Major > Labels: build, cmake, patch > Fix For: 1.12 > > Attachments: 0001-Add-CMake-build-system.patch > > Original Estimate: 504h > Remaining Estimate: 504h > > h4. Introduction > The attached patch implements a CMake build for Xalan-C++. I have spent > significant effort performing a "comprehensive" conversion of the existing > GNU autotools and MSVC project file logic to a unified CMake build which > supports all platforms with a single set of build files, as well as testing > it on several platforms. The existing GNU autotools build and MSVC project > builds will continue to function and are unaffected by this addition. > This is a companion to https://issues.apache.org/jira/browse/XERCESC-2077 > which was merged last year and included in Xerces-C++ 3.2.0. I mentioned > this work on the list last year in > https://marc.info/?l=xalan-dev=149748238016328=2 > h4. Background > CMake is a meta-build system which generates the build files for a specified > build system, such as make, Visual Studio msbuild, nmake, ninja or a number > of other build tools and IDEs. This allows Xalan-C++ to be built on any > supported platform with the native tools for that platform. The reason why I > originally needed this was due to the large maintenance burden of patching > the provided Visual Studio project files, both for fixing bugs in those files > and in being able to support versions of Visual Studio which aren't yet > supported by the provided project files or for unsupported configurations > e.g. Clang/C2, other platforms etc. The lack of an install target also meant > that to integrate this with a larger build required manually copying bits out > of the build tree. The cost of debugging and patching the existing project > files for use in our CI builds was getting too great--maintaining and using > this CMake build out of tree will be cheaper and more robust. I thought it > might benefit others to have this merged upstream so that it would be > available to the benefit of all. I have done a direct conversion of the > existing autoconf build logic. The automake Makefile.am logic is directly > represented in the corresponding CMakeLists.txt files. > Unfortunately, and unlike for Xerces, the Xalan Autoconf build is in a very > bad state, and it's become increasingly unusable over time. It has these > major problems: > * No feature tests. Platform-specific behaviour is hardcoded in > "Include/XXXDefinitions.hpp" files which is inflexible and not future-proof > as platforms evolve. Autoconf feature tests could be used like in Xerces-C++ > * No Autoconf enable/with options. Configuration is with a hacky and > nonportable "runConfigure" script which works around the lack of options. > * MinGW64 is broken right now because of a lack of feature test for gmtime_r > / localtime_r, for example. The static platform configuration says it > doesn't have these functions, but it does and the build breaks because Xalan > unnecessarily redefines them. > The patch included here can't solve all these problems. But right now I'm > finding it extremely hard to build and install Xalan on a range of platforms, > and the amount of effort required to patch all of the Project/Solution files, > Autoconf/Automake files and platform-specific headers is untenable. This > CMake build will work on every platform. > Some feature tests do require adding to the CMake build, replacing the > Platform-specific headers, but I've not done that in this inital patch, which > has a smaller scope of working with the existing headers without making any > major changes. > I'm prepared to do the extra work to bring this up to the equivalent state as > already done for Xerces-C++ which will allow these libraries to build on all > contemporary platforms. This includes fixing it to work with C++17 as > reported separately by another user. > > Kind regards, > Roger -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Assigned] (XALANC-776) Add CMake build system
[ https://issues.apache.org/jira/browse/XALANC-776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Leigh reassigned XALANC-776: -- Fix Version/s: 1.12 Affects Version/s: 1.11 Assignee: Roger Leigh (was: Steven J. Hathaway) Remaining Estimate: 504h Original Estimate: 504h > Add CMake build system > -- > > Key: XALANC-776 > URL: https://issues.apache.org/jira/browse/XALANC-776 > Project: XalanC > Issue Type: Improvement > Components: XalanC >Affects Versions: 1.11 >Reporter: Roger Leigh >Assignee: Roger Leigh >Priority: Major > Labels: build, cmake, patch > Fix For: 1.12 > > Attachments: 0001-Add-CMake-build-system.patch > > Original Estimate: 504h > Remaining Estimate: 504h > > h4. Introduction > The attached patch implements a CMake build for Xalan-C++. I have spent > significant effort performing a "comprehensive" conversion of the existing > GNU autotools and MSVC project file logic to a unified CMake build which > supports all platforms with a single set of build files, as well as testing > it on several platforms. The existing GNU autotools build and MSVC project > builds will continue to function and are unaffected by this addition. > This is a companion to https://issues.apache.org/jira/browse/XERCESC-2077 > which was merged last year and included in Xerces-C++ 3.2.0. I mentioned > this work on the list last year in > https://marc.info/?l=xalan-dev=149748238016328=2 > h4. Background > CMake is a meta-build system which generates the build files for a specified > build system, such as make, Visual Studio msbuild, nmake, ninja or a number > of other build tools and IDEs. This allows Xalan-C++ to be built on any > supported platform with the native tools for that platform. The reason why I > originally needed this was due to the large maintenance burden of patching > the provided Visual Studio project files, both for fixing bugs in those files > and in being able to support versions of Visual Studio which aren't yet > supported by the provided project files or for unsupported configurations > e.g. Clang/C2, other platforms etc. The lack of an install target also meant > that to integrate this with a larger build required manually copying bits out > of the build tree. The cost of debugging and patching the existing project > files for use in our CI builds was getting too great--maintaining and using > this CMake build out of tree will be cheaper and more robust. I thought it > might benefit others to have this merged upstream so that it would be > available to the benefit of all. I have done a direct conversion of the > existing autoconf build logic. The automake Makefile.am logic is directly > represented in the corresponding CMakeLists.txt files. > Unfortunately, and unlike for Xerces, the Xalan Autoconf build is in a very > bad state, and it's become increasingly unusable over time. It has these > major problems: > * No feature tests. Platform-specific behaviour is hardcoded in > "Include/XXXDefinitions.hpp" files which is inflexible and not future-proof > as platforms evolve. Autoconf feature tests could be used like in Xerces-C++ > * No Autoconf enable/with options. Configuration is with a hacky and > nonportable "runConfigure" script which works around the lack of options. > * MinGW64 is broken right now because of a lack of feature test for gmtime_r > / localtime_r, for example. The static platform configuration says it > doesn't have these functions, but it does and the build breaks because Xalan > unnecessarily redefines them. > The patch included here can't solve all these problems. But right now I'm > finding it extremely hard to build and install Xalan on a range of platforms, > and the amount of effort required to patch all of the Project/Solution files, > Autoconf/Automake files and platform-specific headers is untenable. This > CMake build will work on every platform. > Some feature tests do require adding to the CMake build, replacing the > Platform-specific headers, but I've not done that in this inital patch, which > has a smaller scope of working with the existing headers without making any > major changes. > I'm prepared to do the extra work to bring this up to the equivalent state as > already done for Xerces-C++ which will allow these libraries to build on all > contemporary platforms. This includes fixing it to work with C++17 as > reported separately by another user. > > Kind regards, > Roger -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Resolved] (XALANC-805) Apply outstanding critical fixes
[ https://issues.apache.org/jira/browse/XALANC-805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Leigh resolved XALANC-805. Resolution: Fixed Fixed inhttps://github.com/apache/xalan-c/pull/1/commits > Apply outstanding critical fixes > > > Key: XALANC-805 > URL: https://issues.apache.org/jira/browse/XALANC-805 > Project: XalanC > Issue Type: Bug > Components: XalanC >Affects Versions: 1.11 > Environment: Various >Reporter: Roger Leigh >Assignee: Roger Leigh >Priority: Major > Fix For: 1.12 > > Original Estimate: 48h > Remaining Estimate: 48h > > These either break building or cause a fault at runtime. These patches have > been carried over many years by many distributions, from Debian, FreeBSD > Ports, MacPorts, homebrew etc. These are the major driver for a new release: > to have a release that works out of the box without patching. > > * [Add _ALLOW_RTCc_IN_STL to MSVC > build|https://github.com/apache/xalan-c/pull/1/commits/ee075c356deeb2e69d53583a9874d439415400e9] > * [Drop unnecessary MFC requirement from MSVC > build|https://github.com/apache/xalan-c/pull/1/commits/ae9a8473944a30277eb6254e73f45c7e87a84938] > * [Allow use of C++11 char16_t as XMLCh > type|https://github.com/apache/xalan-c/pull/1/commits/de973d5122da27e475a69d50d3829608134d1c64] > * [Use DYLD_FALLBACK_LIBRARY_PATH on > MacOS|https://github.com/apache/xalan-c/pull/1/commits/596b3bbd3dfd3a6d64566de5393b6568ecacae69] > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Created] (XALANC-805) Apply outstanding critical fixes
Roger Leigh created XALANC-805: -- Summary: Apply outstanding critical fixes Key: XALANC-805 URL: https://issues.apache.org/jira/browse/XALANC-805 Project: XalanC Issue Type: Bug Components: XalanC Affects Versions: 1.11 Environment: Various Reporter: Roger Leigh Assignee: Roger Leigh Fix For: 1.12 These either break building or cause a fault at runtime. These patches have been carried over many years by many distributions, from Debian, FreeBSD Ports, MacPorts, homebrew etc. These are the major driver for a new release: to have a release that works out of the box without patching. * [Add _ALLOW_RTCc_IN_STL to MSVC build|https://github.com/apache/xalan-c/pull/1/commits/ee075c356deeb2e69d53583a9874d439415400e9] * [Drop unnecessary MFC requirement from MSVC build|https://github.com/apache/xalan-c/pull/1/commits/ae9a8473944a30277eb6254e73f45c7e87a84938] * [Allow use of C++11 char16_t as XMLCh type|https://github.com/apache/xalan-c/pull/1/commits/de973d5122da27e475a69d50d3829608134d1c64] * [Use DYLD_FALLBACK_LIBRARY_PATH on MacOS|https://github.com/apache/xalan-c/pull/1/commits/596b3bbd3dfd3a6d64566de5393b6568ecacae69] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Resolved] (XALANC-771) Support for Parallel Builds
[ https://issues.apache.org/jira/browse/XALANC-771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Leigh resolved XALANC-771. Assignee: Roger Leigh (was: Steven J. Hathaway) Resolution: Fixed Fixed in https://github.com/apache/xalan-c/pull/2 > Support for Parallel Builds > --- > > Key: XALANC-771 > URL: https://issues.apache.org/jira/browse/XALANC-771 > Project: XalanC > Issue Type: Wish > Components: XalanC >Affects Versions: 1.11 >Reporter: Bill Blough >Assignee: Roger Leigh >Priority: Minor > Fix For: 1.12 > > Attachments: parallel.diff > > > When doing parallel builds (make -j where is the number of parallel > jobs) PlatformSupport is sometimes built before Utils. This causes the build > to fail, as LocalMsgIndex.hpp (required by PlatformSupport and generated by > make -C Utils) is missing. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Updated] (XALANC-771) Support for Parallel Builds
[ https://issues.apache.org/jira/browse/XALANC-771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Leigh updated XALANC-771: --- Fix Version/s: 1.12 Affects Version/s: 1.11 > Support for Parallel Builds > --- > > Key: XALANC-771 > URL: https://issues.apache.org/jira/browse/XALANC-771 > Project: XalanC > Issue Type: Wish > Components: XalanC >Affects Versions: 1.11 >Reporter: Bill Blough >Assignee: Steven J. Hathaway >Priority: Minor > Fix For: 1.12 > > Attachments: parallel.diff > > > When doing parallel builds (make -j where is the number of parallel > jobs) PlatformSupport is sometimes built before Utils. This causes the build > to fail, as LocalMsgIndex.hpp (required by PlatformSupport and generated by > make -C Utils) is missing. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Resolved] (XALANC-751) Segmentation fault in TestXSLT
[ https://issues.apache.org/jira/browse/XALANC-751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Leigh resolved XALANC-751. Resolution: Fixed Fixed in https://github.com/apache/xalan-c/pull/2 > Segmentation fault in TestXSLT > -- > > Key: XALANC-751 > URL: https://issues.apache.org/jira/browse/XALANC-751 > Project: XalanC > Issue Type: Bug > Components: XalanC >Affects Versions: 1.11 > Environment: Debian GNU/Linux >Reporter: Bill Blough >Assignee: Roger Leigh >Priority: Critical > Fix For: 1.12 > > > Forwarded from http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718303 > TestXSLT segfaults under certain input instead of returning an error. My > testing indicates that this issue began in SVN rev 1388736, as 1388735 > appears to exhibit the correct behavior. > The issue can be reproduced as follows: > $ cat var-in-xslkey.xsl > > xmlns:xsl="http://www.w3.org/1999/XSL/Transform;> > > > > $ xalan -xsl var-in-xslkey.xsl -in var-in-xslkey.xsl > Expected Results (1388735 and before): > XSLException Type is: XPathParserException > Message is: A variable reference is allowed in a match pattern or > expression in this context. > pattern = '*[@id != $var]' Remaining tokens are: ( 'var' ']') > (var-in-xslkey.xsl, line 5, column 54) > Actual Results (1388736 and later): > XPath error: A variable reference is allowed in a match pattern or expression > in this context. > pattern = '*[@id != $var]' Remaining tokens are: ( 'var' ']') (Occurred in > an unknown entity, at line 5, column 5.) > Segmentation fault -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Assigned] (XALANC-751) Segmentation fault in TestXSLT
[ https://issues.apache.org/jira/browse/XALANC-751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Leigh reassigned XALANC-751: -- Assignee: Roger Leigh (was: Steven J. Hathaway) > Segmentation fault in TestXSLT > -- > > Key: XALANC-751 > URL: https://issues.apache.org/jira/browse/XALANC-751 > Project: XalanC > Issue Type: Bug > Components: XalanC >Affects Versions: 1.11 > Environment: Debian GNU/Linux >Reporter: Bill Blough >Assignee: Roger Leigh >Priority: Critical > Fix For: 1.12 > > > Forwarded from http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718303 > TestXSLT segfaults under certain input instead of returning an error. My > testing indicates that this issue began in SVN rev 1388736, as 1388735 > appears to exhibit the correct behavior. > The issue can be reproduced as follows: > $ cat var-in-xslkey.xsl > > xmlns:xsl="http://www.w3.org/1999/XSL/Transform;> > > > > $ xalan -xsl var-in-xslkey.xsl -in var-in-xslkey.xsl > Expected Results (1388735 and before): > XSLException Type is: XPathParserException > Message is: A variable reference is allowed in a match pattern or > expression in this context. > pattern = '*[@id != $var]' Remaining tokens are: ( 'var' ']') > (var-in-xslkey.xsl, line 5, column 54) > Actual Results (1388736 and later): > XPath error: A variable reference is allowed in a match pattern or expression > in this context. > pattern = '*[@id != $var]' Remaining tokens are: ( 'var' ']') (Occurred in > an unknown entity, at line 5, column 5.) > Segmentation fault -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Updated] (XALANC-751) Segmentation fault in TestXSLT
[ https://issues.apache.org/jira/browse/XALANC-751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Leigh updated XALANC-751: --- Fix Version/s: 1.12 Description: Forwarded from http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718303 TestXSLT segfaults under certain input instead of returning an error. My testing indicates that this issue began in SVN rev 1388736, as 1388735 appears to exhibit the correct behavior. The issue can be reproduced as follows: $ cat var-in-xslkey.xsl http://www.w3.org/1999/XSL/Transform;> $ xalan -xsl var-in-xslkey.xsl -in var-in-xslkey.xsl Expected Results (1388735 and before): XSLException Type is: XPathParserException Message is: A variable reference is allowed in a match pattern or expression in this context. pattern = '*[@id != $var]' Remaining tokens are: ( 'var' ']') (var-in-xslkey.xsl, line 5, column 54) Actual Results (1388736 and later): XPath error: A variable reference is allowed in a match pattern or expression in this context. pattern = '*[@id != $var]' Remaining tokens are: ( 'var' ']') (Occurred in an unknown entity, at line 5, column 5.) Segmentation fault was: Forwarded from http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718303 TestXSLT segfaults under certain input instead of returning an error. My testing indicates that this issue began in SVN rev 1388736, as 1388735 appears to exhibit the correct behavior. The issue can be reproduced as follows: $ cat var-in-xslkey.xsl http://www.w3.org/1999/XSL/Transform;> $ xalan -xsl var-in-xslkey.xsl -in var-in-xslkey.xsl Expected Results (1388735 and before): XSLException Type is: XPathParserException Message is: A variable reference is allowed in a match pattern or expression in this context. pattern = '*[@id != $var]' Remaining tokens are: ( 'var' ']') (var-in-xslkey.xsl, line 5, column 54) Actual Results (1388736 and later): XPath error: A variable reference is allowed in a match pattern or expression in this context. pattern = '*[@id != $var]' Remaining tokens are: ( 'var' ']') (Occurred in an unknown entity, at line 5, column 5.) Segmentation fault > Segmentation fault in TestXSLT > -- > > Key: XALANC-751 > URL: https://issues.apache.org/jira/browse/XALANC-751 > Project: XalanC > Issue Type: Bug > Components: XalanC >Affects Versions: 1.11 > Environment: Debian GNU/Linux >Reporter: Bill Blough >Assignee: Steven J. Hathaway >Priority: Critical > Fix For: 1.12 > > > Forwarded from http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718303 > TestXSLT segfaults under certain input instead of returning an error. My > testing indicates that this issue began in SVN rev 1388736, as 1388735 > appears to exhibit the correct behavior. > The issue can be reproduced as follows: > $ cat var-in-xslkey.xsl > > xmlns:xsl="http://www.w3.org/1999/XSL/Transform;> > > > > $ xalan -xsl var-in-xslkey.xsl -in var-in-xslkey.xsl > Expected Results (1388735 and before): > XSLException Type is: XPathParserException > Message is: A variable reference is allowed in a match pattern or > expression in this context. > pattern = '*[@id != $var]' Remaining tokens are: ( 'var' ']') > (var-in-xslkey.xsl, line 5, column 54) > Actual Results (1388736 and later): > XPath error: A variable reference is allowed in a match pattern or expression > in this context. > pattern = '*[@id != $var]' Remaining tokens are: ( 'var' ']') (Occurred in > an unknown entity, at line 5, column 5.) > Segmentation fault -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Created] (XALANC-804) Cygwin build is broken
Roger Leigh created XALANC-804: -- Summary: Cygwin build is broken Key: XALANC-804 URL: https://issues.apache.org/jira/browse/XALANC-804 Project: XalanC Issue Type: Bug Components: XalanC Affects Versions: 1.12 Environment: Cygwin Reporter: Roger Leigh Assignee: Gary D. Gregory Fix For: 1.13 FindXercesC CMake module does not support Xerces Cygwin DLLs. Patch created upstream ([here|https://gitlab.kitware.com/cmake/cmake/-/merge_requests/4783]). With that patch applied, and a new CMake release out, we can then look at properly adding Cygwin to our CI. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Created] (XALANC-803) MinGW build is broken
Roger Leigh created XALANC-803: -- Summary: MinGW build is broken Key: XALANC-803 URL: https://issues.apache.org/jira/browse/XALANC-803 Project: XalanC Issue Type: Bug Components: XalanC Affects Versions: 1.12 Reporter: Roger Leigh Assignee: Gary D. Gregory Fix For: 1.13 HANDLE and other macros not defined. Likely need to check if it should be using the Unix or Windows includes and types, and adjust to make MinGW work. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Created] (XALANC-802) Static builds are broken on Windows
Roger Leigh created XALANC-802: -- Summary: Static builds are broken on Windows Key: XALANC-802 URL: https://issues.apache.org/jira/browse/XALANC-802 Project: XalanC Issue Type: Bug Components: XalanC Affects Versions: 1.11 Environment: MSVC Reporter: Roger Leigh Assignee: Gary D. Gregory Fix For: 1.13 The DLL import/export macros are used unconditionally, breaking linking when using a static library. Use a suitable _EXPORT define when building; see CMake GenerateExportHeader for one way to do this which could be easily enabled. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Resolved] (XALANC-800) Add CMake feature tests to replace specific platform definitions
[
https://issues.apache.org/jira/browse/XALANC-800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roger Leigh resolved XALANC-800.
Resolution: Fixed
> Add CMake feature tests to replace specific platform definitions
>
>
> Key: XALANC-800
> URL: https://issues.apache.org/jira/browse/XALANC-800
> Project: XalanC
> Issue Type: Bug
> Components: XalanC
>Affects Versions: 1.12
>Reporter: Roger Leigh
>Assignee: Roger Leigh
>Priority: Major
> Fix For: 1.12
>
>
> Macros:
> {noformat}
> __HPACC_THREAD_SAFE_RB_TREE
> __USE_STD_IOSTREAM
> WINDOWS_THREAD_FUNCTIONS
> XALAN_NEWLINE_IS_CRLF
> XALAN_NO_REENTRANT_TIME_FUNCTIONS
> XALAN_NON_ASCII_PLATFORM
> XALAN_PLATFORM_EXPORT
> XALAN_PLATFORM_IMPORT
> XALAN_POSIX2_AVAILABLE
> XALAN_STATIC_ASSERT
> XALAN_WINDOWS
> XALAN_WINDOWS_DIR_FUNCTIONS
> {noformat}
> The underlying problem is that these hardcoded assumptions can be broken.
> Case in point, XALAN_NO_REENTRANT_TIME_FUNCTIONS is defined for GCC under
> MinGW... but current MinGW actually provides localtime_t and gmtime_r, which
> breaks building due to mutually incompatible function declarations. Feature
> tests will remove these assumptions and make building Xalan more robust and
> able to adapt to changes in platforms over time.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org
For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Resolved] (XALANC-799) Remove use of winres.h in XalanMsgLib.rc
[ https://issues.apache.org/jira/browse/XALANC-799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Leigh resolved XALANC-799. Resolution: Fixed > Remove use of winres.h in XalanMsgLib.rc > > > Key: XALANC-799 > URL: https://issues.apache.org/jira/browse/XALANC-799 > Project: XalanC > Issue Type: Bug > Components: XalanC >Affects Versions: 1.12 >Reporter: Roger Leigh >Assignee: Roger Leigh >Priority: Major > Fix For: 1.12 > > > MinGW doesn't have winres.h so this breaks the build. > XalanC.rc uses windows.h instead, and switching to this header looks like a > non-breaking and safe substitute which will work with MinGW. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Created] (XALANC-801) Enable AppVeyor CI for Windows
Roger Leigh created XALANC-801: -- Summary: Enable AppVeyor CI for Windows Key: XALANC-801 URL: https://issues.apache.org/jira/browse/XALANC-801 Project: XalanC Issue Type: Bug Affects Versions: 1.12 Reporter: Roger Leigh Assignee: Roger Leigh Fix For: 1.12 To complement the Travis CI, add AppVeyor for testing MSVC, MinGW and Cygwin. XALANC-799 and XALANC-800 are prerequisites for MinGW. Cygwin might require an update to FindXercesC.cmake in CMake (it uses a slightly different library naming convention). So Cygwin support might require deferring. MSVC can use vcpkg to obtain the build dependencies. Note Xerces-C++ AppVeyor support can be used as the basis for this. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Created] (XALANC-800) Add CMake feature tests to replace specific platform definitions
Roger Leigh created XALANC-800:
--
Summary: Add CMake feature tests to replace specific platform
definitions
Key: XALANC-800
URL: https://issues.apache.org/jira/browse/XALANC-800
Project: XalanC
Issue Type: Bug
Components: XalanC
Affects Versions: 1.12
Reporter: Roger Leigh
Assignee: Roger Leigh
Fix For: 1.12
Macros:
{noformat}
__HPACC_THREAD_SAFE_RB_TREE
__USE_STD_IOSTREAM
WINDOWS_THREAD_FUNCTIONS
XALAN_NEWLINE_IS_CRLF
XALAN_NO_REENTRANT_TIME_FUNCTIONS
XALAN_NON_ASCII_PLATFORM
XALAN_PLATFORM_EXPORT
XALAN_PLATFORM_IMPORT
XALAN_POSIX2_AVAILABLE
XALAN_STATIC_ASSERT
XALAN_WINDOWS
XALAN_WINDOWS_DIR_FUNCTIONS
{noformat}
The underlying problem is that these hardcoded assumptions can be broken. Case
in point, XALAN_NO_REENTRANT_TIME_FUNCTIONS is defined for GCC under MinGW...
but current MinGW actually provides localtime_t and gmtime_r, which breaks
building due to mutually incompatible function declarations. Feature tests
will remove these assumptions and make building Xalan more robust and able to
adapt to changes in platforms over time.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org
For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Created] (XALANC-799) Remove use of winres.h in XalanMsgLib.rc
Roger Leigh created XALANC-799: -- Summary: Remove use of winres.h in XalanMsgLib.rc Key: XALANC-799 URL: https://issues.apache.org/jira/browse/XALANC-799 Project: XalanC Issue Type: Bug Components: XalanC Affects Versions: 1.12 Reporter: Roger Leigh Assignee: Roger Leigh Fix For: 1.12 MinGW doesn't have winres.h so this breaks the build. XalanC.rc uses windows.h instead, and switching to this header looks like a non-breaking and safe substitute which will work with MinGW. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Resolved] (XALANC-795) CMake CTest should run all samples as well as unit tests
[ https://issues.apache.org/jira/browse/XALANC-795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Leigh resolved XALANC-795. Resolution: Fixed Followup actions: * generate output in build directory, not source directory * validate output matches expected output similar to xerces integration tests > CMake CTest should run all samples as well as unit tests > > > Key: XALANC-795 > URL: https://issues.apache.org/jira/browse/XALANC-795 > Project: XalanC > Issue Type: Bug > Components: XalanC >Reporter: Roger Leigh >Assignee: Roger Leigh >Priority: Major > Fix For: 1.12 > > > Currently, CMake configures CTest to run three unit tests only. The samples > are not run. > Improve test coverage by running all sample executables as well, with > available sample data. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Commented] (XALANC-796) Autogenerate version information in Windows resource files
[ https://issues.apache.org/jira/browse/XALANC-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17106074#comment-17106074 ] Roger Leigh commented on XALANC-796: I ran into a bug with the cmake [resource compiler utility|https://gitlab.kitware.com/cmake/cmake/-/issues/20506] which looks like a recent regression which is already fixed, but not yet in a new release. As such, defer any updates to autogenerate the version information and leave it hardcoded for 1.12. > Autogenerate version information in Windows resource files > -- > > Key: XALANC-796 > URL: https://issues.apache.org/jira/browse/XALANC-796 > Project: XalanC > Issue Type: Bug > Components: XalanC >Affects Versions: 1.11 >Reporter: Roger Leigh >Assignee: Roger Leigh >Priority: Major > Fix For: 1.13 > > > Autogenerate embedded version numbers. Since it can include headers, the > information could be sourced directly from the XalanVersion.hpp. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Updated] (XALANC-796) Autogenerate version information in Windows resource files
[ https://issues.apache.org/jira/browse/XALANC-796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Leigh updated XALANC-796: --- Fix Version/s: (was: 1.12) 1.13 > Autogenerate version information in Windows resource files > -- > > Key: XALANC-796 > URL: https://issues.apache.org/jira/browse/XALANC-796 > Project: XalanC > Issue Type: Bug > Components: XalanC >Affects Versions: 1.11 >Reporter: Roger Leigh >Assignee: Roger Leigh >Priority: Major > Fix For: 1.13 > > > Autogenerate embedded version numbers. Since it can include headers, the > information could be sourced directly from the XalanVersion.hpp. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Updated] (XALANC-796) Autogenerate version information in Windows resource files
[ https://issues.apache.org/jira/browse/XALANC-796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Leigh updated XALANC-796: --- Description: Autogenerate embedded version numbers. Since it can include headers, the information could be sourced directly from the XalanVersion.hpp. (was: To eliminate the Projects directory (no longer used for project files), the remaining two files could be moved under the src directory. Since they contain embedded version numbers, CMake could generate both from a template at configuration time.) > Autogenerate version information in Windows resource files > -- > > Key: XALANC-796 > URL: https://issues.apache.org/jira/browse/XALANC-796 > Project: XalanC > Issue Type: Bug > Components: XalanC >Affects Versions: 1.11 >Reporter: Roger Leigh >Assignee: Roger Leigh >Priority: Major > Fix For: 1.12 > > > Autogenerate embedded version numbers. Since it can include headers, the > information could be sourced directly from the XalanVersion.hpp. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Closed] (XALANC-791) Add full CMake build instructions
[ https://issues.apache.org/jira/browse/XALANC-791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Leigh closed XALANC-791. -- Resolution: Fixed New documentation includes CMake build instructions. > Add full CMake build instructions > - > > Key: XALANC-791 > URL: https://issues.apache.org/jira/browse/XALANC-791 > Project: XalanC > Issue Type: Bug > Components: XalanC >Reporter: Roger Leigh >Assignee: Roger Leigh >Priority: Major > Fix For: 1.2.x > > > Update README, build_instruct.xml, buildlibs.xml, install.xml etc. to > document how to build with CMake. Can be based upon Xerces-C build > instructions. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Updated] (XALANC-796) Autogenerate version information in Windows resource files
[ https://issues.apache.org/jira/browse/XALANC-796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Leigh updated XALANC-796: --- Summary: Autogenerate version information in Windows resource files (was: Move Windows resources to source directory and autogenerate) > Autogenerate version information in Windows resource files > -- > > Key: XALANC-796 > URL: https://issues.apache.org/jira/browse/XALANC-796 > Project: XalanC > Issue Type: Bug > Components: XalanC >Affects Versions: 1.11 >Reporter: Roger Leigh >Assignee: Roger Leigh >Priority: Major > Fix For: 1.12 > > > To eliminate the Projects directory (no longer used for project files), the > remaining two files could be moved under the src directory. Since they > contain embedded version numbers, CMake could generate both from a template > at configuration time. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Closed] (XALANC-792) Replace StyleBook documentation with a supported equivalent
[ https://issues.apache.org/jira/browse/XALANC-792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Leigh closed XALANC-792. -- Resolution: Fixed New documentation is live here: https://apache.github.io/xalan-c/ > Replace StyleBook documentation with a supported equivalent > --- > > Key: XALANC-792 > URL: https://issues.apache.org/jira/browse/XALANC-792 > Project: XalanC > Issue Type: Bug > Components: XalanC >Reporter: Roger Leigh >Assignee: Roger Leigh >Priority: Major > Fix For: 1.12 > > > The StyleBook documentation needs replacement before making a new release. > It's getting nigh on impossible to use given that it's obsolete, unsupported > and requires a JVM which can't be obtained or run on modern platforms without > considerable effort. > Now we have GitBox and GitHub support, I would suggest the lowest cost > solution would be to migrate to markdown and have it published as GitHub > pages, or even just directly browseable on GitHub. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Closed] (XALANC-798) Remove use of version.incl
[ https://issues.apache.org/jira/browse/XALANC-798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Leigh closed XALANC-798. -- Resolution: Fixed > Remove use of version.incl > -- > > Key: XALANC-798 > URL: https://issues.apache.org/jira/browse/XALANC-798 > Project: XalanC > Issue Type: Bug > Components: XalanC >Affects Versions: 1.11 >Reporter: Roger Leigh >Assignee: Roger Leigh >Priority: Major > Fix For: 1.12 > > > This was parsed by CMake via XalanDLL.cmake for strict compatibility with the > autoconf logic. Now the autoconf build is gone, the version numbers can be > moved into the toplevel CMakeLists.txt directly, and version.incl deleted. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Closed] (XALANC-797) Generate XalanVersion.hpp
[
https://issues.apache.org/jira/browse/XALANC-797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roger Leigh closed XALANC-797.
--
Resolution: Fixed
> Generate XalanVersion.hpp
> -
>
> Key: XALANC-797
> URL: https://issues.apache.org/jira/browse/XALANC-797
> Project: XalanC
> Issue Type: Bug
> Components: XalanC
>Affects Versions: 1.11
>Reporter: Roger Leigh
>Assignee: Roger Leigh
>Priority: Major
> Fix For: 1.12
>
>
> XalanVersion.hpp currently hardcodes the release version numbers. This file
> should be automatically generated so that it's kept up-to-date automatically.
> Additionally, when autogenerating the file, we can directly substitute all
> the string variants so all of the {{INVK}} macros can be deleted.
> One additional flaw is that the {{gXalan*}} variables are defined in the
> header, so will be present in all translation units and any external use of
> the header, which may lead to symbol conflicts when linking. There are
> likely few users of these. Move into a translation unit and declare
> {{extern}} to avoid potential problems.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org
For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Created] (XALANC-798) Remove use of version.incl
Roger Leigh created XALANC-798: -- Summary: Remove use of version.incl Key: XALANC-798 URL: https://issues.apache.org/jira/browse/XALANC-798 Project: XalanC Issue Type: Bug Components: XalanC Affects Versions: 1.11 Reporter: Roger Leigh Assignee: Roger Leigh Fix For: 1.12 This was parsed by CMake via XalanDLL.cmake for strict compatibility with the autoconf logic. Now the autoconf build is gone, the version numbers can be moved into the toplevel CMakeLists.txt directly, and version.incl deleted. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Created] (XALANC-797) Generate XalanVersion.hpp
Roger Leigh created XALANC-797:
--
Summary: Generate XalanVersion.hpp
Key: XALANC-797
URL: https://issues.apache.org/jira/browse/XALANC-797
Project: XalanC
Issue Type: Bug
Components: XalanC
Affects Versions: 1.11
Reporter: Roger Leigh
Assignee: Roger Leigh
Fix For: 1.12
XalanVersion.hpp currently hardcodes the release version numbers. This file
should be automatically generated so that it's kept up-to-date automatically.
Additionally, when autogenerating the file, we can directly substitute all the
string variants so all of the {{INVK}} macros can be deleted.
One additional flaw is that the {{gXalan*}} variables are defined in the
header, so will be present in all translation units and any external use of the
header, which may lead to symbol conflicts when linking. There are likely few
users of these. Move into a translation unit and declare {{extern}} to avoid
potential problems.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org
For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Created] (XALANC-796) Move Windows resources to source directory and autogenerate
Roger Leigh created XALANC-796: -- Summary: Move Windows resources to source directory and autogenerate Key: XALANC-796 URL: https://issues.apache.org/jira/browse/XALANC-796 Project: XalanC Issue Type: Bug Components: XalanC Affects Versions: 1.11 Reporter: Roger Leigh Assignee: Roger Leigh Fix For: 1.12 To eliminate the Projects directory (no longer used for project files), the remaining two files could be moved under the src directory. Since they contain embedded version numbers, CMake could generate both from a template at configuration time. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Resolved] (XALANC-790) Ensure CMake is using the library rc files for both libraries
[ https://issues.apache.org/jira/browse/XALANC-790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Leigh resolved XALANC-790. Resolution: Fixed > Ensure CMake is using the library rc files for both libraries > - > > Key: XALANC-790 > URL: https://issues.apache.org/jira/browse/XALANC-790 > Project: XalanC > Issue Type: Bug > Components: XalanC >Reporter: Roger Leigh >Assignee: Roger Leigh >Priority: Major > Fix For: 1.12 > > Time Spent: 20m > Remaining Estimate: 0h > > This is a bit inconsistent in the existing project/solution files, but CMake > can be configured to use the correct rc file for Xerces and XercesMsg. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Resolved] (XALANC-793) CMake build should install pkg-config file
[ https://issues.apache.org/jira/browse/XALANC-793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Leigh resolved XALANC-793. Resolution: Implemented Logic is implemented and functional. > CMake build should install pkg-config file > -- > > Key: XALANC-793 > URL: https://issues.apache.org/jira/browse/XALANC-793 > Project: XalanC > Issue Type: Bug > Components: XalanC >Reporter: Roger Leigh >Assignee: Roger Leigh >Priority: Major > Fix For: 1.12 > > > To duplicate the autoconf build behaviour, ensure the pkg-config file is > installed. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Resolved] (XALANC-789) Check CMake build correctly versions libraries on all platforms
[ https://issues.apache.org/jira/browse/XALANC-789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Leigh resolved XALANC-789. Resolution: Not A Problem Checked on Windows, MacOS X and Linux/FreeBSD. The versioning is correct in all cases. > Check CMake build correctly versions libraries on all platforms > --- > > Key: XALANC-789 > URL: https://issues.apache.org/jira/browse/XALANC-789 > Project: XalanC > Issue Type: Bug > Components: XalanC >Reporter: Roger Leigh >Assignee: Roger Leigh >Priority: Major > Fix For: 1.12 > > > Similar to work done recently for Xerces-C, ensure the versioning logic is > working correctly on supported platforms. > If strict compatibility with the hardcoded platform-specific library naming > in Makefile.incl is dropped, it would be possible to use CMake's SONAME > versioning properly and have it do the right thing by default on all > platforms. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Commented] (XALANC-785) XalanTransformer::Transform gives malloc error after building with libc++ on OSX 10.9
[ https://issues.apache.org/jira/browse/XALANC-785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17081541#comment-17081541 ] Roger Leigh commented on XALANC-785: Are you using 1.11 stock release, or patched? If you use the patched version from MacOS homebrew, does this also show the same issue? Please try applying the two patches linked [here](https://github.com/Homebrew/homebrew-core/blob/3e7ab60725faf9f6d1bccf6657d2ba502ea48320/Formula/xalan-c.rb). If this fixes the problem, it will be fixed in the upcoming 1.12 release. > XalanTransformer::Transform gives malloc error after building with libc++ on > OSX 10.9 > - > > Key: XALANC-785 > URL: https://issues.apache.org/jira/browse/XALANC-785 > Project: XalanC > Issue Type: Bug > Components: XalanC >Affects Versions: 1.11 > Environment: Build and Execution: OS X 10.14, 10.12, 10.9 > XCode version: 9.4, 8.3, 6.2 >Reporter: Pratik Singh Bisht >Assignee: Gary D. Gregory >Priority: Blocker > > We are using Xalan and Xerces C++ libraries for XML transformation and > parsing. > It had been working flawlessly till our 10.8 OS X support (with libstdc++ as > standard library). Recently we upgraded our project to support target OSX > 10.9 with base SDK 10.12 and added C++11 support as well building it on OSX > 10.14 with XCode 9.4. > Since in XCode, C++11 support is only available with libc++, we had to > rebuilt all the dependencies with C++11 to ensure ABI compatibility. But the > Xalan binaries (built through runconfigure script) are crashing after > rebuilding with libc++ and C++11 support flags. > The location is always Xalan Transformer::transform() API. I tried debugging > with help of malloc guards and stepped through inside the Xalan code as well > but the memory for which crash occurs is internally allocated in Xalan code > and has no relation to input parameters. > Below is the call stack: > #00x7fff879bd866 in __pthread_kill () > #10x7fff8cc3535c in pthread_kill () > #20x7fff8e63fb1a in abort () > #30x7fff91e4d690 in szone_error () > #40x7fff91e4ed95 in small_free_list_remove_ptr () > #50x7fff91e4b443 in szone_free_definite_size () > #60x0001011bd487 in xercesc_3_1::MemoryManagerImpl::deallocate(void*) > () > #70x000100d7e539 in > xalanc_1_11::ArenaAllocator xalanc_1_11::ArenaBlock > >::reset() () > #80x000100d82062 in xalanc_1_11::XalanDOMStringPool::clear() () > #90x000100e8088f in > xalanc_1_11::StylesheetConstructionContextDefault::reset() () > #10 0x000100e80329 in > xalanc_1_11::StylesheetConstructionContextDefault::~StylesheetConstructionContextDefault() > () > #11 0x000100ed0559 in > xalanc_1_11::XalanTransformer::doTransform(xalanc_1_11::XalanParsedSource > const&, xalanc_1_11::XalanCompiledStylesheet const*, > xalanc_1_11::XSLTInputSource const*, xalanc_1_11::XSLTResultTarget const&) () > #12 0x000100ece2ad in > xalanc_1_11::XalanTransformer::transform(xalanc_1_11::XSLTInputSource const&, > xalanc_1_11::XSLTInputSource const&, xalanc_1_11::XSLTResultTarget const&) () > And error: > malloc: *** error for object 0x103831c08: incorrect checksum for freed object > - object was probably modified after being freed. > *** set a breakpoint in malloc_error_break to debug > NOTE: Surprisingly the code executes on OSX 10.14 without any issue -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Comment Edited] (XALANC-785) XalanTransformer::Transform gives malloc error after building with libc++ on OSX 10.9
[ https://issues.apache.org/jira/browse/XALANC-785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17081541#comment-17081541 ] Roger Leigh edited comment on XALANC-785 at 4/11/20, 8:06 PM: -- Are you using 1.11 stock release, or patched? If you use the patched version from MacOS homebrew, does this also show the same issue? Please try applying the two patches linked [here|https://github.com/Homebrew/homebrew-core/blob/3e7ab60725faf9f6d1bccf6657d2ba502ea48320/Formula/xalan-c.rb]. If this fixes the problem, it will be fixed in the upcoming 1.12 release. was (Author: rleigh): Are you using 1.11 stock release, or patched? If you use the patched version from MacOS homebrew, does this also show the same issue? Please try applying the two patches linked [here](https://github.com/Homebrew/homebrew-core/blob/3e7ab60725faf9f6d1bccf6657d2ba502ea48320/Formula/xalan-c.rb). If this fixes the problem, it will be fixed in the upcoming 1.12 release. > XalanTransformer::Transform gives malloc error after building with libc++ on > OSX 10.9 > - > > Key: XALANC-785 > URL: https://issues.apache.org/jira/browse/XALANC-785 > Project: XalanC > Issue Type: Bug > Components: XalanC >Affects Versions: 1.11 > Environment: Build and Execution: OS X 10.14, 10.12, 10.9 > XCode version: 9.4, 8.3, 6.2 >Reporter: Pratik Singh Bisht >Assignee: Gary D. Gregory >Priority: Blocker > > We are using Xalan and Xerces C++ libraries for XML transformation and > parsing. > It had been working flawlessly till our 10.8 OS X support (with libstdc++ as > standard library). Recently we upgraded our project to support target OSX > 10.9 with base SDK 10.12 and added C++11 support as well building it on OSX > 10.14 with XCode 9.4. > Since in XCode, C++11 support is only available with libc++, we had to > rebuilt all the dependencies with C++11 to ensure ABI compatibility. But the > Xalan binaries (built through runconfigure script) are crashing after > rebuilding with libc++ and C++11 support flags. > The location is always Xalan Transformer::transform() API. I tried debugging > with help of malloc guards and stepped through inside the Xalan code as well > but the memory for which crash occurs is internally allocated in Xalan code > and has no relation to input parameters. > Below is the call stack: > #00x7fff879bd866 in __pthread_kill () > #10x7fff8cc3535c in pthread_kill () > #20x7fff8e63fb1a in abort () > #30x7fff91e4d690 in szone_error () > #40x7fff91e4ed95 in small_free_list_remove_ptr () > #50x7fff91e4b443 in szone_free_definite_size () > #60x0001011bd487 in xercesc_3_1::MemoryManagerImpl::deallocate(void*) > () > #70x000100d7e539 in > xalanc_1_11::ArenaAllocator xalanc_1_11::ArenaBlock > >::reset() () > #80x000100d82062 in xalanc_1_11::XalanDOMStringPool::clear() () > #90x000100e8088f in > xalanc_1_11::StylesheetConstructionContextDefault::reset() () > #10 0x000100e80329 in > xalanc_1_11::StylesheetConstructionContextDefault::~StylesheetConstructionContextDefault() > () > #11 0x000100ed0559 in > xalanc_1_11::XalanTransformer::doTransform(xalanc_1_11::XalanParsedSource > const&, xalanc_1_11::XalanCompiledStylesheet const*, > xalanc_1_11::XSLTInputSource const*, xalanc_1_11::XSLTResultTarget const&) () > #12 0x000100ece2ad in > xalanc_1_11::XalanTransformer::transform(xalanc_1_11::XSLTInputSource const&, > xalanc_1_11::XSLTInputSource const&, xalanc_1_11::XSLTResultTarget const&) () > And error: > malloc: *** error for object 0x103831c08: incorrect checksum for freed object > - object was probably modified after being freed. > *** set a breakpoint in malloc_error_break to debug > NOTE: Surprisingly the code executes on OSX 10.14 without any issue -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Resolved] (XALANC-794) XalanTransform does not transform anything
[ https://issues.apache.org/jira/browse/XALANC-794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Leigh resolved XALANC-794. Resolution: Fixed > XalanTransform does not transform anything > -- > > Key: XALANC-794 > URL: https://issues.apache.org/jira/browse/XALANC-794 > Project: XalanC > Issue Type: Bug > Components: XalanC >Affects Versions: 1.11 >Reporter: Roger Leigh >Assignee: Roger Leigh >Priority: Major > Fix For: 1.12 > > Time Spent: 20m > Remaining Estimate: 0h > > XalanTransform has a UnaryFunction function parameter, but doesn't use it > with std::transform, so the transform is more of a copy than a transform... > Make it use the function parameter. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Resolved] (XALANC-788) Drop Autoconf build
[ 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: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Created] (XALANC-795) CMake CTest should run all samples as well as unit tests
Roger Leigh created XALANC-795: -- Summary: CMake CTest should run all samples as well as unit tests Key: XALANC-795 URL: https://issues.apache.org/jira/browse/XALANC-795 Project: XalanC Issue Type: Bug Components: XalanC Reporter: Roger Leigh Assignee: Roger Leigh Fix For: 1.12 Currently, CMake configures CTest to run three unit tests only. The samples are not run. Improve test coverage by running all sample executables as well, with available sample data. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Created] (XALANC-794) XalanTransform does not transform anything
Roger Leigh created XALANC-794: -- Summary: XalanTransform does not transform anything Key: XALANC-794 URL: https://issues.apache.org/jira/browse/XALANC-794 Project: XalanC Issue Type: Bug Components: XalanC Affects Versions: 1.11 Reporter: Roger Leigh Assignee: Roger Leigh Fix For: 1.12 XalanTransform has a UnaryFunction function parameter, but doesn't use it with std::transform, so the transform is more of a copy than a transform... Make it use the function parameter. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Resolved] (XALANC-787) Drop MacOS and Windows project files
[ https://issues.apache.org/jira/browse/XALANC-787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Leigh resolved XALANC-787. Resolution: Fixed > Drop MacOS and Windows project files > > > Key: XALANC-787 > URL: https://issues.apache.org/jira/browse/XALANC-787 > Project: XalanC > Issue Type: Bug > Components: XalanC >Reporter: Roger Leigh >Assignee: Roger Leigh >Priority: Major > Fix For: 1.12 > > Time Spent: 20m > Remaining Estimate: 0h > > With the addition of the CMake build, the IDE version-specific solution and > project files are no longer required. The CMake tool can generate > configurations for all supported Visual Studio versions. The last supported > version was VC11 (VS2012), so right now these project files are missing > support for VS 2013, 2015, 2017 and 2019, i.e. all the most recent ones. > Rather than manually copying and maintaining project files which are > impossible to test, the CMake build should replace these entirely. This was > the primary reason for adding it. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Assigned] (XALANC-793) CMake build should install pkg-config file
[ https://issues.apache.org/jira/browse/XALANC-793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Leigh reassigned XALANC-793: -- Component/s: XalanC Fix Version/s: 1.12 Assignee: Roger Leigh (was: Gary D. Gregory) Description: To duplicate the autoconf build behaviour, ensure the pkg-config file is installed. Due Date: 23/Apr/20 > CMake build should install pkg-config file > -- > > Key: XALANC-793 > URL: https://issues.apache.org/jira/browse/XALANC-793 > Project: XalanC > Issue Type: Bug > Components: XalanC >Reporter: Roger Leigh >Assignee: Roger Leigh >Priority: Major > Fix For: 1.12 > > > To duplicate the autoconf build behaviour, ensure the pkg-config file is > installed. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Created] (XALANC-793) CMake build should install pkg-config file
Roger Leigh created XALANC-793: -- Summary: CMake build should install pkg-config file Key: XALANC-793 URL: https://issues.apache.org/jira/browse/XALANC-793 Project: XalanC Issue Type: Bug Reporter: Roger Leigh Assignee: Gary D. Gregory -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Created] (XALANC-792) Replace StyleBook documentation with a supported equivalent
Roger Leigh created XALANC-792: -- Summary: Replace StyleBook documentation with a supported equivalent Key: XALANC-792 URL: https://issues.apache.org/jira/browse/XALANC-792 Project: XalanC Issue Type: Bug Components: XalanC Reporter: Roger Leigh Assignee: Roger Leigh Fix For: 1.12 The StyleBook documentation needs replacement before making a new release. It's getting nigh on impossible to use given that it's obsolete, unsupported and requires a JVM which can't be obtained or run on modern platforms without considerable effort. Now we have GitBox and GitHub support, I would suggest the lowest cost solution would be to migrate to markdown and have it published as GitHub pages, or even just directly browseable on GitHub. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Created] (XALANC-791) Add full CMake build instructions
Roger Leigh created XALANC-791: -- Summary: Add full CMake build instructions Key: XALANC-791 URL: https://issues.apache.org/jira/browse/XALANC-791 Project: XalanC Issue Type: Bug Components: XalanC Reporter: Roger Leigh Assignee: Roger Leigh Fix For: 1.2.x Update README, build_instruct.xml, buildlibs.xml, install.xml etc. to document how to build with CMake. Can be based upon Xerces-C build instructions. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Created] (XALANC-790) Ensure CMake is using the library rc files for both libraries
Roger Leigh created XALANC-790: -- Summary: Ensure CMake is using the library rc files for both libraries Key: XALANC-790 URL: https://issues.apache.org/jira/browse/XALANC-790 Project: XalanC Issue Type: Bug Components: XalanC Reporter: Roger Leigh Assignee: Roger Leigh Fix For: 1.12 This is a bit inconsistent in the existing project/solution files, but CMake can be configured to use the correct rc file for Xerces and XercesMsg. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Created] (XALANC-789) Check CMake build correctly versions libraries on all platforms
Roger Leigh created XALANC-789: -- Summary: Check CMake build correctly versions libraries on all platforms Key: XALANC-789 URL: https://issues.apache.org/jira/browse/XALANC-789 Project: XalanC Issue Type: Bug Components: XalanC Reporter: Roger Leigh Assignee: Roger Leigh Fix For: 1.12 Similar to work done recently for Xerces-C, ensure the versioning logic is working correctly on supported platforms. If strict compatibility with the hardcoded platform-specific library naming in Makefile.incl is dropped, it would be possible to use CMake's SONAME versioning properly and have it do the right thing by default on all platforms. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Created] (XALANC-788) Drop Autoconf build
Roger Leigh created XALANC-788: -- Summary: 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 Fix For: 1.12 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: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Created] (XALANC-787) Drop MacOS and Windows project files
Roger Leigh created XALANC-787: -- Summary: Drop MacOS and Windows project files Key: XALANC-787 URL: https://issues.apache.org/jira/browse/XALANC-787 Project: XalanC Issue Type: Bug Components: XalanC Reporter: Roger Leigh Assignee: Roger Leigh Fix For: 1.12 With the addition of the CMake build, the IDE version-specific solution and project files are no longer required. The CMake tool can generate configurations for all supported Visual Studio versions. The last supported version was VC11 (VS2012), so right now these project files are missing support for VS 2013, 2015, 2017 and 2019, i.e. all the most recent ones. Rather than manually copying and maintaining project files which are impossible to test, the CMake build should replace these entirely. This was the primary reason for adding it. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Commented] (XALANC-781) Compilation fails with ICU
[
https://issues.apache.org/jira/browse/XALANC-781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16848515#comment-16848515
]
Roger Leigh commented on XALANC-781:
I have fixed up all the ICU compile failures on the git master branch. If you
try it out with the new CMake build, it should auto-detect ICU, or you can
manually select with {{-Dtranscoder=icu}}. However, note that while this fixes
up the ICU bridge, the ICU message loader is still broken and will require
additional work to fix up. That can be enabled with {{-Dmsgloader=icu-broken}}.
> Compilation fails with ICU
> --
>
> Key: XALANC-781
> URL: https://issues.apache.org/jira/browse/XALANC-781
> Project: XalanC
> Issue Type: Bug
> Components: XalanC
>Affects Versions: 1.11
> Environment: GNU/Linux Kernel 3.0.13 x86_64
> gcc (GCC) 8.0.1 20180307 (experimental)
> Compilation with -std=gnu++17
>Reporter: Laurent Stacul
>Assignee: Steven J. Hathaway
>Priority: Major
> Labels: easyfix
> Attachments: xalanc_fix_compilation_with_icu.patch
>
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> There are several errors when compiling xalanc with ICU (XALAN_USE_ICU) in
> the folder ICUBridge. In several places, the namespace of ICU
> classes/functions is not given leading to the following types of error:
> {code:java}
> xalan-c-1.11/c/src/xalanc/ICUBridge/ICUFormatNumberFunctor.hpp:227:12: error:
> 'DecimalFormat' does not name a type;{code}
> I provide a patch for such issues.
> Stac
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org
For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Commented] (XALANC-775) Xalan is incompatible with C++17
[ https://issues.apache.org/jira/browse/XALANC-775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665264#comment-16665264 ] Roger Leigh commented on XALANC-775: I have decoupled the unary_/binary_function patches from the rest of the patchset and attached them here so they can be applied standalone. This permits compiling with -std:c++17 with VS2017. > Xalan is incompatible with C++17 > > > Key: XALANC-775 > URL: https://issues.apache.org/jira/browse/XALANC-775 > Project: XalanC > Issue Type: Bug > Components: XalanC >Affects Versions: 1.11 >Reporter: Hermann Walth >Assignee: Steven J. Hathaway >Priority: Major > Attachments: > 0001-Remove-usage-of-std-unary_function-and-std-binary_fu.patch, > 0002-Remove-unused-compatibility-macro-XALAN_SGI_BASED_ST.patch > > > In C++ 17, the template classes std::unary_function and std::binary_function > have been removed. Since Xalan derives multiple classes from these classes, > using it with the flag -std=c++17 fails. > This does not just affect compilation of Xalan itself, but any project that > includes Xalan's header files, as including those files causes errors about > the nonexisting symbol std::unary_function. > I'm currently working on a project that uses Xalan, and this issue is > stopping us from moving our codebase to C++17. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Updated] (XALANC-775) Xalan is incompatible with C++17
[ https://issues.apache.org/jira/browse/XALANC-775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Leigh updated XALANC-775: --- Attachment: 0001-Remove-usage-of-std-unary_function-and-std-binary_fu.patch > Xalan is incompatible with C++17 > > > Key: XALANC-775 > URL: https://issues.apache.org/jira/browse/XALANC-775 > Project: XalanC > Issue Type: Bug > Components: XalanC >Affects Versions: 1.11 >Reporter: Hermann Walth >Assignee: Steven J. Hathaway >Priority: Major > Attachments: > 0001-Remove-usage-of-std-unary_function-and-std-binary_fu.patch, > 0002-Remove-unused-compatibility-macro-XALAN_SGI_BASED_ST.patch > > > In C++ 17, the template classes std::unary_function and std::binary_function > have been removed. Since Xalan derives multiple classes from these classes, > using it with the flag -std=c++17 fails. > This does not just affect compilation of Xalan itself, but any project that > includes Xalan's header files, as including those files causes errors about > the nonexisting symbol std::unary_function. > I'm currently working on a project that uses Xalan, and this issue is > stopping us from moving our codebase to C++17. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Updated] (XALANC-775) Xalan is incompatible with C++17
[ https://issues.apache.org/jira/browse/XALANC-775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Leigh updated XALANC-775: --- Attachment: 0002-Remove-unused-compatibility-macro-XALAN_SGI_BASED_ST.patch > Xalan is incompatible with C++17 > > > Key: XALANC-775 > URL: https://issues.apache.org/jira/browse/XALANC-775 > Project: XalanC > Issue Type: Bug > Components: XalanC >Affects Versions: 1.11 >Reporter: Hermann Walth >Assignee: Steven J. Hathaway >Priority: Major > Attachments: > 0001-Remove-usage-of-std-unary_function-and-std-binary_fu.patch, > 0002-Remove-unused-compatibility-macro-XALAN_SGI_BASED_ST.patch > > > In C++ 17, the template classes std::unary_function and std::binary_function > have been removed. Since Xalan derives multiple classes from these classes, > using it with the flag -std=c++17 fails. > This does not just affect compilation of Xalan itself, but any project that > includes Xalan's header files, as including those files causes errors about > the nonexisting symbol std::unary_function. > I'm currently working on a project that uses Xalan, and this issue is > stopping us from moving our codebase to C++17. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Commented] (XALANC-775) Xalan is incompatible with C++17
[ https://issues.apache.org/jira/browse/XALANC-775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16509938#comment-16509938 ] Roger Leigh commented on XALANC-775: Please see https://github.com/rleigh-codelibre/xalan-c/tree/remove-unary-binary-function for a work in progress fix. I don't have any access to xalan-c's version control to commit it, and I don't have the time available to finish it off. But feel free to pick it up. > Xalan is incompatible with C++17 > > > Key: XALANC-775 > URL: https://issues.apache.org/jira/browse/XALANC-775 > Project: XalanC > Issue Type: Bug > Components: XalanC >Affects Versions: 1.11 >Reporter: Hermann Walth >Assignee: Steven J. Hathaway >Priority: Major > > In C++ 17, the template classes std::unary_function and std::binary_function > have been removed. Since Xalan derives multiple classes from these classes, > using it with the flag -std=c++17 fails. > This does not just affect compilation of Xalan itself, but any project that > includes Xalan's header files, as including those files causes errors about > the nonexisting symbol std::unary_function. > I'm currently working on a project that uses Xalan, and this issue is > stopping us from moving our codebase to C++17. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Comment Edited] (XALANC-782) Mismatched types when compiling Xalan on Windows with native wchar_t
[
https://issues.apache.org/jira/browse/XALANC-782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16500286#comment-16500286
]
Roger Leigh edited comment on XALANC-782 at 6/4/18 2:25 PM:
Xerces-C++ 3.x uses wchar_t by default on Windows, and 3.2.1 can optionally use
char16_t with C++11. Xalan 1.11 works fine with 3.x and wchar_t. I would
update it to support char16_t, but I have yet to hear back from any of the
maintainers regarding joining the project.
was (Author: rleigh):
Xerces-C++ 3.x uses wchar_t by default, and 3.2.1 can optionally use char16_t
with C++11. Xalan 1.11 works fine with 3.x and wchar_t. I would update it to
support char16_t, but I have yet to hear back from any of the maintainers
regarding joining the project.
> Mismatched types when compiling Xalan on Windows with native wchar_t
>
>
> Key: XALANC-782
> URL: https://issues.apache.org/jira/browse/XALANC-782
> Project: XalanC
> Issue Type: Bug
>Affects Versions: 1.10
>Reporter: Hermann Walth
>Assignee: Steven J. Hathaway
>Priority: Major
>
> I have the following scenario:
> I built Xerces C++ 2.7 successfully with the flag /Zc:wchar_t set, using
> Visual Studio 2017.
> If I now try to build Xalan C++ 1.10 with Visual Studio 2017 (by opening and
> retargeting the provided solution VC7.1/Xalan.sln), I get error messages like
> the following:
> {code:java}
> C2664: 'void XalanFileOutputStream::write(const char *,unsigned int)': cannot
> convert argument 1 from 'XMLCh [512]' to 'const UTF16Ch *'
> (xml-xalan\c\src\xalanc\utils\msgcreator\icureshandler.cpp:89){code}
> The problem here is that XalanFileOutputStream::write expects to be called
> with an array of XMLCh (which Xerces defines to be native wchar_t), but is
> actually called with an array of UTF16Ch (which is a type alias of unsigned
> short). Hence, there is a type error.
> I also get the error
> {code:java}
> C1083: Cannot open include file: 'LocalMsgIndex.hpp': No such file or
> directory (xml-xalan\c\src\xalanc\xslt\elemtemplateelement.hpp:45)
> {code}
> Is there a way to successfully compile Xalan 1.10 even with the flag
> /Zc:wchar_t set? I don't want to set this flag because it causes other
> problems in my codebase, and I updating to Xalan 1.11 and to Xerces 3.x would
> take some effort because both libraries changed their API without a clear
> migration guide.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org
For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Commented] (XALANC-782) Mismatched types when compiling Xalan on Windows with native wchar_t
[
https://issues.apache.org/jira/browse/XALANC-782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16500286#comment-16500286
]
Roger Leigh commented on XALANC-782:
Xerces-C++ 3.x uses wchar_t by default, and 3.2.1 can optionally use char16_t
with C++11. Xalan 1.11 works fine with 3.x and wchar_t. I would update it to
support char16_t, but I have yet to hear back from any of the maintainers
regarding joining the project.
> Mismatched types when compiling Xalan on Windows with native wchar_t
>
>
> Key: XALANC-782
> URL: https://issues.apache.org/jira/browse/XALANC-782
> Project: XalanC
> Issue Type: Bug
>Affects Versions: 1.10
>Reporter: Hermann Walth
>Assignee: Steven J. Hathaway
>Priority: Major
>
> I have the following scenario:
> I built Xerces C++ 2.7 successfully with the flag /Zc:wchar_t set, using
> Visual Studio 2017.
> If I now try to build Xalan C++ 1.10 with Visual Studio 2017 (by opening and
> retargeting the provided solution VC7.1/Xalan.sln), I get error messages like
> the following:
> {code:java}
> C2664: 'void XalanFileOutputStream::write(const char *,unsigned int)': cannot
> convert argument 1 from 'XMLCh [512]' to 'const UTF16Ch *'
> (xml-xalan\c\src\xalanc\utils\msgcreator\icureshandler.cpp:89){code}
> The problem here is that XalanFileOutputStream::write expects to be called
> with an array of XMLCh (which Xerces defines to be native wchar_t), but is
> actually called with an array of UTF16Ch (which is a type alias of unsigned
> short). Hence, there is a type error.
> I also get the error
> {code:java}
> C1083: Cannot open include file: 'LocalMsgIndex.hpp': No such file or
> directory (xml-xalan\c\src\xalanc\xslt\elemtemplateelement.hpp:45)
> {code}
> Is there a way to successfully compile Xalan 1.10 even with the flag
> /Zc:wchar_t set? I don't want to set this flag because it causes other
> problems in my codebase, and I updating to Xalan 1.11 and to Xerces 3.x would
> take some effort because both libraries changed their API without a clear
> migration guide.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org
For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Updated] (XALANC-780) Use xalanc namespace unconditionally
[ https://issues.apache.org/jira/browse/XALANC-780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Leigh updated XALANC-780: --- Flags: Patch > Use xalanc namespace unconditionally > > > Key: XALANC-780 > URL: https://issues.apache.org/jira/browse/XALANC-780 > Project: XalanC > Issue Type: Improvement > Components: XalanC >Affects Versions: 1.11 >Reporter: Roger Leigh >Assignee: Steven J. Hathaway >Priority: Major > Attachments: 0001-Remove-XALAN_CPP_NAMESPACE_BEGIN-and-_END.patch, > 0002-Drop-use-of-XALAN_CPP_NAMESPACE_USE.patch, > 0003-Remove-XALAN_USING_XALAN_CLASS-and-_STRUCT.patch, > 0004-Remove-XALAN_USING_XALAN-macro.patch, > 0005-Remove-XALAN_DECLARE_CLASS-and-_STRUCT-macros.patch, > 0006-Remove-XALAN_USING_STD-macro.patch, 0007-Remove-XALAN_USING-macro.patch, > 0008-Remove-XALAN_STD_QUALIFIER.patch, > 0009-Remove-XALAN_NO_STD_NAMESPACE-and-workarounds.patch, > 0010-Remove-XALAN_HAS_CPP_NAMESPACE-and-workarounds.patch > > > Related to XALANC-779. > > All currently supported platforms can cope with namespaces. This patchset > removes all the special case workarounds and macros used to handle > non-namespace-capable compilers. The aim being to simplify the code for > ongoing maintenance and drop unnecessary logic from the platform-specific > headers (with the intention being to replace them entirely by feature tests). > But there's little point adding feature tests for features which have been > supported for decades; we may as well drop the special-casing at this point. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Updated] (XALANC-779) Use xercesc namespace unconditionally
[ https://issues.apache.org/jira/browse/XALANC-779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Leigh updated XALANC-779: --- Flags: Patch > Use xercesc namespace unconditionally > - > > Key: XALANC-779 > URL: https://issues.apache.org/jira/browse/XALANC-779 > Project: XalanC > Issue Type: Improvement > Components: XalanC >Reporter: Roger Leigh >Assignee: Steven J. Hathaway >Priority: Major > Attachments: 0001-Use-xercesc-namespace-unconditionally.patch, > 0002-Remove-XALAN_USING_XERCES-macro.patch, > 0003-Remove-XALAN_DECLARE_XERCES_CLASS-macro.patch, > 0004-Remove-XALAN_DECLARE_XERCES_STRUCT-macro.patch, > 0005-Remove-XERCES_HAS_CPP_NAMESPACE-check.patch, > 0006-Drop-use-of-XERCES_CPP_NAMESPACE_USE.patch, > 0007-Tidy-Xerces-namespace-usage.patch > > > There are no current compilers which lack namespace support, and all current > xerces-c builds are using namespaces by default, making this macro redundant > and overly complex. > > This should not have any portability or compatibility concerns given the > ubiquity of namespace support on contemporary systems. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Updated] (XALANC-779) Use xercesc namespace unconditionally
[ https://issues.apache.org/jira/browse/XALANC-779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Leigh updated XALANC-779: --- Attachment: 0007-Tidy-Xerces-namespace-usage.patch > Use xercesc namespace unconditionally > - > > Key: XALANC-779 > URL: https://issues.apache.org/jira/browse/XALANC-779 > Project: XalanC > Issue Type: Improvement > Components: XalanC >Reporter: Roger Leigh >Assignee: Steven J. Hathaway >Priority: Major > Attachments: 0001-Use-xercesc-namespace-unconditionally.patch, > 0002-Remove-XALAN_USING_XERCES-macro.patch, > 0003-Remove-XALAN_DECLARE_XERCES_CLASS-macro.patch, > 0004-Remove-XALAN_DECLARE_XERCES_STRUCT-macro.patch, > 0005-Remove-XERCES_HAS_CPP_NAMESPACE-check.patch, > 0006-Drop-use-of-XERCES_CPP_NAMESPACE_USE.patch, > 0007-Tidy-Xerces-namespace-usage.patch > > > There are no current compilers which lack namespace support, and all current > xerces-c builds are using namespaces by default, making this macro redundant > and overly complex. > > This should not have any portability or compatibility concerns given the > ubiquity of namespace support on contemporary systems. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Commented] (XALANC-779) Use xercesc namespace unconditionally
[ https://issues.apache.org/jira/browse/XALANC-779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16377669#comment-16377669 ] Roger Leigh commented on XALANC-779: Note this is a companion to the changes in https://issues.apache.org/jira/browse/XERCESC-2138 which drops the use of these macros in Xerces-C++ by dropping compatibility workarounds for pre-C++98 compilers two decades back. > Use xercesc namespace unconditionally > - > > Key: XALANC-779 > URL: https://issues.apache.org/jira/browse/XALANC-779 > Project: XalanC > Issue Type: Improvement > Components: XalanC >Reporter: Roger Leigh >Assignee: Steven J. Hathaway >Priority: Major > Attachments: 0001-Use-xercesc-namespace-unconditionally.patch, > 0002-Remove-XALAN_USING_XERCES-macro.patch, > 0003-Remove-XALAN_DECLARE_XERCES_CLASS-macro.patch, > 0004-Remove-XALAN_DECLARE_XERCES_STRUCT-macro.patch, > 0005-Remove-XERCES_HAS_CPP_NAMESPACE-check.patch, > 0006-Drop-use-of-XERCES_CPP_NAMESPACE_USE.patch > > > There are no current compilers which lack namespace support, and all current > xerces-c builds are using namespaces by default, making this macro redundant > and overly complex. > > This should not have any portability or compatibility concerns given the > ubiquity of namespace support on contemporary systems. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Created] (XALANC-779) Use xercesc namespace unconditionally
Roger Leigh created XALANC-779: -- Summary: Use xercesc namespace unconditionally Key: XALANC-779 URL: https://issues.apache.org/jira/browse/XALANC-779 Project: XalanC Issue Type: Improvement Components: XalanC Reporter: Roger Leigh Assignee: Steven J. Hathaway Attachments: 0001-Use-xercesc-namespace-unconditionally.patch There are no current compilers which lack namespace support, and all current xerces-c builds are using namespaces by default, making this macro redundant and overly complex. This should not have any portability or compatibility concerns given the ubiquity of namespace support on contemporary systems. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Created] (XALANC-776) Add CMake build system
Roger Leigh created XALANC-776: -- Summary: Add CMake build system Key: XALANC-776 URL: https://issues.apache.org/jira/browse/XALANC-776 Project: XalanC Issue Type: Improvement Components: XalanC Reporter: Roger Leigh Assignee: Steven J. Hathaway Attachments: 0001-Add-CMake-build-system.patch h4. Introduction The attached patch implements a CMake build for Xalan-C++. I have spent significant effort performing a "comprehensive" conversion of the existing GNU autotools and MSVC project file logic to a unified CMake build which supports all platforms with a single set of build files, as well as testing it on several platforms. The existing GNU autotools build and MSVC project builds will continue to function and are unaffected by this addition. This is a companion to https://issues.apache.org/jira/browse/XERCESC-2077 which was merged last year and included in Xerces-C++ 3.2.0. I mentioned this work on the list last year in https://marc.info/?l=xalan-dev=149748238016328=2 h4. Background CMake is a meta-build system which generates the build files for a specified build system, such as make, Visual Studio msbuild, nmake, ninja or a number of other build tools and IDEs. This allows Xalan-C++ to be built on any supported platform with the native tools for that platform. The reason why I originally needed this was due to the large maintenance burden of patching the provided Visual Studio project files, both for fixing bugs in those files and in being able to support versions of Visual Studio which aren't yet supported by the provided project files or for unsupported configurations e.g. Clang/C2, other platforms etc. The lack of an install target also meant that to integrate this with a larger build required manually copying bits out of the build tree. The cost of debugging and patching the existing project files for use in our CI builds was getting too great--maintaining and using this CMake build out of tree will be cheaper and more robust. I thought it might benefit others to have this merged upstream so that it would be available to the benefit of all. I have done a direct conversion of the existing autoconf build logic. The automake Makefile.am logic is directly represented in the corresponding CMakeLists.txt files. Unfortunately, and unlike for Xerces, the Xalan Autoconf build is in a very bad state, and it's become increasingly unusable over time. It has these major problems: * No feature tests. Platform-specific behaviour is hardcoded in "Include/XXXDefinitions.hpp" files which is inflexible and not future-proof as platforms evolve. Autoconf feature tests could be used like in Xerces-C++ * No Autoconf enable/with options. Configuration is with a hacky and nonportable "runConfigure" script which works around the lack of options. * MinGW64 is broken right now because of a lack of feature test for gmtime_r / localtime_r, for example. The static platform configuration says it doesn't have these functions, but it does and the build breaks because Xalan unnecessarily redefines them. The patch included here can't solve all these problems. But right now I'm finding it extremely hard to build and install Xalan on a range of platforms, and the amount of effort required to patch all of the Project/Solution files, Autoconf/Automake files and platform-specific headers is untenable. This CMake build will work on every platform. Some feature tests do require adding to the CMake build, replacing the Platform-specific headers, but I've not done that in this inital patch, which has a smaller scope of working with the existing headers without making any major changes. I'm prepared to do the extra work to bring this up to the equivalent state as already done for Xerces-C++ which will allow these libraries to build on all contemporary platforms. This includes fixing it to work with C++17 as reported separately by another user. Kind regards, Roger -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Commented] (XALANC-773) Build failure with Xerces-C++ 3.2.0 and VS2015
[ https://issues.apache.org/jira/browse/XALANC-773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16374369#comment-16374369 ] Roger Leigh commented on XALANC-773: Is there any chance of this patch being applied? It's been six months without a response. I've asked a few times on the list if I could join the project to fix this and other outstanding issues, but without any response. Is there anyone looking after the project who could action this? We're just about to release Xerces-C++ 3.2.1, and it would be very desirable to have Xalan-C++ work with it. Thanks, Roger > Build failure with Xerces-C++ 3.2.0 and VS2015 > -- > > Key: XALANC-773 > URL: https://issues.apache.org/jira/browse/XALANC-773 > Project: XalanC > Issue Type: Bug > Components: XalanC >Affects Versions: 1.11 > Environment: Windows with VS2015 >Reporter: Roger Leigh >Assignee: Steven J. Hathaway >Priority: Major > Labels: PlatformSupport, build > Attachments: xerces-char16_t.diff > > > Xerces-C++ 3.2.0 will allow XMLChar to be char16_t instead of wchar_t on a > compiler with C++11 support such as VS2015. The attached patch is required > to fix a few places in the Xalan-C sources where implicit wchar_t to > XalanDOMChar* conversions were used without casts. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
[jira] [Created] (XALANC-766) Documentation generation fails on MacOS X
Roger Leigh created XALANC-766:
--
Summary: Documentation generation fails on MacOS X
Key: XALANC-766
URL: https://issues.apache.org/jira/browse/XALANC-766
Project: XalanC
Issue Type: Bug
Components: XalanC
Affects Versions: 1.11
Environment: MacOS X 10.11 and earlier
Reporter: Roger Leigh
Assignee: Steven J. Hathaway
In order to get the documentation to build on MacOS X, I had to make this
adjustment:
In xdocs/sources/make-xalan.sh, replace:
{code}
"${XALANCMD}" \
{code}
with
{code}
export DYLD_FALLBACK_LIBRARY_PATH=${BUILDPATH}/c/lib:$DYLD_FALLBACK_LIBRARY_PATH
"${XALANCMD}" \
{code}
We need to know what the BUILDPATH is though. Could this script file be
renamed to make-xalan.sh.in and generated by configure with the correct build
path embedded?
While this is an issue on MacOS X, it's likely also an issue on Linux and BSD,
where LD_LIBRARY_PATH needs setting to allow the Xalan binary to run. Unless
that's already taken care of, and DYLD_LIBRARY_PATH could be set there as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org
For additional commands, e-mail: dev-h...@xalan.apache.org
