Re: [Audacity-devel] MSVC 2013 Yes. wxWidgets 3.0.1 Maybe.

[Martyn S. <mar...@gm...>]

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
>