I have installed MSYS2, its mingw, toolchain, and the list of packages
from our README.md.

Things have started to build. I have to create an import library for
Python x64. MSYS2 comes with its own Python, but I assume I should use
regular Windows x64 Python from python.org.

The Lua library problem mentioned in our README.md can probably be
fixed with a file copy or symbolic link.

I have installed NW.js for x64, and plan to use that for HTML5 stuff.
The current beta version of NW.js enables NaCl for x64 so a 64 bit
build of Csound for NaCl should run as well as the 64 bit build of
csound.node.

I am not sure what to do for CsoundQt. If NW.js works I see no
particular need to build CsoundQt, but on the other the Qt SDK is
installed in my MSYS2 environment so CsoundQt shouldn't be that hard
to build.

I also am not sure what to do about the Java interface. Presumably
you, Steven, would like blue to run with x64 Csound.

I also am not sure what to do about Jack, perhaps Windows support for
Jack now exists, and if so, this could be added to the build.

For a full build I think we should have package recipes for STK,
LuaJIT, and perhaps NW.js.

There are also compiler warnings about various handles and pointers
that are different sizes on different platforms. I would like to fix
all of these with some sort of padding or aliasing.

I'm not sure how much of this I can do for the next release but I am
shooting for at least LuaJIT. NW.js, and STK.

Regards,
Mike

-----------------------------------------------------
Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com

Hi Michael,

I haven't had any problems building for 64-bit Java here and I am
running my local version of Blue on Windows with 64-bit Java and
Csound. For Python, I have also been using the installer version of
Python with an import library rather than the one from MSYS2.

For pointer sizes, as previously mentioned, I have been converting
code to use intptr_t instead of long.  That seems like the correct way
to handle casting pointers to integer values when dealing with
different builds and word sizes.  Maybe we could just use that for the
places you're seeing issues?

steven

On Sat, Feb 27, 2016 at 12:54 PM, Michael Gogins
 wrote:
> I have installed MSYS2, its mingw, toolchain, and the list of packages
> from our README.md.
>
> Things have started to build. I have to create an import library for
> Python x64. MSYS2 comes with its own Python, but I assume I should use
> regular Windows x64 Python from python.org.
>
> The Lua library problem mentioned in our README.md can probably be
> fixed with a file copy or symbolic link.
>
> I have installed NW.js for x64, and plan to use that for HTML5 stuff.
> The current beta version of NW.js enables NaCl for x64 so a 64 bit
> build of Csound for NaCl should run as well as the 64 bit build of
> csound.node.
>
> I am not sure what to do for CsoundQt. If NW.js works I see no
> particular need to build CsoundQt, but on the other the Qt SDK is
> installed in my MSYS2 environment so CsoundQt shouldn't be that hard
> to build.
>
> I also am not sure what to do about the Java interface. Presumably
> you, Steven, would like blue to run with x64 Csound.
>
> I also am not sure what to do about Jack, perhaps Windows support for
> Jack now exists, and if so, this could be added to the build.
>
> For a full build I think we should have package recipes for STK,
> LuaJIT, and perhaps NW.js.
>
> There are also compiler warnings about various handles and pointers
> that are different sizes on different platforms. I would like to fix
> all of these with some sort of padding or aliasing.
>
> I'm not sure how much of this I can do for the next release but I am
> shooting for at least LuaJIT. NW.js, and STK.
>
> Regards,
> Mike
>
> -----------------------------------------------------
> Michael Gogins
> Irreducible Productions
> http://michaelgogins.tumblr.com

Another thing, should I support Python 2.7 or Python 3?

Regards,
Mike

-----------------------------------------------------
Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com


On Sat, Feb 27, 2016 at 12:54 PM, Michael Gogins
 wrote:
> I have installed MSYS2, its mingw, toolchain, and the list of packages
> from our README.md.
>
> Things have started to build. I have to create an import library for
> Python x64. MSYS2 comes with its own Python, but I assume I should use
> regular Windows x64 Python from python.org.
>
> The Lua library problem mentioned in our README.md can probably be
> fixed with a file copy or symbolic link.
>
> I have installed NW.js for x64, and plan to use that for HTML5 stuff.
> The current beta version of NW.js enables NaCl for x64 so a 64 bit
> build of Csound for NaCl should run as well as the 64 bit build of
> csound.node.
>
> I am not sure what to do for CsoundQt. If NW.js works I see no
> particular need to build CsoundQt, but on the other the Qt SDK is
> installed in my MSYS2 environment so CsoundQt shouldn't be that hard
> to build.
>
> I also am not sure what to do about the Java interface. Presumably
> you, Steven, would like blue to run with x64 Csound.
>
> I also am not sure what to do about Jack, perhaps Windows support for
> Jack now exists, and if so, this could be added to the build.
>
> For a full build I think we should have package recipes for STK,
> LuaJIT, and perhaps NW.js.
>
> There are also compiler warnings about various handles and pointers
> that are different sizes on different platforms. I would like to fix
> all of these with some sort of padding or aliasing.
>
> I'm not sure how much of this I can do for the next release but I am
> shooting for at least LuaJIT. NW.js, and STK.
>
> Regards,
> Mike
>
> -----------------------------------------------------
> Michael Gogins
> Irreducible Productions
> http://michaelgogins.tumblr.com

I will try the intptr_t fix. It will not work everywhere but I think I
know what to do.

I disabled Python support for now but I get a runtime error on
starting Csound, presumably this comes from a mixed up runtime
environment (I installed Cabbage which is built for x64):

D:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/5.3.0/../../../../x86_64-w64-mingw32/lib/../lib/crt2.o:C:/repo/mingw-w64-crt-git/src/mingw-w64/mingw-w64-crt/crt/crtexe.c:118:
first defined here
./csound.exe:crtexe.c:(.CRT+0x20): multiple definition of `mingw_pcinit'
D:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/5.3.0/../../../../x86_64-w64-mingw32/lib/../lib/crt2.o:C:/repo/mingw-w64-crt-git/src/mingw-w64/mingw-w64-crt/crt/crtexe.c:118:
first defined here
./csound.exe:csound_main.c:(.rdata+0x540): multiple definition of
`.refptr._gnu_exception_handler'
D:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/5.3.0/../../../../x86_64-w64-mingw32/lib/../lib/crt2.o:C:/repo/mingw-w64-crt-git/src/mingw-w64/mingw-w64-crt/crt/crtexe.c:118:
first defined here
./csound.exe:csound_main.c:(.rdata+0x4c0): multiple definition of
`.refptr.__onexitbegin'
D:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/5.3.0/../../../../x86_64-w64-mingw32/lib/../lib/crt2.o:C:/repo/mingw-w64-crt-git/src/mingw-w64/mingw-w64-crt/crt/crtexe.c:118:
first defined here
./csound.exe:csound_main.c:(.rdata+0x570): multiple definition of
`.refptr.mingw_app_type'
D:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/5.3.0/../../../../x86_64-w64-mingw32/lib/../lib/crt2.o:C:/repo/mingw-w64-crt-git/src/mingw-w64/mingw-w64-crt/crt/crtexe.c:118:
first defined here
./csound.exe:csound_main.c:(.rdata+0x460): multiple definition of
`.refptr.__imp__acmdln'
D:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/5.3.0/../../../../x86_64-w64-mingw32/lib/../lib/crt2.o:C:/repo/mingw-w64-crt-git/src/mingw-w64/mingw-w64-crt/crt/crtexe.c:118:
first defined here
./csound.exe:csound_main.c:(.rdata+0x440): multiple definition of
`.refptr.__image_base__'
D:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/5.3.0/../../../../x86_64-w64-mingw32/lib/../lib/crt2.o:C:/repo/mingw-w64-crt-git/src/mingw-w64/mingw-w64-crt/crt/crtexe.c:118:
first defined here
./csound.exe:csound_main.c:(.rdata+0x530): multiple definition of
`.refptr._fmode'
D:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/5.3.0/../../../../x86_64-w64-mingw32/lib/../lib/crt2.o:C:/repo/mingw-w64-crt-git/src/mingw-w64/mingw-w64-crt/crt/crtexe.c:118:
first defined here
./csound.exe:csound_main.c:(.rdata+0x4e0): multiple definition of
`.refptr.__xc_a'
D:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/5.3.0/../../../../x86_64-w64-mingw32/lib/../lib/crt2.o:C:/repo/mingw-w64-crt-git/src/mingw-w64/mingw-w64-crt/crt/crtexe.c:118:
first defined here
./csound.exe:csound_main.c:(.rdata+0x510): multiple definition of
`.refptr.__xi_z'
D:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/5.3.0/../../../../x86_64-w64-mingw32/lib/../lib/crt2.o:C:/repo/mingw-w64-crt-git/src/mingw-w64/mingw-w64-crt/crt/crtexe.c:118:
first defined here
./csound.exe:csound_main.c:(.rdata+0x400): multiple definition of
`.refptr._MINGW_INSTALL_DEBUG_MATHERR'
D:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/5.3.0/../../../../x86_64-w64-mingw32/lib/../lib/crt2.o:C:/repo/mingw-w64-crt-git/src/mingw-w64/mingw-w64-crt/crt/crtexe.c:118:
first defined here
./csound.exe:csound_main.c:(.rdata+0x4f0): multiple definition of
`.refptr.__xc_z'
D:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/5.3.0/../../../../x86_64-w64-mingw32/lib/../lib/crt2.o:C:/repo/mingw-w64-crt-git/src/mingw-w64/mingw-w64-crt/crt/crtexe.c:118:
first defined here
D:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/5.3.0/crtbegin.o:cygming-crtbegin.c:(.text+0x66):
undefined reference to `_Jv_RegisterClasses'
collect2.exe: error: ld returned 1 exit status


Regards,
Mike


-----------------------------------------------------
Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com


On Sat, Feb 27, 2016 at 1:22 PM, Michael Gogins
 wrote:
> Another thing, should I support Python 2.7 or Python 3?
>
> Regards,
> Mike
>
> -----------------------------------------------------
> Michael Gogins
> Irreducible Productions
> http://michaelgogins.tumblr.com
> Michael dot Gogins at gmail dot com
>
>
> On Sat, Feb 27, 2016 at 12:54 PM, Michael Gogins
>  wrote:
>> I have installed MSYS2, its mingw, toolchain, and the list of packages
>> from our README.md.
>>
>> Things have started to build. I have to create an import library for
>> Python x64. MSYS2 comes with its own Python, but I assume I should use
>> regular Windows x64 Python from python.org.
>>
>> The Lua library problem mentioned in our README.md can probably be
>> fixed with a file copy or symbolic link.
>>
>> I have installed NW.js for x64, and plan to use that for HTML5 stuff.
>> The current beta version of NW.js enables NaCl for x64 so a 64 bit
>> build of Csound for NaCl should run as well as the 64 bit build of
>> csound.node.
>>
>> I am not sure what to do for CsoundQt. If NW.js works I see no
>> particular need to build CsoundQt, but on the other the Qt SDK is
>> installed in my MSYS2 environment so CsoundQt shouldn't be that hard
>> to build.
>>
>> I also am not sure what to do about the Java interface. Presumably
>> you, Steven, would like blue to run with x64 Csound.
>>
>> I also am not sure what to do about Jack, perhaps Windows support for
>> Jack now exists, and if so, this could be added to the build.
>>
>> For a full build I think we should have package recipes for STK,
>> LuaJIT, and perhaps NW.js.
>>
>> There are also compiler warnings about various handles and pointers
>> that are different sizes on different platforms. I would like to fix
>> all of these with some sort of padding or aliasing.
>>
>> I'm not sure how much of this I can do for the next release but I am
>> shooting for at least LuaJIT. NW.js, and STK.
>>
>> Regards,
>> Mike
>>
>> -----------------------------------------------------
>> Michael Gogins
>> Irreducible Productions
>> http://michaelgogins.tumblr.com

I've been building for 2.7 myself.  I suppose the only way to satisfy
everyone is to build something that works for both.  Perhaps we should
finally add a build target specifically for Python 3 for all
platforms?  We'd have to work out all the details for install
locations for OSX and Linux.  Another option is to start leveraging
python's package system to build the interfaces and have the user
install those packages separately.

Maybe just start with 2.7 for now as that was the last supported
Python and punt on Python 3 until after this build?  Might be best so
we can coordinate a solution for all platforms.

On Sat, Feb 27, 2016 at 1:22 PM, Michael Gogins
 wrote:
> Another thing, should I support Python 2.7 or Python 3?
>
> Regards,
> Mike
>
> -----------------------------------------------------
> Michael Gogins
> Irreducible Productions
> http://michaelgogins.tumblr.com
> Michael dot Gogins at gmail dot com
>
>
> On Sat, Feb 27, 2016 at 12:54 PM, Michael Gogins
>  wrote:
>> I have installed MSYS2, its mingw, toolchain, and the list of packages
>> from our README.md.
>>
>> Things have started to build. I have to create an import library for
>> Python x64. MSYS2 comes with its own Python, but I assume I should use
>> regular Windows x64 Python from python.org.
>>
>> The Lua library problem mentioned in our README.md can probably be
>> fixed with a file copy or symbolic link.
>>
>> I have installed NW.js for x64, and plan to use that for HTML5 stuff.
>> The current beta version of NW.js enables NaCl for x64 so a 64 bit
>> build of Csound for NaCl should run as well as the 64 bit build of
>> csound.node.
>>
>> I am not sure what to do for CsoundQt. If NW.js works I see no
>> particular need to build CsoundQt, but on the other the Qt SDK is
>> installed in my MSYS2 environment so CsoundQt shouldn't be that hard
>> to build.
>>
>> I also am not sure what to do about the Java interface. Presumably
>> you, Steven, would like blue to run with x64 Csound.
>>
>> I also am not sure what to do about Jack, perhaps Windows support for
>> Jack now exists, and if so, this could be added to the build.
>>
>> For a full build I think we should have package recipes for STK,
>> LuaJIT, and perhaps NW.js.
>>
>> There are also compiler warnings about various handles and pointers
>> that are different sizes on different platforms. I would like to fix
>> all of these with some sort of padding or aliasing.
>>
>> I'm not sure how much of this I can do for the next release but I am
>> shooting for at least LuaJIT. NW.js, and STK.
>>
>> Regards,
>> Mike
>>
>> -----------------------------------------------------
>> Michael Gogins
>> Irreducible Productions
>> http://michaelgogins.tumblr.com

I will go with Python 2.7 for now.

Best,
Mike

-----------------------------------------------------
Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com


On Sat, Feb 27, 2016 at 1:39 PM, Steven Yi  wrote:
> I've been building for 2.7 myself.  I suppose the only way to satisfy
> everyone is to build something that works for both.  Perhaps we should
> finally add a build target specifically for Python 3 for all
> platforms?  We'd have to work out all the details for install
> locations for OSX and Linux.  Another option is to start leveraging
> python's package system to build the interfaces and have the user
> install those packages separately.
>
> Maybe just start with 2.7 for now as that was the last supported
> Python and punt on Python 3 until after this build?  Might be best so
> we can coordinate a solution for all platforms.
>
> On Sat, Feb 27, 2016 at 1:22 PM, Michael Gogins
>  wrote:
>> Another thing, should I support Python 2.7 or Python 3?
>>
>> Regards,
>> Mike
>>
>> -----------------------------------------------------
>> Michael Gogins
>> Irreducible Productions
>> http://michaelgogins.tumblr.com
>> Michael dot Gogins at gmail dot com
>>
>>
>> On Sat, Feb 27, 2016 at 12:54 PM, Michael Gogins
>>  wrote:
>>> I have installed MSYS2, its mingw, toolchain, and the list of packages
>>> from our README.md.
>>>
>>> Things have started to build. I have to create an import library for
>>> Python x64. MSYS2 comes with its own Python, but I assume I should use
>>> regular Windows x64 Python from python.org.
>>>
>>> The Lua library problem mentioned in our README.md can probably be
>>> fixed with a file copy or symbolic link.
>>>
>>> I have installed NW.js for x64, and plan to use that for HTML5 stuff.
>>> The current beta version of NW.js enables NaCl for x64 so a 64 bit
>>> build of Csound for NaCl should run as well as the 64 bit build of
>>> csound.node.
>>>
>>> I am not sure what to do for CsoundQt. If NW.js works I see no
>>> particular need to build CsoundQt, but on the other the Qt SDK is
>>> installed in my MSYS2 environment so CsoundQt shouldn't be that hard
>>> to build.
>>>
>>> I also am not sure what to do about the Java interface. Presumably
>>> you, Steven, would like blue to run with x64 Csound.
>>>
>>> I also am not sure what to do about Jack, perhaps Windows support for
>>> Jack now exists, and if so, this could be added to the build.
>>>
>>> For a full build I think we should have package recipes for STK,
>>> LuaJIT, and perhaps NW.js.
>>>
>>> There are also compiler warnings about various handles and pointers
>>> that are different sizes on different platforms. I would like to fix
>>> all of these with some sort of padding or aliasing.
>>>
>>> I'm not sure how much of this I can do for the next release but I am
>>> shooting for at least LuaJIT. NW.js, and STK.
>>>
>>> Regards,
>>> Mike
>>>
>>> -----------------------------------------------------
>>> Michael Gogins
>>> Irreducible Productions
>>> http://michaelgogins.tumblr.com

Hi,

And if you say MSYS2 has Qt, please do build alwo CsoundQt and let know if 
there are any problems or anything to do in the source code or project files.

Thanks!

On Saturday 27 February 2016 13:42:28 you wrote:
> I will go with Python 2.7 for now.
> 
> Best,
> Mike
> 
> -----------------------------------------------------
> Michael Gogins
> Irreducible Productions
> http://michaelgogins.tumblr.com
> Michael dot Gogins at gmail dot com
> 
> On Sat, Feb 27, 2016 at 1:39 PM, Steven Yi  wrote:
> > I've been building for 2.7 myself.  I suppose the only way to satisfy
> > everyone is to build something that works for both.  Perhaps we should
> > finally add a build target specifically for Python 3 for all
> > platforms?  We'd have to work out all the details for install
> > locations for OSX and Linux.  Another option is to start leveraging
> > python's package system to build the interfaces and have the user
> > install those packages separately.
> > 
> > Maybe just start with 2.7 for now as that was the last supported
> > Python and punt on Python 3 until after this build?  Might be best so
> > we can coordinate a solution for all platforms.
> > 
> > On Sat, Feb 27, 2016 at 1:22 PM, Michael Gogins
> > 
> >  wrote:
> >> Another thing, should I support Python 2.7 or Python 3?
> >> 
> >> Regards,
> >> Mike
> >> 
> >> -----------------------------------------------------
> >> Michael Gogins
> >> Irreducible Productions
> >> http://michaelgogins.tumblr.com
> >> Michael dot Gogins at gmail dot com
> >> 
> >> 
> >> On Sat, Feb 27, 2016 at 12:54 PM, Michael Gogins
> >> 
> >>  wrote:
> >>> I have installed MSYS2, its mingw, toolchain, and the list of packages
> >>> from our README.md.
> >>> 
> >>> Things have started to build. I have to create an import library for
> >>> Python x64. MSYS2 comes with its own Python, but I assume I should use
> >>> regular Windows x64 Python from python.org.
> >>> 
> >>> The Lua library problem mentioned in our README.md can probably be
> >>> fixed with a file copy or symbolic link.
> >>> 
> >>> I have installed NW.js for x64, and plan to use that for HTML5 stuff.
> >>> The current beta version of NW.js enables NaCl for x64 so a 64 bit
> >>> build of Csound for NaCl should run as well as the 64 bit build of
> >>> csound.node.
> >>> 
> >>> I am not sure what to do for CsoundQt. If NW.js works I see no
> >>> particular need to build CsoundQt, but on the other the Qt SDK is
> >>> installed in my MSYS2 environment so CsoundQt shouldn't be that hard
> >>> to build.
> >>> 
> >>> I also am not sure what to do about the Java interface. Presumably
> >>> you, Steven, would like blue to run with x64 Csound.
> >>> 
> >>> I also am not sure what to do about Jack, perhaps Windows support for
> >>> Jack now exists, and if so, this could be added to the build.
> >>> 
> >>> For a full build I think we should have package recipes for STK,
> >>> LuaJIT, and perhaps NW.js.
> >>> 
> >>> There are also compiler warnings about various handles and pointers
> >>> that are different sizes on different platforms. I would like to fix
> >>> all of these with some sort of padding or aliasing.
> >>> 
> >>> I'm not sure how much of this I can do for the next release but I am
> >>> shooting for at least LuaJIT. NW.js, and STK.
> >>> 
> >>> Regards,
> >>> Mike
> >>> 
> >>> -----------------------------------------------------
> >>> Michael Gogins
> >>> Irreducible Productions
> >>> http://michaelgogins.tumblr.com

Hi Tarmo,

Regarding CsoundQT, is there someone from the CsoundQT developers that
could contribute time to investigating building on Windows with MSYS2?

Thanks!
steven


On Sat, Feb 27, 2016 at 1:57 PM, Tarmo Johannes  wrote:
> Hi,
>
> And if you say MSYS2 has Qt, please do build alwo CsoundQt and let know if
> there are any problems or anything to do in the source code or project files.
>
> Thanks!
>
> On Saturday 27 February 2016 13:42:28 you wrote:
>> I will go with Python 2.7 for now.
>>
>> Best,
>> Mike
>>
>> -----------------------------------------------------
>> Michael Gogins
>> Irreducible Productions
>> http://michaelgogins.tumblr.com
>> Michael dot Gogins at gmail dot com
>>
>> On Sat, Feb 27, 2016 at 1:39 PM, Steven Yi  wrote:
>> > I've been building for 2.7 myself.  I suppose the only way to satisfy
>> > everyone is to build something that works for both.  Perhaps we should
>> > finally add a build target specifically for Python 3 for all
>> > platforms?  We'd have to work out all the details for install
>> > locations for OSX and Linux.  Another option is to start leveraging
>> > python's package system to build the interfaces and have the user
>> > install those packages separately.
>> >
>> > Maybe just start with 2.7 for now as that was the last supported
>> > Python and punt on Python 3 until after this build?  Might be best so
>> > we can coordinate a solution for all platforms.
>> >
>> > On Sat, Feb 27, 2016 at 1:22 PM, Michael Gogins
>> >
>> >  wrote:
>> >> Another thing, should I support Python 2.7 or Python 3?
>> >>
>> >> Regards,
>> >> Mike
>> >>
>> >> -----------------------------------------------------
>> >> Michael Gogins
>> >> Irreducible Productions
>> >> http://michaelgogins.tumblr.com
>> >> Michael dot Gogins at gmail dot com
>> >>
>> >>
>> >> On Sat, Feb 27, 2016 at 12:54 PM, Michael Gogins
>> >>
>> >>  wrote:
>> >>> I have installed MSYS2, its mingw, toolchain, and the list of packages
>> >>> from our README.md.
>> >>>
>> >>> Things have started to build. I have to create an import library for
>> >>> Python x64. MSYS2 comes with its own Python, but I assume I should use
>> >>> regular Windows x64 Python from python.org.
>> >>>
>> >>> The Lua library problem mentioned in our README.md can probably be
>> >>> fixed with a file copy or symbolic link.
>> >>>
>> >>> I have installed NW.js for x64, and plan to use that for HTML5 stuff.
>> >>> The current beta version of NW.js enables NaCl for x64 so a 64 bit
>> >>> build of Csound for NaCl should run as well as the 64 bit build of
>> >>> csound.node.
>> >>>
>> >>> I am not sure what to do for CsoundQt. If NW.js works I see no
>> >>> particular need to build CsoundQt, but on the other the Qt SDK is
>> >>> installed in my MSYS2 environment so CsoundQt shouldn't be that hard
>> >>> to build.
>> >>>
>> >>> I also am not sure what to do about the Java interface. Presumably
>> >>> you, Steven, would like blue to run with x64 Csound.
>> >>>
>> >>> I also am not sure what to do about Jack, perhaps Windows support for
>> >>> Jack now exists, and if so, this could be added to the build.
>> >>>
>> >>> For a full build I think we should have package recipes for STK,
>> >>> LuaJIT, and perhaps NW.js.
>> >>>
>> >>> There are also compiler warnings about various handles and pointers
>> >>> that are different sizes on different platforms. I would like to fix
>> >>> all of these with some sort of padding or aliasing.
>> >>>
>> >>> I'm not sure how much of this I can do for the next release but I am
>> >>> shooting for at least LuaJIT. NW.js, and STK.
>> >>>
>> >>> Regards,
>> >>> Mike
>> >>>
>> >>> -----------------------------------------------------
>> >>> Michael Gogins
>> >>> Irreducible Productions
>> >>> http://michaelgogins.tumblr.com

Hi,
This is a problematic topic. We just discussed it with Joachim and don't have a dedicee to it right - there is truly lack of experienced Windows people... But keep thinking about it. I will read about MSYS2 myself too to be more aware.
Thanks!
Tarmo

Hi,
This is a problematic topic. We just discussed it with Joachim and don't have a dedicee to it right - there is truly lack of experienced Windows people... But keep thinking about it. I will read about MSYS2 myself too to be more aware.
Thanks!
Tarmo

27.02.2016 21:51 kirjutas kuupäeval "Steven Yi" <stevenyi@gmail.com>:

Hi Tarmo,

Regarding CsoundQT, is there someone from the CsoundQT developers that
could contribute time to investigating building on Windows with MSYS2?

Thanks!
steven


