[
https://issues.apache.org/jira/browse/XERCESC-2257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17898391#comment-17898391
]
Ryan Carsten Schmidt commented on XERCESC-2257:
-----------------------------------------------
If your intent is to abandon xerces-c in the future, I think it would be
advantageous to communicate with the projects currently relying on xerces-c so
that they can take appropriate steps. The possibilities, once you stop
maintaining xerces-c, seem to be 1: the project dies, or 2: someone else takes
it over. Maybe someone else who currently uses xerces-c in their project would
prefer to become the new maintainer rather than switch to a different library.
There's nothing in [https://github.com/apache/xerces-c/blob/master/README] or
[https://xerces.apache.org/] about xerces-c being deprecated or in need of new
maintainers. Maybe a notice could be added? You're unlikely to get new
contributors if nobody knows you're looking for them.
If someone else is to take it over, you'll probably want to see many good
contributions from them before handing the project over to them, and a working
CI system is part of the portfolio of ways that you could use to verify whether
contributions are good. Future maintainers of the project would likely want a
CI system as well.
CMake is a popular build system to which many projects have switched so I
understand the motivation for adding it. But the xerces-c CMake build system
does have a rather a large amount of files and code. I can see that it would be
challenging to maintain especially if you're not familiar with CMake. And you
still have the autotools build system, and keeping multiple builds systems in
sync is an additional challenge. Personally I prefer autotools, but proponents
of CMake will point out that it works on Windows while autotools does not.
Does the maintenance problem apply only to xerces-c or also the other xerces
projects: xerces2-j, xerces-p, xml-commons?
> symbol not found in flat namespace (_xercesc_messages_3_2_dat)
> --------------------------------------------------------------
>
> Key: XERCESC-2257
> URL: https://issues.apache.org/jira/browse/XERCESC-2257
> Project: Xerces-C++
> Issue Type: Bug
> Affects Versions: 3.3.0
> Reporter: Ryan Carsten Schmidt
> Priority: Major
>
> Software linking with libxerces-c-3.3.dylib fails to work:
>
> {noformat}
> dyld[5155]: symbol not found in flat namespace (_xercesc_messages_3_2_dat)
> {noformat}
>
> This was reported to MacPorts here: [https://trac.macports.org/ticket/71304]
> This is a regression; 3.2.4 didn't have this problem.
> Surely for version 3.3.x on these lines {{3_2}} should be changed to
> {{{}3_3{}}}?
> [https://github.com/apache/xerces-c/blob/v3.3.0/src/xercesc/util/MsgLoaders/ICU/ICUMsgLoader.cpp#L54-L55]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org
For additional commands, e-mail: c-dev-h...@xerces.apache.org
