> On May 24, 2016, at 19:29, Jeff Gilbert <jgilb...@mozilla.com> wrote: > > What's the build-time impact of this?
It should be marginal compared to all the other stuff that happens during a build, even a light build. Local and automation builds print the timing numbers and I've been doing a lot of work lately to surface and monitor this data better. If you feel this change has a noticeable negative impact on a particular workflow because of the overhead, please file a bug. > >> On Tue, May 24, 2016 at 4:00 PM, Gregory Szorc <g...@mozilla.com> wrote: >> Coming soon to your local builds, Visual Studio project files will be >> generated automatically when building on Windows because we want to >> encourage more people to use them because fully-featured IDEs can be >> productivity wins. >> >> The Visual Studio projects now automatically target the Visual Studio >> version being used (1 week ago they would always generate VS2013 project >> files). Another new change is that unless the build configuration changes, >> the Visual Studio files won't be updated by the build system unless they >> need changed. That means if you do a pull+build when Visual Studio is open, >> you shouldn't get tons of warnings that you need to reload files to pick up >> changes. >> >> The Visual Studio integration isn't perfect. We'd like to encourage more >> development on Windows because that's where most Firefox users are. So if >> you'd like improvements to the Visual Studio project files, please file >> Core :: Build Config bugs. >> >> This change was tracked in bug 1275297. Bug 1275419 tracks a follow-up to >> allow disabling their generation. >> _______________________________________________ >> dev-platform mailing list >> dev-platform@lists.mozilla.org >> https://lists.mozilla.org/listinfo/dev-platform _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