On Sat, Feb 27, 2016 at 1:57 PM, Tarmo Johannes <trmjhnns@gmail.com> wrote:
> Hi,
>
> And if you say MSYS2 has Qt, please do build alwo CsoundQt and let know if
> there are any problems or anything to do in the source code or project files.
>
> Thanks!
>
> On Saturday 27 February 2016 13:42:28 you wrote:
>> I will go with Python 2.7 for now.
>>
>> Best,
>> Mike
>>
>> -----------------------------------------------------
>> Michael Gogins
>> Irreducible Productions
>> http://michaelgogins.tumblr.com
>> Michael dot Gogins at gmail dot com
>>
>> On Sat, Feb 27, 2016 at 1:39 PM, Steven Yi <stevenyi@gmail.com> wrote:
>> > I've been building for 2.7 myself.  I suppose the only way to satisfy
>> > everyone is to build something that works for both.  Perhaps we should
>> > finally add a build target specifically for Python 3 for all
>> > platforms?  We'd have to work out all the details for install
>> > locations for OSX and Linux.  Another option is to start leveraging
>> > python's package system to build the interfaces and have the user
>> > install those packages separately.
>> >
>> > Maybe just start with 2.7 for now as that was the last supported
>> > Python and punt on Python 3 until after this build?  Might be best so
>> > we can coordinate a solution for all platforms.
>> >
>> > On Sat, Feb 27, 2016 at 1:22 PM, Michael Gogins
>> >
>> > <michael.gogins@gmail.com> wrote:
>> >> Another thing, should I support Python 2.7 or Python 3?
>> >>
>> >> Regards,
>> >> Mike
>> >>
>> >> -----------------------------------------------------
>> >> Michael Gogins
>> >> Irreducible Productions
>> >> http://michaelgogins.tumblr.com
>> >> Michael dot Gogins at gmail dot com
>> >>
>> >>
>> >> On Sat, Feb 27, 2016 at 12:54 PM, Michael Gogins
>> >>
>> >> <michael.gogins@gmail.com> wrote:
>> >>> I have installed MSYS2, its mingw, toolchain, and the list of packages
>> >>> from our README.md.
>> >>>
>> >>> Things have started to build. I have to create an import library for
>> >>> Python x64. MSYS2 comes with its own Python, but I assume I should use
>> >>> regular Windows x64 Python from python.org.
>> >>>
>> >>> The Lua library problem mentioned in our README.md can probably be
>> >>> fixed with a file copy or symbolic link.
>> >>>
>> >>> I have installed NW.js for x64, and plan to use that for HTML5 stuff.
>> >>> The current beta version of NW.js enables NaCl for x64 so a 64 bit
>> >>> build of Csound for NaCl should run as well as the 64 bit build of
>> >>> csound.node.
>> >>>
>> >>> I am not sure what to do for CsoundQt. If NW.js works I see no
>> >>> particular need to build CsoundQt, but on the other the Qt SDK is
>> >>> installed in my MSYS2 environment so CsoundQt shouldn't be that hard
>> >>> to build.
>> >>>
>> >>> I also am not sure what to do about the Java interface. Presumably
>> >>> you, Steven, would like blue to run with x64 Csound.
>> >>>
>> >>> I also am not sure what to do about Jack, perhaps Windows support for
>> >>> Jack now exists, and if so, this could be added to the build.
>> >>>
>> >>> For a full build I think we should have package recipes for STK,
>> >>> LuaJIT, and perhaps NW.js.
>> >>>
>> >>> There are also compiler warnings about various handles and pointers
>> >>> that are different sizes on different platforms. I would like to fix
>> >>> all of these with some sort of padding or aliasing.
>> >>>
>> >>> I'm not sure how much of this I can do for the next release but I am
>> >>> shooting for at least LuaJIT. NW.js, and STK.
>> >>>
>> >>> Regards,
>> >>> Mike
>> >>>
>> >>> -----------------------------------------------------
>> >>> Michael Gogins
>> >>> Irreducible Productions
>> >>> http://michaelgogins.tumblr.com
>> >>> Michael dot Gogins at gmail dot com

I'm running into a serious problem. I can build csound.exe with
MSYS2/mingw64, but it does not run. I have cleaned up my environment
so there are no binaries in the PATH but MSYS, mingw, and Csound and
its opcodes.

(gdb) run
Starting program:
D:\msys64\home\restore\csound\mingw64\csound-mingw64\csound.exe
[New Thread 5784.0x6d8]

Program received signal SIGSEGV, Segmentation fault.
0x000007f8f3d17740 in ntdll!RtlMultiAppendUnicodeStringBuffer ()
   from C:\Windows\SYSTEM32\ntdll.dll
(gdb) bt
#0  0x000007f8f3d17740 in ntdll!RtlMultiAppendUnicodeStringBuffer ()
   from C:\Windows\SYSTEM32\ntdll.dll
#1  0x000007f8f3d0c5a5 in ntdll!RtlInitializeCriticalSection ()
   from C:\Windows\SYSTEM32\ntdll.dll
#2  0x000000006c5eed8d in csoundInitialize (flags=flags@entry=1)
    at D:/msys64/home/restore/csound/Top/csound.c:1119
#3  0x0000000000402fe5 in main (argc=1, argv=0x304700)
    at D:/msys64/home/restore/csound/frontends/csound/csound_main.c:258
(gdb)


-----------------------------------------------------
Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com


On Sat, Feb 27, 2016 at 4:33 PM, Victor Lazzarini
 wrote:
> Maybe try to get one of the Norwegian guys, they know about Windows.
>
> Victor Lazzarini
> Dean of Arts, Celtic Studies, and Philosophy
> Maynooth University
> Ireland
>
> On 27 Feb 2016, at 20:48, Tarmo Johannes  wrote:
>
> Hi,
> This is a problematic topic. We just discussed it with Joachim and don't
> have a dedicee to it right - there is truly lack of experienced Windows
> people... But keep thinking about it. I will read about MSYS2 myself too to
> be more aware.
> Thanks!
> Tarmo
>
> 27.02.2016 21:51 kirjutas kuupäeval "Steven Yi" :
>>
>> Hi Tarmo,
>>
>> Regarding CsoundQT, is there someone from the CsoundQT developers that
>> could contribute time to investigating building on Windows with MSYS2?
>>
>> Thanks!
>> steven
>>
>>
>> On Sat, Feb 27, 2016 at 1:57 PM, Tarmo Johannes 
>> wrote:
>> > Hi,
>> >
>> > And if you say MSYS2 has Qt, please do build alwo CsoundQt and let know
>> > if
>> > there are any problems or anything to do in the source code or project
>> > files.
>> >
>> > Thanks!
>> >
>> > On Saturday 27 February 2016 13:42:28 you wrote:
>> >> I will go with Python 2.7 for now.
>> >>
>> >> Best,
>> >> Mike
>> >>
>> >> -----------------------------------------------------
>> >> Michael Gogins
>> >> Irreducible Productions
>> >> http://michaelgogins.tumblr.com
>> >> Michael dot Gogins at gmail dot com
>> >>
>> >> On Sat, Feb 27, 2016 at 1:39 PM, Steven Yi  wrote:
>> >> > I've been building for 2.7 myself.  I suppose the only way to satisfy
>> >> > everyone is to build something that works for both.  Perhaps we
>> >> > should
>> >> > finally add a build target specifically for Python 3 for all
>> >> > platforms?  We'd have to work out all the details for install
>> >> > locations for OSX and Linux.  Another option is to start leveraging
>> >> > python's package system to build the interfaces and have the user
>> >> > install those packages separately.
>> >> >
>> >> > Maybe just start with 2.7 for now as that was the last supported
>> >> > Python and punt on Python 3 until after this build?  Might be best so
>> >> > we can coordinate a solution for all platforms.
>> >> >
>> >> > On Sat, Feb 27, 2016 at 1:22 PM, Michael Gogins
>> >> >
>> >> >  wrote:
>> >> >> Another thing, should I support Python 2.7 or Python 3?
>> >> >>
>> >> >> Regards,
>> >> >> Mike
>> >> >>
>> >> >> -----------------------------------------------------
>> >> >> Michael Gogins
>> >> >> Irreducible Productions
>> >> >> http://michaelgogins.tumblr.com
>> >> >> Michael dot Gogins at gmail dot com
>> >> >>
>> >> >>
>> >> >> On Sat, Feb 27, 2016 at 12:54 PM, Michael Gogins
>> >> >>
>> >> >>  wrote:
>> >> >>> I have installed MSYS2, its mingw, toolchain, and the list of
>> >> >>> packages
>> >> >>> from our README.md.
>> >> >>>
>> >> >>> Things have started to build. I have to create an import library
>> >> >>> for
>> >> >>> Python x64. MSYS2 comes with its own Python, but I assume I should
>> >> >>> use
>> >> >>> regular Windows x64 Python from python.org.
>> >> >>>
>> >> >>> The Lua library problem mentioned in our README.md can probably be
>> >> >>> fixed with a file copy or symbolic link.
>> >> >>>
>> >> >>> I have installed NW.js for x64, and plan to use that for HTML5
>> >> >>> stuff.
>> >> >>> The current beta version of NW.js enables NaCl for x64 so a 64 bit
>> >> >>> build of Csound for NaCl should run as well as the 64 bit build of
>> >> >>> csound.node.
>> >> >>>
>> >> >>> I am not sure what to do for CsoundQt. If NW.js works I see no
>> >> >>> particular need to build CsoundQt, but on the other the Qt SDK is
>> >> >>> installed in my MSYS2 environment so CsoundQt shouldn't be that
>> >> >>> hard
>> >> >>> to build.
>> >> >>>
>> >> >>> I also am not sure what to do about the Java interface. Presumably
>> >> >>> you, Steven, would like blue to run with x64 Csound.
>> >> >>>
>> >> >>> I also am not sure what to do about Jack, perhaps Windows support
>> >> >>> for
>> >> >>> Jack now exists, and if so, this could be added to the build.
>> >> >>>
>> >> >>> For a full build I think we should have package recipes for STK,
>> >> >>> LuaJIT, and perhaps NW.js.
>> >> >>>
>> >> >>> There are also compiler warnings about various handles and pointers
>> >> >>> that are different sizes on different platforms. I would like to
>> >> >>> fix
>> >> >>> all of these with some sort of padding or aliasing.
>> >> >>>
>> >> >>> I'm not sure how much of this I can do for the next release but I
>> >> >>> am
>> >> >>> shooting for at least LuaJIT. NW.js, and STK.
>> >> >>>
>> >> >>> Regards,
>> >> >>> Mike
>> >> >>>
>> >> >>> -----------------------------------------------------
>> >> >>> Michael Gogins
>> >> >>> Irreducible Productions
>> >> >>> http://michaelgogins.tumblr.com

It's an odd issue as it's crashing on csoundLock() in csound.c (if my
line numbers match up with yours). I'm wondering what PTHREAD library
was picked up during your run of CMake?   Mine has this in the
CmakeCache.txt:

PTHREAD_LIBRARY:FILEPATH=C:/msys64/mingw64/bin/libwinpthread-1.dll

On Sun, Feb 28, 2016 at 11:58 AM, Rory Walsh  wrote:
> Hi Mike. I'm not sure what the problem there is. You are running the
> build.sh script from the MSYS2 shell? I built afresh again yesterday without
> any issues, albeit with many plugin opcodes disabled.
>
> On 28 February 2016 at 16:44, Michael Gogins 
> wrote:
>>
>> I'm running into a serious problem. I can build csound.exe with
>> MSYS2/mingw64, but it does not run. I have cleaned up my environment
>> so there are no binaries in the PATH but MSYS, mingw, and Csound and
>> its opcodes.
>>
>> (gdb) run
>> Starting program:
>> D:\msys64\home\restore\csound\mingw64\csound-mingw64\csound.exe
>> [New Thread 5784.0x6d8]
>>
>> Program received signal SIGSEGV, Segmentation fault.
>> 0x000007f8f3d17740 in ntdll!RtlMultiAppendUnicodeStringBuffer ()
>>    from C:\Windows\SYSTEM32\ntdll.dll
>> (gdb) bt
>> #0  0x000007f8f3d17740 in ntdll!RtlMultiAppendUnicodeStringBuffer ()
>>    from C:\Windows\SYSTEM32\ntdll.dll
>> #1  0x000007f8f3d0c5a5 in ntdll!RtlInitializeCriticalSection ()
>>    from C:\Windows\SYSTEM32\ntdll.dll
>> #2  0x000000006c5eed8d in csoundInitialize (flags=flags@entry=1)
>>     at D:/msys64/home/restore/csound/Top/csound.c:1119
>> #3  0x0000000000402fe5 in main (argc=1, argv=0x304700)
>>     at D:/msys64/home/restore/csound/frontends/csound/csound_main.c:258
>> (gdb)
>>
>>
>> -----------------------------------------------------
>> Michael Gogins
>> Irreducible Productions
>> http://michaelgogins.tumblr.com
>> Michael dot Gogins at gmail dot com
>>
>>
>> On Sat, Feb 27, 2016 at 4:33 PM, Victor Lazzarini
>>  wrote:
>> > Maybe try to get one of the Norwegian guys, they know about Windows.
>> >
>> > Victor Lazzarini
>> > Dean of Arts, Celtic Studies, and Philosophy
>> > Maynooth University
>> > Ireland
>> >
>> > On 27 Feb 2016, at 20:48, Tarmo Johannes  wrote:
>> >
>> > Hi,
>> > This is a problematic topic. We just discussed it with Joachim and don't
>> > have a dedicee to it right - there is truly lack of experienced Windows
>> > people... But keep thinking about it. I will read about MSYS2 myself too
>> > to
>> > be more aware.
>> > Thanks!
>> > Tarmo
>> >
>> > 27.02.2016 21:51 kirjutas kuupäeval "Steven Yi" :
>> >>
>> >> Hi Tarmo,
>> >>
>> >> Regarding CsoundQT, is there someone from the CsoundQT developers that
>> >> could contribute time to investigating building on Windows with MSYS2?
>> >>
>> >> Thanks!
>> >> steven
>> >>
>> >>
>> >> On Sat, Feb 27, 2016 at 1:57 PM, Tarmo Johannes 
>> >> wrote:
>> >> > Hi,
>> >> >
>> >> > And if you say MSYS2 has Qt, please do build alwo CsoundQt and let
>> >> > know
>> >> > if
>> >> > there are any problems or anything to do in the source code or
>> >> > project
>> >> > files.
>> >> >
>> >> > Thanks!
>> >> >
>> >> > On Saturday 27 February 2016 13:42:28 you wrote:
>> >> >> I will go with Python 2.7 for now.
>> >> >>
>> >> >> Best,
>> >> >> Mike
>> >> >>
>> >> >> -----------------------------------------------------
>> >> >> Michael Gogins
>> >> >> Irreducible Productions
>> >> >> http://michaelgogins.tumblr.com
>> >> >> Michael dot Gogins at gmail dot com
>> >> >>
>> >> >> On Sat, Feb 27, 2016 at 1:39 PM, Steven Yi 
>> >> >> wrote:
>> >> >> > I've been building for 2.7 myself.  I suppose the only way to
>> >> >> > satisfy
>> >> >> > everyone is to build something that works for both.  Perhaps we
>> >> >> > should
>> >> >> > finally add a build target specifically for Python 3 for all
>> >> >> > platforms?  We'd have to work out all the details for install
>> >> >> > locations for OSX and Linux.  Another option is to start
>> >> >> > leveraging
>> >> >> > python's package system to build the interfaces and have the user
>> >> >> > install those packages separately.
>> >> >> >
>> >> >> > Maybe just start with 2.7 for now as that was the last supported
>> >> >> > Python and punt on Python 3 until after this build?  Might be best
>> >> >> > so
>> >> >> > we can coordinate a solution for all platforms.
>> >> >> >
>> >> >> > On Sat, Feb 27, 2016 at 1:22 PM, Michael Gogins
>> >> >> >
>> >> >> >  wrote:
>> >> >> >> Another thing, should I support Python 2.7 or Python 3?
>> >> >> >>
>> >> >> >> Regards,
>> >> >> >> Mike
>> >> >> >>
>> >> >> >> -----------------------------------------------------
>> >> >> >> Michael Gogins
>> >> >> >> Irreducible Productions
>> >> >> >> http://michaelgogins.tumblr.com
>> >> >> >> Michael dot Gogins at gmail dot com
>> >> >> >>
>> >> >> >>
>> >> >> >> On Sat, Feb 27, 2016 at 12:54 PM, Michael Gogins
>> >> >> >>
>> >> >> >>  wrote:
>> >> >> >>> I have installed MSYS2, its mingw, toolchain, and the list of
>> >> >> >>> packages
>> >> >> >>> from our README.md.
>> >> >> >>>
>> >> >> >>> Things have started to build. I have to create an import library
>> >> >> >>> for
>> >> >> >>> Python x64. MSYS2 comes with its own Python, but I assume I
>> >> >> >>> should
>> >> >> >>> use
>> >> >> >>> regular Windows x64 Python from python.org.
>> >> >> >>>
>> >> >> >>> The Lua library problem mentioned in our README.md can probably
>> >> >> >>> be
>> >> >> >>> fixed with a file copy or symbolic link.
>> >> >> >>>
>> >> >> >>> I have installed NW.js for x64, and plan to use that for HTML5
>> >> >> >>> stuff.
>> >> >> >>> The current beta version of NW.js enables NaCl for x64 so a 64
>> >> >> >>> bit
>> >> >> >>> build of Csound for NaCl should run as well as the 64 bit build
>> >> >> >>> of
>> >> >> >>> csound.node.
>> >> >> >>>
>> >> >> >>> I am not sure what to do for CsoundQt. If NW.js works I see no
>> >> >> >>> particular need to build CsoundQt, but on the other the Qt SDK
>> >> >> >>> is
>> >> >> >>> installed in my MSYS2 environment so CsoundQt shouldn't be that
>> >> >> >>> hard
>> >> >> >>> to build.
>> >> >> >>>
>> >> >> >>> I also am not sure what to do about the Java interface.
>> >> >> >>> Presumably
>> >> >> >>> you, Steven, would like blue to run with x64 Csound.
>> >> >> >>>
>> >> >> >>> I also am not sure what to do about Jack, perhaps Windows
>> >> >> >>> support
>> >> >> >>> for
>> >> >> >>> Jack now exists, and if so, this could be added to the build.
>> >> >> >>>
>> >> >> >>> For a full build I think we should have package recipes for STK,
>> >> >> >>> LuaJIT, and perhaps NW.js.
>> >> >> >>>
>> >> >> >>> There are also compiler warnings about various handles and
>> >> >> >>> pointers
>> >> >> >>> that are different sizes on different platforms. I would like to
>> >> >> >>> fix
>> >> >> >>> all of these with some sort of padding or aliasing.
>> >> >> >>>
>> >> >> >>> I'm not sure how much of this I can do for the next release but
>> >> >> >>> I
>> >> >> >>> am
>> >> >> >>> shooting for at least LuaJIT. NW.js, and STK.
>> >> >> >>>
>> >> >> >>> Regards,
>> >> >> >>> Mike
>> >> >> >>>
>> >> >> >>> -----------------------------------------------------
>> >> >> >>> Michael Gogins
>> >> >> >>> Irreducible Productions
>> >> >> >>> http://michaelgogins.tumblr.com
>> >> >> >>> Michael dot Gogins at gmail dot com
>

I am running the build script from the MINGW64 shell, not the MSYS2
shell. MSYS2 installs both of these shells.

Regards,
Mike

-----------------------------------------------------
Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com


On Sun, Feb 28, 2016 at 11:58 AM, Rory Walsh  wrote:
> Hi Mike. I'm not sure what the problem there is. You are running the
> build.sh script from the MSYS2 shell? I built afresh again yesterday without
> any issues, albeit with many plugin opcodes disabled.
>
> On 28 February 2016 at 16:44, Michael Gogins 
> wrote:
>>
>> I'm running into a serious problem. I can build csound.exe with
>> MSYS2/mingw64, but it does not run. I have cleaned up my environment
>> so there are no binaries in the PATH but MSYS, mingw, and Csound and
>> its opcodes.
>>
>> (gdb) run
>> Starting program:
>> D:\msys64\home\restore\csound\mingw64\csound-mingw64\csound.exe
>> [New Thread 5784.0x6d8]
>>
>> Program received signal SIGSEGV, Segmentation fault.
>> 0x000007f8f3d17740 in ntdll!RtlMultiAppendUnicodeStringBuffer ()
>>    from C:\Windows\SYSTEM32\ntdll.dll
>> (gdb) bt
>> #0  0x000007f8f3d17740 in ntdll!RtlMultiAppendUnicodeStringBuffer ()
>>    from C:\Windows\SYSTEM32\ntdll.dll
>> #1  0x000007f8f3d0c5a5 in ntdll!RtlInitializeCriticalSection ()
>>    from C:\Windows\SYSTEM32\ntdll.dll
>> #2  0x000000006c5eed8d in csoundInitialize (flags=flags@entry=1)
>>     at D:/msys64/home/restore/csound/Top/csound.c:1119
>> #3  0x0000000000402fe5 in main (argc=1, argv=0x304700)
>>     at D:/msys64/home/restore/csound/frontends/csound/csound_main.c:258
>> (gdb)
>>
>>
>> -----------------------------------------------------
>> Michael Gogins
>> Irreducible Productions
>> http://michaelgogins.tumblr.com
>> Michael dot Gogins at gmail dot com
>>
>>
>> On Sat, Feb 27, 2016 at 4:33 PM, Victor Lazzarini
>>  wrote:
>> > Maybe try to get one of the Norwegian guys, they know about Windows.
>> >
>> > Victor Lazzarini
>> > Dean of Arts, Celtic Studies, and Philosophy
>> > Maynooth University
>> > Ireland
>> >
>> > On 27 Feb 2016, at 20:48, Tarmo Johannes  wrote:
>> >
>> > Hi,
>> > This is a problematic topic. We just discussed it with Joachim and don't
>> > have a dedicee to it right - there is truly lack of experienced Windows
>> > people... But keep thinking about it. I will read about MSYS2 myself too
>> > to
>> > be more aware.
>> > Thanks!
>> > Tarmo
>> >
>> > 27.02.2016 21:51 kirjutas kuupäeval "Steven Yi" :
>> >>
>> >> Hi Tarmo,
>> >>
>> >> Regarding CsoundQT, is there someone from the CsoundQT developers that
>> >> could contribute time to investigating building on Windows with MSYS2?
>> >>
>> >> Thanks!
>> >> steven
>> >>
>> >>
>> >> On Sat, Feb 27, 2016 at 1:57 PM, Tarmo Johannes 
>> >> wrote:
>> >> > Hi,
>> >> >
>> >> > And if you say MSYS2 has Qt, please do build alwo CsoundQt and let
>> >> > know
>> >> > if
>> >> > there are any problems or anything to do in the source code or
>> >> > project
>> >> > files.
>> >> >
>> >> > Thanks!
>> >> >
>> >> > On Saturday 27 February 2016 13:42:28 you wrote:
>> >> >> I will go with Python 2.7 for now.
>> >> >>
>> >> >> Best,
>> >> >> Mike
>> >> >>
>> >> >> -----------------------------------------------------
>> >> >> Michael Gogins
>> >> >> Irreducible Productions
>> >> >> http://michaelgogins.tumblr.com
>> >> >> Michael dot Gogins at gmail dot com
>> >> >>
>> >> >> On Sat, Feb 27, 2016 at 1:39 PM, Steven Yi 
>> >> >> wrote:
>> >> >> > I've been building for 2.7 myself.  I suppose the only way to
>> >> >> > satisfy
>> >> >> > everyone is to build something that works for both.  Perhaps we
>> >> >> > should
>> >> >> > finally add a build target specifically for Python 3 for all
>> >> >> > platforms?  We'd have to work out all the details for install
>> >> >> > locations for OSX and Linux.  Another option is to start
>> >> >> > leveraging
>> >> >> > python's package system to build the interfaces and have the user
>> >> >> > install those packages separately.
>> >> >> >
>> >> >> > Maybe just start with 2.7 for now as that was the last supported
>> >> >> > Python and punt on Python 3 until after this build?  Might be best
>> >> >> > so
>> >> >> > we can coordinate a solution for all platforms.
>> >> >> >
>> >> >> > On Sat, Feb 27, 2016 at 1:22 PM, Michael Gogins
>> >> >> >
>> >> >> >  wrote:
>> >> >> >> Another thing, should I support Python 2.7 or Python 3?
>> >> >> >>
>> >> >> >> Regards,
>> >> >> >> Mike
>> >> >> >>
>> >> >> >> -----------------------------------------------------
>> >> >> >> Michael Gogins
>> >> >> >> Irreducible Productions
>> >> >> >> http://michaelgogins.tumblr.com
>> >> >> >> Michael dot Gogins at gmail dot com
>> >> >> >>
>> >> >> >>
>> >> >> >> On Sat, Feb 27, 2016 at 12:54 PM, Michael Gogins
>> >> >> >>
>> >> >> >>  wrote:
>> >> >> >>> I have installed MSYS2, its mingw, toolchain, and the list of
>> >> >> >>> packages
>> >> >> >>> from our README.md.
>> >> >> >>>
>> >> >> >>> Things have started to build. I have to create an import library
>> >> >> >>> for
>> >> >> >>> Python x64. MSYS2 comes with its own Python, but I assume I
>> >> >> >>> should
>> >> >> >>> use
>> >> >> >>> regular Windows x64 Python from python.org.
>> >> >> >>>
>> >> >> >>> The Lua library problem mentioned in our README.md can probably
>> >> >> >>> be
>> >> >> >>> fixed with a file copy or symbolic link.
>> >> >> >>>
>> >> >> >>> I have installed NW.js for x64, and plan to use that for HTML5
>> >> >> >>> stuff.
>> >> >> >>> The current beta version of NW.js enables NaCl for x64 so a 64
>> >> >> >>> bit
>> >> >> >>> build of Csound for NaCl should run as well as the 64 bit build
>> >> >> >>> of
>> >> >> >>> csound.node.
>> >> >> >>>
>> >> >> >>> I am not sure what to do for CsoundQt. If NW.js works I see no
>> >> >> >>> particular need to build CsoundQt, but on the other the Qt SDK
>> >> >> >>> is
>> >> >> >>> installed in my MSYS2 environment so CsoundQt shouldn't be that
>> >> >> >>> hard
>> >> >> >>> to build.
>> >> >> >>>
>> >> >> >>> I also am not sure what to do about the Java interface.
>> >> >> >>> Presumably
>> >> >> >>> you, Steven, would like blue to run with x64 Csound.
>> >> >> >>>
>> >> >> >>> I also am not sure what to do about Jack, perhaps Windows
>> >> >> >>> support
>> >> >> >>> for
>> >> >> >>> Jack now exists, and if so, this could be added to the build.
>> >> >> >>>
>> >> >> >>> For a full build I think we should have package recipes for STK,
>> >> >> >>> LuaJIT, and perhaps NW.js.
>> >> >> >>>
>> >> >> >>> There are also compiler warnings about various handles and
>> >> >> >>> pointers
>> >> >> >>> that are different sizes on different platforms. I would like to
>> >> >> >>> fix
>> >> >> >>> all of these with some sort of padding or aliasing.
>> >> >> >>>
>> >> >> >>> I'm not sure how much of this I can do for the next release but
>> >> >> >>> I
>> >> >> >>> am
>> >> >> >>> shooting for at least LuaJIT. NW.js, and STK.
>> >> >> >>>
>> >> >> >>> Regards,
>> >> >> >>> Mike
>> >> >> >>>
>> >> >> >>> -----------------------------------------------------
>> >> >> >>> Michael Gogins
>> >> >> >>> Irreducible Productions
>> >> >> >>> http://michaelgogins.tumblr.com
>> >> >> >>> Michael dot Gogins at gmail dot com
>

