On Fri, Jul 24, 2020 at 8:04 PM Alex Remily wrote:
> I'd recommend using MinGW. I installed it through brew on my Mac and cross
> compiled the windows build with little difficulty. I expect a similar
> experience on Linux. The MinGW install contains all the necessary windows
> headers.
>
Yep,
There is a docker Maven plugin:
io.fabric8
docker-maven-plugin
0.33.0
Gary
On Sat, Jul 25, 2020, 00:20 Geoffrey Blake
wrote:
> Docker would be great. Next question, can that be integrated into
> Maven for automating these releases that someone k
I don't see why it couldn't. I don't think OSX images are publicly
accessible in Docker Hub though, and if not we'd need a Mac as the
base machine to run the build. From the base machine we should be
able to call docker using the Maven exec plugin, use docker to pull in
the desired linux arch hos
Docker would be great. Next question, can that be integrated into
Maven for automating these releases that someone knows offhand?
-Geoff
On Fri, Jul 24, 2020 at 7:50 PM Alex Remily wrote:
>
> Sounds like a great idea.
>
> On Fri, Jul 24, 2020, 8:29 PM Marcelo Vanzin wrote:
>
> > Is it possible
Sounds like a great idea.
On Fri, Jul 24, 2020, 8:29 PM Marcelo Vanzin wrote:
> Is it possible to cross-compile from Linux to MacOS?
>
> Even if it isn't, might be a good idea to write a docker image to do
> the other cross-builds; then from a Mac you can build the MacOS binary
> and call docker
Is it possible to cross-compile from Linux to MacOS?
Even if it isn't, might be a good idea to write a docker image to do
the other cross-builds; then from a Mac you can build the MacOS binary
and call docker to build all the others.
On Fri, Jul 24, 2020 at 5:04 PM Alex Remily wrote:
>
> I'd rec
I'd recommend using MinGW. I installed it through brew on my Mac and cross
compiled the windows build with little difficulty. I expect a similar
experience on Linux. The MinGW install contains all the necessary windows
headers.
On Fri, Jul 24, 2020, 7:16 PM Gary Gregory wrote:
> Thanks Geoffr
Thanks Geoffrey,
Are you available at some point to do a webex to straighten out my local
set up? Just email me directly so we can coordinate.
Gary
On Fri, Jul 24, 2020 at 4:34 PM Geoffrey Blake
wrote:
> Hi Gary,
>
> windows.h/Windows.h/WINDOWS.H are all names for the same file, on
> Windows I
Hi Gary,
windows.h/Windows.h/WINDOWS.H are all names for the same file, on
Windows I've found out, the FS is case-insensitive. This is not true
on a Linux box though. I submitted a new PR to fix this and get
Windows builds working again on a Linux box, as well as testing that
windows artifacts w
On Thu, Jul 2, 2020 at 12:39 PM Geoffrey Blake
wrote:
> I took a bit of time to set up an x86 Ubuntu 14.04 VM via virtualbox
> and vagrant, but it looks like the windows build is broken. There are
> typos trying to include "Windows.h" which should be "windows.h" to
>
Are you sure that this incl
I took a bit of time to set up an x86 Ubuntu 14.04 VM via virtualbox
and vagrant, but it looks like the windows build is broken. There are
typos trying to include "Windows.h" which should be "windows.h" to
compile with mingw and redefined macros that I think are mixing
between Linux and windows he
I'll see if I have any time this weekend, but this part is largely
unfamiliar to me, so not sure how far I'll get even if I have the time
to look at it.
On Tue, Jun 30, 2020 at 4:59 PM Geoffrey Blake
wrote:
>
> I think you're right Alex. I just happened to look at the Makefile
> and saw this abo
I think you're right Alex. I just happened to look at the Makefile
and saw this above the win64 target:
# for cross-compilation on Ubuntu, install the g++-mingw-w64-x86-64 package
We could potentially build everything but MacOS on 1 Ubuntu 16.04LTS
box. Or even a 14.04 box if necessary. Anybod
Not sure if it's relevant or not, but to get the build to compile on
Windows with MinGW, I commented out line 137 of
https://github.com/apache/commons-crypto/blob/master/src/main/native/org/apache/commons/crypto/org_apache_commons_crypto.h:
//#define inline __inline;
I never did learn why it was
Is there anything needed to help move this release along? From the
looks of the Makefile, Windows was using GCC. I don't think the
compiler is going to have much of an impact since the JNI bindings are
simply calling through to the OpenSSL library that is already
precompiled for the environment.
I have a feeling about both mingw or cygwin build output will be slower
than microsoft-visual-studio build output...
Just a feeling, but no evidence.
Alex Remily 于2020年6月14日周日 上午7:02写道：
> I used MinGW64. It does indeed ship with make. I can provide a link
> to the distribution I used if there'
I used MinGW64. It does indeed ship with make. I can provide a link
to the distribution I used if there's interest.
On Sat, Jun 13, 2020 at 6:26 PM Marcelo Vanzin wrote:
>
> Pretty sure I remember comments in the code about building with mingw
> on Windows (not cygwin). That should have a versi
Use of cmake could be useful for cross platform builds, though I’ve only
used some of the basic functionality so far and can’t comment on how big a
task it is to convert to use.
On Sat, Jun 13, 2020 at 17:26 Marcelo Vanzin wrote:
> Pretty sure I remember comments in the code about building with
Pretty sure I remember comments in the code about building with mingw
on Windows (not cygwin). That should have a version of make, too,
IIRC.
On Sat, Jun 13, 2020 at 3:11 PM Gary Gregory wrote:
>
> Except that you can't build on plain Windows because the build uses make
> and Microsoft version is
Except that you can't build on plain Windows because the build uses make
and Microsoft version is called nmake. I might have to cobble up some
cygwin thing...
Gary
On Sat, Jun 13, 2020, 18:02 Alex Remily wrote:
> I can't speak to how the original developers did the build, but all
> the Windows
I can't speak to how the original developers did the build, but all
the Windows builds that I did were on a Windows machine. I always
assumed that the original developers just manually packed the release
jar with artifacts from each supported environment. I never did any
investigation into the pr
Hi Matt:
> I have:
>
> /mnt/c/git/commons-crypto# find /usr -name windows.h
> /usr/i686-w64-mingw32/include/windows.h
> /usr/share/mingw-w64/include/windows.h
> /usr/x86_64-w64-mingw32/include/windows.h
>
> Case matters here, so I wonder if the original others did not cross
compile
> from Linux an
Are the Windows headers even available when using Ming32 or Cygwin?
That sounds more like a Visual Studio compiler thing.
On Sat, 13 Jun 2020 at 09:29, Gary Gregory wrote:
>
> The challenge is getting everything set up just right for building the
> various OS profiles. This component is quite dif
The challenge is getting everything set up just right for building the
various OS profiles. This component is quite different in this regard,
getting help from the original contributors would be helpful.
After much fiddling to install the proper packages, this builds OK:
mvn package -DskipTests -
Just checking in on the status of the 1.1 release.
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
25 matches
Mail list logo
