View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0005166||GNUnet||build process||public||2017-10-30 16:20||2019-02-28 11:48|
|Priority||normal||Severity||minor||Reproducibility||have not tried|
|Target Version||Fixed in Version|
|Summary||0005166: Change/Fix the build system for Windows|
|Description||Right now, at least according to documentation, the builds for Windows rely on|
Editions of Enterprise to Server and the features within them (NAT, etc).
For example (old preview manual: https://dist.ng0.infotropique.org/dist/manual/gnunet/gnunet.html#Build-Instructions-for-Microsoft-Windows-Platforms https://dist.ng0.infotropique.org/dist/manual/gnunet/gnunet.html#Instructions-for-Microsoft-Windows-Platforms-_0028Old_0029)
The way the builds are done isn't particular nice (mingw32 etc). I know in an ideal world everyone would be able to just build on our favorite GNU Userland or be able to use cross-distro package managers such as Guix (hey, some people are experimenting with the idea of Guix on Windows). But we aren't in this ideal world.
So without knowing anything beyond the documentation (not the code) about our Windows builds, is it technically possible for our build- and dependency chain to make the build produce a result users of MS Windows can use native on their systems?
I know next to nothing about building on MS platforms, but I'm curious and improving the situation would be nice if it is possible. The obvious target should be Windows 10 these days (no matter what we think about its antiprivacy features etc).
|Tags||No tags attached.|
In particular this should lead to "providing official Windows binaries" if a solution can be found or improved.
Guix can (cross-)build for mingw32 and produce a guix pack, but this is just a preference I would investigate, anything which gets the job done and improves the "build it yourself AND you have to have an enterprise or server edition" is acceptable.
||AFAIK there is the upcoming "Linux subsystem for W32" which should make it possible to use the standard GNU process to build on W32. Also, in the absence of a W32-affine hacker, I think we should just for now mothball the W32 port and focus on all of the important bugs for the important platforms ;-).|
||As per our more recent discussion, where I'll commit (hopefully) tomorrow the code for, about the support of OS' from our side - I agree.|
|2017-10-30 16:20||ng0||New Issue|
|2017-10-30 16:35||ng0||Description Updated||View Revisions|
|2017-10-30 16:39||ng0||Note Added: 0012528|
|2017-10-30 16:43||ng0||Note Edited: 0012528||View Revisions|
|2018-06-07 23:30||Christian Grothoff||Note Added: 0013025|
|2018-06-08 06:39||ng0||Note Added: 0013030|
|2019-02-28 10:14||ng0||Summary||the Windows build system => Change/Fix the build system for Windows|
|2019-02-28 11:48||Christian Grothoff||Status||new => acknowledged|