Mine has that as well: D:/msys64/mingw64/bin/libwinpthread-1.dll.

But perhaps there is one of these in the WIndows system directories, I
am checking.

Best,
Mike


-----------------------------------------------------
Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com


On Sun, Feb 28, 2016 at 12:06 PM, Michael Gogins
 wrote:
> I am running the build script from the MINGW64 shell, not the MSYS2
> shell. MSYS2 installs both of these shells.
>
> Regards,
> Mike
>
> -----------------------------------------------------
> Michael Gogins
> Irreducible Productions
> http://michaelgogins.tumblr.com
> Michael dot Gogins at gmail dot com
>
>
> On Sun, Feb 28, 2016 at 11:58 AM, Rory Walsh  wrote:
>> Hi Mike. I'm not sure what the problem there is. You are running the
>> build.sh script from the MSYS2 shell? I built afresh again yesterday without
>> any issues, albeit with many plugin opcodes disabled.
>>
>> On 28 February 2016 at 16:44, Michael Gogins 
>> wrote:
>>>
>>> I'm running into a serious problem. I can build csound.exe with
>>> MSYS2/mingw64, but it does not run. I have cleaned up my environment
>>> so there are no binaries in the PATH but MSYS, mingw, and Csound and
>>> its opcodes.
>>>
>>> (gdb) run
>>> Starting program:
>>> D:\msys64\home\restore\csound\mingw64\csound-mingw64\csound.exe
>>> [New Thread 5784.0x6d8]
>>>
>>> Program received signal SIGSEGV, Segmentation fault.
>>> 0x000007f8f3d17740 in ntdll!RtlMultiAppendUnicodeStringBuffer ()
>>>    from C:\Windows\SYSTEM32\ntdll.dll
>>> (gdb) bt
>>> #0  0x000007f8f3d17740 in ntdll!RtlMultiAppendUnicodeStringBuffer ()
>>>    from C:\Windows\SYSTEM32\ntdll.dll
>>> #1  0x000007f8f3d0c5a5 in ntdll!RtlInitializeCriticalSection ()
>>>    from C:\Windows\SYSTEM32\ntdll.dll
>>> #2  0x000000006c5eed8d in csoundInitialize (flags=flags@entry=1)
>>>     at D:/msys64/home/restore/csound/Top/csound.c:1119
>>> #3  0x0000000000402fe5 in main (argc=1, argv=0x304700)
>>>     at D:/msys64/home/restore/csound/frontends/csound/csound_main.c:258
>>> (gdb)
>>>
>>>
>>> -----------------------------------------------------
>>> Michael Gogins
>>> Irreducible Productions
>>> http://michaelgogins.tumblr.com
>>> Michael dot Gogins at gmail dot com
>>>
>>>
>>> On Sat, Feb 27, 2016 at 4:33 PM, Victor Lazzarini
>>>  wrote:
>>> > Maybe try to get one of the Norwegian guys, they know about Windows.
>>> >
>>> > Victor Lazzarini
>>> > Dean of Arts, Celtic Studies, and Philosophy
>>> > Maynooth University
>>> > Ireland
>>> >
>>> > On 27 Feb 2016, at 20:48, Tarmo Johannes  wrote:
>>> >
>>> > Hi,
>>> > This is a problematic topic. We just discussed it with Joachim and don't
>>> > have a dedicee to it right - there is truly lack of experienced Windows
>>> > people... But keep thinking about it. I will read about MSYS2 myself too
>>> > to
>>> > be more aware.
>>> > Thanks!
>>> > Tarmo
>>> >
>>> > 27.02.2016 21:51 kirjutas kuupäeval "Steven Yi" :
>>> >>
>>> >> Hi Tarmo,
>>> >>
>>> >> Regarding CsoundQT, is there someone from the CsoundQT developers that
>>> >> could contribute time to investigating building on Windows with MSYS2?
>>> >>
>>> >> Thanks!
>>> >> steven
>>> >>
>>> >>
>>> >> On Sat, Feb 27, 2016 at 1:57 PM, Tarmo Johannes 
>>> >> wrote:
>>> >> > Hi,
>>> >> >
>>> >> > And if you say MSYS2 has Qt, please do build alwo CsoundQt and let
>>> >> > know
>>> >> > if
>>> >> > there are any problems or anything to do in the source code or
>>> >> > project
>>> >> > files.
>>> >> >
>>> >> > Thanks!
>>> >> >
>>> >> > On Saturday 27 February 2016 13:42:28 you wrote:
>>> >> >> I will go with Python 2.7 for now.
>>> >> >>
>>> >> >> Best,
>>> >> >> Mike
>>> >> >>
>>> >> >> -----------------------------------------------------
>>> >> >> Michael Gogins
>>> >> >> Irreducible Productions
>>> >> >> http://michaelgogins.tumblr.com
>>> >> >> Michael dot Gogins at gmail dot com
>>> >> >>
>>> >> >> On Sat, Feb 27, 2016 at 1:39 PM, Steven Yi 
>>> >> >> wrote:
>>> >> >> > I've been building for 2.7 myself.  I suppose the only way to
>>> >> >> > satisfy
>>> >> >> > everyone is to build something that works for both.  Perhaps we
>>> >> >> > should
>>> >> >> > finally add a build target specifically for Python 3 for all
>>> >> >> > platforms?  We'd have to work out all the details for install
>>> >> >> > locations for OSX and Linux.  Another option is to start
>>> >> >> > leveraging
>>> >> >> > python's package system to build the interfaces and have the user
>>> >> >> > install those packages separately.
>>> >> >> >
>>> >> >> > Maybe just start with 2.7 for now as that was the last supported
>>> >> >> > Python and punt on Python 3 until after this build?  Might be best
>>> >> >> > so
>>> >> >> > we can coordinate a solution for all platforms.
>>> >> >> >
>>> >> >> > On Sat, Feb 27, 2016 at 1:22 PM, Michael Gogins
>>> >> >> >
>>> >> >> >  wrote:
>>> >> >> >> Another thing, should I support Python 2.7 or Python 3?
>>> >> >> >>
>>> >> >> >> Regards,
>>> >> >> >> Mike
>>> >> >> >>
>>> >> >> >> -----------------------------------------------------
>>> >> >> >> Michael Gogins
>>> >> >> >> Irreducible Productions
>>> >> >> >> http://michaelgogins.tumblr.com
>>> >> >> >> Michael dot Gogins at gmail dot com
>>> >> >> >>
>>> >> >> >>
>>> >> >> >> On Sat, Feb 27, 2016 at 12:54 PM, Michael Gogins
>>> >> >> >>
>>> >> >> >>  wrote:
>>> >> >> >>> I have installed MSYS2, its mingw, toolchain, and the list of
>>> >> >> >>> packages
>>> >> >> >>> from our README.md.
>>> >> >> >>>
>>> >> >> >>> Things have started to build. I have to create an import library
>>> >> >> >>> for
>>> >> >> >>> Python x64. MSYS2 comes with its own Python, but I assume I
>>> >> >> >>> should
>>> >> >> >>> use
>>> >> >> >>> regular Windows x64 Python from python.org.
>>> >> >> >>>
>>> >> >> >>> The Lua library problem mentioned in our README.md can probably
>>> >> >> >>> be
>>> >> >> >>> fixed with a file copy or symbolic link.
>>> >> >> >>>
>>> >> >> >>> I have installed NW.js for x64, and plan to use that for HTML5
>>> >> >> >>> stuff.
>>> >> >> >>> The current beta version of NW.js enables NaCl for x64 so a 64
>>> >> >> >>> bit
>>> >> >> >>> build of Csound for NaCl should run as well as the 64 bit build
>>> >> >> >>> of
>>> >> >> >>> csound.node.
>>> >> >> >>>
>>> >> >> >>> I am not sure what to do for CsoundQt. If NW.js works I see no
>>> >> >> >>> particular need to build CsoundQt, but on the other the Qt SDK
>>> >> >> >>> is
>>> >> >> >>> installed in my MSYS2 environment so CsoundQt shouldn't be that
>>> >> >> >>> hard
>>> >> >> >>> to build.
>>> >> >> >>>
>>> >> >> >>> I also am not sure what to do about the Java interface.
>>> >> >> >>> Presumably
>>> >> >> >>> you, Steven, would like blue to run with x64 Csound.
>>> >> >> >>>
>>> >> >> >>> I also am not sure what to do about Jack, perhaps Windows
>>> >> >> >>> support
>>> >> >> >>> for
>>> >> >> >>> Jack now exists, and if so, this could be added to the build.
>>> >> >> >>>
>>> >> >> >>> For a full build I think we should have package recipes for STK,
>>> >> >> >>> LuaJIT, and perhaps NW.js.
>>> >> >> >>>
>>> >> >> >>> There are also compiler warnings about various handles and
>>> >> >> >>> pointers
>>> >> >> >>> that are different sizes on different platforms. I would like to
>>> >> >> >>> fix
>>> >> >> >>> all of these with some sort of padding or aliasing.
>>> >> >> >>>
>>> >> >> >>> I'm not sure how much of this I can do for the next release but
>>> >> >> >>> I
>>> >> >> >>> am
>>> >> >> >>> shooting for at least LuaJIT. NW.js, and STK.
>>> >> >> >>>
>>> >> >> >>> Regards,
>>> >> >> >>> Mike
>>> >> >> >>>
>>> >> >> >>> -----------------------------------------------------
>>> >> >> >>> Michael Gogins
>>> >> >> >>> Irreducible Productions
>>> >> >> >>> http://michaelgogins.tumblr.com
>>> >> >> >>> Michael dot Gogins at gmail dot com
>>

No libwinpthread in WIndows system directories. I am going to run the
dependency checker on Csound.

-----------------------------------------------------
Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com


On Sun, Feb 28, 2016 at 12:08 PM, Michael Gogins
 wrote:
> Mine has that as well: D:/msys64/mingw64/bin/libwinpthread-1.dll.
>
> But perhaps there is one of these in the WIndows system directories, I
> am checking.
>
> Best,
> Mike
>
>
> -----------------------------------------------------
> Michael Gogins
> Irreducible Productions
> http://michaelgogins.tumblr.com
> Michael dot Gogins at gmail dot com
>
>
> On Sun, Feb 28, 2016 at 12:06 PM, Michael Gogins
>  wrote:
>> I am running the build script from the MINGW64 shell, not the MSYS2
>> shell. MSYS2 installs both of these shells.
>>
>> Regards,
>> Mike
>>
>> -----------------------------------------------------
>> Michael Gogins
>> Irreducible Productions
>> http://michaelgogins.tumblr.com
>> Michael dot Gogins at gmail dot com
>>
>>
>> On Sun, Feb 28, 2016 at 11:58 AM, Rory Walsh  wrote:
>>> Hi Mike. I'm not sure what the problem there is. You are running the
>>> build.sh script from the MSYS2 shell? I built afresh again yesterday without
>>> any issues, albeit with many plugin opcodes disabled.
>>>
>>> On 28 February 2016 at 16:44, Michael Gogins 
>>> wrote:
>>>>
>>>> I'm running into a serious problem. I can build csound.exe with
>>>> MSYS2/mingw64, but it does not run. I have cleaned up my environment
>>>> so there are no binaries in the PATH but MSYS, mingw, and Csound and
>>>> its opcodes.
>>>>
>>>> (gdb) run
>>>> Starting program:
>>>> D:\msys64\home\restore\csound\mingw64\csound-mingw64\csound.exe
>>>> [New Thread 5784.0x6d8]
>>>>
>>>> Program received signal SIGSEGV, Segmentation fault.
>>>> 0x000007f8f3d17740 in ntdll!RtlMultiAppendUnicodeStringBuffer ()
>>>>    from C:\Windows\SYSTEM32\ntdll.dll
>>>> (gdb) bt
>>>> #0  0x000007f8f3d17740 in ntdll!RtlMultiAppendUnicodeStringBuffer ()
>>>>    from C:\Windows\SYSTEM32\ntdll.dll
>>>> #1  0x000007f8f3d0c5a5 in ntdll!RtlInitializeCriticalSection ()
>>>>    from C:\Windows\SYSTEM32\ntdll.dll
>>>> #2  0x000000006c5eed8d in csoundInitialize (flags=flags@entry=1)
>>>>     at D:/msys64/home/restore/csound/Top/csound.c:1119
>>>> #3  0x0000000000402fe5 in main (argc=1, argv=0x304700)
>>>>     at D:/msys64/home/restore/csound/frontends/csound/csound_main.c:258
>>>> (gdb)
>>>>
>>>>
>>>> -----------------------------------------------------
>>>> Michael Gogins
>>>> Irreducible Productions
>>>> http://michaelgogins.tumblr.com
>>>> Michael dot Gogins at gmail dot com
>>>>
>>>>
>>>> On Sat, Feb 27, 2016 at 4:33 PM, Victor Lazzarini
>>>>  wrote:
>>>> > Maybe try to get one of the Norwegian guys, they know about Windows.
>>>> >
>>>> > Victor Lazzarini
>>>> > Dean of Arts, Celtic Studies, and Philosophy
>>>> > Maynooth University
>>>> > Ireland
>>>> >
>>>> > On 27 Feb 2016, at 20:48, Tarmo Johannes  wrote:
>>>> >
>>>> > Hi,
>>>> > This is a problematic topic. We just discussed it with Joachim and don't
>>>> > have a dedicee to it right - there is truly lack of experienced Windows
>>>> > people... But keep thinking about it. I will read about MSYS2 myself too
>>>> > to
>>>> > be more aware.
>>>> > Thanks!
>>>> > Tarmo
>>>> >
>>>> > 27.02.2016 21:51 kirjutas kuupäeval "Steven Yi" :
>>>> >>
>>>> >> Hi Tarmo,
>>>> >>
>>>> >> Regarding CsoundQT, is there someone from the CsoundQT developers that
>>>> >> could contribute time to investigating building on Windows with MSYS2?
>>>> >>
>>>> >> Thanks!
>>>> >> steven
>>>> >>
>>>> >>
>>>> >> On Sat, Feb 27, 2016 at 1:57 PM, Tarmo Johannes 
>>>> >> wrote:
>>>> >> > Hi,
>>>> >> >
>>>> >> > And if you say MSYS2 has Qt, please do build alwo CsoundQt and let
>>>> >> > know
>>>> >> > if
>>>> >> > there are any problems or anything to do in the source code or
>>>> >> > project
>>>> >> > files.
>>>> >> >
>>>> >> > Thanks!
>>>> >> >
>>>> >> > On Saturday 27 February 2016 13:42:28 you wrote:
>>>> >> >> I will go with Python 2.7 for now.
>>>> >> >>
>>>> >> >> Best,
>>>> >> >> Mike
>>>> >> >>
>>>> >> >> -----------------------------------------------------
>>>> >> >> Michael Gogins
>>>> >> >> Irreducible Productions
>>>> >> >> http://michaelgogins.tumblr.com
>>>> >> >> Michael dot Gogins at gmail dot com
>>>> >> >>
>>>> >> >> On Sat, Feb 27, 2016 at 1:39 PM, Steven Yi 
>>>> >> >> wrote:
>>>> >> >> > I've been building for 2.7 myself.  I suppose the only way to
>>>> >> >> > satisfy
>>>> >> >> > everyone is to build something that works for both.  Perhaps we
>>>> >> >> > should
>>>> >> >> > finally add a build target specifically for Python 3 for all
>>>> >> >> > platforms?  We'd have to work out all the details for install
>>>> >> >> > locations for OSX and Linux.  Another option is to start
>>>> >> >> > leveraging
>>>> >> >> > python's package system to build the interfaces and have the user
>>>> >> >> > install those packages separately.
>>>> >> >> >
>>>> >> >> > Maybe just start with 2.7 for now as that was the last supported
>>>> >> >> > Python and punt on Python 3 until after this build?  Might be best
>>>> >> >> > so
>>>> >> >> > we can coordinate a solution for all platforms.
>>>> >> >> >
>>>> >> >> > On Sat, Feb 27, 2016 at 1:22 PM, Michael Gogins
>>>> >> >> >
>>>> >> >> >  wrote:
>>>> >> >> >> Another thing, should I support Python 2.7 or Python 3?
>>>> >> >> >>
>>>> >> >> >> Regards,
>>>> >> >> >> Mike
>>>> >> >> >>
>>>> >> >> >> -----------------------------------------------------
>>>> >> >> >> Michael Gogins
>>>> >> >> >> Irreducible Productions
>>>> >> >> >> http://michaelgogins.tumblr.com
>>>> >> >> >> Michael dot Gogins at gmail dot com
>>>> >> >> >>
>>>> >> >> >>
>>>> >> >> >> On Sat, Feb 27, 2016 at 12:54 PM, Michael Gogins
>>>> >> >> >>
>>>> >> >> >>  wrote:
>>>> >> >> >>> I have installed MSYS2, its mingw, toolchain, and the list of
>>>> >> >> >>> packages
>>>> >> >> >>> from our README.md.
>>>> >> >> >>>
>>>> >> >> >>> Things have started to build. I have to create an import library
>>>> >> >> >>> for
>>>> >> >> >>> Python x64. MSYS2 comes with its own Python, but I assume I
>>>> >> >> >>> should
>>>> >> >> >>> use
>>>> >> >> >>> regular Windows x64 Python from python.org.
>>>> >> >> >>>
>>>> >> >> >>> The Lua library problem mentioned in our README.md can probably
>>>> >> >> >>> be
>>>> >> >> >>> fixed with a file copy or symbolic link.
>>>> >> >> >>>
>>>> >> >> >>> I have installed NW.js for x64, and plan to use that for HTML5
>>>> >> >> >>> stuff.
>>>> >> >> >>> The current beta version of NW.js enables NaCl for x64 so a 64
>>>> >> >> >>> bit
>>>> >> >> >>> build of Csound for NaCl should run as well as the 64 bit build
>>>> >> >> >>> of
>>>> >> >> >>> csound.node.
>>>> >> >> >>>
>>>> >> >> >>> I am not sure what to do for CsoundQt. If NW.js works I see no
>>>> >> >> >>> particular need to build CsoundQt, but on the other the Qt SDK
>>>> >> >> >>> is
>>>> >> >> >>> installed in my MSYS2 environment so CsoundQt shouldn't be that
>>>> >> >> >>> hard
>>>> >> >> >>> to build.
>>>> >> >> >>>
>>>> >> >> >>> I also am not sure what to do about the Java interface.
>>>> >> >> >>> Presumably
>>>> >> >> >>> you, Steven, would like blue to run with x64 Csound.
>>>> >> >> >>>
>>>> >> >> >>> I also am not sure what to do about Jack, perhaps Windows
>>>> >> >> >>> support
>>>> >> >> >>> for
>>>> >> >> >>> Jack now exists, and if so, this could be added to the build.
>>>> >> >> >>>
>>>> >> >> >>> For a full build I think we should have package recipes for STK,
>>>> >> >> >>> LuaJIT, and perhaps NW.js.
>>>> >> >> >>>
>>>> >> >> >>> There are also compiler warnings about various handles and
>>>> >> >> >>> pointers
>>>> >> >> >>> that are different sizes on different platforms. I would like to
>>>> >> >> >>> fix
>>>> >> >> >>> all of these with some sort of padding or aliasing.
>>>> >> >> >>>
>>>> >> >> >>> I'm not sure how much of this I can do for the next release but
>>>> >> >> >>> I
>>>> >> >> >>> am
>>>> >> >> >>> shooting for at least LuaJIT. NW.js, and STK.
>>>> >> >> >>>
>>>> >> >> >>> Regards,
>>>> >> >> >>> Mike
>>>> >> >> >>>
>>>> >> >> >>> -----------------------------------------------------
>>>> >> >> >>> Michael Gogins
>>>> >> >> >>> Irreducible Productions
>>>> >> >> >>> http://michaelgogins.tumblr.com
>>>> >> >> >>> Michael dot Gogins at gmail dot com
>>>

All DLLs shown by the 64 bit dependency walker are in WIndows/system32
or in the Csound build directory. Also they are all x64 as they should
be. LIbsndfile does not show up however which seems wrong. Is it
staticallhy linked now?

Regards,
Mike

-----------------------------------------------------
Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com


On Sun, Feb 28, 2016 at 12:17 PM, Michael Gogins
 wrote:
