I tried to get a VS CMake build going about a year and a half ago
without much luck.  I think though it would be nice to have it be
possible, especially if we'll get more developers interested in
compiling and working on Csound. I don't think anyone's really been
looking at WinRT, but I think it'd be nice to see Csound there and on
Win 8 Mobile too.

On Sun, Jul 21, 2013 at 3:09 PM, Richard Henninger  wrote:
> I tried this a few weeks ago so I could be better able to use the VS
> debugger better for the csound code while writing a .net bridge to csound.
>
> Mike is right on many points about the futility of doing this.
>
> The MS (the c part is c88 not c99) compiler will give you scads of errors
> when compiling csound libraries.  Here is a partial list from an excerpt of
> an earlier post:
>
> Four come to mind right away:
>
> MS C tries to encourage use of the posix secure strxxx_s functions for
> string operations to thwart buffer overflow hacks.  Error can be turned off
> by a flag, but the recommendation represents a best practice.
> It is totally unforgiving of implicit casts from void*.  For code
> readability, I agree with them.  Code clarity in open source seems
> ultra-desirable. No flag for these.
> Declaring new variables mid-codeblock confuses the compiler. [It spews crazy
> error messages once encountered]
> It won’t accept really old, deprecated library calls like open and insists
> on newer equivalents.
>
>
> namehist.c is particulary delinquent in this regard.  VS2013’s C (in beta)
> wants to be c99 compliant, maybe some of this will just evaporate with
> VS2013 re-written c compiler. [Mike’s concern about c++ stl generics should
> also evaporate as MS makes itself compliant with VC11. Although you never
> know with MS, they do talk a good line on standards compliance these days.
> We’ll just have to wait and see...]
>
> Since dealing with these is a pre-requisite to porting to WinRT which must
> use an MS compiler, cleaning this kind of this up might make a good [project
> for me to start contributing with].
>
> For now, I’d just set up the gnu environment as Mike’s article describes.
> That’s what I’ve decided to do.
>
> Richard Henninger
> richard@rghmusic.com
>
> From: Michael Gogins
> Sent: Sunday, July 21, 2013 2:41 PM
> To: Developer discussions
>
> I tried to build Csound and CsoundAC with Visual C++ about four years ago,
> and I gave up.
>
> The issue for me was that the Microsoft Standard C++ Library (STL) did not
> generate code that could be exported in shared libraries. This was a serious
> problem that prevented CsoundAC from linking into shared libraries using
> Visual C++, as CsoundAC uses std::vector and other such classes in exported
> interfaces.
>
> Aside from this the C interfaces should not, in theory, present a problem.
> However, because the Visual C++ build has not been maintained for a long
> time, there may be many minor problems.
>
> Your best bet is to create a branch in GIT for your Visual C++ build and
> modify the CMakeList.txt files to build with Visual C++ in the Microsoft
> Windows SDK console. If you get it to work, we can merge your branch back
> in.
>
> Please tell us your reason for wanting a Visual C++ build. I would not go
> down this path, myself, without a very good reason.
>
> Both the C API, and the low-level C++ api in csound.hpp, can be used from
> Visual C++ while linking with the MinGW built code in the Windows installer.
>
> In other words, if you are creating a Visual C++ project to use the Csound
> API, you should be able use the libraries and headers in the Windows
> installer with Visual C++ as long as you only reference C header files such
> as csound.h and the csound.hpp C++ header. If you find out differently,
> please let me know.
>
> At this time, the MinGW compiler is pretty even with the Visual C++ compiler
> in terms of code quality, execution speed, and probably a bit better for C++
> standards compliance.
>
> Hope this helps,
> Mike
>
>
>
>
> ===========================
> Michael Gogins
> Irreducible Productions
> http://michaelgogins.tumblr.com
> Michael dot Gogins at gmail dot com
>
>
> On Sun, Jul 21, 2013 at 1:15 PM, Stephen Kyne  wrote:
>>
>> Hi guys,
>>
>> I was wondering if anyone has or if it is supposed to be possible to
>> generate a VS2010 project file using CMake and building Csound this way?
>>
>> It is straight forward finding the necessary dependencies and generating
>> the project file but it's running into a lot of errors when I try and build.
>> Is it worth hacking around and fixing these errors or is this
>> fundamentally not going to work without serious effort?
>>
>> Thanks,
>> Stephen
>>
>>
>> ------------------------------------------------------------------------------
>> See everything from the browser to the database with AppDynamics
>> Get end-to-end visibility with application monitoring from AppDynamics
>> Isolate bottlenecks and diagnose root cause in seconds.
>> Start your free trial of AppDynamics Pro today!
>>
>> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>
>
> ------------------------------------------------------------------------------
> See everything from the browser to the database with AppDynamics
> Get end-to-end visibility with application monitoring from AppDynamics
> Isolate bottlenecks and diagnose root cause in seconds.
> Start your free trial of AppDynamics Pro today!
> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>

------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

You could use another IDE: QtCreator, CodeBlocks, Eclipse CDT.

Thanks for the report. I'm following this with interest!

On 13 September 2013 00:58, Stephen Kyne  wrote:
> Hey guys,
>
> Visual Studio 2013 RC was released there recently. It has partial support
> for C99.
> http://blogs.msdn.com/b/vcblog/archive/2013/07/19/c99-library-support-in-visual-studio-2013.aspx
>
> I've been hacking away with it and managed to build Csound. The build was
> mostly stripped down but I managed to get the xanadu.csd to compile a .wav
> file.
> So it's a start at least!
>
> The changes required were fairly minor, mostly just alterations to the
> project(s) file for libraries and some small code changes here and there.
> I had to replace some GCC atomic intrinsics with MSVC ones.
> I'm not sure the full effect of that but I guess in theory it should (and
> seems to) work.
>
> I'm hoping to get some real-time performance working next.
>
> Stephen
>
> ________________________________
> Date: Sun, 21 Jul 2013 23:48:03 -0400
> From: michael.gogins@gmail.com
> To: csound-devel@lists.sourceforge.net
>
> Subject: Re: [Cs-dev] VS2010 building from source
>
> You could use another IDE: QtCreator, CodeBlocks, Eclipse CDT.
>
> On Jul 21, 2013 7:31 PM, "Stephen Kyne"  wrote:
>
> Thanks for the replies.
>
> I mainly want to build in Visual Studio just for using the IDE itself but it
> sounds like a no go at the minute.
> Maybe something for the future.
>
> Cheers,
> Stephen
>
> ________________________________
> From: richard@rghmusic.com
> To: csound-devel@lists.sourceforge.net
> Date: Sun, 21 Jul 2013 21:15:47 +0000
> Subject: Re: [Cs-dev] VS2010 building from source
>
> Last Spring, I explored porting to WinRT using the 5.18 code base.  Really
> tough!  Once I started following in the changes you guys were putting into
> csound 6, I saw how your architectural evolutions would solve a number of
> issues I encountered.
>
> So I’ve held off until 6.0 becomes a stable base from which to rethink an
> approach.  Being patient gave me another reward: WinRT 8.1 finally provides
> the ability to feed audio streams from an algorithm as PCM rather than from
> only a file or existing audio stream.  So direct programming of COM (WASAPI)
> is no longer necessary.  Maybe MIDI will show up before long...
>
> I am pretty familiar with the issues involved in a WinRT port and would be
> happy to be a part of such an effort at some point in the future.  For now,
> I am content to explore the api from VS2012 and Win8 desktop apps via a C#
> wrapper I have.  As it stands now, the sounds created from a desktop-style
> app are trouble free on a Surface Pro - you just can’t create apps to
> distribute from the Windows app store.  It’s an acceptable compromise to me
> for now.
>
> Richard Henninger
> richard@rghmusic.com
>
> From: Steven Yi
> Sent: Sunday, July 21, 2013 4:27 PM
> To: Developer discussions
>
> I tried to get a VS CMake build going about a year and a half ago
> without much luck.  I think though it would be nice to have it be
> possible, especially if we'll get more developers interested in
> compiling and working on Csound. I don't think anyone's really been
> looking at WinRT, but I think it'd be nice to see Csound there and on
> Win 8 Mobile too.
>
> On Sun, Jul 21, 2013 at 3:09 PM, Richard Henninger 
> wrote:
>> I tried this a few weeks ago so I could be better able to use the VS
>> debugger better for the csound code while writing a .net bridge to csound.
>>
>> Mike is right on many points about the futility of doing this.
>>
>> The MS (the c part is c88 not c99) compiler will give you scads of errors
>> when compiling csound libraries.  Here is a partial list from an excerpt
>> of
>> an earlier post:
>>
>> Four come to mind right away:
>>
>> MS C tries to encourage use of the posix secure strxxx_s functions for
>> string operations to thwart buffer overflow hacks.  Error can be turned
>> off
>> by a flag, but the recommendation represents a best practice.
>> It is totally unforgiving of implicit casts from void*.  For code
>> readability, I agree with them.  Code clarity in open source seems
>> ultra-desirable. No flag for these.
>> Declaring new variables mid-codeblock confuses the compiler. [It spews
>> crazy
>> error messages once encountered]
>> It won’t accept really old, deprecated library calls like open and insists
>> on newer equivalents.
>>
>>
>> namehist.c is particulary delinquent in this regard.  VS2013’s C (in beta)
>> wants to be c99 compliant, maybe some of this will just evaporate with
>> VS2013 re-written c compiler. [Mike’s concern about c++ stl generics
>> should
>> also evaporate as MS makes itself compliant with VC11. Although you never
>> know with MS, they do talk a good line on standards compliance these days.
>> We’ll just have to wait and see...]
>>
>> Since dealing with these is a pre-requisite to porting to WinRT which must
>> use an MS compiler, cleaning this kind of this up might make a good
>> [project
>> for me to start contributing with].
>>
>> For now, I’d just set up the gnu environment as Mike’s article describes.
>> That’s what I’ve decided to do.
>>
>> Richard Henninger
>> richard@rghmusic.com
>>
>> From: Michael Gogins
>> Sent: Sunday, July 21, 2013 2:41 PM
>> To: Developer discussions
>>
>> I tried to build Csound and CsoundAC with Visual C++ about four years ago,
>> and I gave up.
>>
>> The issue for me was that the Microsoft Standard C++ Library (STL) did not
>> generate code that could be exported in shared libraries. This was a
>> serious
>> problem that prevented CsoundAC from linking into shared libraries using
>> Visual C++, as CsoundAC uses std::vector and other such classes in
>> exported
>> interfaces.
>>
>> Aside from this the C interfaces should not, in theory, present a problem.
>> However, because the Visual C++ build has not been maintained for a long
>> time, there may be many minor problems.
>>
>> Your best bet is to create a branch in GIT for your Visual C++ build and
>> modify the CMakeList.txt files to build with Visual C++ in the Microsoft
>> Windows SDK console. If you get it to work, we can merge your branch back
>> in.
>>
>> Please tell us your reason for wanting a Visual C++ build. I would not go
>> down this path, myself, without a very good reason.
>>
>> Both the C API, and the low-level C++ api in csound.hpp, can be used from
>> Visual C++ while linking with the MinGW built code in the Windows
>> installer.
>>
>> In other words, if you are creating a Visual C++ project to use the Csound
>> API, you should be able use the libraries and headers in the Windows
>> installer with Visual C++ as long as you only reference C header files
>> such
>> as csound.h and the csound.hpp C++ header. If you find out differently,
>> please let me know.
>>
>> At this time, the MinGW compiler is pretty even with the Visual C++
>> compiler
>> in terms of code quality, execution speed, and probably a bit better for
>> C++
>> standards compliance.
>>
>> Hope this helps,
>> Mike
>>
>>
>>
>>
>> ===========================
>> Michael Gogins
>> Irreducible Productions
>> http://michaelgogins.tumblr.com
>> Michael dot Gogins at gmail dot com
>>
>>
>> On Sun, Jul 21, 2013 at 1:15 PM, Stephen Kyne  wrote:
>>>
>>> Hi guys,
>>>
>>> I was wondering if anyone has or if it is supposed to be possible to
>>> generate a VS2010 project file using CMake and building Csound this way?
>>>
>>> It is straight forward finding the necessary dependencies and generating
>>> the project file but it's running into a lot of errors when I try and
>>> build.
>>> Is it worth hacking around and fixing these errors or is this
>>> fundamentally not going to work without serious effort?
>>>
>>> Thanks,
>>> Stephen
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> See everything from the browser to the database with AppDynamics
>>> Get end-to-end visibility with application monitoring from AppDynamics
>>> Isolate bottlenecks and diagnose root cause in seconds.
>>> Start your free trial of AppDynamics Pro today!
>>>
>>>
>>> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> See everything from the browser to the database with AppDynamics
>> Get end-to-end visibility with application monitoring from AppDynamics
>> Isolate bottlenecks and diagnose root cause in seconds.
>> Start your free trial of AppDynamics Pro today!
>>
>> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>
> ------------------------------------------------------------------------------
> See everything from the browser to the database with AppDynamics
> Get end-to-end visibility with application monitoring from AppDynamics
> Isolate bottlenecks and diagnose root cause in seconds.
> Start your free trial of AppDynamics Pro today!
> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
> ------------------------------------------------------------------------------
> See everything from the browser to the database with AppDynamics Get
> end-to-end visibility with application monitoring from AppDynamics Isolate
> bottlenecks and diagnose root cause in seconds. Start your free trial of
> AppDynamics Pro today!
> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
> _______________________________________________ Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
> ------------------------------------------------------------------------------
> See everything from the browser to the database with AppDynamics
> Get end-to-end visibility with application monitoring from AppDynamics
> Isolate bottlenecks and diagnose root cause in seconds.
> Start your free trial of AppDynamics Pro today!
> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
> ------------------------------------------------------------------------------
> See everything from the browser to the database with AppDynamics Get
> end-to-end visibility with application monitoring from AppDynamics Isolate
> bottlenecks and diagnose root cause in seconds. Start your free trial of
> AppDynamics Pro today!
> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
> _______________________________________________ Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
> ------------------------------------------------------------------------------
> How ServiceNow helps IT people transform IT departments:
> 1. Consolidate legacy IT systems to a single system of record for IT
> 2. Standardize and globalize service processes across IT
> 3. Implement zero-touch automation to replace manual, redundant tasks
> http://pubads.g.doubleclick.net/gampad/clk?id=51271111&iu=/4140/ostg.clktrk
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>

------------------------------------------------------------------------------
How ServiceNow helps IT people transform IT departments:
1. Consolidate legacy IT systems to a single system of record for IT
2. Standardize and globalize service processes across IT
3. Implement zero-touch automation to replace manual, redundant tasks
http://pubads.g.doubleclick.net/gampad/clk?id=51271111&iu=/4140/ostg.clktrk
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Hi Stephen,

Just wanted to say this all sounds great and I'm glad you're looking
into this. Thanks!

steven

On Sun, Sep 15, 2013 at 11:48 AM, Stephen Kyne  wrote:
> Hi Andrés,
>
> Yes the project generated from CMake is almost fully correct. Just some
> edits to a few CMakeLists.txt files will be needed to load some missing
> libraries.
> I'm not building all features yet so there may be more changes as time goes
> by but the csound core is working well.
>
> Stephen
>
> ________________________________
> Date: Sat, 14 Sep 2013 19:28:55 -0700
> From: mantaraya36@gmail.com
>
> To: csound-devel@lists.sourceforge.net
> Subject: Re: [Cs-dev] VS2010 building from source
>
> Hi,
>
> Do you think the VS porject generated by cmake is useful? Ideally this work
> should go in the CMakeLists.txt file rather than a separate VS project.
>
> Cheers,
> Andrés
>
>
> On Fri, Sep 13, 2013 at 11:46 AM, Stephen Kyne  wrote:
>
> Cool, any help would be appreciated. I'm still getting to grips with the
> Csound code base and most of my code changes are probably far from elegant.
>
> As far as I know, the Release Candidate is required unless there is an
> update to the preview.
> I know I had tried before and I was getting all kinds of errors from missing
> lib functions as you described.
>
> In the meantime, the portaudio module is working so real time audio is
> possible.
> There are still some elements of MSVC build that will be need to be fixed
> though.
> I saw a crash relating to heap corruptiong due to vfprintf use but these
> errors are relatively easy to fix with the debugger.
>
> Stephen
>
> ________________________________
> From: richard@rghmusic.com
> To: csound-devel@lists.sourceforge.net
> Date: Fri, 13 Sep 2013 17:03:15 +0000
>
> Subject: Re: [Cs-dev] VS2010 building from source
>
> Me too.  I tried with VS2012 and decided that too much of the code depended
> on liberties that C99 permitted that C88 did not and gave up - thinking the
> source would need too much rework to bother.
>
> I have VS2013 preview on an 8.1 machine so I’d be interested in sharing the
> workload to speed this along.  Perhaps there should be a git branch to hold
> the project files and changes for this?
>
> My interest is access to MS debugging tools while using .net front-ends and
> for ultimately targeting WinRT getting csound back closer to its original
> goal of being multiplatform.
>
> Richard Henninger
> richard@rghmusic.com
>
> From: Rory Walsh
> Sent: Friday, September 13, 2013 12:21 PM
> To: Developer discussions
>
> Thanks for the report. I'm following this with interest!
>
> On 13 September 2013 00:58, Stephen Kyne  wrote:
>> Hey guys,
>>
>> Visual Studio 2013 RC was released there recently. It has partial support
>> for C99.
>>
>> http://blogs.msdn.com/b/vcblog/archive/2013/07/19/c99-library-support-in-visual-studio-2013.aspx
>>
>> I've been hacking away with it and managed to build Csound. The build was
>> mostly stripped down but I managed to get the xanadu.csd to compile a .wav
>> file.
>> So it's a start at least!
>>
>> The changes required were fairly minor, mostly just alterations to the
>> project(s) file for libraries and some small code changes here and there.
>> I had to replace some GCC atomic intrinsics with MSVC ones.
>> I'm not sure the full effect of that but I guess in theory it should (and
>> seems to) work.
>>
>> I'm hoping to get some real-time performance working next.
>>
>> Stephen
>>
>> ________________________________
>> Date: Sun, 21 Jul 2013 23:48:03 -0400
>> From: michael.gogins@gmail.com
>> To: csound-devel@lists.sourceforge.net
>>
>> Subject: Re: [Cs-dev] VS2010 building from source
>>
>> You could use another IDE: QtCreator, CodeBlocks, Eclipse CDT.
>>
>> On Jul 21, 2013 7:31 PM, "Stephen Kyne"  wrote:
>>
>> Thanks for the replies.
>>
>> I mainly want to build in Visual Studio just for using the IDE itself but
>> it
>> sounds like a no go at the minute.
>> Maybe something for the future.
>>
>> Cheers,
>> Stephen
>>
>> ________________________________
>> From: richard@rghmusic.com
>> To: csound-devel@lists.sourceforge.net
>> Date: Sun, 21 Jul 2013 21:15:47 +0000
>> Subject: Re: [Cs-dev] VS2010 building from source
>>
>> Last Spring, I explored porting to WinRT using the 5.18 code base.  Really
>> tough!  Once I started following in the changes you guys were putting into
>> csound 6, I saw how your architectural evolutions would solve a number of
>> issues I encountered.
>>
>> So I’ve held off until 6.0 becomes a stable base from which to rethink an
>> approach.  Being patient gave me another reward: WinRT 8.1 finally
>> provides
>> the ability to feed audio streams from an algorithm as PCM rather than
>> from
>> only a file or existing audio stream.  So direct programming of COM
>> (WASAPI)
>> is no longer necessary.  Maybe MIDI will show up before long...
>>
>> I am pretty familiar with the issues involved in a WinRT port and would be
>> happy to be a part of such an effort at some point in the future.  For
>> now,
>> I am content to explore the api from VS2012 and Win8 desktop apps via a C#
>> wrapper I have.  As it stands now, the sounds created from a desktop-style
>> app are trouble free on a Surface Pro - you just can’t create apps to
>> distribute from the Windows app store.  It’s an acceptable compromise to
>> me
>> for now.
>>
>> Richard Henninger
>> richard@rghmusic.com
>>
>> From: Steven Yi
>> Sent: Sunday, July 21, 2013 4:27 PM
>> To: Developer discussions
>>
>> I tried to get a VS CMake build going about a year and a half ago
>> without much luck.  I think though it would be nice to have it be
>> possible, especially if we'll get more developers interested in
>> compiling and working on Csound. I don't think anyone's really been
>> looking at WinRT, but I think it'd be nice to see Csound there and on
>> Win 8 Mobile too.
>>
>> On Sun, Jul 21, 2013 at 3:09 PM, Richard Henninger 
>> wrote:
>>> I tried this a few weeks ago so I could be better able to use the VS
>>> debugger better for the csound code while writing a .net bridge to
>>> csound.
>>>
>>> Mike is right on many points about the futility of doing this.
>>>
>>> The MS (the c part is c88 not c99) compiler will give you scads of errors
>>> when compiling csound libraries.  Here is a partial list from an excerpt
>>> of
>>> an earlier post:
>>>
>>> Four come to mind right away:
>>>
>>> MS C tries to encourage use of the posix secure strxxx_s functions for
>>> string operations to thwart buffer overflow hacks.  Error can be turned
>>> off
>>> by a flag, but the recommendation represents a best practice.
>>> It is totally unforgiving of implicit casts from void*.  For code
>>> readability, I agree with them.  Code clarity in open source seems
>>> ultra-desirable. No flag for these.
>>> Declaring new variables mid-codeblock confuses the compiler. [It spews
>>> crazy
>>> error messages once encountered]
>>> It won’t accept really old, deprecated library calls like open and
>>> insists
>>> on newer equivalents.
>>>
>>>
>>> namehist.c is particulary delinquent in this regard.  VS2013’s C (in
>>> beta)
>>> wants to be c99 compliant, maybe some of this will just evaporate with
>>> VS2013 re-written c compiler. [Mike’s concern about c++ stl generics
>>> should
>>> also evaporate as MS makes itself compliant with VC11. Although you never
>>> know with MS, they do talk a good line on standards compliance these
>>> days.
>>> We’ll just have to wait and see...]
>>>
>>> Since dealing with these is a pre-requisite to porting to WinRT which
>>> must
>>> use an MS compiler, cleaning this kind of this up might make a good
>>> [project
>>> for me to start contributing with].
>>>
>>> For now, I’d just set up the gnu environment as Mike’s article describes.
>>> That’s what I’ve decided to do.
>>>
>>> Richard Henninger
>>> richard@rghmusic.com
>>>
>>> From: Michael Gogins
>>> Sent: Sunday, July 21, 2013 2:41 PM
>>> To: Developer discussions
>>>
>>> I tried to build Csound and CsoundAC with Visual C++ about four years
>>> ago,
>>> and I gave up.
>>>
>>> The issue for me was that the Microsoft Standard C++ Library (STL) did
>>> not
>>> generate code that could be exported in shared libraries. This was a
>>> serious
>>> problem that prevented CsoundAC from linking into shared libraries using
>>> Visual C++, as CsoundAC uses std::vector and other such classes in
>>> exported
>>> interfaces.
>>>
>>> Aside from this the C interfaces should not, in theory, present a
>>> problem.
>>> However, because the Visual C++ build has not been maintained for a long
>>> time, there may be many minor problems.
>>>
>>> Your best bet is to create a branch in GIT for your Visual C++ build and
>>> modify the CMakeList.txt files to build with Visual C++ in the Microsoft
>>> Windows SDK console. If you get it to work, we can merge your branch back
>>> in.
>>>
>>> Please tell us your reason for wanting a Visual C++ build. I would not go
>>> down this path, myself, without a very good reason.
>>>
>>> Both the C API, and the low-level C++ api in csound.hpp, can be used from
>>> Visual C++ while linking with the MinGW built code in the Windows
>>> installer.
>>>
>>> In other words, if you are creating a Visual C++ project to use the
>>> Csound
>>> API, you should be able use the libraries and headers in the Windows
>>> installer with Visual C++ as long as you only reference C header files
>>> such
>>> as csound.h and the csound.hpp C++ header. If you find out differently,
>>> please let me know.
>>>
>>> At this time, the MinGW compiler is pretty even with the Visual C++
>>> compiler
>>> in terms of code quality, execution speed, and probably a bit better for
>>> C++
>>> standards compliance.
>>>
>>> Hope this helps,
>>> Mike
>>>
>>>
>>>
>>>
>>> ===========================
>>> Michael Gogins
>>> Irreducible Productions
>>> http://michaelgogins.tumblr.com
>>> Michael dot Gogins at gmail dot com
>>>
>>>
>>> On Sun, Jul 21, 2013 at 1:15 PM, Stephen Kyne  wrote:
>>>>
>>>> Hi guys,
>>>>
>>>> I was wondering if anyone has or if it is supposed to be possible to
>>>> generate a VS2010 project file using CMake and building Csound this way?
>>>>
>>>> It is straight forward finding the necessary dependencies and generating
>>>> the project file but it's running into a lot of errors when I try and
>>>> build.
>>>> Is it worth hacking around and fixing these errors or is this
>>>> fundamentally not going to work without serious effort?
>>>>
>>>> Thanks,
>>>> Stephen
>>>>
>>>>
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> See everything from the browser to the database with AppDynamics
>>>> Get end-to-end visibility with application monitoring from AppDynamics
>>>> Isolate bottlenecks and diagnose root cause in seconds.
>>>> Start your free trial of AppDynamics Pro today!
>>>>
>>>>
>>>>
>>>> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
>>>> _______________________________________________
>>>> Csound-devel mailing list
>>>> Csound-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>
>>>
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> See everything from the browser to the database with AppDynamics
>>> Get end-to-end visibility with application monitoring from AppDynamics
>>> Isolate bottlenecks and diagnose root cause in seconds.
>>> Start your free trial of AppDynamics Pro today!
>>>
>>>
>>> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>
>>
>> ------------------------------------------------------------------------------
>> See everything from the browser to the database with AppDynamics
>> Get end-to-end visibility with application monitoring from AppDynamics
>> Isolate bottlenecks and diagnose root cause in seconds.
>> Start your free trial of AppDynamics Pro today!
>>
>> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>>
>> ------------------------------------------------------------------------------
>> See everything from the browser to the database with AppDynamics Get
>> end-to-end visibility with application monitoring from AppDynamics Isolate
>> bottlenecks and diagnose root cause in seconds. Start your free trial of
>> AppDynamics Pro today!
>>
>> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
>> _______________________________________________ Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>>
>> ------------------------------------------------------------------------------
>> See everything from the browser to the database with AppDynamics
>> Get end-to-end visibility with application monitoring from AppDynamics
>> Isolate bottlenecks and diagnose root cause in seconds.
>> Start your free trial of AppDynamics Pro today!
>>
>> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>>
>>
>> ------------------------------------------------------------------------------
>> See everything from the browser to the database with AppDynamics Get
>> end-to-end visibility with application monitoring from AppDynamics Isolate
>> bottlenecks and diagnose root cause in seconds. Start your free trial of
>> AppDynamics Pro today!
>>
>> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
>> _______________________________________________ Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>>
>> ------------------------------------------------------------------------------
>> How ServiceNow helps IT people transform IT departments:
>> 1. Consolidate legacy IT systems to a single system of record for IT
>> 2. Standardize and globalize service processes across IT
>> 3. Implement zero-touch automation to replace manual, redundant tasks
>>
>> http://pubads.g.doubleclick.net/gampad/clk?id=51271111&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>
> ------------------------------------------------------------------------------
> How ServiceNow helps IT people transform IT departments:
> 1. Consolidate legacy IT systems to a single system of record for IT
> 2. Standardize and globalize service processes across IT
> 3. Implement zero-touch automation to replace manual, redundant tasks
> http://pubads.g.doubleclick.net/gampad/clk?id=51271111&iu=/4140/ostg.clktrk
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
> ------------------------------------------------------------------------------
> How ServiceNow helps IT people transform IT departments: 1. Consolidate
> legacy IT systems to a single system of record for IT 2. Standardize and
> globalize service processes across IT 3. Implement zero-touch automation to
> replace manual, redundant tasks
> http://pubads.g.doubleclick.net/gampad/clk?id=51271111&iu=/4140/ostg.clktrk
> _______________________________________________ Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
> ------------------------------------------------------------------------------
> How ServiceNow helps IT people transform IT departments:
> 1. Consolidate legacy IT systems to a single system of record for IT
> 2. Standardize and globalize service processes across IT
> 3. Implement zero-touch automation to replace manual, redundant tasks
> http://pubads.g.doubleclick.net/gampad/clk?id=51271111&iu=/4140/ostg.clktrk
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
>
> ------------------------------------------------------------------------------
> LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99! 1,500+
> hours of tutorials including VisualStudio 2012, Windows 8, SharePoint 2013,
> SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes
> Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/22/13.
> http://pubads.g.doubleclick.net/gampad/clk?id=64545871&iu=/4140/ostg.clktrk
>
> _______________________________________________ Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
> ------------------------------------------------------------------------------
> LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99!
> 1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint
> 2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack
> includes
> Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/22/13.
> http://pubads.g.doubleclick.net/gampad/clk?id=64545871&iu=/4140/ostg.clktrk
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>

------------------------------------------------------------------------------
LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99!
1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint
2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes
Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/22/13. 
http://pubads.g.doubleclick.net/gampad/clk?id=64545871&iu=/4140/ostg.clktrk
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Hi Stephen and Richard,

If you'd like, I don't think anyone would mind adding you two to the
devs list for Csound.  You'd be welcome to create a feature branch off
the develop branch (using git-flow).  Another option is that you could
use Sourceforge's fork system (if you see on
https://sourceforge.net/p/csound/csound6-git/ci/master/tree/ there is
an option to fork). You could then do pull requests from there. I
found SF's fork/pull-request system a bit awkward compared to
bitbucket and github though.

steven

On Mon, Sep 16, 2013 at 4:51 PM, Richard Henninger  wrote:
> Hi Stephen,
>
> We should probably make a separate “native windows build” branch off of
> “develop” especially since the cMakeList files are still being fine tuned
> for the mingw windows build.  We shouldn’t interfere with that until it (and
> the rest of csound6) is stable.
>
> Do you have “write” access to the project yet? I don’t.  I’ve been holding
> off on my request for that until csound6 had become reasonably quiescent.
> Still, using a separate git branch should keep this work out of the way of
> the mainstream.  Down the road, I worry about built in assumption in the
> codebase about threads, library and other compatibility issues - but
> resolving those is the whole point eventually.
>
> My original plan has been to become an active developer after attending the
> relevant sessions at the conference next month and confirming that I had a
> legitimate mingw build environment for testing changes ahead of committing
> code.  Are you attending?
>
>
> Richard Henninger
> richard@rghmusic.com
>
> From: Stephen Kyne
> Sent: Monday, September 16, 2013 4:21 PM
> To: Developer discussions
>
> Hey Richard,
>
> Well I switched my Csound branch to "develop" from the main one recently and
> there was a few more errors but nothing major.
> I'm currently trying to fix the missing libraries in the cMakeLists files (I
> had just added them to the sln file for testing).
> I'm afraid it's a bit new to me so it's taking a little bit of time to do it
> nicely.
>
> Once that is finished though, there should be a version of Csound that will
> be building successfully.
> I guess from there we can add additional build features and fix the errors
> as they happen.
>
> If you want to make a branch that sounds fine with me.
>
> Stephen
>
> ________________________________
> From: richard@rghmusic.com
> To: csound-devel@lists.sourceforge.net
> Date: Mon, 16 Sep 2013 16:25:10 +0000
> Subject: Re: [Cs-dev] VS2010 building from source
>
> Stephen,
>
> Your were right about VS2013 Preview.  Also, VS2013 RC won’t work over
> Win8.1 Preview.
>
> So, over the weekend, I hosed my 8.1 box back to 8.0 and loaded the VS2013
> RC (and git) and am ready to play.  How do I catch up to the point where you
> are currently?  Shall we make a git branch so we can keep track of, share
> and merge what we alter?
>
>
> Richard Henninger
> richard@rghmusic.com
>
> From: Stephen Kyne
> Sent: Sunday, September 15, 2013 11:48 AM
> To: Developer discussions
>
> Hi Andrés,
>
> Yes the project generated from CMake is almost fully correct. Just some
> edits to a few CMakeLists.txt files will be needed to load some missing
> libraries.
> I'm not building all features yet so there may be more changes as time goes
> by but the csound core is working well.
>
> Stephen
>
> ________________________________
> Date: Sat, 14 Sep 2013 19:28:55 -0700
> From: mantaraya36@gmail.com
> To: csound-devel@lists.sourceforge.net
> Subject: Re: [Cs-dev] VS2010 building from source
>
> Hi,
>
> Do you think the VS porject generated by cmake is useful? Ideally this work
> should go in the CMakeLists.txt file rather than a separate VS project.
>
> Cheers,
> Andrés
>
>
> On Fri, Sep 13, 2013 at 11:46 AM, Stephen Kyne  wrote:
>
> Cool, any help would be appreciated. I'm still getting to grips with the
> Csound code base and most of my code changes are probably far from elegant.
>
> As far as I know, the Release Candidate is required unless there is an
> update to the preview.
> I know I had tried before and I was getting all kinds of errors from missing
> lib functions as you described.
>
> In the meantime, the portaudio module is working so real time audio is
> possible.
> There are still some elements of MSVC build that will be need to be fixed
> though.
> I saw a crash relating to heap corruptiong due to vfprintf use but these
> errors are relatively easy to fix with the debugger.
>
> Stephen
>
> ________________________________
> From: richard@rghmusic.com
> To: csound-devel@lists.sourceforge.net
> Date: Fri, 13 Sep 2013 17:03:15 +0000
>
> Subject: Re: [Cs-dev] VS2010 building from source
>
> Me too.  I tried with VS2012 and decided that too much of the code depended
> on liberties that C99 permitted that C88 did not and gave up - thinking the
> source would need too much rework to bother.
>
> I have VS2013 preview on an 8.1 machine so I’d be interested in sharing the
> workload to speed this along.  Perhaps there should be a git branch to hold
> the project files and changes for this?
>
> My interest is access to MS debugging tools while using .net front-ends and
> for ultimately targeting WinRT getting csound back closer to its original
> goal of being multiplatform.
>
> Richard Henninger
> richard@rghmusic.com
>
> From: Rory Walsh
> Sent: Friday, September 13, 2013 12:21 PM
> To: Developer discussions
>
> Thanks for the report. I'm following this with interest!
>
> On 13 September 2013 00:58, Stephen Kyne  wrote:
>> Hey guys,
>>
>> Visual Studio 2013 RC was released there recently. It has partial support
>> for C99.
>>
>> http://blogs.msdn.com/b/vcblog/archive/2013/07/19/c99-library-support-in-visual-studio-2013.aspx
>>
>> I've been hacking away with it and managed to build Csound. The build was
>> mostly stripped down but I managed to get the xanadu.csd to compile a .wav
>> file.
>> So it's a start at least!
>>
>> The changes required were fairly minor, mostly just alterations to the
>> project(s) file for libraries and some small code changes here and there.
>> I had to replace some GCC atomic intrinsics with MSVC ones.
>> I'm not sure the full effect of that but I guess in theory it should (and
>> seems to) work.
>>
>> I'm hoping to get some real-time performance working next.
>>
>> Stephen
>>
>> ________________________________
>> Date: Sun, 21 Jul 2013 23:48:03 -0400
>> From: michael.gogins@gmail.com
>> To: csound-devel@lists.sourceforge.net
>>
>> Subject: Re: [Cs-dev] VS2010 building from source
>>
>> You could use another IDE: QtCreator, CodeBlocks, Eclipse CDT.
>>
>> On Jul 21, 2013 7:31 PM, "Stephen Kyne"  wrote:
>>
>> Thanks for the replies.
>>
>> I mainly want to build in Visual Studio just for using the IDE itself but
>> it
>> sounds like a no go at the minute.
>> Maybe something for the future.
>>
>> Cheers,
>> Stephen
>>
>> ________________________________
>> From: richard@rghmusic.com
>> To: csound-devel@lists.sourceforge.net
>> Date: Sun, 21 Jul 2013 21:15:47 +0000
>> Subject: Re: [Cs-dev] VS2010 building from source
>>
>> Last Spring, I explored porting to WinRT using the 5.18 code base.  Really
>> tough!  Once I started following in the changes you guys were putting into
>> csound 6, I saw how your architectural evolutions would solve a number of
>> issues I encountered.
>>
>> So I’ve held off until 6.0 becomes a stable base from which to rethink an
>> approach.  Being patient gave me another reward: WinRT 8.1 finally
>> provides
>> the ability to feed audio streams from an algorithm as PCM rather than
>> from
>> only a file or existing audio stream.  So direct programming of COM
>> (WASAPI)
>> is no longer necessary.  Maybe MIDI will show up before long...
>>
>> I am pretty familiar with the issues involved in a WinRT port and would be
>> happy to be a part of such an effort at some point in the future.  For
>> now,
>> I am content to explore the api from VS2012 and Win8 desktop apps via a C#
>> wrapper I have.  As it stands now, the sounds created from a desktop-style
>> app are trouble free on a Surface Pro - you just can’t create apps to
>> distribute from the Windows app store.  It’s an acceptable compromise to
>> me
>> for now.
>>
>> Richard Henninger
>> richard@rghmusic.com
>>
>> From: Steven Yi
>> Sent: Sunday, July 21, 2013 4:27 PM
>> To: Developer discussions
>>
>> I tried to get a VS CMake build going about a year and a half ago
>> without much luck.  I think though it would be nice to have it be
>> possible, especially if we'll get more developers interested in
>> compiling and working on Csound. I don't think anyone's really been
>> looking at WinRT, but I think it'd be nice to see Csound there and on
>> Win 8 Mobile too.
>>
>> On Sun, Jul 21, 2013 at 3:09 PM, Richard Henninger 
>> wrote:
>>> I tried this a few weeks ago so I could be better able to use the VS
>>> debugger better for the csound code while writing a .net bridge to
>>> csound.
>>>
>>> Mike is right on many points about the futility of doing this.
>>>
>>> The MS (the c part is c88 not c99) compiler will give you scads of errors
>>> when compiling csound libraries.  Here is a partial list from an excerpt
>>> of
>>> an earlier post:
>>>
>>> Four come to mind right away:
>>>
>>> MS C tries to encourage use of the posix secure strxxx_s functions for
>>> string operations to thwart buffer overflow hacks.  Error can be turned
>>> off
>>> by a flag, but the recommendation represents a best practice.
>>> It is totally unforgiving of implicit casts from void*.  For code
>>> readability, I agree with them.  Code clarity in open source seems
>>> ultra-desirable. No flag for these.
>>> Declaring new variables mid-codeblock confuses the compiler. [It spews
>>> crazy
>>> error messages once encountered]
>>> It won’t accept really old, deprecated library calls like open and
>>> insists
>>> on newer equivalents.
>>>
>>>
>>> namehist.c is particulary delinquent in this regard.  VS2013’s C (in
>>> beta)
>>> wants to be c99 compliant, maybe some of this will just evaporate with
>>> VS2013 re-written c compiler. [Mike’s concern about c++ stl generics
>>> should
>>> also evaporate as MS makes itself compliant with VC11. Although you never
>>> know with MS, they do talk a good line on standards compliance these
>>> days.
>>> We’ll just have to wait and see...]
>>>
>>> Since dealing with these is a pre-requisite to porting to WinRT which
>>> must
>>> use an MS compiler, cleaning this kind of this up might make a good
>>> [project
>>> for me to start contributing with].
>>>
>>> For now, I’d just set up the gnu environment as Mike’s article describes.
>>> That’s what I’ve decided to do.
>>>
>>> Richard Henninger
>>> richard@rghmusic.com
>>>
>>> From: Michael Gogins
>>> Sent: Sunday, July 21, 2013 2:41 PM
>>> To: Developer discussions
>>>
>>> I tried to build Csound and CsoundAC with Visual C++ about four years
>>> ago,
>>> and I gave up.
>>>
>>> The issue for me was that the Microsoft Standard C++ Library (STL) did
>>> not
>>> generate code that could be exported in shared libraries. This was a
>>> serious
>>> problem that prevented CsoundAC from linking into shared libraries using
>>> Visual C++, as CsoundAC uses std::vector and other such classes in
>>> exported
>>> interfaces.
>>>
>>> Aside from this the C interfaces should not, in theory, present a
>>> problem.
>>> However, because the Visual C++ build has not been maintained for a long
>>> time, there may be many minor problems.
>>>
>>> Your best bet is to create a branch in GIT for your Visual C++ build and
>>> modify the CMakeList.txt files to build with Visual C++ in the Microsoft
>>> Windows SDK console. If you get it to work, we can merge your branch back
>>> in.
>>>
>>> Please tell us your reason for wanting a Visual C++ build. I would not go
>>> down this path, myself, without a very good reason.
>>>
>>> Both the C API, and the low-level C++ api in csound.hpp, can be used from
>>> Visual C++ while linking with the MinGW built code in the Windows
>>> installer.
>>>
>>> In other words, if you are creating a Visual C++ project to use the
>>> Csound
>>> API, you should be able use the libraries and headers in the Windows
>>> installer with Visual C++ as long as you only reference C header files
>>> such
>>> as csound.h and the csound.hpp C++ header. If you find out differently,
>>> please let me know.
>>>
>>> At this time, the MinGW compiler is pretty even with the Visual C++
>>> compiler
>>> in terms of code quality, execution speed, and probably a bit better for
>>> C++
>>> standards compliance.
>>>
>>> Hope this helps,
>>> Mike
>>>
>>>
>>>
>>>
>>> ===========================
>>> Michael Gogins
>>> Irreducible Productions
>>> http://michaelgogins.tumblr.com
>>> Michael dot Gogins at gmail dot com
>>>
>>>
>>> On Sun, Jul 21, 2013 at 1:15 PM, Stephen Kyne  wrote:
>>>>
>>>> Hi guys,
>>>>
>>>> I was wondering if anyone has or if it is supposed to be possible to
>>>> generate a VS2010 project file using CMake and building Csound this way?
>>>>
>>>> It is straight forward finding the necessary dependencies and generating
>>>> the project file but it's running into a lot of errors when I try and
>>>> build.
>>>> Is it worth hacking around and fixing these errors or is this
>>>> fundamentally not going to work without serious effort?
>>>>
>>>> Thanks,
>>>> Stephen
>>>>
>>>>
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> See everything from the browser to the database with AppDynamics
>>>> Get end-to-end visibility with application monitoring from AppDynamics
>>>> Isolate bottlenecks and diagnose root cause in seconds.
>>>> Start your free trial of AppDynamics Pro today!
>>>>
>>>>
>>>>
>>>> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
>>>> _______________________________________________
>>>> Csound-devel mailing list
>>>> Csound-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>
>>>
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> See everything from the browser to the database with AppDynamics
>>> Get end-to-end visibility with application monitoring from AppDynamics
>>> Isolate bottlenecks and diagnose root cause in seconds.
>>> Start your free trial of AppDynamics Pro today!
>>>
>>>
>>> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>
>>
>> ------------------------------------------------------------------------------
>> See everything from the browser to the database with AppDynamics
>> Get end-to-end visibility with application monitoring from AppDynamics
>> Isolate bottlenecks and diagnose root cause in seconds.
>> Start your free trial of AppDynamics Pro today!
>>
>> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>>
>> ------------------------------------------------------------------------------
>> See everything from the browser to the database with AppDynamics Get
>> end-to-end visibility with application monitoring from AppDynamics Isolate
>> bottlenecks and diagnose root cause in seconds. Start your free trial of
>> AppDynamics Pro today!
>>
>> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
>> _______________________________________________ Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>>
>> ------------------------------------------------------------------------------
>> See everything from the browser to the database with AppDynamics
>> Get end-to-end visibility with application monitoring from AppDynamics
>> Isolate bottlenecks and diagnose root cause in seconds.
>> Start your free trial of AppDynamics Pro today!
>>
>> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>>
>>
>> ------------------------------------------------------------------------------
>> See everything from the browser to the database with AppDynamics Get
>> end-to-end visibility with application monitoring from AppDynamics Isolate
>> bottlenecks and diagnose root cause in seconds. Start your free trial of
>> AppDynamics Pro today!
>>
>> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
>> _______________________________________________ Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>>
>> ------------------------------------------------------------------------------
>> How ServiceNow helps IT people transform IT departments:
>> 1. Consolidate legacy IT systems to a single system of record for IT
>> 2. Standardize and globalize service processes across IT
>> 3. Implement zero-touch automation to replace manual, redundant tasks
>>
>> http://pubads.g.doubleclick.net/gampad/clk?id=51271111&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>
> ------------------------------------------------------------------------------
> How ServiceNow helps IT people transform IT departments:
> 1. Consolidate legacy IT systems to a single system of record for IT
> 2. Standardize and globalize service processes across IT
> 3. Implement zero-touch automation to replace manual, redundant tasks
> http://pubads.g.doubleclick.net/gampad/clk?id=51271111&iu=/4140/ostg.clktrk
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
> ------------------------------------------------------------------------------
> How ServiceNow helps IT people transform IT departments: 1. Consolidate
> legacy IT systems to a single system of record for IT 2. Standardize and
> globalize service processes across IT 3. Implement zero-touch automation to
> replace manual, redundant tasks
> http://pubads.g.doubleclick.net/gampad/clk?id=51271111&iu=/4140/ostg.clktrk
> _______________________________________________ Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
> ------------------------------------------------------------------------------
> How ServiceNow helps IT people transform IT departments:
> 1. Consolidate legacy IT systems to a single system of record for IT
> 2. Standardize and globalize service processes across IT
> 3. Implement zero-touch automation to replace manual, redundant tasks
> http://pubads.g.doubleclick.net/gampad/clk?id=51271111&iu=/4140/ostg.clktrk
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
>
> ------------------------------------------------------------------------------
> LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99! 1,500+
> hours of tutorials including VisualStudio 2012, Windows 8, SharePoint 2013,
> SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes
> Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/22/13.
> http://pubads.g.doubleclick.net/gampad/clk?id=64545871&iu=/4140/ostg.clktrk
> _______________________________________________ Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
> ------------------------------------------------------------------------------
> LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99! 1,500+
> hours of tutorials including VisualStudio 2012, Windows 8, SharePoint 2013,
> SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes
> Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13.
> http://pubads.g.doubleclick.net/gampad/clk?id=58041151&iu=/4140/ostg.clktrk
> _______________________________________________ Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
> ------------------------------------------------------------------------------
> LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99!
> 1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint
> 2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack
> includes
> Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13.
> http://pubads.g.doubleclick.net/gampad/clk?id=58041151&iu=/4140/ostg.clktrk
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>

------------------------------------------------------------------------------
LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99!
1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint
2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes
Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13. 
http://pubads.g.doubleclick.net/gampad/clk?id=58041151&iu=/4140/ostg.clktrk
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

I think this stuff might be best to do in a feature branch using "git
flow feature start vs2013".  You would then be able to check out the
feature branch using "git flow feature checkout vs2013".

Stephen and Richard: how about sending me your sourceforge usernames
and I'll add you to the project.  If you're uncomfortable with git
flow, I can start the vs2013 feature branch and guide you all through
checking it out.  When you're done and want to have that pulled in,
you'd probably do a pull from develop to merge all the most recent
changes, then one of us could pull back into develop.

steven

On Tue, Sep 17, 2013 at 2:11 PM, Richard Henninger  wrote:
> Hi Mike,
>
> Thanks for offering to keep things simple.
>
>
>
> BTW, my understanding is the VS2013 is a complete rewrite of the C compiler
> behind Visual C++  (finally C99 compliant) along with a major commitment to
> be 100% compliant with C++/11 to which MS is a major contributor now.  They
> have been making a major push over the past few years to be
> standards-compliant in a number of areas.
>
> If you want, you could check out whether the STL vectors and maps now play
> nice with other libraries like SWIG by downloading and trying the VS2013 RC
> images which just became available last week.  (
> http://www.microsoft.com/visualstudio/eng/2013-downloads )  Any VS2013
> version is free (runs on Win 8 or 7 (but not 8.1 preview)) this fall.
> Release is scheduled for mid November.
>
>
>
>
> Richard Henninger
> richard@rghmusic.com
>
> From: Michael Gogins
> Sent: Tuesday, September 17, 2013 1:47 PM
> To: Developer discussions
>
> As far as I am concerned, you can work in the develop branch. I build the
> develop branch for Windows with MinGW every day or so. I'm sure we can keep
> the build options straightened out.
>
> If you want to create another branch, that's fine too. I don't find it
> difficult to manage branches just with plain git commands.
>
> For your information, the reason that I did not create a Microsoft build for
> Windows myself is that the CsoundAC component would not build a SWIG
> interface for Python with Visual C++. The cause is that the standard vector
> and map collections would not compile with a DLL interface for SWIG using
> Visual C++. Since I am the author and one of the main users of CsoundAC,
> that caused me to lose interest in Visual C++.
>
> Things have changed a bit since then. In the first place I don't depend on
> the SWIG-generated Python interface so much any more, I often compose
> directly in C++. I'm also interested to hear if this serious limitation of
> Visual C++, which is not standard compliant, has been fixed.
>
> Regards,
> Mike
>
>
>
>
> ===========================
> Michael Gogins
> Irreducible Productions
> http://michaelgogins.tumblr.com
> Michael dot Gogins at gmail dot com
>
>
> On Tue, Sep 17, 2013 at 1:37 PM, Richard Henninger 
> wrote:
>>
>> Stephen,
>>
>>
>> As we get set up, I noticed that Steven was talking about “git-flow” which
>> is an add-on to git proper that encapsulates a workflow by imposing
>> high-level commands over git that standardize branching operations.  This
>> was new to me.  If it is new to you too, let’s read up before imposing a new
>> branch on “develop”.
>>
>>
>>
>> I now remember some discussions about using git-flow in early August where
>> this was proposed.  Steven provided some basic links for info:
>> http://csound.1045644.n5.nabble.com/New-Git-Flow-based-workflow-for-Csound6-td5726363.html
>>
>> Also, here is a pretty good explanation:
>> http://yakiloo.com/getting-started-git-flow/
>>
>> Steven: Let us know the procedure we need to follow regarding dev status.
>> Thanks.
>>
>>
>> Richard Henninger
>> richard@rghmusic.com
>>
>> From: Richard Henninger
>> Sent: Monday, September 16, 2013 7:25 PM
>> To: Developer discussions
>>
>> I’ve got good doc on git and it feels like the project is moving towards
>> and  getting more comfortable with git workflows, so that’s my vote.
>>
>> Richard Henninger
>> richard@rghmusic.com
>>
>> From: Stephen Kyne
>> Sent: Monday, September 16, 2013 6:41 PM
>> To: Developer discussions
>>
>> Hi guys,
>>
>> Richard; That sounds reasonable. I wouldn't like to destabilise the
>> codebase so a separate branch is probably a safe choice.
>> I won't be at the conference unfortunately but it sounds really
>> interesting.
>>
>> Steven; Thanks that would be great if you could set that up.
>> As for the two options you gave, what would be easier for you guys? I
>> don't mind either way to be honest.
>>
>> Stephen
>>
>> > Date: Mon, 16 Sep 2013 17:55:30 -0400
>> > From: stevenyi@gmail.com
>> > To: csound-devel@lists.sourceforge.net
>> > Subject: Re: [Cs-dev] VS2010 building from source
>> >
>> > Hi Stephen and Richard,
>> >
>> > If you'd like, I don't think anyone would mind adding you two to the
>> > devs list for Csound. You'd be welcome to create a feature branch off
>> > the develop branch (using git-flow). Another option is that you could
>> > use Sourceforge's fork system (if you see on
>> > https://sourceforge.net/p/csound/csound6-git/ci/master/tree/ there is
>> > an option to fork). You could then do pull requests from there. I
>> > found SF's fork/pull-request system a bit awkward compared to
>> > bitbucket and github though.
>> >
>> > steven
>> >
>> > On Mon, Sep 16, 2013 at 4:51 PM, Richard Henninger
>> >  wrote:
>> > > Hi Stephen,
>> > >
>> > > We should probably make a separate “native windows build” branch off
>> > > of
>> > > “develop” especially since the cMakeList files are still being fine
>> > > tuned
>> > > for the mingw windows build. We shouldn’t interfere with that until it
>> > > (and
>> > > the rest of csound6) is stable.
>> > >
>> > > Do you have “write” access to the project yet? I don’t. I’ve been
>> > > holding
>> > > off on my request for that until csound6 had become reasonably
>> > > quiescent.
>> > > Still, using a separate git branch should keep this work out of the
>> > > way of
>> > > the mainstream. Down the road, I worry about built in assumption in
>> > > the
>> > > codebase about threads, library and other compatibility issues - but
>> > > resolving those is the whole point eventually.
>> > >
>> > > My original plan has been to become an active developer after
>> > > attending the
>> > > relevant sessions at the conference next month and confirming that I
>> > > had a
>> > > legitimate mingw build environment for testing changes ahead of
>> > > committing
>> > > code. Are you attending?
>> > >
>> > >
>> > > Richard Henninger
>> > > richard@rghmusic.com
>> > >
>> > > From: Stephen Kyne
>> > > Sent: Monday, September 16, 2013 4:21 PM
>> > > To: Developer discussions
>> > >
>> > > Hey Richard,
>> > >
>> > > Well I switched my Csound branch to "develop" from the main one
>> > > recently and
>> > > there was a few more errors but nothing major.
>> > > I'm currently trying to fix the missing libraries in the cMakeLists
>> > > files (I
>> > > had just added them to the sln file for testing).
>> > > I'm afraid it's a bit new to me so it's taking a little bit of time to
>> > > do it
>> > > nicely.
>> > >
>> > > Once that is finished though, there should be a version of Csound that
>> > > will
>> > > be building successfully.
>> > > I guess from there we can add additional build features and fix the
>> > > errors
>> > > as they happen.
>> > >
>> > > If you want to make a branch that sounds fine with me.
>> > >
>> > > Stephen
>> > >
>> > > ________________________________
>> > > From: richard@rghmusic.com
>> > > To: csound-devel@lists.sourceforge.net
>> > > Date: Mon, 16 Sep 2013 16:25:10 +0000
>> > > Subject: Re: [Cs-dev] VS2010 building from source
>> > >
>> > > Stephen,
>> > >
>> > > Your were right about VS2013 Preview. Also, VS2013 RC won’t work over
>> > > Win8.1 Preview.
>> > >
>> > > So, over the weekend, I hosed my 8.1 box back to 8.0 and loaded the
>> > > VS2013
>> > > RC (and git) and am ready to play. How do I catch up to the point
>> > > where you
>> > > are currently? Shall we make a git branch so we can keep track of,
>> > > share
>> > > and merge what we alter?
>> > >
>> > >
>> > > Richard Henninger
>> > > richard@rghmusic.com
>> > >
>> > > From: Stephen Kyne
>> > > Sent: Sunday, September 15, 2013 11:48 AM
>> > > To: Developer discussions
>> > >
>> > > Hi Andrés,
>> > >
>> > > Yes the project generated from CMake is almost fully correct. Just
>> > > some
>> > > edits to a few CMakeLists.txt files will be needed to load some
>> > > missing
>> > > libraries.
>> > > I'm not building all features yet so there may be more changes as time
>> > > goes
>> > > by but the csound core is working well.
>> > >
>> > > Stephen
>> > >
>> > > ________________________________
>> > > Date: Sat, 14 Sep 2013 19:28:55 -0700
>> > > From: mantaraya36@gmail.com
>> > > To: csound-devel@lists.sourceforge.net
>> > > Subject: Re: [Cs-dev] VS2010 building from source
>> > >
>> > > Hi,
>> > >
>> > > Do you think the VS porject generated by cmake is useful? Ideally this
>> > > work
>> > > should go in the CMakeLists.txt file rather than a separate VS
>> > > project.
>> > >
>> > > Cheers,
>> > > Andrés
>> > >
>> > >
>> > > On Fri, Sep 13, 2013 at 11:46 AM, Stephen Kyne 
>> > > wrote:
>> > >
>> > > Cool, any help would be appreciated. I'm still getting to grips with
>> > > the
>> > > Csound code base and most of my code changes are probably far from
>> > > elegant.
>> > >
>> > > As far as I know, the Release Candidate is required unless there is an
>> > > update to the preview.
>> > > I know I had tried before and I was getting all kinds of errors from
>> > > missing
>> > > lib functions as you described.
>> > >
>> > > In the meantime, the portaudio module is working so real time audio is
>> > > possible.
>> > > There are still some elements of MSVC build that will be need to be
>> > > fixed
>> > > though.
>> > > I saw a crash relating to heap corruptiong due to vfprintf use but
>> > > these
>> > > errors are relatively easy to fix with the debugger.
>> > >
>> > > Stephen
>> > >
>> > > ________________________________
>> > > From: richard@rghmusic.com
>> > > To: csound-devel@lists.sourceforge.net
>> > > Date: Fri, 13 Sep 2013 17:03:15 +0000
>> > >
>> > > Subject: Re: [Cs-dev] VS2010 building from source
>> > >
>> > > Me too. I tried with VS2012 and decided that too much of the code
>> > > depended
>> > > on liberties that C99 permitted that C88 did not and gave up -
>> > > thinking the
>> > > source would need too much rework to bother.
>> > >
>> > > I have VS2013 preview on an 8.1 machine so I’d be interested in
>> > > sharing the
>> > > workload to speed this along. Perhaps there should be a git branch to
>> > > hold
>> > > the project files and changes for this?
>> > >
>> > > My interest is access to MS debugging tools while using .net
>> > > front-ends and
>> > > for ultimately targeting WinRT getting csound back closer to its
>> > > original
>> > > goal of being multiplatform.
>> > >
>> > > Richard Henninger
>> > > richard@rghmusic.com
>> > >
>> > > From: Rory Walsh
>> > > Sent: Friday, September 13, 2013 12:21 PM
>> > > To: Developer discussions
>> > >
>> > > Thanks for the report. I'm following this with interest!
>> > >
>> > > On 13 September 2013 00:58, Stephen Kyne  wrote:
>> > >> Hey guys,
>> > >>
>> > >> Visual Studio 2013 RC was released there recently. It has partial
>> > >> support
>> > >> for C99.
>> > >>
>> > >>
>> > >> http://blogs.msdn.com/b/vcblog/archive/2013/07/19/c99-library-support-in-visual-studio-2013.aspx
>> > >>
>> > >> I've been hacking away with it and managed to build Csound. The build
>> > >> was
>> > >> mostly stripped down but I managed to get the xanadu.csd to compile a
>> > >> .wav
>> > >> file.
>> > >> So it's a start at least!
>> > >>
>> > >> The changes required were fairly minor, mostly just alterations to
>> > >> the
>> > >> project(s) file for libraries and some small code changes here and
>> > >> there.
>> > >> I had to replace some GCC atomic intrinsics with MSVC ones.
>> > >> I'm not sure the full effect of that but I guess in theory it should
>> > >> (and
>> > >> seems to) work.
>> > >>
>> > >> I'm hoping to get some real-time performance working next.
>> > >>
>> > >> Stephen
>> > >>
>> > >> ________________________________
>> > >> Date: Sun, 21 Jul 2013 23:48:03 -0400
>> > >> From: michael.gogins@gmail.com
>> > >> To: csound-devel@lists.sourceforge.net
>> > >>
>> > >> Subject: Re: [Cs-dev] VS2010 building from source
>> > >>
>> > >> You could use another IDE: QtCreator, CodeBlocks, Eclipse CDT.
>> > >>
>> > >> On Jul 21, 2013 7:31 PM, "Stephen Kyne"  wrote:
>> > >>
>> > >> Thanks for the replies.
>> > >>
>> > >> I mainly want to build in Visual Studio just for using the IDE itself
>> > >> but
>> > >> it
>> > >> sounds like a no go at the minute.
>> > >> Maybe something for the future.
>> > >>
>> > >> Cheers,
>> > >> Stephen
>> > >>
>> > >> ________________________________
>> > >> From: richard@rghmusic.com
>> > >> To: csound-devel@lists.sourceforge.net
>> > >> Date: Sun, 21 Jul 2013 21:15:47 +0000
>> > >> Subject: Re: [Cs-dev] VS2010 building from source
>> > >>
>> > >> Last Spring, I explored porting to WinRT using the 5.18 code base.
>> > >> Really
>> > >> tough! Once I started following in the changes you guys were putting
>> > >> into
>> > >> csound 6, I saw how your architectural evolutions would solve a
>> > >> number of
>> > >> issues I encountered.
>> > >>
>> > >> So I’ve held off until 6.0 becomes a stable base from which to
>> > >> rethink an
>> > >> approach. Being patient gave me another reward: WinRT 8.1 finally
>> > >> provides
>> > >> the ability to feed audio streams from an algorithm as PCM rather
>> > >> than
>> > >> from
>> > >> only a file or existing audio stream. So direct programming of COM
>> > >> (WASAPI)
>> > >> is no longer necessary. Maybe MIDI will show up before long...
>> > >>
>> > >> I am pretty familiar with the issues involved in a WinRT port and
>> > >> would be
>> > >> happy to be a part of such an effort at some point in the future. For
>> > >> now,
>> > >> I am content to explore the api from VS2012 and Win8 desktop apps via
>> > >> a C#
>> > >> wrapper I have. As it stands now, the sounds created from a
>> > >> desktop-style
>> > >> app are trouble free on a Surface Pro - you just can’t create apps to
>> > >> distribute from the Windows app store. It’s an acceptable compromise
>> > >> to
>> > >> me
>> > >> for now.
>> > >>
>> > >> Richard Henninger
>> > >> richard@rghmusic.com
>> > >>
>> > >> From: Steven Yi
>> > >> Sent: Sunday, July 21, 2013 4:27 PM
>> > >> To: Developer discussions
>> > >>
>> > >> I tried to get a VS CMake build going about a year and a half ago
>> > >> without much luck. I think though it would be nice to have it be
>> > >> possible, especially if we'll get more developers interested in
>> > >> compiling and working on Csound. I don't think anyone's really been
>> > >> looking at WinRT, but I think it'd be nice to see Csound there and on
>> > >> Win 8 Mobile too.
>> > >>
>> > >> On Sun, Jul 21, 2013 at 3:09 PM, Richard Henninger
>> > >> 
>> > >> wrote:
>> > >>> I tried this a few weeks ago so I could be better able to use the VS
>> > >>> debugger better for the csound code while writing a .net bridge to
>> > >>> csound.
>> > >>>
>> > >>> Mike is right on many points about the futility of doing this.
>> > >>>
>> > >>> The MS (the c part is c88 not c99) compiler will give you scads of
>> > >>> errors
>> > >>> when compiling csound libraries. Here is a partial list from an
>> > >>> excerpt
>> > >>> of
>> > >>> an earlier post:
>> > >>>
>> > >>> Four come to mind right away:
>> > >>>
>> > >>> MS C tries to encourage use of the posix secure strxxx_s functions
>> > >>> for
>> > >>> string operations to thwart buffer overflow hacks. Error can be
>> > >>> turned
>> > >>> off
>> > >>> by a flag, but the recommendation represents a best practice.
>> > >>> It is totally unforgiving of implicit casts from void*. For code
>> > >>> readability, I agree with them. Code clarity in open source seems
>> > >>> ultra-desirable. No flag for these.
>> > >>> Declaring new variables mid-codeblock confuses the compiler. [It
>> > >>> spews
>> > >>> crazy
>> > >>> error messages once encountered]
>> > >>> It won’t accept really old, deprecated library calls like open and
>> > >>> insists
>> > >>> on newer equivalents.
>> > >>>
>> > >>>
>> > >>> namehist.c is particulary delinquent in this regard. VS2013’s C (in
>> > >>> beta)
>> > >>> wants to be c99 compliant, maybe some of this will just evaporate
>> > >>> with
>> > >>> VS2013 re-written c compiler. [Mike’s concern about c++ stl generics
>> > >>> should
>> > >>> also evaporate as MS makes itself compliant with VC11. Although you
>> > >>> never
>> > >>> know with MS, they do talk a good line on standards compliance these
>> > >>> days.
>> > >>> We’ll just have to wait and see...]
>> > >>>
>> > >>> Since dealing with these is a pre-requisite to porting to WinRT
>> > >>> which
>> > >>> must
>> > >>> use an MS compiler, cleaning this kind of this up might make a good
>> > >>> [project
>> > >>> for me to start contributing with].
>> > >>>
>> > >>> For now, I’d just set up the gnu environment as Mike’s article
>> > >>> describes.
>> > >>> That’s what I’ve decided to do.
>> > >>>
>> > >>> Richard Henninger
>> > >>> richard@rghmusic.com
>> > >>>
>> > >>> From: Michael Gogins
>> > >>> Sent: Sunday, July 21, 2013 2:41 PM
>> > >>> To: Developer discussions
>> > >>>
>> > >>> I tried to build Csound and CsoundAC with Visual C++ about four
>> > >>> years
>> > >>> ago,
>> > >>> and I gave up.
>> > >>>
>> > >>> The issue for me was that the Microsoft Standard C++ Library (STL)
>> > >>> did
>> > >>> not
>> > >>> generate code that could be exported in shared libraries. This was a
>> > >>> serious
>> > >>> problem that prevented CsoundAC from linking into shared libraries
>> > >>> using
>> > >>> Visual C++, as CsoundAC uses std::vector and other such classes in
>> > >>> exported
>> > >>> interfaces.
>> > >>>
>> > >>> Aside from this the C interfaces should not, in theory, present a
>> > >>> problem.
>> > >>> However, because the Visual C++ build has not been maintained for a
>> > >>> long
>> > >>> time, there may be many minor problems.
>> > >>>
>> > >>> Your best bet is to create a branch in GIT for your Visual C++ build
>> > >>> and
>> > >>> modify the CMakeList.txt files to build with Visual C++ in the
>> > >>> Microsoft
>> > >>> Windows SDK console. If you get it to work, we can merge your branch
>> > >>> back
>> > >>> in.
>> > >>>
>> > >>> Please tell us your reason for wanting a Visual C++ build. I would
>> > >>> not go
>> > >>> down this path, myself, without a very good reason.
>> > >>>
>> > >>> Both the C API, and the low-level C++ api in csound.hpp, can be used
>> > >>> from
>> > >>> Visual C++ while linking with the MinGW built code in the Windows
>> > >>> installer.
>> > >>>
>> > >>> In other words, if you are creating a Visual C++ project to use the
>> > >>> Csound
>> > >>> API, you should be able use the libraries and headers in the Windows
>> > >>> installer with Visual C++ as long as you only reference C header
>> > >>> files
>> > >>> such
>> > >>> as csound.h and the csound.hpp C++ header. If you find out
>> > >>> differently,
>> > >>> please let me know.
>> > >>>
>> > >>> At this time, the MinGW compiler is pretty even with the Visual C++
>> > >>> compiler
>> > >>> in terms of code quality, execution speed, and probably a bit better
>> > >>> for
>> > >>> C++
>> > >>> standards compliance.
>> > >>>
>> > >>> Hope this helps,
>> > >>> Mike
>> > >>>
>> > >>>
>> > >>>
>> > >>>
>> > >>> ===========================
>> > >>> Michael Gogins
>> > >>> Irreducible Productions
>> > >>> http://michaelgogins.tumblr.com
>> > >>> Michael dot Gogins at gmail dot com
>> > >>>
>> > >>>
>> > >>> On Sun, Jul 21, 2013 at 1:15 PM, Stephen Kyne 
>> > >>> wrote:
>> > >>>>
>> > >>>> Hi guys,
>> > >>>>
>> > >>>> I was wondering if anyone has or if it is supposed to be possible
>> > >>>> to
>> > >>>> generate a VS2010 project file using CMake and building Csound this
>> > >>>> way?
>> > >>>>
>> > >>>> It is straight forward finding the necessary dependencies and
>> > >>>> generating
>> > >>>> the project file but it's running into a lot of errors when I try
>> > >>>> and
>> > >>>> build.
>> > >>>> Is it worth hacking around and fixing these errors or is this
>> > >>>> fundamentally not going to work without serious effort?
>> > >>>>
>> > >>>> Thanks,
>> > >>>> Stephen
>> > >>>>
>> > >>>>
>> > >>>>
>> > >>>>
>> > >>>>
>> > >>>> ------------------------------------------------------------------------------
>> > >>>> See everything from the browser to the database with AppDynamics
>> > >>>> Get end-to-end visibility with application monitoring from
>> > >>>> AppDynamics
>> > >>>> Isolate bottlenecks and diagnose root cause in seconds.
>> > >>>> Start your free trial of AppDynamics Pro today!
>> > >>>>
>> > >>>>
>> > >>>>
>> > >>>>
>> > >>>> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
>> > >>>> _______________________________________________
>> > >>>> Csound-devel mailing list
>> > >>>> Csound-devel@lists.sourceforge.net
>> > >>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>> > >>>>
>> > >>>
>> > >>>
>> > >>>
>> > >>>
>> > >>>
>> > >>> ------------------------------------------------------------------------------
>> > >>> See everything from the browser to the database with AppDynamics
>> > >>> Get end-to-end visibility with application monitoring from
>> > >>> AppDynamics
>> > >>> Isolate bottlenecks and diagnose root cause in seconds.
>> > >>> Start your free trial of AppDynamics Pro today!
>> > >>>
>> > >>>
>> > >>>
>> > >>> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
>> > >>> _______________________________________________
>> > >>> Csound-devel mailing list
>> > >>> Csound-devel@lists.sourceforge.net
>> > >>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>> > >>>
>> > >>
>> > >>
>> > >>
>> > >> ------------------------------------------------------------------------------
>> > >> See everything from the browser to the database with AppDynamics
>> > >> Get end-to-end visibility with application monitoring from
>> > >> AppDynamics
>> > >> Isolate bottlenecks and diagnose root cause in seconds.
>> > >> Start your free trial of AppDynamics Pro today!
>> > >>
>> > >>
>> > >> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
>> > >> _______________________________________________
>> > >> Csound-devel mailing list
>> > >> Csound-devel@lists.sourceforge.net
>> > >> https://lists.sourceforge.net/lists/listinfo/csound-devel
>> > >>
>> > >>
>> > >>
>> > >> ------------------------------------------------------------------------------
>> > >> See everything from the browser to the database with AppDynamics Get
>> > >> end-to-end visibility with application monitoring from AppDynamics
>> > >> Isolate
>> > >> bottlenecks and diagnose root cause in seconds. Start your free trial
>> > >> of
>> > >> AppDynamics Pro today!
>> > >>
>> > >>
>> > >> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
>> > >> _______________________________________________ Csound-devel mailing
>> > >> list
>> > >> Csound-devel@lists.sourceforge.net
>> > >> https://lists.sourceforge.net/lists/listinfo/csound-devel
>> > >>
>> > >>
>> > >>
>> > >> ------------------------------------------------------------------------------
>> > >> See everything from the browser to the database with AppDynamics
>> > >> Get end-to-end visibility with application monitoring from
>> > >> AppDynamics
>> > >> Isolate bottlenecks and diagnose root cause in seconds.
>> > >> Start your free trial of AppDynamics Pro today!
>> > >>
>> > >>
>> > >> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
>> > >> _______________________________________________
>> > >> Csound-devel mailing list
>> > >> Csound-devel@lists.sourceforge.net
>> > >> https://lists.sourceforge.net/lists/listinfo/csound-devel
>> > >>
>> > >>
>> > >>
>> > >>
>> > >> ------------------------------------------------------------------------------
>> > >> See everything from the browser to the database with AppDynamics Get
>> > >> end-to-end visibility with application monitoring from AppDynamics
>> > >> Isolate
>> > >> bottlenecks and diagnose root cause in seconds. Start your free trial
>> > >> of
>> > >> AppDynamics Pro today!
>> > >>
>> > >>
>> > >> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
>> > >> _______________________________________________ Csound-devel mailing
>> > >> list
>> > >> Csound-devel@lists.sourceforge.net
>> > >> https://lists.sourceforge.net/lists/listinfo/csound-devel
>> > >>
>> > >>
>> > >>
>> > >> ------------------------------------------------------------------------------
>> > >> How ServiceNow helps IT people transform IT departments:
>> > >> 1. Consolidate legacy IT systems to a single system of record for IT
>> > >> 2. Standardize and globalize service processes across IT
>> > >> 3. Implement zero-touch automation to replace manual, redundant tasks
>> > >>
>> > >>
>> > >> http://pubads.g.doubleclick.net/gampad/clk?id=51271111&iu=/4140/ostg.clktrk
>> > >> _______________________________________________
>> > >> Csound-devel mailing list
>> > >> Csound-devel@lists.sourceforge.net
>> > >> https://lists.sourceforge.net/lists/listinfo/csound-devel
>> > >>
>> > >
>> > >
>> > > ------------------------------------------------------------------------------
>> > > How ServiceNow helps IT people transform IT departments:
>> > > 1. Consolidate legacy IT systems to a single system of record for IT
>> > > 2. Standardize and globalize service processes across IT
>> > > 3. Implement zero-touch automation to replace manual, redundant tasks
>> > >
>> > > http://pubads.g.doubleclick.net/gampad/clk?id=51271111&iu=/4140/ostg.clktrk
>> > > _______________________________________________
>> > > Csound-devel mailing list
>> > > Csound-devel@lists.sourceforge.net
>> > > https://lists.sourceforge.net/lists/listinfo/csound-devel
>> > >
>> > >
>> > > ------------------------------------------------------------------------------
>> > > How ServiceNow helps IT people transform IT departments: 1.
>> > > Consolidate
>> > > legacy IT systems to a single system of record for IT 2. Standardize
>> > > and
>> > > globalize service processes across IT 3. Implement zero-touch
>> > > automation to
>> > > replace manual, redundant tasks
>> > >
>> > > http://pubads.g.doubleclick.net/gampad/clk?id=51271111&iu=/4140/ostg.clktrk
>> > > _______________________________________________ Csound-devel mailing
>> > > list
>> > > Csound-devel@lists.sourceforge.net
>> > > https://lists.sourceforge.net/lists/listinfo/csound-devel
>> > >
>> > >
>> > > ------------------------------------------------------------------------------
>> > > How ServiceNow helps IT people transform IT departments:
>> > > 1. Consolidate legacy IT systems to a single system of record for IT
>> > > 2. Standardize and globalize service processes across IT
>> > > 3. Implement zero-touch automation to replace manual, redundant tasks
>> > >
>> > > http://pubads.g.doubleclick.net/gampad/clk?id=51271111&iu=/4140/ostg.clktrk
>> > > _______________________________________________
>> > > Csound-devel mailing list
>> > > Csound-devel@lists.sourceforge.net
>> > > https://lists.sourceforge.net/lists/listinfo/csound-devel
>> > >
>> > >
>> > >
>> > >
>> > > ------------------------------------------------------------------------------
>> > > LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99!
>> > > 1,500+
>> > > hours of tutorials including VisualStudio 2012, Windows 8, SharePoint
>> > > 2013,
>> > > SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack
>> > > includes
>> > > Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/22/13.
>> > >
>> > > http://pubads.g.doubleclick.net/gampad/clk?id=64545871&iu=/4140/ostg.clktrk
>> > > _______________________________________________ Csound-devel mailing
>> > > list
>> > > Csound-devel@lists.sourceforge.net
>> > > https://lists.sourceforge.net/lists/listinfo/csound-devel
>> > >
>> > >
>> > > ------------------------------------------------------------------------------
>> > > LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99!
>> > > 1,500+
>> > > hours of tutorials including VisualStudio 2012, Windows 8, SharePoint
>> > > 2013,
>> > > SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack
>> > > includes
>> > > Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13.
>> > >
>> > > http://pubads.g.doubleclick.net/gampad/clk?id=58041151&iu=/4140/ostg.clktrk
>> > > _______________________________________________ Csound-devel mailing
>> > > list
>> > > Csound-devel@lists.sourceforge.net
>> > > https://lists.sourceforge.net/lists/listinfo/csound-devel
>> > >
>> > >
>> > > ------------------------------------------------------------------------------
>> > > LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99!
>> > > 1,500+ hours of tutorials including VisualStudio 2012, Windows 8,
>> > > SharePoint
>> > > 2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack
>> > > includes
>> > > Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13.
>> > >
>> > > http://pubads.g.doubleclick.net/gampad/clk?id=58041151&iu=/4140/ostg.clktrk
>> > > _______________________________________________
>> > > Csound-devel mailing list
>> > > Csound-devel@lists.sourceforge.net
>> > > https://lists.sourceforge.net/lists/listinfo/csound-devel
>> > >
>> >
>> >
>> > ------------------------------------------------------------------------------
>> > LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99!
>> > 1,500+ hours of tutorials including VisualStudio 2012, Windows 8,
>> > SharePoint
>> > 2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack
>> > includes
>> > Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13.
>> >
>> > http://pubads.g.doubleclick.net/gampad/clk?id=58041151&iu=/4140/ostg.clktrk
>> > _______________________________________________
>> > Csound-devel mailing list
>> > Csound-devel@lists.sourceforge.net
>> > https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>>
>> ------------------------------------------------------------------------------
>> LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99!
>> 1,500+ hours of tutorials including VisualStudio 2012, Windows 8,
>> SharePoint
>> 2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack
>> includes
>> Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13.
>>
>> http://pubads.g.doubleclick.net/gampad/clk?id=58041151&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>
>
> ------------------------------------------------------------------------------
> LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99!
> 1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint
> 2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack
> includes
> Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13.
> http://pubads.g.doubleclick.net/gampad/clk?id=58041151&iu=/4140/ostg.clktrk
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>

------------------------------------------------------------------------------
LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99!
1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint
2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes
Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13. 
http://pubads.g.doubleclick.net/gampad/clk?id=58041151&iu=/4140/ostg.clktrk
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net