On Friday, 2 March 2018 19:54:43 UTC, Alex Dubois wrote: > On Saturday, 10 February 2018 01:20:22 UTC, Marek Marczykowski-Górecki wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA256 > > > > On Fri, Feb 09, 2018 at 11:11:50AM -0800, b...@gmail.com wrote: > > > On Wednesday, February 7, 2018 at 8:13:42 PM UTC-5, Marek > > > Marczykowski-Górecki wrote: > > > > For anyone interested, here is instruction how to setup build > > > > environment: > > > > https://github.com/QubesOS/qubes-builder-windows/ > > > > > > > > I know Rafał "Omeg" used Visual Studio for development, but I have no > > > > idea if anything special was needed there. I see vs2012, vs2013, vs2015 > > > > etc directories in relevant repositories. > > > > > > Hi Marek, > > > > > > If you have time... > > > > > > Just FYI, the instructions you linked to above no longer work. I say this > > > based on more than several hours of trying to figure out how to build the > > > tools. I get all the way, without errors or warnings, to the last step, > > > which is `make qubes`. That step throws an error about rpm not being > > > installed: "No rule to make target 'please.install.rpm.and.try.again', > > > needed by 'check.rpm'. Stop." > > > > Hmm, exactly this issue should be fixed by: > > https://github.com/QubesOS/qubes-builder-windows/commit/5a637757d69dc952b0d19ef0cb86574ba54e0717 > > > > Check if you have qubes-builder/qubes-src/builder-windows/builder.conf, > > with that content. Or, maybe something have changed in cygwin in the > > meantime? What is the output of "uname -o" command? > > > > - -- > > Best Regards, > > Marek Marczykowski-Górecki > > Invisible Things Lab > > A: Because it messes up the order in which people normally read text. > > Q: Why is top-posting such a bad thing? > > -----BEGIN PGP SIGNATURE----- > > > > iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAlp+uU4ACgkQ24/THMrX > > 1yw4ogf+MdN914rsdJV65ROfwFzHFhYRdEdG2KSH+GrrdTmdORI26IG1E4Z4qSwK > > aB9sTDnwb2+qkjv9yVDYM3qpL7GGyfp2TgbFwFwEFrs3L07ryc7eWW1mhNcq+Wgn > > aCPAVOQDN8gNm/GjC3hr22aJPfe/S+XKw3I5f3xegfN49M08jKpiI2U+6jkK0BTW > > okMh+wFFWfIgiOadoFPHwdD4fEq7pMDBcGwuZadIx9LXNRU6F52HH0sBN8eV1cZg > > 2a2h8vLClriEvqb3lM3Nr8AQ8+F+R2+SQc1pcF4RC0y/6qXQB8byVx9Oig/Rs6tE > > v8cOGsTOSMlo2PnuUBFeeEr124jEnw== > > =aHm1 > > -----END PGP SIGNATURE----- > > I am trying to bring the build env up to date. > MinGW was probably selected initially with the view to: > 1- cross-compile some components which comes from linux > 2- ensure no GPL lock-in (as initially these components were closed source) > > Would you now if this still apply or if the Unix stack is only used for file > management (i.e. not compiling with gcc)? Cygwin would allow easier > installation of python, bash, make, git in a single env. > At the moment I am using: > - MinGW/MSYS (legacy) > - Windows Git version (launched from the most recent MinGW (using mingw-get) > - Windows Embeded Python (in preparation, have not tested it) > > I am hoping to make the windows build compatible with vs2017 and WDK10. > But for now, I have only automated > - qubes-builder set-up from get-be.ps1 file > > sourceforge being DDOSed these last few days does not help...
Sorry, I found some use of gcc. So MinGW is required. -- You received this message because you are subscribed to the Google Groups "qubes-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-devel+unsubscr...@googlegroups.com. To post to this group, send email to qubes-devel@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-devel/c02a9d12-f56a-4c80-ab4b-280ec2f86a53%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