> No libwinpthread in WIndows system directories. I am going to run the
> dependency checker on Csound.
>
> -----------------------------------------------------
> Michael Gogins
> Irreducible Productions
> http://michaelgogins.tumblr.com
> Michael dot Gogins at gmail dot com
>
>
> On Sun, Feb 28, 2016 at 12:08 PM, Michael Gogins
>  wrote:
>> Mine has that as well: D:/msys64/mingw64/bin/libwinpthread-1.dll.
>>
>> But perhaps there is one of these in the WIndows system directories, I
>> am checking.
>>
>> Best,
>> Mike
>>
>>
>> -----------------------------------------------------
>> Michael Gogins
>> Irreducible Productions
>> http://michaelgogins.tumblr.com
>> Michael dot Gogins at gmail dot com
>>
>>
>> On Sun, Feb 28, 2016 at 12:06 PM, Michael Gogins
>>  wrote:
>>> I am running the build script from the MINGW64 shell, not the MSYS2
>>> shell. MSYS2 installs both of these shells.
>>>
>>> Regards,
>>> Mike
>>>
>>> -----------------------------------------------------
>>> Michael Gogins
>>> Irreducible Productions
>>> http://michaelgogins.tumblr.com
>>> Michael dot Gogins at gmail dot com
>>>
>>>
>>> On Sun, Feb 28, 2016 at 11:58 AM, Rory Walsh  wrote:
>>>> Hi Mike. I'm not sure what the problem there is. You are running the
>>>> build.sh script from the MSYS2 shell? I built afresh again yesterday without
>>>> any issues, albeit with many plugin opcodes disabled.
>>>>
>>>> On 28 February 2016 at 16:44, Michael Gogins 
>>>> wrote:
>>>>>
>>>>> I'm running into a serious problem. I can build csound.exe with
>>>>> MSYS2/mingw64, but it does not run. I have cleaned up my environment
>>>>> so there are no binaries in the PATH but MSYS, mingw, and Csound and
>>>>> its opcodes.
>>>>>
>>>>> (gdb) run
>>>>> Starting program:
>>>>> D:\msys64\home\restore\csound\mingw64\csound-mingw64\csound.exe
>>>>> [New Thread 5784.0x6d8]
>>>>>
>>>>> Program received signal SIGSEGV, Segmentation fault.
>>>>> 0x000007f8f3d17740 in ntdll!RtlMultiAppendUnicodeStringBuffer ()
>>>>>    from C:\Windows\SYSTEM32\ntdll.dll
>>>>> (gdb) bt
>>>>> #0  0x000007f8f3d17740 in ntdll!RtlMultiAppendUnicodeStringBuffer ()
>>>>>    from C:\Windows\SYSTEM32\ntdll.dll
>>>>> #1  0x000007f8f3d0c5a5 in ntdll!RtlInitializeCriticalSection ()
>>>>>    from C:\Windows\SYSTEM32\ntdll.dll
>>>>> #2  0x000000006c5eed8d in csoundInitialize (flags=flags@entry=1)
>>>>>     at D:/msys64/home/restore/csound/Top/csound.c:1119
>>>>> #3  0x0000000000402fe5 in main (argc=1, argv=0x304700)
>>>>>     at D:/msys64/home/restore/csound/frontends/csound/csound_main.c:258
>>>>> (gdb)
>>>>>
>>>>>
>>>>> -----------------------------------------------------
>>>>> Michael Gogins
>>>>> Irreducible Productions
>>>>> http://michaelgogins.tumblr.com
>>>>> Michael dot Gogins at gmail dot com
>>>>>
>>>>>
>>>>> On Sat, Feb 27, 2016 at 4:33 PM, Victor Lazzarini
>>>>>  wrote:
>>>>> > Maybe try to get one of the Norwegian guys, they know about Windows.
>>>>> >
>>>>> > Victor Lazzarini
>>>>> > Dean of Arts, Celtic Studies, and Philosophy
>>>>> > Maynooth University
>>>>> > Ireland
>>>>> >
>>>>> > On 27 Feb 2016, at 20:48, Tarmo Johannes  wrote:
>>>>> >
>>>>> > Hi,
>>>>> > This is a problematic topic. We just discussed it with Joachim and don't
>>>>> > have a dedicee to it right - there is truly lack of experienced Windows
>>>>> > people... But keep thinking about it. I will read about MSYS2 myself too
>>>>> > to
>>>>> > be more aware.
>>>>> > Thanks!
>>>>> > Tarmo
>>>>> >
>>>>> > 27.02.2016 21:51 kirjutas kuupäeval "Steven Yi" :
>>>>> >>
>>>>> >> Hi Tarmo,
>>>>> >>
>>>>> >> Regarding CsoundQT, is there someone from the CsoundQT developers that
>>>>> >> could contribute time to investigating building on Windows with MSYS2?
>>>>> >>
>>>>> >> Thanks!
>>>>> >> steven
>>>>> >>
>>>>> >>
>>>>> >> On Sat, Feb 27, 2016 at 1:57 PM, Tarmo Johannes 
>>>>> >> wrote:
>>>>> >> > Hi,
>>>>> >> >
>>>>> >> > And if you say MSYS2 has Qt, please do build alwo CsoundQt and let
>>>>> >> > know
>>>>> >> > if
>>>>> >> > there are any problems or anything to do in the source code or
>>>>> >> > project
>>>>> >> > files.
>>>>> >> >
>>>>> >> > Thanks!
>>>>> >> >
>>>>> >> > On Saturday 27 February 2016 13:42:28 you wrote:
>>>>> >> >> I will go with Python 2.7 for now.
>>>>> >> >>
>>>>> >> >> Best,
>>>>> >> >> Mike
>>>>> >> >>
>>>>> >> >> -----------------------------------------------------
>>>>> >> >> Michael Gogins
>>>>> >> >> Irreducible Productions
>>>>> >> >> http://michaelgogins.tumblr.com
>>>>> >> >> Michael dot Gogins at gmail dot com
>>>>> >> >>
>>>>> >> >> On Sat, Feb 27, 2016 at 1:39 PM, Steven Yi 
>>>>> >> >> wrote:
>>>>> >> >> > I've been building for 2.7 myself.  I suppose the only way to
>>>>> >> >> > satisfy
>>>>> >> >> > everyone is to build something that works for both.  Perhaps we
>>>>> >> >> > should
>>>>> >> >> > finally add a build target specifically for Python 3 for all
>>>>> >> >> > platforms?  We'd have to work out all the details for install
>>>>> >> >> > locations for OSX and Linux.  Another option is to start
>>>>> >> >> > leveraging
>>>>> >> >> > python's package system to build the interfaces and have the user
>>>>> >> >> > install those packages separately.
>>>>> >> >> >
>>>>> >> >> > Maybe just start with 2.7 for now as that was the last supported
>>>>> >> >> > Python and punt on Python 3 until after this build?  Might be best
>>>>> >> >> > so
>>>>> >> >> > we can coordinate a solution for all platforms.
>>>>> >> >> >
>>>>> >> >> > On Sat, Feb 27, 2016 at 1:22 PM, Michael Gogins
>>>>> >> >> >
>>>>> >> >> >  wrote:
>>>>> >> >> >> Another thing, should I support Python 2.7 or Python 3?
>>>>> >> >> >>
>>>>> >> >> >> Regards,
>>>>> >> >> >> Mike
>>>>> >> >> >>
>>>>> >> >> >> -----------------------------------------------------
>>>>> >> >> >> Michael Gogins
>>>>> >> >> >> Irreducible Productions
>>>>> >> >> >> http://michaelgogins.tumblr.com
>>>>> >> >> >> Michael dot Gogins at gmail dot com
>>>>> >> >> >>
>>>>> >> >> >>
>>>>> >> >> >> On Sat, Feb 27, 2016 at 12:54 PM, Michael Gogins
>>>>> >> >> >>
>>>>> >> >> >>  wrote:
>>>>> >> >> >>> I have installed MSYS2, its mingw, toolchain, and the list of
>>>>> >> >> >>> packages
>>>>> >> >> >>> from our README.md.
>>>>> >> >> >>>
>>>>> >> >> >>> Things have started to build. I have to create an import library
>>>>> >> >> >>> for
>>>>> >> >> >>> Python x64. MSYS2 comes with its own Python, but I assume I
>>>>> >> >> >>> should
>>>>> >> >> >>> use
>>>>> >> >> >>> regular Windows x64 Python from python.org.
>>>>> >> >> >>>
>>>>> >> >> >>> The Lua library problem mentioned in our README.md can probably
>>>>> >> >> >>> be
>>>>> >> >> >>> fixed with a file copy or symbolic link.
>>>>> >> >> >>>
>>>>> >> >> >>> I have installed NW.js for x64, and plan to use that for HTML5
>>>>> >> >> >>> stuff.
>>>>> >> >> >>> The current beta version of NW.js enables NaCl for x64 so a 64
>>>>> >> >> >>> bit
>>>>> >> >> >>> build of Csound for NaCl should run as well as the 64 bit build
>>>>> >> >> >>> of
>>>>> >> >> >>> csound.node.
>>>>> >> >> >>>
>>>>> >> >> >>> I am not sure what to do for CsoundQt. If NW.js works I see no
>>>>> >> >> >>> particular need to build CsoundQt, but on the other the Qt SDK
>>>>> >> >> >>> is
>>>>> >> >> >>> installed in my MSYS2 environment so CsoundQt shouldn't be that
>>>>> >> >> >>> hard
>>>>> >> >> >>> to build.
>>>>> >> >> >>>
>>>>> >> >> >>> I also am not sure what to do about the Java interface.
>>>>> >> >> >>> Presumably
>>>>> >> >> >>> you, Steven, would like blue to run with x64 Csound.
>>>>> >> >> >>>
>>>>> >> >> >>> I also am not sure what to do about Jack, perhaps Windows
>>>>> >> >> >>> support
>>>>> >> >> >>> for
>>>>> >> >> >>> Jack now exists, and if so, this could be added to the build.
>>>>> >> >> >>>
>>>>> >> >> >>> For a full build I think we should have package recipes for STK,
>>>>> >> >> >>> LuaJIT, and perhaps NW.js.
>>>>> >> >> >>>
>>>>> >> >> >>> There are also compiler warnings about various handles and
>>>>> >> >> >>> pointers
>>>>> >> >> >>> that are different sizes on different platforms. I would like to
>>>>> >> >> >>> fix
>>>>> >> >> >>> all of these with some sort of padding or aliasing.
>>>>> >> >> >>>
>>>>> >> >> >>> I'm not sure how much of this I can do for the next release but
>>>>> >> >> >>> I
>>>>> >> >> >>> am
>>>>> >> >> >>> shooting for at least LuaJIT. NW.js, and STK.
>>>>> >> >> >>>
>>>>> >> >> >>> Regards,
>>>>> >> >> >>> Mike
>>>>> >> >> >>>
>>>>> >> >> >>> -----------------------------------------------------
>>>>> >> >> >>> Michael Gogins
>>>>> >> >> >>> Irreducible Productions
>>>>> >> >> >>> http://michaelgogins.tumblr.com
>>>>> >> >> >>> Michael dot Gogins at gmail dot com
>>>>

csGblMtx.h (ghastly filename) uses WIndows threads in my build. Is
there some mixup between Windows threads and pthreads? It almost looks
like EnterCriticalSection (Windows API) is being called without the
critical section object first being initialized. Are you defining
WIN32 or GNUC or what for CMake?

Best,
Mike

-----------------------------------------------------
Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com


On Sun, Feb 28, 2016 at 12:34 PM, Michael Gogins
 wrote:
> All DLLs shown by the 64 bit dependency walker are in WIndows/system32
> or in the Csound build directory. Also they are all x64 as they should
> be. LIbsndfile does not show up however which seems wrong. Is it
> staticallhy linked now?
>
> Regards,
> Mike
>
> -----------------------------------------------------
> Michael Gogins
> Irreducible Productions
> http://michaelgogins.tumblr.com
> Michael dot Gogins at gmail dot com
>
>
> On Sun, Feb 28, 2016 at 12:17 PM, Michael Gogins
>  wrote:
>> No libwinpthread in WIndows system directories. I am going to run the
>> dependency checker on Csound.
>>
>> -----------------------------------------------------
>> Michael Gogins
>> Irreducible Productions
>> http://michaelgogins.tumblr.com
>> Michael dot Gogins at gmail dot com
>>
>>
>> On Sun, Feb 28, 2016 at 12:08 PM, Michael Gogins
>>  wrote:
>>> Mine has that as well: D:/msys64/mingw64/bin/libwinpthread-1.dll.
>>>
>>> But perhaps there is one of these in the WIndows system directories, I
>>> am checking.
>>>
>>> Best,
>>> Mike
>>>
>>>
>>> -----------------------------------------------------
>>> Michael Gogins
>>> Irreducible Productions
>>> http://michaelgogins.tumblr.com
>>> Michael dot Gogins at gmail dot com
>>>
>>>
>>> On Sun, Feb 28, 2016 at 12:06 PM, Michael Gogins
>>>  wrote:
>>>> I am running the build script from the MINGW64 shell, not the MSYS2
>>>> shell. MSYS2 installs both of these shells.
>>>>
>>>> Regards,
>>>> Mike
>>>>
>>>> -----------------------------------------------------
>>>> Michael Gogins
>>>> Irreducible Productions
>>>> http://michaelgogins.tumblr.com
>>>> Michael dot Gogins at gmail dot com
>>>>
>>>>
>>>> On Sun, Feb 28, 2016 at 11:58 AM, Rory Walsh  wrote:
>>>>> Hi Mike. I'm not sure what the problem there is. You are running the
>>>>> build.sh script from the MSYS2 shell? I built afresh again yesterday without
>>>>> any issues, albeit with many plugin opcodes disabled.
>>>>>
>>>>> On 28 February 2016 at 16:44, Michael Gogins 
>>>>> wrote:
>>>>>>
>>>>>> I'm running into a serious problem. I can build csound.exe with
>>>>>> MSYS2/mingw64, but it does not run. I have cleaned up my environment
>>>>>> so there are no binaries in the PATH but MSYS, mingw, and Csound and
>>>>>> its opcodes.
>>>>>>
>>>>>> (gdb) run
>>>>>> Starting program:
>>>>>> D:\msys64\home\restore\csound\mingw64\csound-mingw64\csound.exe
>>>>>> [New Thread 5784.0x6d8]
>>>>>>
>>>>>> Program received signal SIGSEGV, Segmentation fault.
>>>>>> 0x000007f8f3d17740 in ntdll!RtlMultiAppendUnicodeStringBuffer ()
>>>>>>    from C:\Windows\SYSTEM32\ntdll.dll
>>>>>> (gdb) bt
>>>>>> #0  0x000007f8f3d17740 in ntdll!RtlMultiAppendUnicodeStringBuffer ()
>>>>>>    from C:\Windows\SYSTEM32\ntdll.dll
>>>>>> #1  0x000007f8f3d0c5a5 in ntdll!RtlInitializeCriticalSection ()
>>>>>>    from C:\Windows\SYSTEM32\ntdll.dll
>>>>>> #2  0x000000006c5eed8d in csoundInitialize (flags=flags@entry=1)
>>>>>>     at D:/msys64/home/restore/csound/Top/csound.c:1119
>>>>>> #3  0x0000000000402fe5 in main (argc=1, argv=0x304700)
>>>>>>     at D:/msys64/home/restore/csound/frontends/csound/csound_main.c:258
>>>>>> (gdb)
>>>>>>
>>>>>>
>>>>>> -----------------------------------------------------
>>>>>> Michael Gogins
>>>>>> Irreducible Productions
>>>>>> http://michaelgogins.tumblr.com
>>>>>> Michael dot Gogins at gmail dot com
>>>>>>
>>>>>>
>>>>>> On Sat, Feb 27, 2016 at 4:33 PM, Victor Lazzarini
>>>>>>  wrote:
>>>>>> > Maybe try to get one of the Norwegian guys, they know about Windows.
>>>>>> >
>>>>>> > Victor Lazzarini
>>>>>> > Dean of Arts, Celtic Studies, and Philosophy
>>>>>> > Maynooth University
>>>>>> > Ireland
>>>>>> >
>>>>>> > On 27 Feb 2016, at 20:48, Tarmo Johannes  wrote:
>>>>>> >
>>>>>> > Hi,
>>>>>> > This is a problematic topic. We just discussed it with Joachim and don't
>>>>>> > have a dedicee to it right - there is truly lack of experienced Windows
>>>>>> > people... But keep thinking about it. I will read about MSYS2 myself too
>>>>>> > to
>>>>>> > be more aware.
>>>>>> > Thanks!
>>>>>> > Tarmo
>>>>>> >
>>>>>> > 27.02.2016 21:51 kirjutas kuupäeval "Steven Yi" :
>>>>>> >>
>>>>>> >> Hi Tarmo,
>>>>>> >>
>>>>>> >> Regarding CsoundQT, is there someone from the CsoundQT developers that
>>>>>> >> could contribute time to investigating building on Windows with MSYS2?
>>>>>> >>
>>>>>> >> Thanks!
>>>>>> >> steven
>>>>>> >>
>>>>>> >>
>>>>>> >> On Sat, Feb 27, 2016 at 1:57 PM, Tarmo Johannes 
>>>>>> >> wrote:
>>>>>> >> > Hi,
>>>>>> >> >
>>>>>> >> > And if you say MSYS2 has Qt, please do build alwo CsoundQt and let
>>>>>> >> > know
>>>>>> >> > if
>>>>>> >> > there are any problems or anything to do in the source code or
>>>>>> >> > project
>>>>>> >> > files.
>>>>>> >> >
>>>>>> >> > Thanks!
>>>>>> >> >
>>>>>> >> > On Saturday 27 February 2016 13:42:28 you wrote:
>>>>>> >> >> I will go with Python 2.7 for now.
>>>>>> >> >>
>>>>>> >> >> Best,
>>>>>> >> >> Mike
>>>>>> >> >>
>>>>>> >> >> -----------------------------------------------------
>>>>>> >> >> Michael Gogins
>>>>>> >> >> Irreducible Productions
>>>>>> >> >> http://michaelgogins.tumblr.com
>>>>>> >> >> Michael dot Gogins at gmail dot com
>>>>>> >> >>
>>>>>> >> >> On Sat, Feb 27, 2016 at 1:39 PM, Steven Yi 
>>>>>> >> >> wrote:
>>>>>> >> >> > I've been building for 2.7 myself.  I suppose the only way to
>>>>>> >> >> > satisfy
>>>>>> >> >> > everyone is to build something that works for both.  Perhaps we
>>>>>> >> >> > should
>>>>>> >> >> > finally add a build target specifically for Python 3 for all
>>>>>> >> >> > platforms?  We'd have to work out all the details for install
>>>>>> >> >> > locations for OSX and Linux.  Another option is to start
>>>>>> >> >> > leveraging
>>>>>> >> >> > python's package system to build the interfaces and have the user
>>>>>> >> >> > install those packages separately.
>>>>>> >> >> >
>>>>>> >> >> > Maybe just start with 2.7 for now as that was the last supported
>>>>>> >> >> > Python and punt on Python 3 until after this build?  Might be best
>>>>>> >> >> > so
>>>>>> >> >> > we can coordinate a solution for all platforms.
>>>>>> >> >> >
>>>>>> >> >> > On Sat, Feb 27, 2016 at 1:22 PM, Michael Gogins
>>>>>> >> >> >
>>>>>> >> >> >  wrote:
>>>>>> >> >> >> Another thing, should I support Python 2.7 or Python 3?
>>>>>> >> >> >>
>>>>>> >> >> >> Regards,
>>>>>> >> >> >> Mike
>>>>>> >> >> >>
>>>>>> >> >> >> -----------------------------------------------------
>>>>>> >> >> >> Michael Gogins
>>>>>> >> >> >> Irreducible Productions
>>>>>> >> >> >> http://michaelgogins.tumblr.com
>>>>>> >> >> >> Michael dot Gogins at gmail dot com
>>>>>> >> >> >>
>>>>>> >> >> >>
>>>>>> >> >> >> On Sat, Feb 27, 2016 at 12:54 PM, Michael Gogins
>>>>>> >> >> >>
>>>>>> >> >> >>  wrote:
>>>>>> >> >> >>> I have installed MSYS2, its mingw, toolchain, and the list of
>>>>>> >> >> >>> packages
>>>>>> >> >> >>> from our README.md.
>>>>>> >> >> >>>
>>>>>> >> >> >>> Things have started to build. I have to create an import library
>>>>>> >> >> >>> for
>>>>>> >> >> >>> Python x64. MSYS2 comes with its own Python, but I assume I
>>>>>> >> >> >>> should
>>>>>> >> >> >>> use
>>>>>> >> >> >>> regular Windows x64 Python from python.org.
>>>>>> >> >> >>>
>>>>>> >> >> >>> The Lua library problem mentioned in our README.md can probably
>>>>>> >> >> >>> be
>>>>>> >> >> >>> fixed with a file copy or symbolic link.
>>>>>> >> >> >>>
>>>>>> >> >> >>> I have installed NW.js for x64, and plan to use that for HTML5
>>>>>> >> >> >>> stuff.
>>>>>> >> >> >>> The current beta version of NW.js enables NaCl for x64 so a 64
>>>>>> >> >> >>> bit
>>>>>> >> >> >>> build of Csound for NaCl should run as well as the 64 bit build
>>>>>> >> >> >>> of
>>>>>> >> >> >>> csound.node.
>>>>>> >> >> >>>
>>>>>> >> >> >>> I am not sure what to do for CsoundQt. If NW.js works I see no
>>>>>> >> >> >>> particular need to build CsoundQt, but on the other the Qt SDK
>>>>>> >> >> >>> is
>>>>>> >> >> >>> installed in my MSYS2 environment so CsoundQt shouldn't be that
>>>>>> >> >> >>> hard
>>>>>> >> >> >>> to build.
>>>>>> >> >> >>>
>>>>>> >> >> >>> I also am not sure what to do about the Java interface.
>>>>>> >> >> >>> Presumably
>>>>>> >> >> >>> you, Steven, would like blue to run with x64 Csound.
>>>>>> >> >> >>>
>>>>>> >> >> >>> I also am not sure what to do about Jack, perhaps Windows
>>>>>> >> >> >>> support
>>>>>> >> >> >>> for
>>>>>> >> >> >>> Jack now exists, and if so, this could be added to the build.
>>>>>> >> >> >>>
>>>>>> >> >> >>> For a full build I think we should have package recipes for STK,
>>>>>> >> >> >>> LuaJIT, and perhaps NW.js.
>>>>>> >> >> >>>
>>>>>> >> >> >>> There are also compiler warnings about various handles and
>>>>>> >> >> >>> pointers
>>>>>> >> >> >>> that are different sizes on different platforms. I would like to
>>>>>> >> >> >>> fix
>>>>>> >> >> >>> all of these with some sort of padding or aliasing.
>>>>>> >> >> >>>
>>>>>> >> >> >>> I'm not sure how much of this I can do for the next release but
>>>>>> >> >> >>> I
>>>>>> >> >> >>> am
>>>>>> >> >> >>> shooting for at least LuaJIT. NW.js, and STK.
>>>>>> >> >> >>>
>>>>>> >> >> >>> Regards,
>>>>>> >> >> >>> Mike
>>>>>> >> >> >>>
>>>>>> >> >> >>> -----------------------------------------------------
>>>>>> >> >> >>> Michael Gogins
>>>>>> >> >> >>> Irreducible Productions
>>>>>> >> >> >>> http://michaelgogins.tumblr.com
>>>>>> >> >> >>> Michael dot Gogins at gmail dot com
>>>>>

In fact the critical section is NOT initialized. Why would this work
for you and not for me?

Regards,
Mike

-----------------------------------------------------
Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com


On Sun, Feb 28, 2016 at 1:14 PM, Michael Gogins
 wrote:
> csGblMtx.h (ghastly filename) uses WIndows threads in my build. Is
> there some mixup between Windows threads and pthreads? It almost looks
> like EnterCriticalSection (Windows API) is being called without the
> critical section object first being initialized. Are you defining
> WIN32 or GNUC or what for CMake?
>
> Best,
> Mike
>
> -----------------------------------------------------
> Michael Gogins
> Irreducible Productions
> http://michaelgogins.tumblr.com
> Michael dot Gogins at gmail dot com
>
>
> On Sun, Feb 28, 2016 at 12:34 PM, Michael Gogins
>  wrote:
>> All DLLs shown by the 64 bit dependency walker are in WIndows/system32
>> or in the Csound build directory. Also they are all x64 as they should
>> be. LIbsndfile does not show up however which seems wrong. Is it
>> staticallhy linked now?
>>
>> Regards,
>> Mike
>>
>> -----------------------------------------------------
>> Michael Gogins
>> Irreducible Productions
>> http://michaelgogins.tumblr.com
>> Michael dot Gogins at gmail dot com
>>
>>
>> On Sun, Feb 28, 2016 at 12:17 PM, Michael Gogins
>>  wrote:
>>> No libwinpthread in WIndows system directories. I am going to run the
>>> dependency checker on Csound.
>>>
>>> -----------------------------------------------------
>>> Michael Gogins
>>> Irreducible Productions
>>> http://michaelgogins.tumblr.com
>>> Michael dot Gogins at gmail dot com
>>>
>>>
>>> On Sun, Feb 28, 2016 at 12:08 PM, Michael Gogins
>>>  wrote:
>>>> Mine has that as well: D:/msys64/mingw64/bin/libwinpthread-1.dll.
>>>>
>>>> But perhaps there is one of these in the WIndows system directories, I
>>>> am checking.
>>>>
>>>> Best,
>>>> Mike
>>>>
>>>>
>>>> -----------------------------------------------------
>>>> Michael Gogins
>>>> Irreducible Productions
>>>> http://michaelgogins.tumblr.com
>>>> Michael dot Gogins at gmail dot com
>>>>
>>>>
>>>> On Sun, Feb 28, 2016 at 12:06 PM, Michael Gogins
>>>>  wrote:
>>>>> I am running the build script from the MINGW64 shell, not the MSYS2
>>>>> shell. MSYS2 installs both of these shells.
>>>>>
>>>>> Regards,
>>>>> Mike
>>>>>
>>>>> -----------------------------------------------------
>>>>> Michael Gogins
>>>>> Irreducible Productions
>>>>> http://michaelgogins.tumblr.com
>>>>> Michael dot Gogins at gmail dot com
>>>>>
>>>>>
>>>>> On Sun, Feb 28, 2016 at 11:58 AM, Rory Walsh  wrote:
>>>>>> Hi Mike. I'm not sure what the problem there is. You are running the
>>>>>> build.sh script from the MSYS2 shell? I built afresh again yesterday without
>>>>>> any issues, albeit with many plugin opcodes disabled.
>>>>>>
>>>>>> On 28 February 2016 at 16:44, Michael Gogins 
>>>>>> wrote:
>>>>>>>
>>>>>>> I'm running into a serious problem. I can build csound.exe with
>>>>>>> MSYS2/mingw64, but it does not run. I have cleaned up my environment
>>>>>>> so there are no binaries in the PATH but MSYS, mingw, and Csound and
>>>>>>> its opcodes.
>>>>>>>
>>>>>>> (gdb) run
>>>>>>> Starting program:
>>>>>>> D:\msys64\home\restore\csound\mingw64\csound-mingw64\csound.exe
>>>>>>> [New Thread 5784.0x6d8]
>>>>>>>
>>>>>>> Program received signal SIGSEGV, Segmentation fault.
>>>>>>> 0x000007f8f3d17740 in ntdll!RtlMultiAppendUnicodeStringBuffer ()
>>>>>>>    from C:\Windows\SYSTEM32\ntdll.dll
>>>>>>> (gdb) bt
>>>>>>> #0  0x000007f8f3d17740 in ntdll!RtlMultiAppendUnicodeStringBuffer ()
>>>>>>>    from C:\Windows\SYSTEM32\ntdll.dll
>>>>>>> #1  0x000007f8f3d0c5a5 in ntdll!RtlInitializeCriticalSection ()
>>>>>>>    from C:\Windows\SYSTEM32\ntdll.dll
>>>>>>> #2  0x000000006c5eed8d in csoundInitialize (flags=flags@entry=1)
>>>>>>>     at D:/msys64/home/restore/csound/Top/csound.c:1119
>>>>>>> #3  0x0000000000402fe5 in main (argc=1, argv=0x304700)
>>>>>>>     at D:/msys64/home/restore/csound/frontends/csound/csound_main.c:258
>>>>>>> (gdb)
>>>>>>>
>>>>>>>
>>>>>>> -----------------------------------------------------
>>>>>>> Michael Gogins
>>>>>>> Irreducible Productions
>>>>>>> http://michaelgogins.tumblr.com
>>>>>>> Michael dot Gogins at gmail dot com
>>>>>>>
>>>>>>>
>>>>>>> On Sat, Feb 27, 2016 at 4:33 PM, Victor Lazzarini
>>>>>>>  wrote:
>>>>>>> > Maybe try to get one of the Norwegian guys, they know about Windows.
>>>>>>> >
>>>>>>> > Victor Lazzarini
>>>>>>> > Dean of Arts, Celtic Studies, and Philosophy
>>>>>>> > Maynooth University
>>>>>>> > Ireland
>>>>>>> >
>>>>>>> > On 27 Feb 2016, at 20:48, Tarmo Johannes  wrote:
>>>>>>> >
>>>>>>> > Hi,
>>>>>>> > This is a problematic topic. We just discussed it with Joachim and don't
>>>>>>> > have a dedicee to it right - there is truly lack of experienced Windows
>>>>>>> > people... But keep thinking about it. I will read about MSYS2 myself too
>>>>>>> > to
>>>>>>> > be more aware.
>>>>>>> > Thanks!
>>>>>>> > Tarmo
>>>>>>> >
>>>>>>> > 27.02.2016 21:51 kirjutas kuupäeval "Steven Yi" :
>>>>>>> >>
>>>>>>> >> Hi Tarmo,
>>>>>>> >>
>>>>>>> >> Regarding CsoundQT, is there someone from the CsoundQT developers that
>>>>>>> >> could contribute time to investigating building on Windows with MSYS2?
>>>>>>> >>
>>>>>>> >> Thanks!
>>>>>>> >> steven
>>>>>>> >>
>>>>>>> >>
>>>>>>> >> On Sat, Feb 27, 2016 at 1:57 PM, Tarmo Johannes 
>>>>>>> >> wrote:
>>>>>>> >> > Hi,
>>>>>>> >> >
>>>>>>> >> > And if you say MSYS2 has Qt, please do build alwo CsoundQt and let
>>>>>>> >> > know
>>>>>>> >> > if
>>>>>>> >> > there are any problems or anything to do in the source code or
>>>>>>> >> > project
>>>>>>> >> > files.
>>>>>>> >> >
>>>>>>> >> > Thanks!
>>>>>>> >> >
>>>>>>> >> > On Saturday 27 February 2016 13:42:28 you wrote:
>>>>>>> >> >> I will go with Python 2.7 for now.
>>>>>>> >> >>
>>>>>>> >> >> Best,
>>>>>>> >> >> Mike
>>>>>>> >> >>
>>>>>>> >> >> -----------------------------------------------------
>>>>>>> >> >> Michael Gogins
>>>>>>> >> >> Irreducible Productions
>>>>>>> >> >> http://michaelgogins.tumblr.com
>>>>>>> >> >> Michael dot Gogins at gmail dot com
>>>>>>> >> >>
>>>>>>> >> >> On Sat, Feb 27, 2016 at 1:39 PM, Steven Yi 
>>>>>>> >> >> wrote:
>>>>>>> >> >> > I've been building for 2.7 myself.  I suppose the only way to
>>>>>>> >> >> > satisfy
>>>>>>> >> >> > everyone is to build something that works for both.  Perhaps we
>>>>>>> >> >> > should
>>>>>>> >> >> > finally add a build target specifically for Python 3 for all
>>>>>>> >> >> > platforms?  We'd have to work out all the details for install
>>>>>>> >> >> > locations for OSX and Linux.  Another option is to start
>>>>>>> >> >> > leveraging
>>>>>>> >> >> > python's package system to build the interfaces and have the user
>>>>>>> >> >> > install those packages separately.
>>>>>>> >> >> >
>>>>>>> >> >> > Maybe just start with 2.7 for now as that was the last supported
>>>>>>> >> >> > Python and punt on Python 3 until after this build?  Might be best
>>>>>>> >> >> > so
>>>>>>> >> >> > we can coordinate a solution for all platforms.
>>>>>>> >> >> >
>>>>>>> >> >> > On Sat, Feb 27, 2016 at 1:22 PM, Michael Gogins
>>>>>>> >> >> >
>>>>>>> >> >> >  wrote:
>>>>>>> >> >> >> Another thing, should I support Python 2.7 or Python 3?
>>>>>>> >> >> >>
>>>>>>> >> >> >> Regards,
>>>>>>> >> >> >> Mike
>>>>>>> >> >> >>
>>>>>>> >> >> >> -----------------------------------------------------
>>>>>>> >> >> >> Michael Gogins
>>>>>>> >> >> >> Irreducible Productions
>>>>>>> >> >> >> http://michaelgogins.tumblr.com
>>>>>>> >> >> >> Michael dot Gogins at gmail dot com
>>>>>>> >> >> >>
>>>>>>> >> >> >>
>>>>>>> >> >> >> On Sat, Feb 27, 2016 at 12:54 PM, Michael Gogins
>>>>>>> >> >> >>
>>>>>>> >> >> >>  wrote:
>>>>>>> >> >> >>> I have installed MSYS2, its mingw, toolchain, and the list of
>>>>>>> >> >> >>> packages
>>>>>>> >> >> >>> from our README.md.
>>>>>>> >> >> >>>
>>>>>>> >> >> >>> Things have started to build. I have to create an import library
>>>>>>> >> >> >>> for
>>>>>>> >> >> >>> Python x64. MSYS2 comes with its own Python, but I assume I
>>>>>>> >> >> >>> should
>>>>>>> >> >> >>> use
>>>>>>> >> >> >>> regular Windows x64 Python from python.org.
>>>>>>> >> >> >>>
>>>>>>> >> >> >>> The Lua library problem mentioned in our README.md can probably
>>>>>>> >> >> >>> be
>>>>>>> >> >> >>> fixed with a file copy or symbolic link.
>>>>>>> >> >> >>>
>>>>>>> >> >> >>> I have installed NW.js for x64, and plan to use that for HTML5
>>>>>>> >> >> >>> stuff.
>>>>>>> >> >> >>> The current beta version of NW.js enables NaCl for x64 so a 64
>>>>>>> >> >> >>> bit
>>>>>>> >> >> >>> build of Csound for NaCl should run as well as the 64 bit build
>>>>>>> >> >> >>> of
>>>>>>> >> >> >>> csound.node.
>>>>>>> >> >> >>>
>>>>>>> >> >> >>> I am not sure what to do for CsoundQt. If NW.js works I see no
>>>>>>> >> >> >>> particular need to build CsoundQt, but on the other the Qt SDK
>>>>>>> >> >> >>> is
>>>>>>> >> >> >>> installed in my MSYS2 environment so CsoundQt shouldn't be that
>>>>>>> >> >> >>> hard
>>>>>>> >> >> >>> to build.
>>>>>>> >> >> >>>
>>>>>>> >> >> >>> I also am not sure what to do about the Java interface.
>>>>>>> >> >> >>> Presumably
>>>>>>> >> >> >>> you, Steven, would like blue to run with x64 Csound.
>>>>>>> >> >> >>>
>>>>>>> >> >> >>> I also am not sure what to do about Jack, perhaps Windows
>>>>>>> >> >> >>> support
>>>>>>> >> >> >>> for
>>>>>>> >> >> >>> Jack now exists, and if so, this could be added to the build.
>>>>>>> >> >> >>>
>>>>>>> >> >> >>> For a full build I think we should have package recipes for STK,
>>>>>>> >> >> >>> LuaJIT, and perhaps NW.js.
>>>>>>> >> >> >>>
>>>>>>> >> >> >>> There are also compiler warnings about various handles and
>>>>>>> >> >> >>> pointers
>>>>>>> >> >> >>> that are different sizes on different platforms. I would like to
>>>>>>> >> >> >>> fix
>>>>>>> >> >> >>> all of these with some sort of padding or aliasing.
>>>>>>> >> >> >>>
>>>>>>> >> >> >>> I'm not sure how much of this I can do for the next release but
>>>>>>> >> >> >>> I
>>>>>>> >> >> >>> am
>>>>>>> >> >> >>> shooting for at least LuaJIT. NW.js, and STK.
>>>>>>> >> >> >>>
>>>>>>> >> >> >>> Regards,
>>>>>>> >> >> >>> Mike
>>>>>>> >> >> >>>
>>>>>>> >> >> >>> -----------------------------------------------------
>>>>>>> >> >> >>> Michael Gogins
>>>>>>> >> >> >>> Irreducible Productions
>>>>>>> >> >> >>> http://michaelgogins.tumblr.com
>>>>>>> >> >> >>> Michael dot Gogins at gmail dot com
>>>>>>

