Re: Generating Visual Studio project files by default

2016-06-06 Thread Gregory Szorc
On Thu, Jun 2, 2016 at 9:47 PM, Jean-Yves Avenard 
wrote:

> On Wednesday, May 25, 2016 at 9:00:48 AM UTC+10, Gregory Szorc wrote:
> > This change was tracked in bug 1275297. Bug 1275419 tracks a follow-up to
> > allow disabling their generation.
>
> so when is xcode support coming too ? :)
>
>
Patches welcome.

I've heard bad stories about Xcode scalability to large projects. It might
be prudent to Eclipse or another IDE on OS X.
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Re: Generating Visual Studio project files by default

2016-06-02 Thread Jean-Yves Avenard
On Wednesday, May 25, 2016 at 9:00:48 AM UTC+10, Gregory Szorc wrote:
> This change was tracked in bug 1275297. Bug 1275419 tracks a follow-up to
> allow disabling their generation.

so when is xcode support coming too ? :)
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Re: Generating Visual Studio project files by default

2016-05-26 Thread Gregory Szorc
On Tue, May 24, 2016 at 11:22 PM, Wei-Cheng Pan  wrote:

> This is great!
>
> Just few questions:
>
> Can we debug firefox in the IDE during mochitest?
>
> i.e.: ./mach mochitest --debugger=devenv
>

I think we'll need some magic in the mach commands to make this work the
way you want it to. Please file a bug and CC gps and Nat.


>
> Does it supports nmake as well?
>

No. It effectively shells out to `mach build` for the heavy lifting.


>
> Thanks.
>
> Wei-Cheng Pan
>
> On 5/25/16 7:00 AM, Gregory Szorc 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
>
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Re: Generating Visual Studio project files by default

2016-05-26 Thread Chris Pearce
Awesome. Using the VisualStudio project file makes me significantly more 
productive, so I recommend everyone on Windows use it for debugging, learning 
about, and editing code.

The experience is significantly better if you install the Visual Assist plugin 
by Whole Tomato Software:
http://www.wholetomato.com/

This makes VisualStudio's IntelliSense perform significantly better, i.e. less 
crashy; you don't have to roll the dice every time you jump-to-definition on a 
symbol. It also adds ALT+SHIFT+O to open file in project, and ALT+SHIFT+S to 
search for symbol, which also perform significantly faster than VisualStudio's 
built-in equivalent feature (CTRL+,).

Install it. They have a free trial, and once that expires, get Mozilla to pay 
for a license. You'll be more productive because of it. It's worth it.


cpearce.





On Wednesday, May 25, 2016 at 11:00:48 AM UTC+12, Gregory Szorc 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


Re: Generating Visual Studio project files by default

2016-05-24 Thread Wei-Cheng Pan
This is great!

Just few questions:

Can we debug firefox in the IDE during mochitest?

i.e.: ./mach mochitest --debugger=devenv

Does it supports nmake as well?

Thanks.

Wei-Cheng Pan

On 5/25/16 7:00 AM, Gregory Szorc 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


Re: Generating Visual Studio project files by default

2016-05-24 Thread Gregory Szorc


> On May 24, 2016, at 19:29, Jeff Gilbert  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  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


Re: Generating Visual Studio project files by default

2016-05-24 Thread Martin Thomson
On Tue, May 24, 2016 at 7:29 PM, Jeff Gilbert  wrote:
> What's the build-time impact of this?

The implicit question being, if this impact is non-zero, can I turn it
off?  Also, does it make any sense to do this on try machines?
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Re: Generating Visual Studio project files by default

2016-05-24 Thread Jeff Gilbert
What's the build-time impact of this?

On Tue, May 24, 2016 at 4:00 PM, Gregory Szorc  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


Generating Visual Studio project files by default

2016-05-24 Thread Gregory Szorc
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