I don't currently have ready access to a Windows host, and have so far
failed to find the correct setting of jn[ai].library.path required to
cause OpenSSL to be loaded rather than the default which seems to be
LibreSSL.
So if anyone with Windows and OpenSSL 1.1.x can help that would be great!
The
I believe it is for cross compilation, owing to the comments in the
makefile:
# for cross-compilation on Ubuntu, install the g++-mingw-w64-x86-64 package
# for cross-compilation on Ubuntu, install the g++-arm-linux-gnueabi package
# for cross-compilation on Ubuntu, install the g++-arm-linux-gnuea
The supported architectures documentation is limited to the discussion on
this distribution list. At least, that's my recollection and
understanding. I agree that this should be documented at least in the
release notes and web site. Users shouldn't need to crack open the jar to
figure that out.
On 26/10/2023 13:48, Gary Gregory wrote:
Java 8 is required.
This phrasing is somewhat confusing. "Java 8 or newer is required" would
help clarify things.
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For add
The Crypto makefile includes a lot of different OS and architecture
combinations.
Not all of these are included in the binary jar.
I don't think we need to generate native binaries for all the
combinations, but I do think we need to document which ones are
included, and note that any others must
On Wed, 1 Nov 2023 at 12:53, Gary Gregory wrote:
>
> Maybe there are cross compilation issues... I don't know for sure.
But CXX is only used for the link phase.
> What I
> do know is that it quite tricky and time consuming to get everything just
> right when I do a release from multiple machines
Maybe there are cross compilation issues... I don't know for sure. What I
do know is that it quite tricky and time consuming to get everything just
right when I do a release from multiple machines to get macOS, Linux, and
Windows binaries correctly compiled, linked, and packaged up. I hope
nothing
Crypto currently only uses .c files, and the Makefile uses CC
throughout, except for creating the object output. [This has been the
case since the initial release.]
Using CXX (C++) for the link does not make sense to me - surely CC can
create the object equally well?
It would simplify builds (and