The system does statically link just about everything now.  I think
the change was first introduced by Rory a while back.

For CMake, everything I'm using is included in the build.sh script and
the Custom-mingw64.cmake file, and I am not adding anything else
outside of those so that we can all share the same exact build
parameters.  Assuming that MSYS2 installs the same for everyone, we
should hopefully have a completely reproducible build here for
everyone.

One thing to note, I am on a Windows 10 64-bit system.  Are you
building on Windows 10?  Maybe that's a difference that might account
for discrepancy in behavior.


On Sun, Feb 28, 2016 at 1:14 PM, Michael Gogins
 wrote:
> csGblMtx.h (ghastly filename) uses WIndows threads in my build. Is
> there some mixup between Windows threads and pthreads? It almost looks
> like EnterCriticalSection (Windows API) is being called without the
> critical section object first being initialized. Are you defining
> WIN32 or GNUC or what for CMake?
>
> Best,
> Mike
>
> -----------------------------------------------------
> Michael Gogins
> Irreducible Productions
> http://michaelgogins.tumblr.com
> Michael dot Gogins at gmail dot com
>
>
> On Sun, Feb 28, 2016 at 12:34 PM, Michael Gogins
>  wrote:
>> All DLLs shown by the 64 bit dependency walker are in WIndows/system32
>> or in the Csound build directory. Also they are all x64 as they should
>> be. LIbsndfile does not show up however which seems wrong. Is it
>> staticallhy linked now?
>>
>> Regards,
>> Mike
>>
>> -----------------------------------------------------
>> Michael Gogins
>> Irreducible Productions
>> http://michaelgogins.tumblr.com
>> Michael dot Gogins at gmail dot com
>>
>>
>> On Sun, Feb 28, 2016 at 12:17 PM, Michael Gogins
>>  wrote:
>>> No libwinpthread in WIndows system directories. I am going to run the
>>> dependency checker on Csound.
>>>
>>> -----------------------------------------------------
>>> Michael Gogins
>>> Irreducible Productions
>>> http://michaelgogins.tumblr.com
>>> Michael dot Gogins at gmail dot com
>>>
>>>
>>> On Sun, Feb 28, 2016 at 12:08 PM, Michael Gogins
>>>  wrote:
>>>> Mine has that as well: D:/msys64/mingw64/bin/libwinpthread-1.dll.
>>>>
>>>> But perhaps there is one of these in the WIndows system directories, I
>>>> am checking.
>>>>
>>>> Best,
>>>> Mike
>>>>
>>>>
>>>> -----------------------------------------------------
>>>> Michael Gogins
>>>> Irreducible Productions
>>>> http://michaelgogins.tumblr.com
>>>> Michael dot Gogins at gmail dot com
>>>>
>>>>
>>>> On Sun, Feb 28, 2016 at 12:06 PM, Michael Gogins
>>>>  wrote:
>>>>> I am running the build script from the MINGW64 shell, not the MSYS2
>>>>> shell. MSYS2 installs both of these shells.
>>>>>
>>>>> Regards,
>>>>> Mike
>>>>>
>>>>> -----------------------------------------------------
>>>>> Michael Gogins
>>>>> Irreducible Productions
>>>>> http://michaelgogins.tumblr.com
>>>>> Michael dot Gogins at gmail dot com
>>>>>
>>>>>
>>>>> On Sun, Feb 28, 2016 at 11:58 AM, Rory Walsh  wrote:
>>>>>> Hi Mike. I'm not sure what the problem there is. You are running the
>>>>>> build.sh script from the MSYS2 shell? I built afresh again yesterday without
>>>>>> any issues, albeit with many plugin opcodes disabled.
>>>>>>
>>>>>> On 28 February 2016 at 16:44, Michael Gogins 
>>>>>> wrote:
>>>>>>>
>>>>>>> I'm running into a serious problem. I can build csound.exe with
>>>>>>> MSYS2/mingw64, but it does not run. I have cleaned up my environment
>>>>>>> so there are no binaries in the PATH but MSYS, mingw, and Csound and
>>>>>>> its opcodes.
>>>>>>>
>>>>>>> (gdb) run
>>>>>>> Starting program:
>>>>>>> D:\msys64\home\restore\csound\mingw64\csound-mingw64\csound.exe
>>>>>>> [New Thread 5784.0x6d8]
>>>>>>>
>>>>>>> Program received signal SIGSEGV, Segmentation fault.
>>>>>>> 0x000007f8f3d17740 in ntdll!RtlMultiAppendUnicodeStringBuffer ()
>>>>>>>    from C:\Windows\SYSTEM32\ntdll.dll
>>>>>>> (gdb) bt
>>>>>>> #0  0x000007f8f3d17740 in ntdll!RtlMultiAppendUnicodeStringBuffer ()
>>>>>>>    from C:\Windows\SYSTEM32\ntdll.dll
>>>>>>> #1  0x000007f8f3d0c5a5 in ntdll!RtlInitializeCriticalSection ()
>>>>>>>    from C:\Windows\SYSTEM32\ntdll.dll
>>>>>>> #2  0x000000006c5eed8d in csoundInitialize (flags=flags@entry=1)
>>>>>>>     at D:/msys64/home/restore/csound/Top/csound.c:1119
>>>>>>> #3  0x0000000000402fe5 in main (argc=1, argv=0x304700)
>>>>>>>     at D:/msys64/home/restore/csound/frontends/csound/csound_main.c:258
>>>>>>> (gdb)
>>>>>>>
>>>>>>>
>>>>>>> -----------------------------------------------------
>>>>>>> Michael Gogins
>>>>>>> Irreducible Productions
>>>>>>> http://michaelgogins.tumblr.com
>>>>>>> Michael dot Gogins at gmail dot com
>>>>>>>
>>>>>>>
>>>>>>> On Sat, Feb 27, 2016 at 4:33 PM, Victor Lazzarini
>>>>>>>  wrote:
>>>>>>> > Maybe try to get one of the Norwegian guys, they know about Windows.
>>>>>>> >
>>>>>>> > Victor Lazzarini
>>>>>>> > Dean of Arts, Celtic Studies, and Philosophy
>>>>>>> > Maynooth University
>>>>>>> > Ireland
>>>>>>> >
>>>>>>> > On 27 Feb 2016, at 20:48, Tarmo Johannes  wrote:
>>>>>>> >
>>>>>>> > Hi,
>>>>>>> > This is a problematic topic. We just discussed it with Joachim and don't
>>>>>>> > have a dedicee to it right - there is truly lack of experienced Windows
>>>>>>> > people... But keep thinking about it. I will read about MSYS2 myself too
>>>>>>> > to
>>>>>>> > be more aware.
>>>>>>> > Thanks!
>>>>>>> > Tarmo
>>>>>>> >
>>>>>>> > 27.02.2016 21:51 kirjutas kuupäeval "Steven Yi" :
>>>>>>> >>
>>>>>>> >> Hi Tarmo,
>>>>>>> >>
>>>>>>> >> Regarding CsoundQT, is there someone from the CsoundQT developers that
>>>>>>> >> could contribute time to investigating building on Windows with MSYS2?
>>>>>>> >>
>>>>>>> >> Thanks!
>>>>>>> >> steven
>>>>>>> >>
>>>>>>> >>
>>>>>>> >> On Sat, Feb 27, 2016 at 1:57 PM, Tarmo Johannes 
>>>>>>> >> wrote:
>>>>>>> >> > Hi,
>>>>>>> >> >
>>>>>>> >> > And if you say MSYS2 has Qt, please do build alwo CsoundQt and let
>>>>>>> >> > know
>>>>>>> >> > if
>>>>>>> >> > there are any problems or anything to do in the source code or
>>>>>>> >> > project
>>>>>>> >> > files.
>>>>>>> >> >
>>>>>>> >> > Thanks!
>>>>>>> >> >
>>>>>>> >> > On Saturday 27 February 2016 13:42:28 you wrote:
>>>>>>> >> >> I will go with Python 2.7 for now.
>>>>>>> >> >>
>>>>>>> >> >> Best,
>>>>>>> >> >> Mike
>>>>>>> >> >>
>>>>>>> >> >> -----------------------------------------------------
>>>>>>> >> >> Michael Gogins
>>>>>>> >> >> Irreducible Productions
>>>>>>> >> >> http://michaelgogins.tumblr.com
>>>>>>> >> >> Michael dot Gogins at gmail dot com
>>>>>>> >> >>
>>>>>>> >> >> On Sat, Feb 27, 2016 at 1:39 PM, Steven Yi 
>>>>>>> >> >> wrote:
>>>>>>> >> >> > I've been building for 2.7 myself.  I suppose the only way to
>>>>>>> >> >> > satisfy
>>>>>>> >> >> > everyone is to build something that works for both.  Perhaps we
>>>>>>> >> >> > should
>>>>>>> >> >> > finally add a build target specifically for Python 3 for all
>>>>>>> >> >> > platforms?  We'd have to work out all the details for install
>>>>>>> >> >> > locations for OSX and Linux.  Another option is to start
>>>>>>> >> >> > leveraging
>>>>>>> >> >> > python's package system to build the interfaces and have the user
>>>>>>> >> >> > install those packages separately.
>>>>>>> >> >> >
>>>>>>> >> >> > Maybe just start with 2.7 for now as that was the last supported
>>>>>>> >> >> > Python and punt on Python 3 until after this build?  Might be best
>>>>>>> >> >> > so
>>>>>>> >> >> > we can coordinate a solution for all platforms.
>>>>>>> >> >> >
>>>>>>> >> >> > On Sat, Feb 27, 2016 at 1:22 PM, Michael Gogins
>>>>>>> >> >> >
>>>>>>> >> >> >  wrote:
>>>>>>> >> >> >> Another thing, should I support Python 2.7 or Python 3?
>>>>>>> >> >> >>
>>>>>>> >> >> >> Regards,
>>>>>>> >> >> >> Mike
>>>>>>> >> >> >>
>>>>>>> >> >> >> -----------------------------------------------------
>>>>>>> >> >> >> Michael Gogins
>>>>>>> >> >> >> Irreducible Productions
>>>>>>> >> >> >> http://michaelgogins.tumblr.com
>>>>>>> >> >> >> Michael dot Gogins at gmail dot com
>>>>>>> >> >> >>
>>>>>>> >> >> >>
>>>>>>> >> >> >> On Sat, Feb 27, 2016 at 12:54 PM, Michael Gogins
>>>>>>> >> >> >>
>>>>>>> >> >> >>  wrote:
>>>>>>> >> >> >>> I have installed MSYS2, its mingw, toolchain, and the list of
>>>>>>> >> >> >>> packages
>>>>>>> >> >> >>> from our README.md.
>>>>>>> >> >> >>>
>>>>>>> >> >> >>> Things have started to build. I have to create an import library
>>>>>>> >> >> >>> for
>>>>>>> >> >> >>> Python x64. MSYS2 comes with its own Python, but I assume I
>>>>>>> >> >> >>> should
>>>>>>> >> >> >>> use
>>>>>>> >> >> >>> regular Windows x64 Python from python.org.
>>>>>>> >> >> >>>
>>>>>>> >> >> >>> The Lua library problem mentioned in our README.md can probably
>>>>>>> >> >> >>> be
>>>>>>> >> >> >>> fixed with a file copy or symbolic link.
>>>>>>> >> >> >>>
>>>>>>> >> >> >>> I have installed NW.js for x64, and plan to use that for HTML5
>>>>>>> >> >> >>> stuff.
>>>>>>> >> >> >>> The current beta version of NW.js enables NaCl for x64 so a 64
>>>>>>> >> >> >>> bit
>>>>>>> >> >> >>> build of Csound for NaCl should run as well as the 64 bit build
>>>>>>> >> >> >>> of
>>>>>>> >> >> >>> csound.node.
>>>>>>> >> >> >>>
>>>>>>> >> >> >>> I am not sure what to do for CsoundQt. If NW.js works I see no
>>>>>>> >> >> >>> particular need to build CsoundQt, but on the other the Qt SDK
>>>>>>> >> >> >>> is
>>>>>>> >> >> >>> installed in my MSYS2 environment so CsoundQt shouldn't be that
>>>>>>> >> >> >>> hard
>>>>>>> >> >> >>> to build.
>>>>>>> >> >> >>>
>>>>>>> >> >> >>> I also am not sure what to do about the Java interface.
>>>>>>> >> >> >>> Presumably
>>>>>>> >> >> >>> you, Steven, would like blue to run with x64 Csound.
>>>>>>> >> >> >>>
>>>>>>> >> >> >>> I also am not sure what to do about Jack, perhaps Windows
>>>>>>> >> >> >>> support
>>>>>>> >> >> >>> for
>>>>>>> >> >> >>> Jack now exists, and if so, this could be added to the build.
>>>>>>> >> >> >>>
>>>>>>> >> >> >>> For a full build I think we should have package recipes for STK,
>>>>>>> >> >> >>> LuaJIT, and perhaps NW.js.
>>>>>>> >> >> >>>
>>>>>>> >> >> >>> There are also compiler warnings about various handles and
>>>>>>> >> >> >>> pointers
>>>>>>> >> >> >>> that are different sizes on different platforms. I would like to
>>>>>>> >> >> >>> fix
>>>>>>> >> >> >>> all of these with some sort of padding or aliasing.
>>>>>>> >> >> >>>
>>>>>>> >> >> >>> I'm not sure how much of this I can do for the next release but
>>>>>>> >> >> >>> I
>>>>>>> >> >> >>> am
>>>>>>> >> >> >>> shooting for at least LuaJIT. NW.js, and STK.
>>>>>>> >> >> >>>
>>>>>>> >> >> >>> Regards,
>>>>>>> >> >> >>> Mike
>>>>>>> >> >> >>>
>>>>>>> >> >> >>> -----------------------------------------------------
>>>>>>> >> >> >>> Michael Gogins
>>>>>>> >> >> >>> Irreducible Productions
>>>>>>> >> >> >>> http://michaelgogins.tumblr.com
>>>>>>> >> >> >>> Michael dot Gogins at gmail dot com
>>>>>>

I am attaching my Cmake cache.

-----------------------------------------------------
Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com


On Sun, Feb 28, 2016 at 1:24 PM, Michael Gogins
 wrote:
