Hi Rob,
The runtime path is outside the purview of cmake. You've got to install
and then set the platform-specific path to include the lib and/or bin
directories as appropriate for the platform. We have no control over
that except for when running unit tests or samples with ctest, where we
could add in any needed directories if cmake isn't already doing it.
Once it's installed, it's entirely in the hands of the
sysadmin/developer/packager.
When it comes to the path for xerces-c, it's expected that this is
already installed and appropriately configured in the environment prior
to running CMake. On Windows, I've even seen it copy the xerces DLL
into the build tree to ensure that the executables are runnable. Maybe
we can do more, but for the CI testing I've done on Windows (with
xerces-c provided by vcpkg), it's all worked as is. If you want to
share the details of your environment and a lot of the cmake run and
build that would be useful. However, a deeper question would be to ask
if both the MsgCreator tool and XalanMsgLib library are needed at all.
There are no translations, and as far as I can see there never have been
any. It's en_US only. It wouldn't take much to persude me that the
entire lot could be stripped out given that it serves no practical
purpose. Not that I'm against translation at all, just that right now
it's unused and quite complex for zero benefit. If there are no
objections, I'd be inclined to remove it for the following release.
Kind regards,
Roger
On 29/05/2020 13:22, Rob Conde wrote:
Hey Roger,
First thanks for your work! This release is actually very timely
for me. I'm running into an issue when building against a shared
xerces library. When the msgcreator is run it crashes because it can't
find the xerces dll. I'm gonna try to handle this externally by
updating PATH/LD_LIBRARY_PATH/DYLD_LIBRARY_PATH depending on the
platform - but this might be better handled in the xalan cmake itself.
I'm not entirely sure the conventions for this scenario.
Thanks,
Rob
------------------------------------------------------------------------
*From:* Roger Leigh <rle...@codelibre.net>
*Sent:* Sunday, May 24, 2020 6:26 PM
*To:* xalan-...@apache.org <xalan-...@apache.org>;
c-users@xalan.apache.org <c-users@xalan.apache.org>
*Subject:* Xalan-C++ 1.12 release candidate 1
Dear all,
I have tagged and made a prerelease of 1.12 which can be obtained here:
https://github.com/apache/xalan-c/releases/tag/Xalan-C_1_12_0_RC1
The above link includes the release notes, links to .tar.gz and .zip
archives, and the signed release tag. The full documentation is at:
https://apache.github.io/xalan-c/ <https://apache.github.io/xalan-c/>
The current iteration fixes all of the major problems I was aware of,
and it's now ready for wider testing. I would be very grateful if all
Xalan-C++ users reading this could take the time to build and test it
with your own code, and report back any successes or failures. If any
problems are found, we can investigate and fix them in an RC2, or
defer to 1.13 if appropriate. If we're confident that this is
release-worthy, then I'll call for a vote and we can make the first
Xalan-C++ release for nearly 8 years!
Kind regards,
Roger Leigh
