Thread: [Audacity-devel] MSVC 2013 Yes. wxWidgets 3.0.1 Maybe.
A free multi-track audio editor and recorder
Brought to you by:
aosiniao
Menu
▾
▴
audacity-devel
|
From: James C. <cr...@in...> - 2014-10-12 14:44:26
|
We intend that MSVC 2013 will be used to build the next released Audacity, which will be numbered 2.1.0. For 2.1.0 we will no longer support building on Windows XP. Leland has deprecated the old MSVC 2008 project files. I currently build with both these deprecated project files, with MSVC2008, and with the new project files with MSVC2013 (both Express). I plan to stop building with MSVC2008 from Nov 1st. We will not maintain the old project files after that. Possibly the version in SVN will already be unusable for building SVN head by then. I hope most people won't need to switch back and forth between tools, which is a reason for setting an end time for the switchover. If we do complete the switchover sooner, and it sounds like we are on course for doing so, with many people already using MSVC 2013, great. Audacity 2.1.0 will continue to run on Windows XP. It's less clear for wxWidgets 3.0.1. For wxWidgets 3.0.1, I am building and running Audacity fine. I had a few minor issues which I have fixed. The one remaining one is with the TagsEditor. I've had crashes when it closes. I am 90% sure that is down to changes in wxString. I think we are doing some dodgy memory allocation/deallocation which we get away with in wx 2.8.12! The TagsEditor leaks memory in both versions, so fixing that may give some clues. If anyone else besides me and Leland is also building with wx3.0.1 and wants to share experience of that, please do so. It will help us decide. It's currently slightly more likely than not that we will shift to wx3.0.1 for 2.1.0. --James. |
|
From: Martyn S. <mar...@gm...> - 2014-10-12 23:45:00
|
Hi
On 12/10/2014 15:44, James Crook wrote:
> We intend that MSVC 2013 will be used to build the next released
> Audacity,
I agree with that.
which will be numbered 2.1.0.
but I'm not sure that agreement has been reached on that. It could be
2.0.1, 2.0.7 or 3.0.0, depending on how we do, I think.
For 2.1.0 we will no longer
> support building on Windows XP.
I think true, but release 'should' run on XP, as noted below.
> Leland has deprecated the old MSVC 2008 project files. I currently
> build with both these deprecated project files, with MSVC2008, and with
> the new project files with MSVC2013 (both Express). I plan to stop
> building with MSVC2008 from Nov 1st. We will not maintain the old
> project files after that. Possibly the version in SVN will already be
> unusable for building SVN head by then. I hope most people won't need
> to switch back and forth between tools, which is a reason for setting an
> end time for the switchover. If we do complete the switchover sooner,
> and it sounds like we are on course for doing so, with many people
> already using MSVC 2013, great.
Yes, and VS12 seems to be working here on my win 7 slightly
underpowered box. Not done much testing, but compiles and runs with
wx 2.8.12.
> Audacity 2.1.0 will continue to run on Windows XP.
That's great that MS are doing that for us!
> It's less clear for wxWidgets 3.0.1. For wxWidgets 3.0.1, I am building
> and running Audacity fine. I had a few minor issues which I have
> fixed. The one remaining one is with the TagsEditor. I've had crashes
> when it closes. I am 90% sure that is down to changes in wxString. I
> think we are doing some dodgy memory allocation/deallocation which we
> get away with in wx 2.8.12! The TagsEditor leaks memory in both
> versions, so fixing that may give some clues.
Why are we talking wx 3.0.1 here, not 3.0.2? I am trying 3.0.2 and I
don't see why not to go with that instead.
I see that I need to change the Audacity -> Properties -> Linker ->
Input -> Additional Dependencies for the '30' (3.0) files, but I don't
have it working. Any tips? I only have this for section 2.3 of
compile.txt.
With wx 3.0.2 you will also need
* _custom_build
to prevent build errors
so is there a patch to make wx 3 work for me?
> If anyone else besides me and Leland is also building with wx3.0.1 and
> wants to share experience of that, please do so. It will help us
> decide. It's currently slightly more likely than not that we will shift
> to wx3.0.1 for 2.1.0.
Happy to try it, have not got it going.
From the wx release notes, it sounds like we def need a g++ compiler
to show us the potential problems, and fix them...
"It is strongly advised to recompile your code with a compiler warning
about passing non-POD objects to vararg functions, such as g++."
Has anyone done that yet? I don't know how to do that.
TTFN
Martyn
> --James.
>
>
>
> ------------------------------------------------------------------------------
> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
> http://p.sf.net/sfu/Zoho
> _______________________________________________
> audacity-devel mailing list
> aud...@li...
> https://lists.sourceforge.net/lists/listinfo/audacity-devel
>
|
|
From: Leland <le...@au...> - 2014-10-13 01:49:27
|
> -----Original Message----- > From: Martyn Shaw [mailto:mar...@gm...] > Sent: Sunday, October 12, 2014 6:45 PM > To: aud...@li... > Subject: Re: [Audacity-devel] MSVC 2013 Yes. wxWidgets 3.0.1 Maybe. > > > Why are we talking wx 3.0.1 here, not 3.0.2? I am trying 3.0.2 and I > don't see why not to go with that instead. +1 for 3.0.2...I've been trying to refer to it as wx3. > > I see that I need to change the Audacity -> Properties -> Linker -> > Input -> Additional Dependencies for the '30' (3.0) files, but I don't > have it working. Any tips? I only have this for section 2.3 of > compile.txt. > > With wx 3.0.2 you will also need > * _custom_build > to prevent build errors > > so is there a patch to make wx 3 work for me? I upgrade to 3.0.2 (haven't yet) andsee what that is all about. > > From the wx release notes, it sounds like we def need a g++ compiler > to show us the potential problems, and fix them... > > "It is strongly advised to recompile your code with a compiler warning > about passing non-POD objects to vararg functions, such as g++." > > Has anyone done that yet? I don't know how to do that. Well, get that be default when we get it Audacity going on OSX and Linux. Working on it, but it won't be tomorrow (or the next day, etc.) ;-) Leland |
|
From: Richard A. <ri...@au...> - 2014-10-13 20:38:46
|
On Sun, 12 Oct 2014 20:49:20 -0500 "Leland" <le...@au...> wrote: > > "It is strongly advised to recompile your code with a compiler > > warning about passing non-POD objects to vararg functions, such as > > g++." > > > > Has anyone done that yet? I don't know how to do that. > > Well, get that be default when we get it Audacity going on OSX and > Linux. For which reason, I think the Audacity code is clear of such issues already, unless they are inside #ifdef WXWIN (etc.), because they cause compile errors for the rest of us. Richard |
|
From: Martyn S. <mar...@gm...> - 2014-10-15 23:19:09
|
Hi Richard On 13/10/2014 21:38, Richard Ash wrote: > On Sun, 12 Oct 2014 20:49:20 -0500 > "Leland" <le...@au...> wrote: >>> "It is strongly advised to recompile your code with a compiler >>> warning about passing non-POD objects to vararg functions, such as >>> g++." >>> >>> Has anyone done that yet? I don't know how to do that. >> >> Well, get that be default when we get it Audacity going on OSX and >> Linux. > > For which reason, I think the Audacity code is clear of such issues > already, unless they are inside #ifdef WXWIN (etc.), because they cause > compile errors for the rest of us. So have you built it with wx3 to check for errors / warnings? I would be surprised if there weren't any, from what I read. What about wx3.0.2? It would be good to hear that all is OK with that. Thanks Martyn > Richard > > ------------------------------------------------------------------------------ > Comprehensive Server Monitoring with Site24x7. > Monitor 10 servers for $9/Month. > Get alerted through email, SMS, voice calls or mobile push notifications. > Take corrective actions from your mobile device. > http://p.sf.net/sfu/Zoho > _______________________________________________ > audacity-devel mailing list > aud...@li... > https://lists.sourceforge.net/lists/listinfo/audacity-devel > |
|
From: Leland <le...@au...> - 2014-10-16 00:01:34
|
> -----Original Message----- > From: Martyn Shaw [mailto:mar...@gm...] > Sent: Wednesday, October 15, 2014 6:19 PM > To: aud...@li... > Subject: Re: [Audacity-devel] MSVC 2013 Yes. wxWidgets 3.0.1 Maybe. > > Hi Richard > > On 13/10/2014 21:38, Richard Ash wrote: > > On Sun, 12 Oct 2014 20:49:20 -0500 > > "Leland" <le...@au...> wrote: > >>> "It is strongly advised to recompile your code with a compiler > >>> warning about passing non-POD objects to vararg functions, such as > >>> g++." > >>> > >>> Has anyone done that yet? I don't know how to do that. > >> > >> Well, get that be default when we get it Audacity going on OSX and > >> Linux. > > > > For which reason, I think the Audacity code is clear of such issues > > already, unless they are inside #ifdef WXWIN (etc.), because they cause > > compile errors for the rest of us. > > So have you built it with wx3 to check for errors / warnings? I would > be surprised if there weren't any, from what I read. What about > wx3.0.2? It would be good to hear that all is OK with that. > Changes coming to allow building with wx3. Just trying to figure out why our wxChoice controls look different than the ones in the wx samples. Leland |
|
From: Martyn S. <mar...@gm...> - 2014-10-16 00:17:24
|
Grand! Is this a requisite for the more major changes, or displacement activity, that we all do (well, I do anyway:-))? TTFN Martyn On 16/10/2014 01:01, Leland wrote: > > >> -----Original Message----- >> From: Martyn Shaw [mailto:mar...@gm...] >> Sent: Wednesday, October 15, 2014 6:19 PM >> To: aud...@li... >> Subject: Re: [Audacity-devel] MSVC 2013 Yes. wxWidgets 3.0.1 Maybe. >> >> Hi Richard >> >> On 13/10/2014 21:38, Richard Ash wrote: >>> On Sun, 12 Oct 2014 20:49:20 -0500 >>> "Leland" <le...@au...> wrote: >>>>> "It is strongly advised to recompile your code with a compiler >>>>> warning about passing non-POD objects to vararg functions, such as >>>>> g++." >>>>> >>>>> Has anyone done that yet? I don't know how to do that. >>>> >>>> Well, get that be default when we get it Audacity going on OSX and >>>> Linux. >>> >>> For which reason, I think the Audacity code is clear of such issues >>> already, unless they are inside #ifdef WXWIN (etc.), because they cause >>> compile errors for the rest of us. >> >> So have you built it with wx3 to check for errors / warnings? I would >> be surprised if there weren't any, from what I read. What about >> wx3.0.2? It would be good to hear that all is OK with that. >> > Changes coming to allow building with wx3. Just trying to figure out why > our wxChoice controls look different than the ones in the wx samples. > > Leland > > > ------------------------------------------------------------------------------ > Comprehensive Server Monitoring with Site24x7. > Monitor 10 servers for $9/Month. > Get alerted through email, SMS, voice calls or mobile push notifications. > Take corrective actions from your mobile device. > http://p.sf.net/sfu/Zoho > _______________________________________________ > audacity-devel mailing list > aud...@li... > https://lists.sourceforge.net/lists/listinfo/audacity-devel > |
|
From: Leland <le...@au...> - 2014-10-14 04:32:41
|
> -----Original Message----- > From: Martyn Shaw [mailto:mar...@gm...] > Sent: Sunday, October 12, 2014 6:45 PM > To: aud...@li... > Subject: Re: [Audacity-devel] MSVC 2013 Yes. wxWidgets 3.0.1 Maybe. > > With wx 3.0.2 you will also need > * _custom_build > to prevent build errors > > so is there a patch to make wx 3 work for me? > I'm not sure what that is talking about at all. All I did to build was to change the Linker input library names, from 28 to 30. And it build just fine. Where did you see that reference? I'll see if I can figure out what they are talking about. Leland |
|
From: Martyn S. <mar...@gm...> - 2014-10-15 23:15:09
|
On 14/10/2014 05:32, Leland wrote: > > >> -----Original Message----- >> From: Martyn Shaw [mailto:mar...@gm...] >> Sent: Sunday, October 12, 2014 6:45 PM >> To: aud...@li... >> Subject: Re: [Audacity-devel] MSVC 2013 Yes. wxWidgets 3.0.1 Maybe. >> >> With wx 3.0.2 you will also need >> * _custom_build >> to prevent build errors >> >> so is there a patch to make wx 3 work for me? >> > I'm not sure what that is talking about at all. All I did to build was to > change the Linker input library names, from 28 to 30. And it build just > fine. > > Where did you see that reference? I'll see if I can figure out what they > are talking about. This was following compile.txt, where we recommend just building some of the projects. I see this has been discussed on other threads. You build everything, even if we don't need it. It shouldn't increase our deliverable size since they are separate dlls, just our build time (but it's only once, and not by much, I guess, so I think we should simplify the instructions in compile.txt). TTFN Martyn > Leland > > > > ------------------------------------------------------------------------------ > Comprehensive Server Monitoring with Site24x7. > Monitor 10 servers for $9/Month. > Get alerted through email, SMS, voice calls or mobile push notifications. > Take corrective actions from your mobile device. > http://p.sf.net/sfu/Zoho > _______________________________________________ > audacity-devel mailing list > aud...@li... > https://lists.sourceforge.net/lists/listinfo/audacity-devel > |
|
From: Leland <le...@au...> - 2014-10-16 01:01:35
|
> -----Original Message----- > From: Martyn Shaw [mailto:mar...@gm...] > Sent: Wednesday, October 15, 2014 7:17 PM > To: aud...@li... > Subject: Re: [Audacity-devel] MSVC 2013 Yes. wxWidgets 3.0.1 Maybe. > > Grand! Is this a requisite for the more major changes, or > displacement activity, that we all do (well, I do anyway:-))? > Probably more displacement than requisite. I was thinking it might be good to get wx3 out of the way before doing the more fun stuff, but I'm slowly starting to think otherwise. I'll get Linux in a wx3 buildable state, but I'll stop there. OSX will just have to wait since he's going to be the most difficult (we will lose accessibility on OSX entirely...or, at best, it will go back to before we started patching the wxWidgets lib on OSX to add accessibility). > TTFN > Martyn > > On 16/10/2014 01:01, Leland wrote: > > > > > >> -----Original Message----- > >> From: Martyn Shaw [mailto:mar...@gm...] > >> Sent: Wednesday, October 15, 2014 6:19 PM > >> To: aud...@li... > >> Subject: Re: [Audacity-devel] MSVC 2013 Yes. wxWidgets 3.0.1 Maybe. > >> > >> Hi Richard > >> > >> On 13/10/2014 21:38, Richard Ash wrote: > >>> On Sun, 12 Oct 2014 20:49:20 -0500 > >>> "Leland" <le...@au...> wrote: > >>>>> "It is strongly advised to recompile your code with a compiler > >>>>> warning about passing non-POD objects to vararg functions, such as > >>>>> g++." > >>>>> > >>>>> Has anyone done that yet? I don't know how to do that. > >>>> > >>>> Well, get that be default when we get it Audacity going on OSX and > >>>> Linux. > >>> > >>> For which reason, I think the Audacity code is clear of such issues > >>> already, unless they are inside #ifdef WXWIN (etc.), because they cause > >>> compile errors for the rest of us. > >> > >> So have you built it with wx3 to check for errors / warnings? I would > >> be surprised if there weren't any, from what I read. What about > >> wx3.0.2? It would be good to hear that all is OK with that. > >> > > Changes coming to allow building with wx3. Just trying to figure out why > > our wxChoice controls look different than the ones in the wx samples. > > > > Leland > > > > > > ---------------------------------------------------------------------------- -- > > Comprehensive Server Monitoring with Site24x7. > > Monitor 10 servers for $9/Month. > > Get alerted through email, SMS, voice calls or mobile push notifications. > > Take corrective actions from your mobile device. > > http://p.sf.net/sfu/Zoho > > _______________________________________________ > > audacity-devel mailing list > > aud...@li... > > https://lists.sourceforge.net/lists/listinfo/audacity-devel > > > > ---------------------------------------------------------------------------- -- > Comprehensive Server Monitoring with Site24x7. > Monitor 10 servers for $9/Month. > Get alerted through email, SMS, voice calls or mobile push notifications. > Take corrective actions from your mobile device. > http://p.sf.net/sfu/Zoho > _______________________________________________ > audacity-devel mailing list > aud...@li... > https://lists.sourceforge.net/lists/listinfo/audacity-devel |
|
From: Gale <ga...@au...> - 2014-10-17 14:22:57
|
I'm just adding here a P2/P3 regression bug that wx3 seems to introduce on Windows. It's no longer possible to request a second instance of Audacity (for example, by opening a file using file manager Open with) and have this passed to open a new Audacity window in the current instance. You now see only "Audacity is already running". If that's a cross-platform problem, it could mean the proposed Linux fix for "Audacity already running": ( http://bugzilla.audacityteam.org/show_bug.cgi?id=202 ) won't now work. Gale -- View this message in context: http://audacity.238276.n2.nabble.com/MSVC-2013-Yes-wxWidgets-3-0-1-Maybe-tp7564053p7564258.html Sent from the audacity-devel mailing list archive at Nabble.com. |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X