> In fact the critical section is NOT initialized. Why would this work
> for you and not for me?
>
> Regards,
> Mike
>
> -----------------------------------------------------
> Michael Gogins
> Irreducible Productions
> http://michaelgogins.tumblr.com
> Michael dot Gogins at gmail dot com
>
>
> On Sun, Feb 28, 2016 at 1:14 PM, Michael Gogins
>  wrote:
>> csGblMtx.h (ghastly filename) uses WIndows threads in my build. Is
>> there some mixup between Windows threads and pthreads? It almost looks
>> like EnterCriticalSection (Windows API) is being called without the
>> critical section object first being initialized. Are you defining
>> WIN32 or GNUC or what for CMake?
>>
>> Best,
>> Mike
>>
>> -----------------------------------------------------
>> Michael Gogins
>> Irreducible Productions
>> http://michaelgogins.tumblr.com
>> Michael dot Gogins at gmail dot com
>>
>>
>> On Sun, Feb 28, 2016 at 12:34 PM, Michael Gogins
>>  wrote:
>>> All DLLs shown by the 64 bit dependency walker are in WIndows/system32
>>> or in the Csound build directory. Also they are all x64 as they should
>>> be. LIbsndfile does not show up however which seems wrong. Is it
>>> staticallhy linked now?
>>>
>>> Regards,
>>> Mike
>>>
>>> -----------------------------------------------------
>>> Michael Gogins
>>> Irreducible Productions
>>> http://michaelgogins.tumblr.com
>>> Michael dot Gogins at gmail dot com
>>>
>>>
>>> On Sun, Feb 28, 2016 at 12:17 PM, Michael Gogins
>>>  wrote:
>>>> No libwinpthread in WIndows system directories. I am going to run the
>>>> dependency checker on Csound.
>>>>
>>>> -----------------------------------------------------
>>>> Michael Gogins
>>>> Irreducible Productions
>>>> http://michaelgogins.tumblr.com
>>>> Michael dot Gogins at gmail dot com
>>>>
>>>>
>>>> On Sun, Feb 28, 2016 at 12:08 PM, Michael Gogins
>>>>  wrote:
>>>>> Mine has that as well: D:/msys64/mingw64/bin/libwinpthread-1.dll.
>>>>>
>>>>> But perhaps there is one of these in the WIndows system directories, I
>>>>> am checking.
>>>>>
>>>>> Best,
>>>>> Mike
>>>>>
>>>>>
>>>>> -----------------------------------------------------
>>>>> Michael Gogins
>>>>> Irreducible Productions
>>>>> http://michaelgogins.tumblr.com
>>>>> Michael dot Gogins at gmail dot com
>>>>>
>>>>>
>>>>> On Sun, Feb 28, 2016 at 12:06 PM, Michael Gogins
>>>>>  wrote:
>>>>>> I am running the build script from the MINGW64 shell, not the MSYS2
>>>>>> shell. MSYS2 installs both of these shells.
>>>>>>
>>>>>> Regards,
>>>>>> Mike
>>>>>>
>>>>>> -----------------------------------------------------
>>>>>> Michael Gogins
>>>>>> Irreducible Productions
>>>>>> http://michaelgogins.tumblr.com
>>>>>> Michael dot Gogins at gmail dot com
>>>>>>
>>>>>>
>>>>>> On Sun, Feb 28, 2016 at 11:58 AM, Rory Walsh  wrote:
>>>>>>> Hi Mike. I'm not sure what the problem there is. You are running the
>>>>>>> build.sh script from the MSYS2 shell? I built afresh again yesterday without
>>>>>>> any issues, albeit with many plugin opcodes disabled.
>>>>>>>
>>>>>>> On 28 February 2016 at 16:44, Michael Gogins 
>>>>>>> wrote:
>>>>>>>>
>>>>>>>> I'm running into a serious problem. I can build csound.exe with
>>>>>>>> MSYS2/mingw64, but it does not run. I have cleaned up my environment
>>>>>>>> so there are no binaries in the PATH but MSYS, mingw, and Csound and
>>>>>>>> its opcodes.
>>>>>>>>
>>>>>>>> (gdb) run
>>>>>>>> Starting program:
>>>>>>>> D:\msys64\home\restore\csound\mingw64\csound-mingw64\csound.exe
>>>>>>>> [New Thread 5784.0x6d8]
>>>>>>>>
>>>>>>>> Program received signal SIGSEGV, Segmentation fault.
>>>>>>>> 0x000007f8f3d17740 in ntdll!RtlMultiAppendUnicodeStringBuffer ()
>>>>>>>>    from C:\Windows\SYSTEM32\ntdll.dll
>>>>>>>> (gdb) bt
>>>>>>>> #0  0x000007f8f3d17740 in ntdll!RtlMultiAppendUnicodeStringBuffer ()
>>>>>>>>    from C:\Windows\SYSTEM32\ntdll.dll
>>>>>>>> #1  0x000007f8f3d0c5a5 in ntdll!RtlInitializeCriticalSection ()
>>>>>>>>    from C:\Windows\SYSTEM32\ntdll.dll
>>>>>>>> #2  0x000000006c5eed8d in csoundInitialize (flags=flags@entry=1)
>>>>>>>>     at D:/msys64/home/restore/csound/Top/csound.c:1119
>>>>>>>> #3  0x0000000000402fe5 in main (argc=1, argv=0x304700)
>>>>>>>>     at D:/msys64/home/restore/csound/frontends/csound/csound_main.c:258
>>>>>>>> (gdb)
>>>>>>>>
>>>>>>>>
>>>>>>>> -----------------------------------------------------
>>>>>>>> Michael Gogins
>>>>>>>> Irreducible Productions
>>>>>>>> http://michaelgogins.tumblr.com
>>>>>>>> Michael dot Gogins at gmail dot com
>>>>>>>>
>>>>>>>>
>>>>>>>> On Sat, Feb 27, 2016 at 4:33 PM, Victor Lazzarini
>>>>>>>>  wrote:
>>>>>>>> > Maybe try to get one of the Norwegian guys, they know about Windows.
>>>>>>>> >
>>>>>>>> > Victor Lazzarini
>>>>>>>> > Dean of Arts, Celtic Studies, and Philosophy
>>>>>>>> > Maynooth University
>>>>>>>> > Ireland
>>>>>>>> >
>>>>>>>> > On 27 Feb 2016, at 20:48, Tarmo Johannes  wrote:
>>>>>>>> >
>>>>>>>> > Hi,
>>>>>>>> > This is a problematic topic. We just discussed it with Joachim and don't
>>>>>>>> > have a dedicee to it right - there is truly lack of experienced Windows
>>>>>>>> > people... But keep thinking about it. I will read about MSYS2 myself too
>>>>>>>> > to
>>>>>>>> > be more aware.
>>>>>>>> > Thanks!
>>>>>>>> > Tarmo
>>>>>>>> >
>>>>>>>> > 27.02.2016 21:51 kirjutas kuupäeval "Steven Yi" :
>>>>>>>> >>
>>>>>>>> >> Hi Tarmo,
>>>>>>>> >>
>>>>>>>> >> Regarding CsoundQT, is there someone from the CsoundQT developers that
>>>>>>>> >> could contribute time to investigating building on Windows with MSYS2?
>>>>>>>> >>
>>>>>>>> >> Thanks!
>>>>>>>> >> steven
>>>>>>>> >>
>>>>>>>> >>
>>>>>>>> >> On Sat, Feb 27, 2016 at 1:57 PM, Tarmo Johannes 
>>>>>>>> >> wrote:
>>>>>>>> >> > Hi,
>>>>>>>> >> >
>>>>>>>> >> > And if you say MSYS2 has Qt, please do build alwo CsoundQt and let
>>>>>>>> >> > know
>>>>>>>> >> > if
>>>>>>>> >> > there are any problems or anything to do in the source code or
>>>>>>>> >> > project
>>>>>>>> >> > files.
>>>>>>>> >> >
>>>>>>>> >> > Thanks!
>>>>>>>> >> >
>>>>>>>> >> > On Saturday 27 February 2016 13:42:28 you wrote:
>>>>>>>> >> >> I will go with Python 2.7 for now.
>>>>>>>> >> >>
>>>>>>>> >> >> Best,
>>>>>>>> >> >> Mike
>>>>>>>> >> >>
>>>>>>>> >> >> -----------------------------------------------------
>>>>>>>> >> >> Michael Gogins
>>>>>>>> >> >> Irreducible Productions
>>>>>>>> >> >> http://michaelgogins.tumblr.com
>>>>>>>> >> >> Michael dot Gogins at gmail dot com
>>>>>>>> >> >>
>>>>>>>> >> >> On Sat, Feb 27, 2016 at 1:39 PM, Steven Yi 
>>>>>>>> >> >> wrote:
>>>>>>>> >> >> > I've been building for 2.7 myself.  I suppose the only way to
>>>>>>>> >> >> > satisfy
>>>>>>>> >> >> > everyone is to build something that works for both.  Perhaps we
>>>>>>>> >> >> > should
>>>>>>>> >> >> > finally add a build target specifically for Python 3 for all
>>>>>>>> >> >> > platforms?  We'd have to work out all the details for install
>>>>>>>> >> >> > locations for OSX and Linux.  Another option is to start
>>>>>>>> >> >> > leveraging
>>>>>>>> >> >> > python's package system to build the interfaces and have the user
>>>>>>>> >> >> > install those packages separately.
>>>>>>>> >> >> >
>>>>>>>> >> >> > Maybe just start with 2.7 for now as that was the last supported
>>>>>>>> >> >> > Python and punt on Python 3 until after this build?  Might be best
>>>>>>>> >> >> > so
>>>>>>>> >> >> > we can coordinate a solution for all platforms.
>>>>>>>> >> >> >
>>>>>>>> >> >> > On Sat, Feb 27, 2016 at 1:22 PM, Michael Gogins
>>>>>>>> >> >> >
>>>>>>>> >> >> >  wrote:
>>>>>>>> >> >> >> Another thing, should I support Python 2.7 or Python 3?
>>>>>>>> >> >> >>
>>>>>>>> >> >> >> Regards,
>>>>>>>> >> >> >> Mike
>>>>>>>> >> >> >>
>>>>>>>> >> >> >> -----------------------------------------------------
>>>>>>>> >> >> >> Michael Gogins
>>>>>>>> >> >> >> Irreducible Productions
>>>>>>>> >> >> >> http://michaelgogins.tumblr.com
>>>>>>>> >> >> >> Michael dot Gogins at gmail dot com
>>>>>>>> >> >> >>
>>>>>>>> >> >> >>
>>>>>>>> >> >> >> On Sat, Feb 27, 2016 at 12:54 PM, Michael Gogins
>>>>>>>> >> >> >>
>>>>>>>> >> >> >>  wrote:
>>>>>>>> >> >> >>> I have installed MSYS2, its mingw, toolchain, and the list of
>>>>>>>> >> >> >>> packages
>>>>>>>> >> >> >>> from our README.md.
>>>>>>>> >> >> >>>
>>>>>>>> >> >> >>> Things have started to build. I have to create an import library
>>>>>>>> >> >> >>> for
>>>>>>>> >> >> >>> Python x64. MSYS2 comes with its own Python, but I assume I
>>>>>>>> >> >> >>> should
>>>>>>>> >> >> >>> use
>>>>>>>> >> >> >>> regular Windows x64 Python from python.org.
>>>>>>>> >> >> >>>
>>>>>>>> >> >> >>> The Lua library problem mentioned in our README.md can probably
>>>>>>>> >> >> >>> be
>>>>>>>> >> >> >>> fixed with a file copy or symbolic link.
>>>>>>>> >> >> >>>
>>>>>>>> >> >> >>> I have installed NW.js for x64, and plan to use that for HTML5
>>>>>>>> >> >> >>> stuff.
>>>>>>>> >> >> >>> The current beta version of NW.js enables NaCl for x64 so a 64
>>>>>>>> >> >> >>> bit
>>>>>>>> >> >> >>> build of Csound for NaCl should run as well as the 64 bit build
>>>>>>>> >> >> >>> of
>>>>>>>> >> >> >>> csound.node.
>>>>>>>> >> >> >>>
>>>>>>>> >> >> >>> I am not sure what to do for CsoundQt. If NW.js works I see no
>>>>>>>> >> >> >>> particular need to build CsoundQt, but on the other the Qt SDK
>>>>>>>> >> >> >>> is
>>>>>>>> >> >> >>> installed in my MSYS2 environment so CsoundQt shouldn't be that
>>>>>>>> >> >> >>> hard
>>>>>>>> >> >> >>> to build.
>>>>>>>> >> >> >>>
>>>>>>>> >> >> >>> I also am not sure what to do about the Java interface.
>>>>>>>> >> >> >>> Presumably
>>>>>>>> >> >> >>> you, Steven, would like blue to run with x64 Csound.
>>>>>>>> >> >> >>>
>>>>>>>> >> >> >>> I also am not sure what to do about Jack, perhaps Windows
>>>>>>>> >> >> >>> support
>>>>>>>> >> >> >>> for
>>>>>>>> >> >> >>> Jack now exists, and if so, this could be added to the build.
>>>>>>>> >> >> >>>
>>>>>>>> >> >> >>> For a full build I think we should have package recipes for STK,
>>>>>>>> >> >> >>> LuaJIT, and perhaps NW.js.
>>>>>>>> >> >> >>>
>>>>>>>> >> >> >>> There are also compiler warnings about various handles and
>>>>>>>> >> >> >>> pointers
>>>>>>>> >> >> >>> that are different sizes on different platforms. I would like to
>>>>>>>> >> >> >>> fix
>>>>>>>> >> >> >>> all of these with some sort of padding or aliasing.
>>>>>>>> >> >> >>>
>>>>>>>> >> >> >>> I'm not sure how much of this I can do for the next release but
>>>>>>>> >> >> >>> I
>>>>>>>> >> >> >>> am
>>>>>>>> >> >> >>> shooting for at least LuaJIT. NW.js, and STK.
>>>>>>>> >> >> >>>
>>>>>>>> >> >> >>> Regards,
>>>>>>>> >> >> >>> Mike
>>>>>>>> >> >> >>>
>>>>>>>> >> >> >>> -----------------------------------------------------
>>>>>>>> >> >> >>> Michael Gogins
>>>>>>>> >> >> >>> Irreducible Productions
>>>>>>>> >> >> >>> http://michaelgogins.tumblr.com
>>>>>>>> >> >> >>> Michael dot Gogins at gmail dot com
>>>>>>>
>>>>>>>

Just for info,
I built on Windows 7 64 bit, and it worked nicely here too.

2016-02-28 19:27 GMT+01:00 Steven Yi :
> The system does statically link just about everything now.  I think
> the change was first introduced by Rory a while back.
>
> For CMake, everything I'm using is included in the build.sh script and
> the Custom-mingw64.cmake file, and I am not adding anything else
> outside of those so that we can all share the same exact build
> parameters.  Assuming that MSYS2 installs the same for everyone, we
> should hopefully have a completely reproducible build here for
> everyone.
>
> One thing to note, I am on a Windows 10 64-bit system.  Are you
> building on Windows 10?  Maybe that's a difference that might account
> for discrepancy in behavior.
>
>
> On Sun, Feb 28, 2016 at 1:14 PM, Michael Gogins
>  wrote:
>> csGblMtx.h (ghastly filename) uses WIndows threads in my build. Is
>> there some mixup between Windows threads and pthreads? It almost looks
>> like EnterCriticalSection (Windows API) is being called without the
>> critical section object first being initialized. Are you defining
>> WIN32 or GNUC or what for CMake?
>>
>> Best,
>> Mike
>>
>> -----------------------------------------------------
>> Michael Gogins
>> Irreducible Productions
>> http://michaelgogins.tumblr.com
>> Michael dot Gogins at gmail dot com
>>
>>
>> On Sun, Feb 28, 2016 at 12:34 PM, Michael Gogins
>>  wrote:
>>> All DLLs shown by the 64 bit dependency walker are in WIndows/system32
>>> or in the Csound build directory. Also they are all x64 as they should
>>> be. LIbsndfile does not show up however which seems wrong. Is it
>>> staticallhy linked now?
>>>
>>> Regards,
>>> Mike
>>>
>>> -----------------------------------------------------
>>> Michael Gogins
>>> Irreducible Productions
>>> http://michaelgogins.tumblr.com
>>> Michael dot Gogins at gmail dot com
>>>
>>>
>>> On Sun, Feb 28, 2016 at 12:17 PM, Michael Gogins
>>>  wrote:
>>>> No libwinpthread in WIndows system directories. I am going to run the
>>>> dependency checker on Csound.
>>>>
>>>> -----------------------------------------------------
>>>> Michael Gogins
>>>> Irreducible Productions
>>>> http://michaelgogins.tumblr.com
>>>> Michael dot Gogins at gmail dot com
>>>>
>>>>
>>>> On Sun, Feb 28, 2016 at 12:08 PM, Michael Gogins
>>>>  wrote:
>>>>> Mine has that as well: D:/msys64/mingw64/bin/libwinpthread-1.dll.
>>>>>
>>>>> But perhaps there is one of these in the WIndows system directories, I
>>>>> am checking.
>>>>>
>>>>> Best,
>>>>> Mike
>>>>>
>>>>>
>>>>> -----------------------------------------------------
>>>>> Michael Gogins
>>>>> Irreducible Productions
>>>>> http://michaelgogins.tumblr.com
>>>>> Michael dot Gogins at gmail dot com
>>>>>
>>>>>
>>>>> On Sun, Feb 28, 2016 at 12:06 PM, Michael Gogins
>>>>>  wrote:
>>>>>> I am running the build script from the MINGW64 shell, not the MSYS2
>>>>>> shell. MSYS2 installs both of these shells.
>>>>>>
>>>>>> Regards,
>>>>>> Mike
>>>>>>
>>>>>> -----------------------------------------------------
>>>>>> Michael Gogins
>>>>>> Irreducible Productions
>>>>>> http://michaelgogins.tumblr.com
>>>>>> Michael dot Gogins at gmail dot com
>>>>>>
>>>>>>
>>>>>> On Sun, Feb 28, 2016 at 11:58 AM, Rory Walsh  wrote:
>>>>>>> Hi Mike. I'm not sure what the problem there is. You are running the
>>>>>>> build.sh script from the MSYS2 shell? I built afresh again yesterday without
>>>>>>> any issues, albeit with many plugin opcodes disabled.
>>>>>>>
>>>>>>> On 28 February 2016 at 16:44, Michael Gogins 
>>>>>>> wrote:
>>>>>>>>
>>>>>>>> I'm running into a serious problem. I can build csound.exe with
>>>>>>>> MSYS2/mingw64, but it does not run. I have cleaned up my environment
>>>>>>>> so there are no binaries in the PATH but MSYS, mingw, and Csound and
>>>>>>>> its opcodes.
>>>>>>>>
>>>>>>>> (gdb) run
>>>>>>>> Starting program:
>>>>>>>> D:\msys64\home\restore\csound\mingw64\csound-mingw64\csound.exe
>>>>>>>> [New Thread 5784.0x6d8]
>>>>>>>>
>>>>>>>> Program received signal SIGSEGV, Segmentation fault.
>>>>>>>> 0x000007f8f3d17740 in ntdll!RtlMultiAppendUnicodeStringBuffer ()
>>>>>>>>    from C:\Windows\SYSTEM32\ntdll.dll
>>>>>>>> (gdb) bt
>>>>>>>> #0  0x000007f8f3d17740 in ntdll!RtlMultiAppendUnicodeStringBuffer ()
>>>>>>>>    from C:\Windows\SYSTEM32\ntdll.dll
>>>>>>>> #1  0x000007f8f3d0c5a5 in ntdll!RtlInitializeCriticalSection ()
>>>>>>>>    from C:\Windows\SYSTEM32\ntdll.dll
>>>>>>>> #2  0x000000006c5eed8d in csoundInitialize (flags=flags@entry=1)
>>>>>>>>     at D:/msys64/home/restore/csound/Top/csound.c:1119
>>>>>>>> #3  0x0000000000402fe5 in main (argc=1, argv=0x304700)
>>>>>>>>     at D:/msys64/home/restore/csound/frontends/csound/csound_main.c:258
>>>>>>>> (gdb)
>>>>>>>>
>>>>>>>>
>>>>>>>> -----------------------------------------------------
>>>>>>>> Michael Gogins
>>>>>>>> Irreducible Productions
>>>>>>>> http://michaelgogins.tumblr.com
>>>>>>>> Michael dot Gogins at gmail dot com
>>>>>>>>
>>>>>>>>
>>>>>>>> On Sat, Feb 27, 2016 at 4:33 PM, Victor Lazzarini
>>>>>>>>  wrote:
>>>>>>>> > Maybe try to get one of the Norwegian guys, they know about Windows.
>>>>>>>> >
>>>>>>>> > Victor Lazzarini
>>>>>>>> > Dean of Arts, Celtic Studies, and Philosophy
>>>>>>>> > Maynooth University
>>>>>>>> > Ireland
>>>>>>>> >
>>>>>>>> > On 27 Feb 2016, at 20:48, Tarmo Johannes  wrote:
>>>>>>>> >
>>>>>>>> > Hi,
>>>>>>>> > This is a problematic topic. We just discussed it with Joachim and don't
>>>>>>>> > have a dedicee to it right - there is truly lack of experienced Windows
>>>>>>>> > people... But keep thinking about it. I will read about MSYS2 myself too
>>>>>>>> > to
>>>>>>>> > be more aware.
>>>>>>>> > Thanks!
>>>>>>>> > Tarmo
>>>>>>>> >
>>>>>>>> > 27.02.2016 21:51 kirjutas kuupäeval "Steven Yi" :
>>>>>>>> >>
>>>>>>>> >> Hi Tarmo,
>>>>>>>> >>
>>>>>>>> >> Regarding CsoundQT, is there someone from the CsoundQT developers that
>>>>>>>> >> could contribute time to investigating building on Windows with MSYS2?
>>>>>>>> >>
>>>>>>>> >> Thanks!
>>>>>>>> >> steven
>>>>>>>> >>
>>>>>>>> >>
>>>>>>>> >> On Sat, Feb 27, 2016 at 1:57 PM, Tarmo Johannes 
>>>>>>>> >> wrote:
>>>>>>>> >> > Hi,
>>>>>>>> >> >
>>>>>>>> >> > And if you say MSYS2 has Qt, please do build alwo CsoundQt and let
>>>>>>>> >> > know
>>>>>>>> >> > if
>>>>>>>> >> > there are any problems or anything to do in the source code or
>>>>>>>> >> > project
>>>>>>>> >> > files.
>>>>>>>> >> >
>>>>>>>> >> > Thanks!
>>>>>>>> >> >
>>>>>>>> >> > On Saturday 27 February 2016 13:42:28 you wrote:
>>>>>>>> >> >> I will go with Python 2.7 for now.
>>>>>>>> >> >>
>>>>>>>> >> >> Best,
>>>>>>>> >> >> Mike
>>>>>>>> >> >>
>>>>>>>> >> >> -----------------------------------------------------
>>>>>>>> >> >> Michael Gogins
>>>>>>>> >> >> Irreducible Productions
>>>>>>>> >> >> http://michaelgogins.tumblr.com
>>>>>>>> >> >> Michael dot Gogins at gmail dot com
>>>>>>>> >> >>
>>>>>>>> >> >> On Sat, Feb 27, 2016 at 1:39 PM, Steven Yi 
>>>>>>>> >> >> wrote:
>>>>>>>> >> >> > I've been building for 2.7 myself.  I suppose the only way to
>>>>>>>> >> >> > satisfy
>>>>>>>> >> >> > everyone is to build something that works for both.  Perhaps we
>>>>>>>> >> >> > should
>>>>>>>> >> >> > finally add a build target specifically for Python 3 for all
>>>>>>>> >> >> > platforms?  We'd have to work out all the details for install
>>>>>>>> >> >> > locations for OSX and Linux.  Another option is to start
>>>>>>>> >> >> > leveraging
>>>>>>>> >> >> > python's package system to build the interfaces and have the user
>>>>>>>> >> >> > install those packages separately.
>>>>>>>> >> >> >
>>>>>>>> >> >> > Maybe just start with 2.7 for now as that was the last supported
>>>>>>>> >> >> > Python and punt on Python 3 until after this build?  Might be best
>>>>>>>> >> >> > so
>>>>>>>> >> >> > we can coordinate a solution for all platforms.
>>>>>>>> >> >> >
>>>>>>>> >> >> > On Sat, Feb 27, 2016 at 1:22 PM, Michael Gogins
>>>>>>>> >> >> >
>>>>>>>> >> >> >  wrote:
>>>>>>>> >> >> >> Another thing, should I support Python 2.7 or Python 3?
>>>>>>>> >> >> >>
>>>>>>>> >> >> >> Regards,
>>>>>>>> >> >> >> Mike
>>>>>>>> >> >> >>
>>>>>>>> >> >> >> -----------------------------------------------------
>>>>>>>> >> >> >> Michael Gogins
>>>>>>>> >> >> >> Irreducible Productions
>>>>>>>> >> >> >> http://michaelgogins.tumblr.com
>>>>>>>> >> >> >> Michael dot Gogins at gmail dot com
>>>>>>>> >> >> >>
>>>>>>>> >> >> >>
>>>>>>>> >> >> >> On Sat, Feb 27, 2016 at 12:54 PM, Michael Gogins
>>>>>>>> >> >> >>
>>>>>>>> >> >> >>  wrote:
>>>>>>>> >> >> >>> I have installed MSYS2, its mingw, toolchain, and the list of
>>>>>>>> >> >> >>> packages
>>>>>>>> >> >> >>> from our README.md.
>>>>>>>> >> >> >>>
>>>>>>>> >> >> >>> Things have started to build. I have to create an import library
>>>>>>>> >> >> >>> for
>>>>>>>> >> >> >>> Python x64. MSYS2 comes with its own Python, but I assume I
>>>>>>>> >> >> >>> should
>>>>>>>> >> >> >>> use
>>>>>>>> >> >> >>> regular Windows x64 Python from python.org.
>>>>>>>> >> >> >>>
>>>>>>>> >> >> >>> The Lua library problem mentioned in our README.md can probably
>>>>>>>> >> >> >>> be
>>>>>>>> >> >> >>> fixed with a file copy or symbolic link.
>>>>>>>> >> >> >>>
>>>>>>>> >> >> >>> I have installed NW.js for x64, and plan to use that for HTML5
>>>>>>>> >> >> >>> stuff.
>>>>>>>> >> >> >>> The current beta version of NW.js enables NaCl for x64 so a 64
>>>>>>>> >> >> >>> bit
>>>>>>>> >> >> >>> build of Csound for NaCl should run as well as the 64 bit build
>>>>>>>> >> >> >>> of
>>>>>>>> >> >> >>> csound.node.
>>>>>>>> >> >> >>>
>>>>>>>> >> >> >>> I am not sure what to do for CsoundQt. If NW.js works I see no
>>>>>>>> >> >> >>> particular need to build CsoundQt, but on the other the Qt SDK
>>>>>>>> >> >> >>> is
>>>>>>>> >> >> >>> installed in my MSYS2 environment so CsoundQt shouldn't be that
>>>>>>>> >> >> >>> hard
>>>>>>>> >> >> >>> to build.
>>>>>>>> >> >> >>>
>>>>>>>> >> >> >>> I also am not sure what to do about the Java interface.
>>>>>>>> >> >> >>> Presumably
>>>>>>>> >> >> >>> you, Steven, would like blue to run with x64 Csound.
>>>>>>>> >> >> >>>
>>>>>>>> >> >> >>> I also am not sure what to do about Jack, perhaps Windows
>>>>>>>> >> >> >>> support
>>>>>>>> >> >> >>> for
>>>>>>>> >> >> >>> Jack now exists, and if so, this could be added to the build.
>>>>>>>> >> >> >>>
>>>>>>>> >> >> >>> For a full build I think we should have package recipes for STK,
>>>>>>>> >> >> >>> LuaJIT, and perhaps NW.js.
>>>>>>>> >> >> >>>
>>>>>>>> >> >> >>> There are also compiler warnings about various handles and
>>>>>>>> >> >> >>> pointers
>>>>>>>> >> >> >>> that are different sizes on different platforms. I would like to
>>>>>>>> >> >> >>> fix
>>>>>>>> >> >> >>> all of these with some sort of padding or aliasing.
>>>>>>>> >> >> >>>
>>>>>>>> >> >> >>> I'm not sure how much of this I can do for the next release but
>>>>>>>> >> >> >>> I
>>>>>>>> >> >> >>> am
>>>>>>>> >> >> >>> shooting for at least LuaJIT. NW.js, and STK.
>>>>>>>> >> >> >>>
>>>>>>>> >> >> >>> Regards,
>>>>>>>> >> >> >>> Mike
>>>>>>>> >> >> >>>
>>>>>>>> >> >> >>> -----------------------------------------------------
>>>>>>>> >> >> >>> Michael Gogins
>>>>>>>> >> >> >>> Irreducible Productions
>>>>>>>> >> >> >>> http://michaelgogins.tumblr.com
>>>>>>>> >> >> >>> Michael dot Gogins at gmail dot com
>>>>>>>
>>>>>>>



-- 

Oeyvind Brandtsegg
Professor of Music Technology
NTNU
7491 Trondheim
Norway
Cell: +47 92 203 205

http://www.partikkelaudio.com/
http://soundcloud.com/brandtsegg
http://flyndresang.no/

It looks to me that in your CMakeCache.txt, the MSYS2 python library
and includes were used, but on mine it uses the system version.  I
remember there being some strange issues with Python in the past when
I was working on OSX that had to do with TCL, but the root cause was
some thing that was auto-run when loading the python library.  Could
you try deleting any python-related opcode and interface libraries in
your build folder and running Csound to check if there is any
interference there?

On Sun, Feb 28, 2016 at 1:27 PM, Michael Gogins
 wrote:
