On Friday, 2 March 2018 21:46:20 UTC, Alex Dubois wrote: > On Friday, 2 March 2018 21:26:33 UTC, Alex Dubois wrote: > > 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, [email protected] 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. > > To be more precise, I found some copy of mingw/bin/gcc to /mingw/bin/cc, no > actual use so far. But I am going to stick to the current set-up of mingw. > There are places where patches are applied to various build binaries.
OK... I am able to build the QWT now (well almost, I have an error at the end with the signing that I am working on). However I had to ticker a bit, and not 100% sure yet how to patch the scripts and update the doc. I don't have enough disk space to have 2 Windows-build machines and I want to keep this one. So it will take me some time to have a PR ready to go through the process again, fix the issues and document, as I want to confirm it is OK on a second new windows-build VM. In summary: - bootstrap with the script/get-be.ps1 script (I did from C:\QubesOS, also the original build was probably done on C:\) - Once you have \QubesOS\qubes-builder (refered as @ after) bootstraped - copy from @example-config\qubes-master.conf to @\builder.conf (+edit remove commentst to enable Windows part) - make COMPONENTS="builder-windows" get-sources - copy form @\qubes-src\builder-windows\windows-tools.conf to @\builder.conf (edit the file, to have debug target, for example) do not override the builder.conf in builder-windows - make get-sources - cd @\qubes-src\vmm... - make (this will do the git submodule bit documented in the readme.md) - cd @ - make COMPONENTS="builder-windows" qubes (can't remember if I had to break it down but safer) - make qubes I lost a lot of time because sourceforge is in limbo due to the recent DDOS attacks due to memcached amplification abuse... Which means that you may: - have to comment out lines that clean tmp directory in the bootstrap script, modify the script so it does not override the files you may have downloaded manually with 1K garbage - have to download manually a number of files for the windows prereqs phase Also because msys version pulled is old, its git fail to connect on github (old SSL/TLS stack). So you'll have to use 2 terminals for the different steps explained above: - msys (when git is not required -> not get-sources targets - git bash (msys2) with path modified to bring msys binaries (which breaks some scripts which use sed Hope it helps others. -- 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 [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-devel/7976fbd9-fdcf-4181-aa19-a430e5fc0b0b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
