On Wed, Mar 12, 2014 at 10:51:40PM -0400, Ehsan Akhgari wrote: > >Here's a thought: how about just making things work with plain msys2 and > >not require MozillaBuild at all anymore? We don't have a MozillaBuild > >for mac, we just rely on homebrew or whatever else. Why not just aim > >for the same? > >What, in a msys2-based MozillaBuild would not come from msys2? The > >environment scripts to find msvc? I'd argue that could/should be handled > >by the build system. > > Does msys2 come with a decent package manager by default? Having to > end up with installing prerequisites manually would be a shame. > Unless there is something better that we can do through the mach > bootstrap script? > > If that can be taken care of, I think this is a great idea!
As Ryan said, msys2 comes with a port of pacman, which is Arch Linux's package manager. Probably not a complete list, but something like: pacman -S make python2 git mercurial perl autoconf2.13 ought to be enough, and that can be documented on the wiki like the homebrew and apt-get/yum invocations for OSX/Linux. And can be automated with mach bootstrap too. I can't tell more because there are many issues preventing the build from working with msys2 currently. I gave it a shot for a couple minutes, and here are the most immediate problems: - The base installation comes as a tar.xz, which is not the most convenient format to install from on windows. - The python 2.7 package doesn't install a "python" executable. Only a "python2.7" executable, and both mach and client.mk default to using "python". - Our config.guess is old and doesn't output the right triplet. - Using the 32 bits mode of the 64 bits msys2 still gives a triplet for 64 bits, so the 32 bits msys2 needs to be used (or a different --target given) - virtualenv installs the python executable in _virtualenv/bin/python and we're looking in _virtualenv/Scripts/python.exe. - either virtualenv or python doesn't work properly: sys.path doesn't have the virtualenv paths when running the virtualenv python with a windows path (c:/foo), although it works when running with a msys path (/c/foo). (And the build system really prefers windows paths) None of those except the first are problems that need a MozillaBuild package. And the first should be dealt with at the msys2 level anyways. The rest are issues with the build system. That being said, I see msys python uses msys paths, and msys APIs, and I'm sure many things will break as a consequence. We might still want to stick with a native win32 python, and *that* would need a MozillaBuild package. Mike _______________________________________________ dev-builds mailing list dev-builds@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-builds
