[Audacity-devel] Windows Development

[Mark Young]

Hi all,

I setup a new dev stack for 2.2.0 to start work on the help buttons
project. I have decided to use the new "Visual Studio 2017" rather than
2013 - however I have not re-targeted the project so this will remain
compatible. This is purely for my own use of the new IDE features in
2017. This blog shows more information on how this is possible:
https://blogs.msdn.microsoft.com/vcblog/2016/02/24/stuck-on-an-older-toolset-version-move-to-visual-studio-2015-without-upgrading-your-toolset/

I noticed that the version number in win/compile.txt was wrong (2.1.2) so I
have changed this to 2.2.0.

I would also like to add /win/.vs/ to the .gitignore file. The .vs
directory holds a number of files related to Visual Studio. It wont have
any impact to the project, but will save other developers having to contend
with this if they too use VS 2017 in the manner I am.

Pull Request at:
https://github.com/audacity/audacity/pull/192

Mark

[Paul Licameli]

I understand there are some dark corners of C++11 not yet implemented in VS
2013, since done in VS 2017. Things like constexpr and nothrow. You just
might break the build if you rely on the new things.

Should we consider making VS 2017 the required platform for building to get
all the latest and best in the compiler?

PRL

Post by Mark Young
Hi all,
I setup a new dev stack for 2.2.0 to start work on the help buttons
project. I have decided to use the new "Visual Studio 2017" rather than
2013 - however I have not re-targeted the project so this will remain
compatible. This is purely for my own use of the new IDE features in
https://blogs.msdn.microsoft.com/vcblog/2016/02/24/stuck-
on-an-older-toolset-version-move-to-visual-studio-2015-
without-upgrading-your-toolset/
I noticed that the version number in win/compile.txt was wrong (2.1.2) so
I have changed this to 2.2.0.
I would also like to add /win/.vs/ to the .gitignore file. The .vs
directory holds a number of files related to Visual Studio. It wont have
any impact to the project, but will save other developers having to contend
with this if they too use VS 2017 in the manner I am.
https://github.com/audacity/audacity/pull/192
Mark
------------------------------------------------------------
------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
audacity-devel mailing list
https://lists.sourceforge.net/lists/listinfo/audacity-devel

[Mark Young]

Hi Paul

With the way this works it builds using VS 2013 which is also on machine. I
just get the added IDE goodness of VS 2017. So shouldn't break :-)

That said, of there is a decision to move to 2017 then happy days.

Mark

On 24 Mar 2017 3:32 pm, "Paul Licameli" <***@gmail.com> wrote:

I understand there are some dark corners of C++11 not yet implemented in VS
2013, since done in VS 2017. Things like constexpr and nothrow. You just
might break the build if you rely on the new things.

Should we consider making VS 2017 the required platform for building to get
all the latest and best in the compiler?

PRL

Post by Mark Young
Hi all,
I setup a new dev stack for 2.2.0 to start work on the help buttons
project. I have decided to use the new "Visual Studio 2017" rather than
2013 - however I have not re-targeted the project so this will remain
compatible. This is purely for my own use of the new IDE features in
https://blogs.msdn.microsoft.com/vcblog/2016/02/24/stuck-on-
an-older-toolset-version-move-to-visual-studio-2015-without-
upgrading-your-toolset/
I noticed that the version number in win/compile.txt was wrong (2.1.2) so
I have changed this to 2.2.0.
I would also like to add /win/.vs/ to the .gitignore file. The .vs
directory holds a number of files related to Visual Studio. It wont have
any impact to the project, but will save other developers having to contend
with this if they too use VS 2017 in the manner I am.
https://github.com/audacity/audacity/pull/192
Mark
------------------------------------------------------------
------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
audacity-devel mailing list
https://lists.sourceforge.net/lists/listinfo/audacity-devel

------------------------------------------------------------
------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

[Paul Licameli]

What I mean is, you might make changes using newer C++ stuff but it might
not compile for the rest of us.

PRL

Post by Mark Young
Hi Paul
With the way this works it builds using VS 2013 which is also on machine.
I just get the added IDE goodness of VS 2017. So shouldn't break :-)
That said, of there is a decision to move to 2017 then happy days.
Mark
I understand there are some dark corners of C++11 not yet implemented in
VS 2013, since done in VS 2017. Things like constexpr and nothrow. You
just might break the build if you rely on the new things.
Should we consider making VS 2017 the required platform for building to
get all the latest and best in the compiler?
PRL

Post by Mark Young
Hi all,
I setup a new dev stack for 2.2.0 to start work on the help buttons
project. I have decided to use the new "Visual Studio 2017" rather than
2013 - however I have not re-targeted the project so this will remain
compatible. This is purely for my own use of the new IDE features in
https://blogs.msdn.microsoft.com/vcblog/2016/02/24/stuck-on-
an-older-toolset-version-move-to-visual-studio-2015-without-
upgrading-your-toolset/
I noticed that the version number in win/compile.txt was wrong (2.1.2) so
I have changed this to 2.2.0.
I would also like to add /win/.vs/ to the .gitignore file. The .vs
directory holds a number of files related to Visual Studio. It wont have
any impact to the project, but will save other developers having to contend
with this if they too use VS 2017 in the manner I am.
https://github.com/audacity/audacity/pull/192
Mark
------------------------------------------------------------
------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
audacity-devel mailing list
https://lists.sourceforge.net/lists/listinfo/audacity-devel

------------------------------------------------------------
------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
audacity-devel mailing list
https://lists.sourceforge.net/lists/listinfo/audacity-devel
------------------------------------------------------------
------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
audacity-devel mailing list
https://lists.sourceforge.net/lists/listinfo/audacity-devel