> I am attaching my Cmake cache.
>
> -----------------------------------------------------
> Michael Gogins
> Irreducible Productions
> http://michaelgogins.tumblr.com
> Michael dot Gogins at gmail dot com
>
>
> On Sun, Feb 28, 2016 at 1:24 PM, Michael Gogins
>  wrote:
>> In fact the critical section is NOT initialized. Why would this work
>> for you and not for me?
>>
>> Regards,
>> Mike
>>
>> -----------------------------------------------------
>> Michael Gogins
>> Irreducible Productions
>> http://michaelgogins.tumblr.com
>> Michael dot Gogins at gmail dot com
>>
>>
>> On Sun, Feb 28, 2016 at 1:14 PM, Michael Gogins
>>  wrote:
>>> csGblMtx.h (ghastly filename) uses WIndows threads in my build. Is
>>> there some mixup between Windows threads and pthreads? It almost looks
>>> like EnterCriticalSection (Windows API) is being called without the
>>> critical section object first being initialized. Are you defining
>>> WIN32 or GNUC or what for CMake?
>>>
>>> Best,
>>> Mike
>>>
>>> -----------------------------------------------------
>>> Michael Gogins
>>> Irreducible Productions
>>> http://michaelgogins.tumblr.com
>>> Michael dot Gogins at gmail dot com
>>>
>>>
>>> On Sun, Feb 28, 2016 at 12:34 PM, Michael Gogins
>>>  wrote:
>>>> All DLLs shown by the 64 bit dependency walker are in WIndows/system32
>>>> or in the Csound build directory. Also they are all x64 as they should
>>>> be. LIbsndfile does not show up however which seems wrong. Is it
>>>> staticallhy linked now?
>>>>
>>>> Regards,
>>>> Mike
>>>>
>>>> -----------------------------------------------------
>>>> Michael Gogins
>>>> Irreducible Productions
>>>> http://michaelgogins.tumblr.com
>>>> Michael dot Gogins at gmail dot com
>>>>
>>>>
>>>> On Sun, Feb 28, 2016 at 12:17 PM, Michael Gogins
>>>>  wrote:
>>>>> No libwinpthread in WIndows system directories. I am going to run the
>>>>> dependency checker on Csound.
>>>>>
>>>>> -----------------------------------------------------
>>>>> Michael Gogins
>>>>> Irreducible Productions
>>>>> http://michaelgogins.tumblr.com
>>>>> Michael dot Gogins at gmail dot com
>>>>>
>>>>>
>>>>> On Sun, Feb 28, 2016 at 12:08 PM, Michael Gogins
>>>>>  wrote:
>>>>>> Mine has that as well: D:/msys64/mingw64/bin/libwinpthread-1.dll.
>>>>>>
>>>>>> But perhaps there is one of these in the WIndows system directories, I
>>>>>> am checking.
>>>>>>
>>>>>> Best,
>>>>>> Mike
>>>>>>
>>>>>>
>>>>>> -----------------------------------------------------
>>>>>> Michael Gogins
>>>>>> Irreducible Productions
>>>>>> http://michaelgogins.tumblr.com
>>>>>> Michael dot Gogins at gmail dot com
>>>>>>
>>>>>>
>>>>>> On Sun, Feb 28, 2016 at 12:06 PM, Michael Gogins
>>>>>>  wrote:
>>>>>>> I am running the build script from the MINGW64 shell, not the MSYS2
>>>>>>> shell. MSYS2 installs both of these shells.
>>>>>>>
>>>>>>> Regards,
>>>>>>> Mike
>>>>>>>
>>>>>>> -----------------------------------------------------
>>>>>>> Michael Gogins
>>>>>>> Irreducible Productions
>>>>>>> http://michaelgogins.tumblr.com
>>>>>>> Michael dot Gogins at gmail dot com
>>>>>>>
>>>>>>>
>>>>>>> On Sun, Feb 28, 2016 at 11:58 AM, Rory Walsh  wrote:
>>>>>>>> Hi Mike. I'm not sure what the problem there is. You are running the
>>>>>>>> build.sh script from the MSYS2 shell? I built afresh again yesterday without
>>>>>>>> any issues, albeit with many plugin opcodes disabled.
>>>>>>>>
>>>>>>>> On 28 February 2016 at 16:44, Michael Gogins 
>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>> I'm running into a serious problem. I can build csound.exe with
>>>>>>>>> MSYS2/mingw64, but it does not run. I have cleaned up my environment
>>>>>>>>> so there are no binaries in the PATH but MSYS, mingw, and Csound and
>>>>>>>>> its opcodes.
>>>>>>>>>
>>>>>>>>> (gdb) run
>>>>>>>>> Starting program:
>>>>>>>>> D:\msys64\home\restore\csound\mingw64\csound-mingw64\csound.exe
>>>>>>>>> [New Thread 5784.0x6d8]
>>>>>>>>>
>>>>>>>>> Program received signal SIGSEGV, Segmentation fault.
>>>>>>>>> 0x000007f8f3d17740 in ntdll!RtlMultiAppendUnicodeStringBuffer ()
>>>>>>>>>    from C:\Windows\SYSTEM32\ntdll.dll
>>>>>>>>> (gdb) bt
>>>>>>>>> #0  0x000007f8f3d17740 in ntdll!RtlMultiAppendUnicodeStringBuffer ()
>>>>>>>>>    from C:\Windows\SYSTEM32\ntdll.dll
>>>>>>>>> #1  0x000007f8f3d0c5a5 in ntdll!RtlInitializeCriticalSection ()
>>>>>>>>>    from C:\Windows\SYSTEM32\ntdll.dll
>>>>>>>>> #2  0x000000006c5eed8d in csoundInitialize (flags=flags@entry=1)
>>>>>>>>>     at D:/msys64/home/restore/csound/Top/csound.c:1119
>>>>>>>>> #3  0x0000000000402fe5 in main (argc=1, argv=0x304700)
>>>>>>>>>     at D:/msys64/home/restore/csound/frontends/csound/csound_main.c:258
>>>>>>>>> (gdb)
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> -----------------------------------------------------
>>>>>>>>> Michael Gogins
>>>>>>>>> Irreducible Productions
>>>>>>>>> http://michaelgogins.tumblr.com
>>>>>>>>> Michael dot Gogins at gmail dot com
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Sat, Feb 27, 2016 at 4:33 PM, Victor Lazzarini
>>>>>>>>>  wrote:
>>>>>>>>> > Maybe try to get one of the Norwegian guys, they know about Windows.
>>>>>>>>> >
>>>>>>>>> > Victor Lazzarini
>>>>>>>>> > Dean of Arts, Celtic Studies, and Philosophy
>>>>>>>>> > Maynooth University
>>>>>>>>> > Ireland
>>>>>>>>> >
>>>>>>>>> > On 27 Feb 2016, at 20:48, Tarmo Johannes  wrote:
>>>>>>>>> >
>>>>>>>>> > Hi,
>>>>>>>>> > This is a problematic topic. We just discussed it with Joachim and don't
>>>>>>>>> > have a dedicee to it right - there is truly lack of experienced Windows
>>>>>>>>> > people... But keep thinking about it. I will read about MSYS2 myself too
>>>>>>>>> > to
>>>>>>>>> > be more aware.
>>>>>>>>> > Thanks!
>>>>>>>>> > Tarmo
>>>>>>>>> >
>>>>>>>>> > 27.02.2016 21:51 kirjutas kuupäeval "Steven Yi" :
>>>>>>>>> >>
>>>>>>>>> >> Hi Tarmo,
>>>>>>>>> >>
>>>>>>>>> >> Regarding CsoundQT, is there someone from the CsoundQT developers that
>>>>>>>>> >> could contribute time to investigating building on Windows with MSYS2?
>>>>>>>>> >>
>>>>>>>>> >> Thanks!
>>>>>>>>> >> steven
>>>>>>>>> >>
>>>>>>>>> >>
>>>>>>>>> >> On Sat, Feb 27, 2016 at 1:57 PM, Tarmo Johannes 
>>>>>>>>> >> wrote:
>>>>>>>>> >> > Hi,
>>>>>>>>> >> >
>>>>>>>>> >> > And if you say MSYS2 has Qt, please do build alwo CsoundQt and let
>>>>>>>>> >> > know
>>>>>>>>> >> > if
>>>>>>>>> >> > there are any problems or anything to do in the source code or
>>>>>>>>> >> > project
>>>>>>>>> >> > files.
>>>>>>>>> >> >
>>>>>>>>> >> > Thanks!
>>>>>>>>> >> >
>>>>>>>>> >> > On Saturday 27 February 2016 13:42:28 you wrote:
>>>>>>>>> >> >> I will go with Python 2.7 for now.
>>>>>>>>> >> >>
>>>>>>>>> >> >> Best,
>>>>>>>>> >> >> Mike
>>>>>>>>> >> >>
>>>>>>>>> >> >> -----------------------------------------------------
>>>>>>>>> >> >> Michael Gogins
>>>>>>>>> >> >> Irreducible Productions
>>>>>>>>> >> >> http://michaelgogins.tumblr.com
>>>>>>>>> >> >> Michael dot Gogins at gmail dot com
>>>>>>>>> >> >>
>>>>>>>>> >> >> On Sat, Feb 27, 2016 at 1:39 PM, Steven Yi 
>>>>>>>>> >> >> wrote:
>>>>>>>>> >> >> > I've been building for 2.7 myself.  I suppose the only way to
>>>>>>>>> >> >> > satisfy
>>>>>>>>> >> >> > everyone is to build something that works for both.  Perhaps we
>>>>>>>>> >> >> > should
>>>>>>>>> >> >> > finally add a build target specifically for Python 3 for all
>>>>>>>>> >> >> > platforms?  We'd have to work out all the details for install
>>>>>>>>> >> >> > locations for OSX and Linux.  Another option is to start
>>>>>>>>> >> >> > leveraging
>>>>>>>>> >> >> > python's package system to build the interfaces and have the user
>>>>>>>>> >> >> > install those packages separately.
>>>>>>>>> >> >> >
>>>>>>>>> >> >> > Maybe just start with 2.7 for now as that was the last supported
>>>>>>>>> >> >> > Python and punt on Python 3 until after this build?  Might be best
>>>>>>>>> >> >> > so
>>>>>>>>> >> >> > we can coordinate a solution for all platforms.
>>>>>>>>> >> >> >
>>>>>>>>> >> >> > On Sat, Feb 27, 2016 at 1:22 PM, Michael Gogins
>>>>>>>>> >> >> >
>>>>>>>>> >> >> >  wrote:
>>>>>>>>> >> >> >> Another thing, should I support Python 2.7 or Python 3?
>>>>>>>>> >> >> >>
>>>>>>>>> >> >> >> Regards,
>>>>>>>>> >> >> >> Mike
>>>>>>>>> >> >> >>
>>>>>>>>> >> >> >> -----------------------------------------------------
>>>>>>>>> >> >> >> Michael Gogins
>>>>>>>>> >> >> >> Irreducible Productions
>>>>>>>>> >> >> >> http://michaelgogins.tumblr.com
>>>>>>>>> >> >> >> Michael dot Gogins at gmail dot com
>>>>>>>>> >> >> >>
>>>>>>>>> >> >> >>
>>>>>>>>> >> >> >> On Sat, Feb 27, 2016 at 12:54 PM, Michael Gogins
>>>>>>>>> >> >> >>
>>>>>>>>> >> >> >>  wrote:
>>>>>>>>> >> >> >>> I have installed MSYS2, its mingw, toolchain, and the list of
>>>>>>>>> >> >> >>> packages
>>>>>>>>> >> >> >>> from our README.md.
>>>>>>>>> >> >> >>>
>>>>>>>>> >> >> >>> Things have started to build. I have to create an import library
>>>>>>>>> >> >> >>> for
>>>>>>>>> >> >> >>> Python x64. MSYS2 comes with its own Python, but I assume I
>>>>>>>>> >> >> >>> should
>>>>>>>>> >> >> >>> use
>>>>>>>>> >> >> >>> regular Windows x64 Python from python.org.
>>>>>>>>> >> >> >>>
>>>>>>>>> >> >> >>> The Lua library problem mentioned in our README.md can probably
>>>>>>>>> >> >> >>> be
>>>>>>>>> >> >> >>> fixed with a file copy or symbolic link.
>>>>>>>>> >> >> >>>
>>>>>>>>> >> >> >>> I have installed NW.js for x64, and plan to use that for HTML5
>>>>>>>>> >> >> >>> stuff.
>>>>>>>>> >> >> >>> The current beta version of NW.js enables NaCl for x64 so a 64
>>>>>>>>> >> >> >>> bit
>>>>>>>>> >> >> >>> build of Csound for NaCl should run as well as the 64 bit build
>>>>>>>>> >> >> >>> of
>>>>>>>>> >> >> >>> csound.node.
>>>>>>>>> >> >> >>>
>>>>>>>>> >> >> >>> I am not sure what to do for CsoundQt. If NW.js works I see no
>>>>>>>>> >> >> >>> particular need to build CsoundQt, but on the other the Qt SDK
>>>>>>>>> >> >> >>> is
>>>>>>>>> >> >> >>> installed in my MSYS2 environment so CsoundQt shouldn't be that
>>>>>>>>> >> >> >>> hard
>>>>>>>>> >> >> >>> to build.
>>>>>>>>> >> >> >>>
>>>>>>>>> >> >> >>> I also am not sure what to do about the Java interface.
>>>>>>>>> >> >> >>> Presumably
>>>>>>>>> >> >> >>> you, Steven, would like blue to run with x64 Csound.
>>>>>>>>> >> >> >>>
>>>>>>>>> >> >> >>> I also am not sure what to do about Jack, perhaps Windows
>>>>>>>>> >> >> >>> support
>>>>>>>>> >> >> >>> for
>>>>>>>>> >> >> >>> Jack now exists, and if so, this could be added to the build.
>>>>>>>>> >> >> >>>
>>>>>>>>> >> >> >>> For a full build I think we should have package recipes for STK,
>>>>>>>>> >> >> >>> LuaJIT, and perhaps NW.js.
>>>>>>>>> >> >> >>>
>>>>>>>>> >> >> >>> There are also compiler warnings about various handles and
>>>>>>>>> >> >> >>> pointers
>>>>>>>>> >> >> >>> that are different sizes on different platforms. I would like to
>>>>>>>>> >> >> >>> fix
>>>>>>>>> >> >> >>> all of these with some sort of padding or aliasing.
>>>>>>>>> >> >> >>>
>>>>>>>>> >> >> >>> I'm not sure how much of this I can do for the next release but
>>>>>>>>> >> >> >>> I
>>>>>>>>> >> >> >>> am
>>>>>>>>> >> >> >>> shooting for at least LuaJIT. NW.js, and STK.
>>>>>>>>> >> >> >>>
>>>>>>>>> >> >> >>> Regards,
>>>>>>>>> >> >> >>> Mike
>>>>>>>>> >> >> >>>
>>>>>>>>> >> >> >>> -----------------------------------------------------
>>>>>>>>> >> >> >>> Michael Gogins
>>>>>>>>> >> >> >>> Irreducible Productions
>>>>>>>>> >> >> >>> http://michaelgogins.tumblr.com
>>>>>>>>> >> >> >>> Michael dot Gogins at gmail dot com
>>>>>>>>

I tried deleting the Python interface and opcodes, same problem. But I
will try again.

Regards,
Mike

-----------------------------------------------------
Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com


On Sun, Feb 28, 2016 at 1:33 PM, Oeyvind Brandtsegg
 wrote:
> Just for info,
> I built on Windows 7 64 bit, and it worked nicely here too.
>
> 2016-02-28 19:27 GMT+01:00 Steven Yi :
>> The system does statically link just about everything now.  I think
>> the change was first introduced by Rory a while back.
>>
>> For CMake, everything I'm using is included in the build.sh script and
>> the Custom-mingw64.cmake file, and I am not adding anything else
>> outside of those so that we can all share the same exact build
>> parameters.  Assuming that MSYS2 installs the same for everyone, we
>> should hopefully have a completely reproducible build here for
>> everyone.
>>
>> One thing to note, I am on a Windows 10 64-bit system.  Are you
>> building on Windows 10?  Maybe that's a difference that might account
>> for discrepancy in behavior.
>>
>>
>> On Sun, Feb 28, 2016 at 1:14 PM, Michael Gogins
>>  wrote:
>>> csGblMtx.h (ghastly filename) uses WIndows threads in my build. Is
>>> there some mixup between Windows threads and pthreads? It almost looks
>>> like EnterCriticalSection (Windows API) is being called without the
>>> critical section object first being initialized. Are you defining
>>> WIN32 or GNUC or what for CMake?
>>>
>>> Best,
>>> Mike
>>>
>>> -----------------------------------------------------
>>> Michael Gogins
>>> Irreducible Productions
>>> http://michaelgogins.tumblr.com
>>> Michael dot Gogins at gmail dot com
>>>
>>>
>>> On Sun, Feb 28, 2016 at 12:34 PM, Michael Gogins
>>>  wrote:
>>>> All DLLs shown by the 64 bit dependency walker are in WIndows/system32
>>>> or in the Csound build directory. Also they are all x64 as they should
>>>> be. LIbsndfile does not show up however which seems wrong. Is it
>>>> staticallhy linked now?
>>>>
>>>> Regards,
>>>> Mike
>>>>
>>>> -----------------------------------------------------
>>>> Michael Gogins
>>>> Irreducible Productions
>>>> http://michaelgogins.tumblr.com
>>>> Michael dot Gogins at gmail dot com
>>>>
>>>>
>>>> On Sun, Feb 28, 2016 at 12:17 PM, Michael Gogins
>>>>  wrote:
>>>>> No libwinpthread in WIndows system directories. I am going to run the
>>>>> dependency checker on Csound.
>>>>>
>>>>> -----------------------------------------------------
>>>>> Michael Gogins
>>>>> Irreducible Productions
>>>>> http://michaelgogins.tumblr.com
>>>>> Michael dot Gogins at gmail dot com
>>>>>
>>>>>
>>>>> On Sun, Feb 28, 2016 at 12:08 PM, Michael Gogins
>>>>>  wrote:
>>>>>> Mine has that as well: D:/msys64/mingw64/bin/libwinpthread-1.dll.
>>>>>>
>>>>>> But perhaps there is one of these in the WIndows system directories, I
>>>>>> am checking.
>>>>>>
>>>>>> Best,
>>>>>> Mike
>>>>>>
>>>>>>
>>>>>> -----------------------------------------------------
>>>>>> Michael Gogins
>>>>>> Irreducible Productions
>>>>>> http://michaelgogins.tumblr.com
>>>>>> Michael dot Gogins at gmail dot com
>>>>>>
>>>>>>
>>>>>> On Sun, Feb 28, 2016 at 12:06 PM, Michael Gogins
>>>>>>  wrote:
>>>>>>> I am running the build script from the MINGW64 shell, not the MSYS2
>>>>>>> shell. MSYS2 installs both of these shells.
>>>>>>>
>>>>>>> Regards,
>>>>>>> Mike
>>>>>>>
>>>>>>> -----------------------------------------------------
>>>>>>> Michael Gogins
>>>>>>> Irreducible Productions
>>>>>>> http://michaelgogins.tumblr.com
>>>>>>> Michael dot Gogins at gmail dot com
>>>>>>>
>>>>>>>
>>>>>>> On Sun, Feb 28, 2016 at 11:58 AM, Rory Walsh  wrote:
>>>>>>>> Hi Mike. I'm not sure what the problem there is. You are running the
>>>>>>>> build.sh script from the MSYS2 shell? I built afresh again yesterday without
>>>>>>>> any issues, albeit with many plugin opcodes disabled.
>>>>>>>>
>>>>>>>> On 28 February 2016 at 16:44, Michael Gogins 
>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>> I'm running into a serious problem. I can build csound.exe with
>>>>>>>>> MSYS2/mingw64, but it does not run. I have cleaned up my environment
>>>>>>>>> so there are no binaries in the PATH but MSYS, mingw, and Csound and
>>>>>>>>> its opcodes.
>>>>>>>>>
>>>>>>>>> (gdb) run
>>>>>>>>> Starting program:
>>>>>>>>> D:\msys64\home\restore\csound\mingw64\csound-mingw64\csound.exe
>>>>>>>>> [New Thread 5784.0x6d8]
>>>>>>>>>
>>>>>>>>> Program received signal SIGSEGV, Segmentation fault.
>>>>>>>>> 0x000007f8f3d17740 in ntdll!RtlMultiAppendUnicodeStringBuffer ()
>>>>>>>>>    from C:\Windows\SYSTEM32\ntdll.dll
>>>>>>>>> (gdb) bt
>>>>>>>>> #0  0x000007f8f3d17740 in ntdll!RtlMultiAppendUnicodeStringBuffer ()
>>>>>>>>>    from C:\Windows\SYSTEM32\ntdll.dll
>>>>>>>>> #1  0x000007f8f3d0c5a5 in ntdll!RtlInitializeCriticalSection ()
>>>>>>>>>    from C:\Windows\SYSTEM32\ntdll.dll
>>>>>>>>> #2  0x000000006c5eed8d in csoundInitialize (flags=flags@entry=1)
>>>>>>>>>     at D:/msys64/home/restore/csound/Top/csound.c:1119
>>>>>>>>> #3  0x0000000000402fe5 in main (argc=1, argv=0x304700)
>>>>>>>>>     at D:/msys64/home/restore/csound/frontends/csound/csound_main.c:258
>>>>>>>>> (gdb)
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> -----------------------------------------------------
>>>>>>>>> Michael Gogins
>>>>>>>>> Irreducible Productions
>>>>>>>>> http://michaelgogins.tumblr.com
>>>>>>>>> Michael dot Gogins at gmail dot com
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Sat, Feb 27, 2016 at 4:33 PM, Victor Lazzarini
>>>>>>>>>  wrote:
>>>>>>>>> > Maybe try to get one of the Norwegian guys, they know about Windows.
>>>>>>>>> >
>>>>>>>>> > Victor Lazzarini
>>>>>>>>> > Dean of Arts, Celtic Studies, and Philosophy
>>>>>>>>> > Maynooth University
>>>>>>>>> > Ireland
>>>>>>>>> >
>>>>>>>>> > On 27 Feb 2016, at 20:48, Tarmo Johannes  wrote:
>>>>>>>>> >
>>>>>>>>> > Hi,
>>>>>>>>> > This is a problematic topic. We just discussed it with Joachim and don't
>>>>>>>>> > have a dedicee to it right - there is truly lack of experienced Windows
>>>>>>>>> > people... But keep thinking about it. I will read about MSYS2 myself too
>>>>>>>>> > to
>>>>>>>>> > be more aware.
>>>>>>>>> > Thanks!
>>>>>>>>> > Tarmo
>>>>>>>>> >
>>>>>>>>> > 27.02.2016 21:51 kirjutas kuupäeval "Steven Yi" :
>>>>>>>>> >>
>>>>>>>>> >> Hi Tarmo,
>>>>>>>>> >>
>>>>>>>>> >> Regarding CsoundQT, is there someone from the CsoundQT developers that
>>>>>>>>> >> could contribute time to investigating building on Windows with MSYS2?
>>>>>>>>> >>
>>>>>>>>> >> Thanks!
>>>>>>>>> >> steven
>>>>>>>>> >>
>>>>>>>>> >>
>>>>>>>>> >> On Sat, Feb 27, 2016 at 1:57 PM, Tarmo Johannes 
>>>>>>>>> >> wrote:
>>>>>>>>> >> > Hi,
>>>>>>>>> >> >
>>>>>>>>> >> > And if you say MSYS2 has Qt, please do build alwo CsoundQt and let
>>>>>>>>> >> > know
>>>>>>>>> >> > if
>>>>>>>>> >> > there are any problems or anything to do in the source code or
>>>>>>>>> >> > project
>>>>>>>>> >> > files.
>>>>>>>>> >> >
>>>>>>>>> >> > Thanks!
>>>>>>>>> >> >
>>>>>>>>> >> > On Saturday 27 February 2016 13:42:28 you wrote:
>>>>>>>>> >> >> I will go with Python 2.7 for now.
>>>>>>>>> >> >>
>>>>>>>>> >> >> Best,
>>>>>>>>> >> >> Mike
>>>>>>>>> >> >>
>>>>>>>>> >> >> -----------------------------------------------------
>>>>>>>>> >> >> Michael Gogins
>>>>>>>>> >> >> Irreducible Productions
>>>>>>>>> >> >> http://michaelgogins.tumblr.com
>>>>>>>>> >> >> Michael dot Gogins at gmail dot com
>>>>>>>>> >> >>
>>>>>>>>> >> >> On Sat, Feb 27, 2016 at 1:39 PM, Steven Yi 
>>>>>>>>> >> >> wrote:
>>>>>>>>> >> >> > I've been building for 2.7 myself.  I suppose the only way to
>>>>>>>>> >> >> > satisfy
>>>>>>>>> >> >> > everyone is to build something that works for both.  Perhaps we
>>>>>>>>> >> >> > should
>>>>>>>>> >> >> > finally add a build target specifically for Python 3 for all
>>>>>>>>> >> >> > platforms?  We'd have to work out all the details for install
>>>>>>>>> >> >> > locations for OSX and Linux.  Another option is to start
>>>>>>>>> >> >> > leveraging
>>>>>>>>> >> >> > python's package system to build the interfaces and have the user
>>>>>>>>> >> >> > install those packages separately.
>>>>>>>>> >> >> >
>>>>>>>>> >> >> > Maybe just start with 2.7 for now as that was the last supported
>>>>>>>>> >> >> > Python and punt on Python 3 until after this build?  Might be best
>>>>>>>>> >> >> > so
>>>>>>>>> >> >> > we can coordinate a solution for all platforms.
>>>>>>>>> >> >> >
>>>>>>>>> >> >> > On Sat, Feb 27, 2016 at 1:22 PM, Michael Gogins
>>>>>>>>> >> >> >
>>>>>>>>> >> >> >  wrote:
>>>>>>>>> >> >> >> Another thing, should I support Python 2.7 or Python 3?
>>>>>>>>> >> >> >>
>>>>>>>>> >> >> >> Regards,
>>>>>>>>> >> >> >> Mike
>>>>>>>>> >> >> >>
>>>>>>>>> >> >> >> -----------------------------------------------------
>>>>>>>>> >> >> >> Michael Gogins
>>>>>>>>> >> >> >> Irreducible Productions
>>>>>>>>> >> >> >> http://michaelgogins.tumblr.com
>>>>>>>>> >> >> >> Michael dot Gogins at gmail dot com
>>>>>>>>> >> >> >>
>>>>>>>>> >> >> >>
>>>>>>>>> >> >> >> On Sat, Feb 27, 2016 at 12:54 PM, Michael Gogins
>>>>>>>>> >> >> >>
>>>>>>>>> >> >> >>  wrote:
>>>>>>>>> >> >> >>> I have installed MSYS2, its mingw, toolchain, and the list of
>>>>>>>>> >> >> >>> packages
>>>>>>>>> >> >> >>> from our README.md.
>>>>>>>>> >> >> >>>
>>>>>>>>> >> >> >>> Things have started to build. I have to create an import library
>>>>>>>>> >> >> >>> for
>>>>>>>>> >> >> >>> Python x64. MSYS2 comes with its own Python, but I assume I
>>>>>>>>> >> >> >>> should
>>>>>>>>> >> >> >>> use
>>>>>>>>> >> >> >>> regular Windows x64 Python from python.org.
>>>>>>>>> >> >> >>>
>>>>>>>>> >> >> >>> The Lua library problem mentioned in our README.md can probably
>>>>>>>>> >> >> >>> be
>>>>>>>>> >> >> >>> fixed with a file copy or symbolic link.
>>>>>>>>> >> >> >>>
>>>>>>>>> >> >> >>> I have installed NW.js for x64, and plan to use that for HTML5
>>>>>>>>> >> >> >>> stuff.
>>>>>>>>> >> >> >>> The current beta version of NW.js enables NaCl for x64 so a 64
>>>>>>>>> >> >> >>> bit
>>>>>>>>> >> >> >>> build of Csound for NaCl should run as well as the 64 bit build
>>>>>>>>> >> >> >>> of
>>>>>>>>> >> >> >>> csound.node.
>>>>>>>>> >> >> >>>
>>>>>>>>> >> >> >>> I am not sure what to do for CsoundQt. If NW.js works I see no
>>>>>>>>> >> >> >>> particular need to build CsoundQt, but on the other the Qt SDK
>>>>>>>>> >> >> >>> is
>>>>>>>>> >> >> >>> installed in my MSYS2 environment so CsoundQt shouldn't be that
>>>>>>>>> >> >> >>> hard
>>>>>>>>> >> >> >>> to build.
>>>>>>>>> >> >> >>>
>>>>>>>>> >> >> >>> I also am not sure what to do about the Java interface.
>>>>>>>>> >> >> >>> Presumably
>>>>>>>>> >> >> >>> you, Steven, would like blue to run with x64 Csound.
>>>>>>>>> >> >> >>>
>>>>>>>>> >> >> >>> I also am not sure what to do about Jack, perhaps Windows
>>>>>>>>> >> >> >>> support
>>>>>>>>> >> >> >>> for
>>>>>>>>> >> >> >>> Jack now exists, and if so, this could be added to the build.
>>>>>>>>> >> >> >>>
>>>>>>>>> >> >> >>> For a full build I think we should have package recipes for STK,
>>>>>>>>> >> >> >>> LuaJIT, and perhaps NW.js.
>>>>>>>>> >> >> >>>
>>>>>>>>> >> >> >>> There are also compiler warnings about various handles and
>>>>>>>>> >> >> >>> pointers
>>>>>>>>> >> >> >>> that are different sizes on different platforms. I would like to
>>>>>>>>> >> >> >>> fix
>>>>>>>>> >> >> >>> all of these with some sort of padding or aliasing.
>>>>>>>>> >> >> >>>
>>>>>>>>> >> >> >>> I'm not sure how much of this I can do for the next release but
>>>>>>>>> >> >> >>> I
>>>>>>>>> >> >> >>> am
>>>>>>>>> >> >> >>> shooting for at least LuaJIT. NW.js, and STK.
>>>>>>>>> >> >> >>>
>>>>>>>>> >> >> >>> Regards,
>>>>>>>>> >> >> >>> Mike
>>>>>>>>> >> >> >>>
>>>>>>>>> >> >> >>> -----------------------------------------------------
>>>>>>>>> >> >> >>> Michael Gogins
>>>>>>>>> >> >> >>> Irreducible Productions
>>>>>>>>> >> >> >>> http://michaelgogins.tumblr.com
>>>>>>>>> >> >> >>> Michael dot Gogins at gmail dot com
>>>>>>>>
>>>>>>>>
>
>
>
> --
>
> Oeyvind Brandtsegg
> Professor of Music Technology
> NTNU
> 7491 Trondheim
> Norway
> Cell: +47 92 203 205
>
> http://www.partikkelaudio.com/
> http://soundcloud.com/brandtsegg
> http://flyndresang.no/

