Re: [crypto] New Release

2020-06-13 Thread Xeno Amess
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

Re: [crypto] New Release

2020-06-13 Thread Alex Remily
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

Re: [crypto] New Release

2020-06-13 Thread Matt Sicker
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

Re: [crypto] New Release

2020-06-13 Thread Marcelo Vanzin
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

Re: [crypto] New Release

2020-06-13 Thread Gary Gregory
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

Re: [crypto] New Release

2020-06-13 Thread Alex Remily
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

Re: [crypto] New Release

2020-06-13 Thread Gary Gregory
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

Re: [crypto] New Release

2020-06-13 Thread Matt Sicker
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

Re: [Graph] Build fails (unit tests)

2020-06-13 Thread Amey Jadiye
On Sat, Jun 13, 2020 at 8:50 PM Gilles Sadowski wrote: > Hi. > > 2020-06-13 16:57 UTC+02:00, Amey Jadiye : > > Hello Gilles, > > > > On Sat, Jun 13, 2020 at 6:36 PM Gilles Sadowski > > wrote: > > > >> Hello. > >> > >> After the migration from SVN to "gitbox", we noticed that the > >> _first_

Re: [Graph] Build fails (unit tests)

2020-06-13 Thread Gilles Sadowski
Hi. 2020-06-13 16:57 UTC+02:00, Amey Jadiye : > Hello Gilles, > > On Sat, Jun 13, 2020 at 6:36 PM Gilles Sadowski > wrote: > >> Hello. >> >> After the migration from SVN to "gitbox", we noticed that the >> _first_ build failed due to 3 unit tests not passing (see e.g. the >> Travis report

Re: [Graph] Build fails (unit tests)

2020-06-13 Thread Amey Jadiye
On Sat, Jun 13, 2020 at 8:27 PM Amey Jadiye wrote: > Hello Gilles, > > On Sat, Jun 13, 2020 at 6:36 PM Gilles Sadowski > wrote: > >> Hello. >> >> After the migration from SVN to "gitbox", we noticed that the >> _first_ build failed due to 3 unit tests not passing (see e.g. the >> Travis report

Re: [Graph] Build fails (unit tests)

2020-06-13 Thread Amey Jadiye
Hello Gilles, On Sat, Jun 13, 2020 at 6:36 PM Gilles Sadowski wrote: > Hello. > > After the migration from SVN to "gitbox", we noticed that the > _first_ build failed due to 3 unit tests not passing (see e.g. the > Travis report referred to the JIRA report[1]). > > The move to "git" was

Re: [crypto] New Release

2020-06-13 Thread Gary Gregory
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

Re: [Graph] Build fails (unit tests)

2020-06-13 Thread Xeno Amess
Hi. > You are welcome to implement your suggestion I want to, but this repo is out of my ability. Although I do have some experiences in ICPC, the graph part is handled by my team mates, and I personally nearly know nothing about any complex graph algorithms. Gilles Sadowski 于2020年6月13日周六

Re: [Graph] Build fails (unit tests)

2020-06-13 Thread Gilles Sadowski
Hi. 2020-06-13 15:11 UTC+02:00, Xeno Amess : >> IMO, the top priority is now to fix the failing unit tests; >> personally, I'm not going to merge any PR before that is >> achieved (and please refer to the JIRA identifier[1] in the >> corresponding commit/PR). > > agreed. > > And I still suggest

Re: [Graph] Build fails (unit tests)

2020-06-13 Thread Xeno Amess
> IMO, the top priority is now to fix the failing unit tests; > personally, I'm not going to merge any PR before that is > achieved (and please refer to the JIRA identifier[1] in the > corresponding commit/PR). agreed. And I still suggest revert back to the last version which can build, and

[Graph] Build fails (unit tests)

2020-06-13 Thread Gilles Sadowski
Hello. After the migration from SVN to "gitbox", we noticed that the _first_ build failed due to 3 unit tests not passing (see e.g. the Travis report referred to the JIRA report[1]). The move to "git" was intended to make it easier for people willing to revive the [Graph] project. IMO, the top

Re: Quick questions about this mailing list

2020-06-13 Thread Mark Thomas
On 13/06/2020 05:06, Miguel Munoz wrote: > When I send an email to this list, my email address shows up in the archive > as ending with .INVALID. Is there anything I can do about this? (I submitted > an ICLA, so that shouldn't be the problem.)