![]() ![]() > could instead base it on the new git for windows (GFW). > I was thinking that instead of basing mozillabuild directly on msys2, we The installer writes a few registry keys to support un-installation and adds some start menu entries. You only need to unpack the archive to a folder to use it. For each 'release' we provide an installer and also an archive. From the start it's be engineered that way. > to me, with mintty working fine with colors.Īll of these features are directly inherited from MSYS2, and AFAIK they use many of our packages directly. > It already has very useful builds (including portable) at > The new git (2.4.1) for windows is based on msys2 and mintty with bash 4.3. I am not belittling the good work that the guys at GFW have done and are continuing to do. Please understand that I am not being negative towards GFW, we're really happy that they've finally ditched MSYS and based their work on MSYS2 and we aim to continue to work together to get all of their fixes merged and working well within MSYS2 itself, but I think - for now at least - that this is the wrong decision for Mozilla to make. (In reply to Avi Halachmi (:avih) from comment #13) The paths could be queried from the registry too. With a bit of work this could be made more general, especially since we now only support VS2013 and above for builds. sh script that sets things up for 64-bit VS2013 (on a 64-bit) machine. two, rewrite/convert into minimal native shell scripts one, keep using our current start-* scripts and just launch a msys bash shell at the end ![]() The MSVC env vars is the tricky part we have two options here: The env vars are purely needed for configure to properly detect the build env I'm not sure which one is actually needed or all three. $PYTHON needing to be native windows python has something to do with virtualenv. we need (some of) these env vars for a native build:įor the last three issues. $PYTHON must point to native windows python, not msys2 python (can we fix?) We need NSIS in the path, unless we -disable-installer:Įxport PATH="/c/path-to/nsis-3.0a2:$PATH" ![]() $ pacman -S yasm p7zip git python2 mercurial upx zip unzip make tar $ pacman -needed -Sy bash pacman pacman-mirrors msys2-runtime So starting from a fresh msys2 install, here's a minimal set of things needed to get a buildable gecko: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |