I'm kind of late to the game on Windows with regards to Csound6, but
the good news is that I'm now running Csound6 from the command line
without any issues. Great stuff Mike. I get a system error if I try to
start CsoundQT. I also noticed that there is no option to really
customise your install, apart from choosing to install support for
Python or not. The down side of this is that is a whopping 250MB
install footprint. I assume there will be support for chosing highly
customised installs again in the future, or at least the same level of
options as the previous windows installers had?

Placing a downloaded copy of MSVCR110.dll into the bin directory
helped to sort out the issue with CsoundQT. I'm afraid it doesn't work
for Cabbage however which hangs on csoundReset(). Are you building
with MSVC12?

On 20 October 2013 12:29, Rory Walsh  wrote:
> I'm kind of late to the game on Windows with regards to Csound6, but
> the good news is that I'm now running Csound6 from the command line
> without any issues. Great stuff Mike. I get a system error if I try to
> start CsoundQT. I also noticed that there is no option to really
> customise your install, apart from choosing to install support for
> Python or not. The down side of this is that is a whopping 250MB
> install footprint. I assume there will be support for chosing highly
> customised installs again in the future, or at least the same level of
> options as the previous windows installers had?

Thanks Mike. I'll look into it further when I get a chance.

On 20 October 2013 17:00, Michael Gogins  wrote:
> Thanks for your feedback about msvcr110.dll. I am not building with
> Microsoft Visual C+ at all. This dependency is now happening because I am
> using a pre-built libportaudio_x86.dll, which brings in this dependency.
>
> PortAudio has been a thorn in my side for years, and I am happy not to have
> to build it myself. This should not be construed as criticism of PortAudio
> or its developers. In order to support all the drivers that PortAudio can
> use on all the current versions of Windows, they have to write code that
> uses a variety of Windows software development kits that I have not
> installed.
>
> I am going to include msvcr110.dll in the Windows installer from now on.
>
> Can you send me more information about your csoundReset problem? A stack
> trace? A list of libraries identified as requirements by depends.exe?
>
> Thanks,
> Mike
>
>
> ===========================
> Michael Gogins
> Irreducible Productions
> http://michaelgogins.tumblr.com
> Michael dot Gogins at gmail dot com
>
>
> On Sun, Oct 20, 2013 at 7:37 AM, Rory Walsh  wrote:
>>
>> Placing a downloaded copy of MSVCR110.dll into the bin directory
>> helped to sort out the issue with CsoundQT. I'm afraid it doesn't work
>> for Cabbage however which hangs on csoundReset(). Are you building
>> with MSVC12?
>>
>> On 20 October 2013 12:29, Rory Walsh  wrote:
>> > I'm kind of late to the game on Windows with regards to Csound6, but
>> > the good news is that I'm now running Csound6 from the command line
>> > without any issues. Great stuff Mike. I get a system error if I try to
>> > start CsoundQT. I also noticed that there is no option to really
>> > customise your install, apart from choosing to install support for
>> > Python or not. The down side of this is that is a whopping 250MB
>> > install footprint. I assume there will be support for chosing highly
>> > customised installs again in the future, or at least the same level of
>> > options as the previous windows installers had?
>>
>>
>> Send bugs reports to the Sourceforge bug trackers
>> csound6:
>>             https://sourceforge.net/p/csound/tickets/
>> csound5:
>>             https://sourceforge.net/p/csound/bugs/
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>>
>>
>