My MSYS2-mingw64 build of Csound now runs.

There was a bug in the code, which I have fixed. Csound was trying to lock the global mutex (a Windows critical section) without first calling InitializeCriticalSection. I fixed this bug by changing threads.c to initialize the critical section. This in turn required changing the conditional compilation to test for WIN32 instead of MSC. WIN32 is true for both MinGW and Microsoft C, and is the correct test for this case, which is about the operating system and not the runtime.

As to why this bug ran for Steven and Oeyvind, I can only conjecture either that their build was configured to use exclusively pthreads rather than Windows threading, or that their operating system and toolchain configuration permitted the uninitialized critical section to function anyway.

-----------------------------------------------------
Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com

On Sun, Feb 28, 2016 at 5:17 PM, Sigurd Saue <sigurd.saue@ntnu.no> wrote:
> Hmm. That sounds like me …
>
>
>
> If you’re not in a great hurry I could probably give it a shot. I just have
> to get going on csound~ first.
>
>
>
> Sigurd
>
>
>
> From: Csound-developers [mailto:CSOUND-DEV@LISTSERV.HEANET.IE] On Behalf Of
> Victor Lazzarini
> Sent: Saturday, February 27, 2016 10:33 PM
> To: CSOUND-DEV@LISTSERV.HEANET.IE
> Subject: Re: [Csnd-dev] Status of MSYS2/x64 Windows build
>
>
>
> Maybe try to get one of the Norwegian guys, they know about Windows.
>
> Victor Lazzarini
>
> Dean of Arts, Celtic Studies, and Philosophy
>
> Maynooth University
>
> Ireland
>
>
> On 27 Feb 2016, at 20:48, Tarmo Johannes <trmjhnns@GMAIL.COM> wrote:
>
> Hi,
> This is a problematic topic. We just discussed it with Joachim and don't
> have a dedicee to it right - there is truly lack of experienced Windows
> people... But keep thinking about it. I will read about MSYS2 myself too to
> be more aware.
> Thanks!
> Tarmo
>
> 27.02.2016 21:51 kirjutas kuupäeval "Steven Yi" <stevenyi@gmail.com>:
>
> Hi Tarmo,
>
> Regarding CsoundQT, is there someone from the CsoundQT developers that
> could contribute time to investigating building on Windows with MSYS2?
>
> Thanks!
> steven
>
>
> On Sat, Feb 27, 2016 at 1:57 PM, Tarmo Johannes <trmjhnns@gmail.com> wrote:
>> Hi,
>>
>> And if you say MSYS2 has Qt, please do build alwo CsoundQt and let know if
>> there are any problems or anything to do in the source code or project
>> files.
>>
>> Thanks!
>>
>> On Saturday 27 February 2016 13:42:28 you wrote:
>>> I will go with Python 2.7 for now.
>>>
>>> Best,
>>> Mike
>>>
>>> -----------------------------------------------------
>>> Michael Gogins
>>> Irreducible Productions
>>> http://michaelgogins.tumblr.com
>>> Michael dot Gogins at gmail dot com
>>>
>>> On Sat, Feb 27, 2016 at 1:39 PM, Steven Yi <stevenyi@gmail.com> wrote:
>>> > I've been building for 2.7 myself. I suppose the only way to satisfy
>>> > everyone is to build something that works for both. Perhaps we should
>>> > finally add a build target specifically for Python 3 for all
>>> > platforms? We'd have to work out all the details for install
>>> > locations for OSX and Linux. Another option is to start leveraging
>>> > python's package system to build the interfaces and have the user
>>> > install those packages separately.
>>> >
>>> > Maybe just start with 2.7 for now as that was the last supported
>>> > Python and punt on Python 3 until after this build? Might be best so
>>> > we can coordinate a solution for all platforms.
>>> >
>>> > On Sat, Feb 27, 2016 at 1:22 PM, Michael Gogins
>>> >
>>> > <michael.gogins@gmail.com> wrote:
>>> >> Another thing, should I support Python 2.7 or Python 3?
>>> >>
>>> >> Regards,
>>> >> Mike
>>> >>
>>> >> -----------------------------------------------------
>>> >> Michael Gogins
>>> >> Irreducible Productions
>>> >> http://michaelgogins.tumblr.com
>>> >> Michael dot Gogins at gmail dot com
>>> >>
>>> >>
>>> >> On Sat, Feb 27, 2016 at 12:54 PM, Michael Gogins
>>> >>
>>> >> <michael.gogins@gmail.com> wrote:
>>> >>> I have installed MSYS2, its mingw, toolchain, and the list of
>>> >>> packages
>>> >>> from our README.md.
>>> >>>
>>> >>> Things have started to build. I have to create an import library for
>>> >>> Python x64. MSYS2 comes with its own Python, but I assume I should
>>> >>> use
>>> >>> regular Windows x64 Python from python.org.
>>> >>>
>>> >>> The Lua library problem mentioned in our README.md can probably be
>>> >>> fixed with a file copy or symbolic link.
>>> >>>
>>> >>> I have installed NW.js for x64, and plan to use that for HTML5 stuff.
>>> >>> The current beta version of NW.js enables NaCl for x64 so a 64 bit
>>> >>> build of Csound for NaCl should run as well as the 64 bit build of
>>> >>> csound.node.
>>> >>>
>>> >>> I am not sure what to do for CsoundQt. If NW.js works I see no
>>> >>> particular need to build CsoundQt, but on the other the Qt SDK is
>>> >>> installed in my MSYS2 environment so CsoundQt shouldn't be that hard
>>> >>> to build.
>>> >>>
>>> >>> I also am not sure what to do about the Java interface. Presumably
>>> >>> you, Steven, would like blue to run with x64 Csound.
>>> >>>
>>> >>> I also am not sure what to do about Jack, perhaps Windows support for
>>> >>> Jack now exists, and if so, this could be added to the build.
>>> >>>
>>> >>> For a full build I think we should have package recipes for STK,
>>> >>> LuaJIT, and perhaps NW.js.
>>> >>>
>>> >>> There are also compiler warnings about various handles and pointers
>>> >>> that are different sizes on different platforms. I would like to fix
>>> >>> all of these with some sort of padding or aliasing.
>>> >>>
>>> >>> I'm not sure how much of this I can do for the next release but I am
>>> >>> shooting for at least LuaJIT. NW.js, and STK.
>>> >>>
>>> >>> Regards,
>>> >>> Mike
>>> >>>
>>> >>> -----------------------------------------------------
>>> >>> Michael Gogins
>>> >>> Irreducible Productions
>>> >>> http://michaelgogins.tumblr.com
>>> >>> Michael dot Gogins at gmail dot com

Same here, works now as before.  I do not have any further ideas as to
what could be the root cause of the issue there.

On Mon, Feb 29, 2016 at 9:29 AM, Rory Walsh  wrote:
> I just built here just now with your changes and it seems to run fine for
> me. For what it's worth, I also had no such issues with my Csound binaries
> before your made these changes. Odd.
>
> On 29 February 2016 at 12:38, Michael Gogins 
> wrote:
>>
>> My MSYS2-mingw64 build of Csound now runs.
>>
>> There was a bug in the code, which I have fixed. Csound was trying to lock
>> the global mutex (a Windows critical section) without first calling
>> InitializeCriticalSection. I fixed this bug by changing threads.c to
>> initialize the critical section. This in turn required changing the
>> conditional compilation to test for WIN32 instead of MSC. WIN32 is true for
>> both MinGW and Microsoft C, and is the correct test for this case, which is
>> about the operating system and not the runtime.
>>
>> As to why this bug ran for Steven and Oeyvind, I can only conjecture
>> either that their build was configured to use exclusively pthreads rather
>> than Windows threading, or that their operating system and toolchain
>> configuration permitted the uninitialized critical section to function
>> anyway.
>>
>> -----------------------------------------------------
>> Michael Gogins
>> Irreducible Productions
>> http://michaelgogins.tumblr.com
>> Michael dot Gogins at gmail dot com
>>
>> On Sun, Feb 28, 2016 at 5:17 PM, Sigurd Saue  wrote:
>> > Hmm. That sounds like me …
>> >
>> >
>> >
>> > If you’re not in a great hurry I could probably give it a shot. I just
>> > have
>> > to get going on csound~ first.
>> >
>> >
>> >
>> > Sigurd
>> >
>> >
>> >
>> > From: Csound-developers [mailto:CSOUND-DEV@LISTSERV.HEANET.IE] On Behalf
>> > Of
>> > Victor Lazzarini
>> > Sent: Saturday, February 27, 2016 10:33 PM
>> > To: CSOUND-DEV@LISTSERV.HEANET.IE
>> > Subject: Re: [Csnd-dev] Status of MSYS2/x64 Windows build
>> >
>> >
>> >
>> > Maybe try to get one of the Norwegian guys, they know about Windows.
>> >
>> > Victor Lazzarini
>> >
>> > Dean of Arts, Celtic Studies, and Philosophy
>> >
>> > Maynooth University
>> >
>> > Ireland
>> >
>> >
>> > On 27 Feb 2016, at 20:48, Tarmo Johannes  wrote:
>> >
>> > Hi,
>> > This is a problematic topic. We just discussed it with Joachim and don't
>> > have a dedicee to it right - there is truly lack of experienced Windows
>> > people... But keep thinking about it. I will read about MSYS2 myself too
>> > to
>> > be more aware.
>> > Thanks!
>> > Tarmo
>> >
>> > 27.02.2016 21:51 kirjutas kuupäeval "Steven Yi" :
>> >
>> > Hi Tarmo,
>> >
>> > Regarding CsoundQT, is there someone from the CsoundQT developers that
>> > could contribute time to investigating building on Windows with MSYS2?
>> >
>> > Thanks!
>> > steven
>> >
>> >
>> > On Sat, Feb 27, 2016 at 1:57 PM, Tarmo Johannes 
>> > wrote:
>> >> Hi,
>> >>
>> >> And if you say MSYS2 has Qt, please do build alwo CsoundQt and let know
>> >> if
>> >> there are any problems or anything to do in the source code or project
>> >> files.
>> >>
>> >> Thanks!
>> >>
>> >> On Saturday 27 February 2016 13:42:28 you wrote:
>> >>> I will go with Python 2.7 for now.
>> >>>
>> >>> Best,
>> >>> Mike
>> >>>
>> >>> -----------------------------------------------------
>> >>> Michael Gogins
>> >>> Irreducible Productions
>> >>> http://michaelgogins.tumblr.com
>> >>> Michael dot Gogins at gmail dot com
>> >>>
>> >>> On Sat, Feb 27, 2016 at 1:39 PM, Steven Yi  wrote:
>> >>> > I've been building for 2.7 myself. I suppose the only way to satisfy
>> >>> > everyone is to build something that works for both. Perhaps we
>> >>> > should
>> >>> > finally add a build target specifically for Python 3 for all
>> >>> > platforms? We'd have to work out all the details for install
>> >>> > locations for OSX and Linux. Another option is to start leveraging
>> >>> > python's package system to build the interfaces and have the user
>> >>> > install those packages separately.
>> >>> >
>> >>> > Maybe just start with 2.7 for now as that was the last supported
>> >>> > Python and punt on Python 3 until after this build? Might be best so
>> >>> > we can coordinate a solution for all platforms.
>> >>> >
>> >>> > On Sat, Feb 27, 2016 at 1:22 PM, Michael Gogins
>> >>> >
>> >>> >  wrote:
>> >>> >> Another thing, should I support Python 2.7 or Python 3?
>> >>> >>
>> >>> >> Regards,
>> >>> >> Mike
>> >>> >>
>> >>> >> -----------------------------------------------------
>> >>> >> Michael Gogins
>> >>> >> Irreducible Productions
>> >>> >> http://michaelgogins.tumblr.com
>> >>> >> Michael dot Gogins at gmail dot com
>> >>> >>
>> >>> >>
>> >>> >> On Sat, Feb 27, 2016 at 12:54 PM, Michael Gogins
>> >>> >>
>> >>> >>  wrote:
>> >>> >>> I have installed MSYS2, its mingw, toolchain, and the list of
>> >>> >>> packages
>> >>> >>> from our README.md.
>> >>> >>>
>> >>> >>> Things have started to build. I have to create an import library
>> >>> >>> for
>> >>> >>> Python x64. MSYS2 comes with its own Python, but I assume I should
>> >>> >>> use
>> >>> >>> regular Windows x64 Python from python.org.
>> >>> >>>
>> >>> >>> The Lua library problem mentioned in our README.md can probably be
>> >>> >>> fixed with a file copy or symbolic link.
>> >>> >>>
>> >>> >>> I have installed NW.js for x64, and plan to use that for HTML5
>> >>> >>> stuff.
>> >>> >>> The current beta version of NW.js enables NaCl for x64 so a 64 bit
>> >>> >>> build of Csound for NaCl should run as well as the 64 bit build of
>> >>> >>> csound.node.
>> >>> >>>
>> >>> >>> I am not sure what to do for CsoundQt. If NW.js works I see no
>> >>> >>> particular need to build CsoundQt, but on the other the Qt SDK is
>> >>> >>> installed in my MSYS2 environment so CsoundQt shouldn't be that
>> >>> >>> hard
>> >>> >>> to build.
>> >>> >>>
>> >>> >>> I also am not sure what to do about the Java interface. Presumably
>> >>> >>> you, Steven, would like blue to run with x64 Csound.
>> >>> >>>
>> >>> >>> I also am not sure what to do about Jack, perhaps Windows support
>> >>> >>> for
>> >>> >>> Jack now exists, and if so, this could be added to the build.
>> >>> >>>
>> >>> >>> For a full build I think we should have package recipes for STK,
>> >>> >>> LuaJIT, and perhaps NW.js.
>> >>> >>>
>> >>> >>> There are also compiler warnings about various handles and
>> >>> >>> pointers
>> >>> >>> that are different sizes on different platforms. I would like to
>> >>> >>> fix
>> >>> >>> all of these with some sort of padding or aliasing.
>> >>> >>>
>> >>> >>> I'm not sure how much of this I can do for the next release but I
>> >>> >>> am
>> >>> >>> shooting for at least LuaJIT. NW.js, and STK.
>> >>> >>>
>> >>> >>> Regards,
>> >>> >>> Mike
>> >>> >>>
>> >>> >>> -----------------------------------------------------
>> >>> >>> Michael Gogins
>> >>> >>> Irreducible Productions
>> >>> >>> http://michaelgogins.tumblr.com
>> >>> >>> Michael dot Gogins at gmail dot com
>

Since there seem to be differences between the builds or the systems,
perhaps it would make sense to test your build here, Mike? I've been
notorious for getting library clashes between csound versions (e.g.
canonical and Cabbage). If you make a binary available somewhere, I
can try it out here.

2016-03-01 18:18 GMT+01:00 Steven Yi :
> Same here, works now as before.  I do not have any further ideas as to
> what could be the root cause of the issue there.
>
> On Mon, Feb 29, 2016 at 9:29 AM, Rory Walsh  wrote:
>> I just built here just now with your changes and it seems to run fine for
>> me. For what it's worth, I also had no such issues with my Csound binaries
>> before your made these changes. Odd.
>>
>> On 29 February 2016 at 12:38, Michael Gogins 
>> wrote:
>>>
>>> My MSYS2-mingw64 build of Csound now runs.
>>>
>>> There was a bug in the code, which I have fixed. Csound was trying to lock
>>> the global mutex (a Windows critical section) without first calling
>>> InitializeCriticalSection. I fixed this bug by changing threads.c to
>>> initialize the critical section. This in turn required changing the
>>> conditional compilation to test for WIN32 instead of MSC. WIN32 is true for
>>> both MinGW and Microsoft C, and is the correct test for this case, which is
>>> about the operating system and not the runtime.
>>>
>>> As to why this bug ran for Steven and Oeyvind, I can only conjecture
>>> either that their build was configured to use exclusively pthreads rather
>>> than Windows threading, or that their operating system and toolchain
>>> configuration permitted the uninitialized critical section to function
>>> anyway.
>>>
>>> -----------------------------------------------------
>>> Michael Gogins
>>> Irreducible Productions
>>> http://michaelgogins.tumblr.com
>>> Michael dot Gogins at gmail dot com
>>>
>>> On Sun, Feb 28, 2016 at 5:17 PM, Sigurd Saue  wrote:
>>> > Hmm. That sounds like me …
>>> >
>>> >
>>> >
>>> > If you’re not in a great hurry I could probably give it a shot. I just
>>> > have
>>> > to get going on csound~ first.
>>> >
>>> >
>>> >
>>> > Sigurd
>>> >
>>> >
>>> >
>>> > From: Csound-developers [mailto:CSOUND-DEV@LISTSERV.HEANET.IE] On Behalf
>>> > Of
>>> > Victor Lazzarini
>>> > Sent: Saturday, February 27, 2016 10:33 PM
>>> > To: CSOUND-DEV@LISTSERV.HEANET.IE
>>> > Subject: Re: [Csnd-dev] Status of MSYS2/x64 Windows build
>>> >
>>> >
>>> >
>>> > Maybe try to get one of the Norwegian guys, they know about Windows.
>>> >
>>> > Victor Lazzarini
>>> >
>>> > Dean of Arts, Celtic Studies, and Philosophy
>>> >
>>> > Maynooth University
>>> >
>>> > Ireland
>>> >
>>> >
>>> > On 27 Feb 2016, at 20:48, Tarmo Johannes  wrote:
>>> >
>>> > Hi,
>>> > This is a problematic topic. We just discussed it with Joachim and don't
>>> > have a dedicee to it right - there is truly lack of experienced Windows
>>> > people... But keep thinking about it. I will read about MSYS2 myself too
>>> > to
>>> > be more aware.
>>> > Thanks!
>>> > Tarmo
>>> >
>>> > 27.02.2016 21:51 kirjutas kuupäeval "Steven Yi" :
>>> >
>>> > Hi Tarmo,
>>> >
>>> > Regarding CsoundQT, is there someone from the CsoundQT developers that
>>> > could contribute time to investigating building on Windows with MSYS2?
>>> >
>>> > Thanks!
>>> > steven
>>> >
>>> >
>>> > On Sat, Feb 27, 2016 at 1:57 PM, Tarmo Johannes 
>>> > wrote:
>>> >> Hi,
>>> >>
>>> >> And if you say MSYS2 has Qt, please do build alwo CsoundQt and let know
>>> >> if
>>> >> there are any problems or anything to do in the source code or project
>>> >> files.
>>> >>
>>> >> Thanks!
>>> >>
>>> >> On Saturday 27 February 2016 13:42:28 you wrote:
>>> >>> I will go with Python 2.7 for now.
>>> >>>
>>> >>> Best,
>>> >>> Mike
>>> >>>
>>> >>> -----------------------------------------------------
>>> >>> Michael Gogins
>>> >>> Irreducible Productions
>>> >>> http://michaelgogins.tumblr.com
>>> >>> Michael dot Gogins at gmail dot com
>>> >>>
>>> >>> On Sat, Feb 27, 2016 at 1:39 PM, Steven Yi  wrote:
>>> >>> > I've been building for 2.7 myself. I suppose the only way to satisfy
>>> >>> > everyone is to build something that works for both. Perhaps we
>>> >>> > should
>>> >>> > finally add a build target specifically for Python 3 for all
>>> >>> > platforms? We'd have to work out all the details for install
>>> >>> > locations for OSX and Linux. Another option is to start leveraging
>>> >>> > python's package system to build the interfaces and have the user
>>> >>> > install those packages separately.
>>> >>> >
>>> >>> > Maybe just start with 2.7 for now as that was the last supported
>>> >>> > Python and punt on Python 3 until after this build? Might be best so
>>> >>> > we can coordinate a solution for all platforms.
>>> >>> >
>>> >>> > On Sat, Feb 27, 2016 at 1:22 PM, Michael Gogins
>>> >>> >
>>> >>> >  wrote:
>>> >>> >> Another thing, should I support Python 2.7 or Python 3?
>>> >>> >>
>>> >>> >> Regards,
>>> >>> >> Mike
>>> >>> >>
>>> >>> >> -----------------------------------------------------
>>> >>> >> Michael Gogins
>>> >>> >> Irreducible Productions
>>> >>> >> http://michaelgogins.tumblr.com
>>> >>> >> Michael dot Gogins at gmail dot com
>>> >>> >>
>>> >>> >>
>>> >>> >> On Sat, Feb 27, 2016 at 12:54 PM, Michael Gogins
>>> >>> >>
>>> >>> >>  wrote:
>>> >>> >>> I have installed MSYS2, its mingw, toolchain, and the list of
>>> >>> >>> packages
>>> >>> >>> from our README.md.
>>> >>> >>>
>>> >>> >>> Things have started to build. I have to create an import library
>>> >>> >>> for
>>> >>> >>> Python x64. MSYS2 comes with its own Python, but I assume I should
>>> >>> >>> use
>>> >>> >>> regular Windows x64 Python from python.org.
>>> >>> >>>
>>> >>> >>> The Lua library problem mentioned in our README.md can probably be
>>> >>> >>> fixed with a file copy or symbolic link.
>>> >>> >>>
>>> >>> >>> I have installed NW.js for x64, and plan to use that for HTML5
>>> >>> >>> stuff.
>>> >>> >>> The current beta version of NW.js enables NaCl for x64 so a 64 bit
>>> >>> >>> build of Csound for NaCl should run as well as the 64 bit build of
>>> >>> >>> csound.node.
>>> >>> >>>
>>> >>> >>> I am not sure what to do for CsoundQt. If NW.js works I see no
>>> >>> >>> particular need to build CsoundQt, but on the other the Qt SDK is
>>> >>> >>> installed in my MSYS2 environment so CsoundQt shouldn't be that
>>> >>> >>> hard
>>> >>> >>> to build.
>>> >>> >>>
>>> >>> >>> I also am not sure what to do about the Java interface. Presumably
>>> >>> >>> you, Steven, would like blue to run with x64 Csound.
>>> >>> >>>
>>> >>> >>> I also am not sure what to do about Jack, perhaps Windows support
>>> >>> >>> for
>>> >>> >>> Jack now exists, and if so, this could be added to the build.
>>> >>> >>>
>>> >>> >>> For a full build I think we should have package recipes for STK,
>>> >>> >>> LuaJIT, and perhaps NW.js.
>>> >>> >>>
>>> >>> >>> There are also compiler warnings about various handles and
>>> >>> >>> pointers
>>> >>> >>> that are different sizes on different platforms. I would like to
>>> >>> >>> fix
>>> >>> >>> all of these with some sort of padding or aliasing.
>>> >>> >>>
>>> >>> >>> I'm not sure how much of this I can do for the next release but I
>>> >>> >>> am
>>> >>> >>> shooting for at least LuaJIT. NW.js, and STK.
>>> >>> >>>
>>> >>> >>> Regards,
>>> >>> >>> Mike
>>> >>> >>>
>>> >>> >>> -----------------------------------------------------
>>> >>> >>> Michael Gogins
>>> >>> >>> Irreducible Productions
>>> >>> >>> http://michaelgogins.tumblr.com
>>> >>> >>> Michael dot Gogins at gmail dot com
>>
>>



-- 

Oeyvind Brandtsegg
Professor of Music Technology
NTNU
7491 Trondheim
Norway
Cell: +47 92 203 205

http://www.partikkelaudio.com/
http://soundcloud.com/brandtsegg
http://flyndresang.no/