Myself and Oeyvind have been trying to track down an issue he and some
other users are having with Cabbage on some versions of
Windows/Ableton Live. For me and lots of users everything works fine,
but for some users the Cabbage plugins are not seen at all. Note the
similarity here to issues arising with the csound~. Anyhow, we created
a bare bones mingw plugin(no Csound) and found we had the same
problems, UNTIL I started to linking statically to the pthread library
(perhaps Windows/Live is somehow flagging the pthread dll as
malicious?). As soon as I start linking to Csound however the problem
returns because, as far as I can tell, Csound is dynamically linked to
this library. Is there a way to set up cmake so that on Windows Csound
links statically with this library? I've no experience whatsoever at
tweaking cmake build settings. Don't even know where to start, but
would love to see if this resolves the problem.

------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

I just took a look at Mike's latest Windows installer and he doesn't
include libpthread, so I might take a go at linking against his build
and see how it goes.

On 28 August 2014 12:04, Rory Walsh  wrote:
> Myself and Oeyvind have been trying to track down an issue he and some
> other users are having with Cabbage on some versions of
> Windows/Ableton Live. For me and lots of users everything works fine,
> but for some users the Cabbage plugins are not seen at all. Note the
> similarity here to issues arising with the csound~. Anyhow, we created
> a bare bones mingw plugin(no Csound) and found we had the same
> problems, UNTIL I started to linking statically to the pthread library
> (perhaps Windows/Live is somehow flagging the pthread dll as
> malicious?). As soon as I start linking to Csound however the problem
> returns because, as far as I can tell, Csound is dynamically linked to
> this library. Is there a way to set up cmake so that on Windows Csound
> links statically with this library? I've no experience whatsoever at
> tweaking cmake build settings. Don't even know where to start, but
> would love to see if this resolves the problem.

------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

I was mistaken. It's there in the bin directory. So back to the first
question, can I statically link Csound to pthread?

On 28 August 2014 13:34, Rory Walsh  wrote:
> I just took a look at Mike's latest Windows installer and he doesn't
> include libpthread, so I might take a go at linking against his build
> and see how it goes.
>
> On 28 August 2014 12:04, Rory Walsh  wrote:
>> Myself and Oeyvind have been trying to track down an issue he and some
>> other users are having with Cabbage on some versions of
>> Windows/Ableton Live. For me and lots of users everything works fine,
>> but for some users the Cabbage plugins are not seen at all. Note the
>> similarity here to issues arising with the csound~. Anyhow, we created
>> a bare bones mingw plugin(no Csound) and found we had the same
>> problems, UNTIL I started to linking statically to the pthread library
>> (perhaps Windows/Live is somehow flagging the pthread dll as
>> malicious?). As soon as I start linking to Csound however the problem
>> returns because, as far as I can tell, Csound is dynamically linked to
>> this library. Is there a way to set up cmake so that on Windows Csound
>> links statically with this library? I've no experience whatsoever at
>> tweaking cmake build settings. Don't even know where to start, but
>> would love to see if this resolves the problem.

------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

You can try a couple of things:

1. Modify your CMakeCache.txt or use cmake-gui to edit the value for
PTHREAD_LIBRARY.  Have it point to a .a instead of whatever DLL it
finds.

2. If that doesn't work, you can modify csound's top-level
CMakeCache.txt and look for the lines:

find_library(PTHREAD_LIBRARY pthread)

if(NOT PTHREAD_LIBRARY AND WIN32)
    find_library(PTHREAD_LIBRARY pthreadGC2)
endif()

and change that to something like:

find_library(PTHREAD_LIBRARY pthread.a)


On Thu, Aug 28, 2014 at 8:23 AM, Rory Walsh  wrote:
> I was mistaken. It's there in the bin directory. So back to the first
> question, can I statically link Csound to pthread?
>
> On 28 August 2014 13:34, Rory Walsh  wrote:
>> I just took a look at Mike's latest Windows installer and he doesn't
>> include libpthread, so I might take a go at linking against his build
>> and see how it goes.
>>
>> On 28 August 2014 12:04, Rory Walsh  wrote:
>>> Myself and Oeyvind have been trying to track down an issue he and some
>>> other users are having with Cabbage on some versions of
>>> Windows/Ableton Live. For me and lots of users everything works fine,
>>> but for some users the Cabbage plugins are not seen at all. Note the
>>> similarity here to issues arising with the csound~. Anyhow, we created
>>> a bare bones mingw plugin(no Csound) and found we had the same
>>> problems, UNTIL I started to linking statically to the pthread library
>>> (perhaps Windows/Live is somehow flagging the pthread dll as
>>> malicious?). As soon as I start linking to Csound however the problem
>>> returns because, as far as I can tell, Csound is dynamically linked to
>>> this library. Is there a way to set up cmake so that on Windows Csound
>>> links statically with this library? I've no experience whatsoever at
>>> tweaking cmake build settings. Don't even know where to start, but
>>> would love to see if this resolves the problem.
>
> ------------------------------------------------------------------------------
> Slashdot TV.
> Video for Nerds.  Stuff that matters.
> http://tv.slashdot.org/
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Hi Steven. These were the first things I tried. Everything continues
to build Ok, but when I run Csound from the command line I keep
getting 'error, libwinpthread-1.dll cannot be found'. My CMakeList.txt
bits look like this:

find_library(PTHREAD_LIBRARY pthread.a)

if(NOT PTHREAD_LIBRARY AND WIN32)
    find_library(PTHREAD_LIBRARY pthread.a)
endif()

if(NOT PTHREAD_LIBRARY AND NOT EMSCRIPTEN)
    message(FATAL_ERROR "Csound requires the pthread library")
endif()

set(CMAKE_REQUIRED_INCLUDES pthread.h)
set(CMAKE_REQUIRED_LIBRARIES pthread.a)

And the cache file looks like this:

//Path to a library.
PTHREAD_LIBRARY:FILEPATH=C:/Users/RoryWalsh/Documents/SourceCode/pthreads/Pre-built/lib/libpthread.a

Any further ideas?


On 28 August 2014 14:33, Steven Yi  wrote:
> You can try a couple of things:
>
> 1. Modify your CMakeCache.txt or use cmake-gui to edit the value for
> PTHREAD_LIBRARY.  Have it point to a .a instead of whatever DLL it
> finds.
>
> 2. If that doesn't work, you can modify csound's top-level
> CMakeCache.txt and look for the lines:
>
> find_library(PTHREAD_LIBRARY pthread)
>
> if(NOT PTHREAD_LIBRARY AND WIN32)
>     find_library(PTHREAD_LIBRARY pthreadGC2)
> endif()
>
> and change that to something like:
>
> find_library(PTHREAD_LIBRARY pthread.a)
>
>
> On Thu, Aug 28, 2014 at 8:23 AM, Rory Walsh  wrote:
>> I was mistaken. It's there in the bin directory. So back to the first
>> question, can I statically link Csound to pthread?
>>
>> On 28 August 2014 13:34, Rory Walsh  wrote:
>>> I just took a look at Mike's latest Windows installer and he doesn't
>>> include libpthread, so I might take a go at linking against his build
>>> and see how it goes.
>>>
>>> On 28 August 2014 12:04, Rory Walsh  wrote:
>>>> Myself and Oeyvind have been trying to track down an issue he and some
>>>> other users are having with Cabbage on some versions of
>>>> Windows/Ableton Live. For me and lots of users everything works fine,
>>>> but for some users the Cabbage plugins are not seen at all. Note the
>>>> similarity here to issues arising with the csound~. Anyhow, we created
>>>> a bare bones mingw plugin(no Csound) and found we had the same
>>>> problems, UNTIL I started to linking statically to the pthread library
>>>> (perhaps Windows/Live is somehow flagging the pthread dll as
>>>> malicious?). As soon as I start linking to Csound however the problem
>>>> returns because, as far as I can tell, Csound is dynamically linked to
>>>> this library. Is there a way to set up cmake so that on Windows Csound
>>>> links statically with this library? I've no experience whatsoever at
>>>> tweaking cmake build settings. Don't even know where to start, but
>>>> would love to see if this resolves the problem.
>>
>> ------------------------------------------------------------------------------
>> Slashdot TV.
>> Video for Nerds.  Stuff that matters.
>> http://tv.slashdot.org/
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
> ------------------------------------------------------------------------------
> Slashdot TV.
> Video for Nerds.  Stuff that matters.
> http://tv.slashdot.org/
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

I'd check that you don't have a libcsound64.dll somewhere in your PATH
that the csound.exe you just built is linking to instead of the one
you built.  Use dependency walker to see exactly what library you're
linking to.

On Thu, Aug 28, 2014 at 9:04 AM, Rory Walsh  wrote:
> Hi Steven. These were the first things I tried. Everything continues
> to build Ok, but when I run Csound from the command line I keep
> getting 'error, libwinpthread-1.dll cannot be found'. My CMakeList.txt
> bits look like this:
>
> find_library(PTHREAD_LIBRARY pthread.a)
>
> if(NOT PTHREAD_LIBRARY AND WIN32)
>     find_library(PTHREAD_LIBRARY pthread.a)
> endif()
>
> if(NOT PTHREAD_LIBRARY AND NOT EMSCRIPTEN)
>     message(FATAL_ERROR "Csound requires the pthread library")
> endif()
>
> set(CMAKE_REQUIRED_INCLUDES pthread.h)
> set(CMAKE_REQUIRED_LIBRARIES pthread.a)
>
> And the cache file looks like this:
>
> //Path to a library.
> PTHREAD_LIBRARY:FILEPATH=C:/Users/RoryWalsh/Documents/SourceCode/pthreads/Pre-built/lib/libpthread.a
>
> Any further ideas?
>
>
> On 28 August 2014 14:33, Steven Yi  wrote:
>> You can try a couple of things:
>>
>> 1. Modify your CMakeCache.txt or use cmake-gui to edit the value for
>> PTHREAD_LIBRARY.  Have it point to a .a instead of whatever DLL it
>> finds.
>>
>> 2. If that doesn't work, you can modify csound's top-level
>> CMakeCache.txt and look for the lines:
>>
>> find_library(PTHREAD_LIBRARY pthread)
>>
>> if(NOT PTHREAD_LIBRARY AND WIN32)
>>     find_library(PTHREAD_LIBRARY pthreadGC2)
>> endif()
>>
>> and change that to something like:
>>
>> find_library(PTHREAD_LIBRARY pthread.a)
>>
>>
>> On Thu, Aug 28, 2014 at 8:23 AM, Rory Walsh  wrote:
>>> I was mistaken. It's there in the bin directory. So back to the first
>>> question, can I statically link Csound to pthread?
>>>
>>> On 28 August 2014 13:34, Rory Walsh  wrote:
>>>> I just took a look at Mike's latest Windows installer and he doesn't
>>>> include libpthread, so I might take a go at linking against his build
>>>> and see how it goes.
>>>>
>>>> On 28 August 2014 12:04, Rory Walsh  wrote:
>>>>> Myself and Oeyvind have been trying to track down an issue he and some
>>>>> other users are having with Cabbage on some versions of
>>>>> Windows/Ableton Live. For me and lots of users everything works fine,
>>>>> but for some users the Cabbage plugins are not seen at all. Note the
>>>>> similarity here to issues arising with the csound~. Anyhow, we created
>>>>> a bare bones mingw plugin(no Csound) and found we had the same
>>>>> problems, UNTIL I started to linking statically to the pthread library
>>>>> (perhaps Windows/Live is somehow flagging the pthread dll as
>>>>> malicious?). As soon as I start linking to Csound however the problem
>>>>> returns because, as far as I can tell, Csound is dynamically linked to
>>>>> this library. Is there a way to set up cmake so that on Windows Csound
>>>>> links statically with this library? I've no experience whatsoever at
>>>>> tweaking cmake build settings. Don't even know where to start, but
>>>>> would love to see if this resolves the problem.
>>>
>>> ------------------------------------------------------------------------------
>>> Slashdot TV.
>>> Video for Nerds.  Stuff that matters.
>>> http://tv.slashdot.org/
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>> ------------------------------------------------------------------------------
>> Slashdot TV.
>> Video for Nerds.  Stuff that matters.
>> http://tv.slashdot.org/
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
> ------------------------------------------------------------------------------
> Slashdot TV.
> Video for Nerds.  Stuff that matters.
> http://tv.slashdot.org/
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

So it turns out that csound64.dll calls LIBGCC_S_DW2-1.DLL which then
calls libwinpthread. I use the compile time flag '-static-libgcc' to
statically link to libgcc? Any ideas how I do this in cmake?

On 28 August 2014 15:09, Steven Yi  wrote:
> I'd check that you don't have a libcsound64.dll somewhere in your PATH
> that the csound.exe you just built is linking to instead of the one
> you built.  Use dependency walker to see exactly what library you're
> linking to.
>
> On Thu, Aug 28, 2014 at 9:04 AM, Rory Walsh  wrote:
>> Hi Steven. These were the first things I tried. Everything continues
>> to build Ok, but when I run Csound from the command line I keep
>> getting 'error, libwinpthread-1.dll cannot be found'. My CMakeList.txt
>> bits look like this:
>>
>> find_library(PTHREAD_LIBRARY pthread.a)
>>
>> if(NOT PTHREAD_LIBRARY AND WIN32)
>>     find_library(PTHREAD_LIBRARY pthread.a)
>> endif()
>>
>> if(NOT PTHREAD_LIBRARY AND NOT EMSCRIPTEN)
>>     message(FATAL_ERROR "Csound requires the pthread library")
>> endif()
>>
>> set(CMAKE_REQUIRED_INCLUDES pthread.h)
>> set(CMAKE_REQUIRED_LIBRARIES pthread.a)
>>
>> And the cache file looks like this:
>>
>> //Path to a library.
>> PTHREAD_LIBRARY:FILEPATH=C:/Users/RoryWalsh/Documents/SourceCode/pthreads/Pre-built/lib/libpthread.a
>>
>> Any further ideas?
>>
>>
>> On 28 August 2014 14:33, Steven Yi  wrote:
>>> You can try a couple of things:
>>>
>>> 1. Modify your CMakeCache.txt or use cmake-gui to edit the value for
>>> PTHREAD_LIBRARY.  Have it point to a .a instead of whatever DLL it
>>> finds.
>>>
>>> 2. If that doesn't work, you can modify csound's top-level
>>> CMakeCache.txt and look for the lines:
>>>
>>> find_library(PTHREAD_LIBRARY pthread)
>>>
>>> if(NOT PTHREAD_LIBRARY AND WIN32)
>>>     find_library(PTHREAD_LIBRARY pthreadGC2)
>>> endif()
>>>
>>> and change that to something like:
>>>
>>> find_library(PTHREAD_LIBRARY pthread.a)
>>>
>>>
>>> On Thu, Aug 28, 2014 at 8:23 AM, Rory Walsh  wrote:
>>>> I was mistaken. It's there in the bin directory. So back to the first
>>>> question, can I statically link Csound to pthread?
>>>>
>>>> On 28 August 2014 13:34, Rory Walsh  wrote:
>>>>> I just took a look at Mike's latest Windows installer and he doesn't
>>>>> include libpthread, so I might take a go at linking against his build
>>>>> and see how it goes.
>>>>>
>>>>> On 28 August 2014 12:04, Rory Walsh  wrote:
>>>>>> Myself and Oeyvind have been trying to track down an issue he and some
>>>>>> other users are having with Cabbage on some versions of
>>>>>> Windows/Ableton Live. For me and lots of users everything works fine,
>>>>>> but for some users the Cabbage plugins are not seen at all. Note the
>>>>>> similarity here to issues arising with the csound~. Anyhow, we created
>>>>>> a bare bones mingw plugin(no Csound) and found we had the same
>>>>>> problems, UNTIL I started to linking statically to the pthread library
>>>>>> (perhaps Windows/Live is somehow flagging the pthread dll as
>>>>>> malicious?). As soon as I start linking to Csound however the problem
>>>>>> returns because, as far as I can tell, Csound is dynamically linked to
>>>>>> this library. Is there a way to set up cmake so that on Windows Csound
>>>>>> links statically with this library? I've no experience whatsoever at
>>>>>> tweaking cmake build settings. Don't even know where to start, but
>>>>>> would love to see if this resolves the problem.
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Slashdot TV.
>>>> Video for Nerds.  Stuff that matters.
>>>> http://tv.slashdot.org/
>>>> _______________________________________________
>>>> Csound-devel mailing list
>>>> Csound-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>> ------------------------------------------------------------------------------
>>> Slashdot TV.
>>> Video for Nerds.  Stuff that matters.
>>> http://tv.slashdot.org/
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>> ------------------------------------------------------------------------------
>> Slashdot TV.
>> Video for Nerds.  Stuff that matters.
>> http://tv.slashdot.org/
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
> ------------------------------------------------------------------------------
> Slashdot TV.
> Video for Nerds.  Stuff that matters.
> http://tv.slashdot.org/
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

I'm just trying with the following modifications to cmakelists.txt:

if(NOT MSVC)
set(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} -mstackrealign -static-libgcc")
set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -mstackrealign -static-libgcc")
endif()

I'll let you know.

On 28 August 2014 16:02, Rory Walsh  wrote:
> So it turns out that csound64.dll calls LIBGCC_S_DW2-1.DLL which then
> calls libwinpthread. I use the compile time flag '-static-libgcc' to
> statically link to libgcc? Any ideas how I do this in cmake?
>
> On 28 August 2014 15:09, Steven Yi  wrote:
>> I'd check that you don't have a libcsound64.dll somewhere in your PATH
>> that the csound.exe you just built is linking to instead of the one
>> you built.  Use dependency walker to see exactly what library you're
>> linking to.
>>
>> On Thu, Aug 28, 2014 at 9:04 AM, Rory Walsh  wrote:
>>> Hi Steven. These were the first things I tried. Everything continues
>>> to build Ok, but when I run Csound from the command line I keep
>>> getting 'error, libwinpthread-1.dll cannot be found'. My CMakeList.txt
>>> bits look like this:
>>>
>>> find_library(PTHREAD_LIBRARY pthread.a)
>>>
>>> if(NOT PTHREAD_LIBRARY AND WIN32)
>>>     find_library(PTHREAD_LIBRARY pthread.a)
>>> endif()
>>>
>>> if(NOT PTHREAD_LIBRARY AND NOT EMSCRIPTEN)
>>>     message(FATAL_ERROR "Csound requires the pthread library")
>>> endif()
>>>
>>> set(CMAKE_REQUIRED_INCLUDES pthread.h)
>>> set(CMAKE_REQUIRED_LIBRARIES pthread.a)
>>>
>>> And the cache file looks like this:
>>>
>>> //Path to a library.
>>> PTHREAD_LIBRARY:FILEPATH=C:/Users/RoryWalsh/Documents/SourceCode/pthreads/Pre-built/lib/libpthread.a
>>>
>>> Any further ideas?
>>>
>>>
>>> On 28 August 2014 14:33, Steven Yi  wrote:
>>>> You can try a couple of things:
>>>>
>>>> 1. Modify your CMakeCache.txt or use cmake-gui to edit the value for
>>>> PTHREAD_LIBRARY.  Have it point to a .a instead of whatever DLL it
>>>> finds.
>>>>
>>>> 2. If that doesn't work, you can modify csound's top-level
>>>> CMakeCache.txt and look for the lines:
>>>>
>>>> find_library(PTHREAD_LIBRARY pthread)
>>>>
>>>> if(NOT PTHREAD_LIBRARY AND WIN32)
>>>>     find_library(PTHREAD_LIBRARY pthreadGC2)
>>>> endif()
>>>>
>>>> and change that to something like:
>>>>
>>>> find_library(PTHREAD_LIBRARY pthread.a)
>>>>
>>>>
>>>> On Thu, Aug 28, 2014 at 8:23 AM, Rory Walsh  wrote:
>>>>> I was mistaken. It's there in the bin directory. So back to the first
>>>>> question, can I statically link Csound to pthread?
>>>>>
>>>>> On 28 August 2014 13:34, Rory Walsh  wrote:
>>>>>> I just took a look at Mike's latest Windows installer and he doesn't
>>>>>> include libpthread, so I might take a go at linking against his build
>>>>>> and see how it goes.
>>>>>>
>>>>>> On 28 August 2014 12:04, Rory Walsh  wrote:
>>>>>>> Myself and Oeyvind have been trying to track down an issue he and some
>>>>>>> other users are having with Cabbage on some versions of
>>>>>>> Windows/Ableton Live. For me and lots of users everything works fine,
>>>>>>> but for some users the Cabbage plugins are not seen at all. Note the
>>>>>>> similarity here to issues arising with the csound~. Anyhow, we created
>>>>>>> a bare bones mingw plugin(no Csound) and found we had the same
>>>>>>> problems, UNTIL I started to linking statically to the pthread library
>>>>>>> (perhaps Windows/Live is somehow flagging the pthread dll as
>>>>>>> malicious?). As soon as I start linking to Csound however the problem
>>>>>>> returns because, as far as I can tell, Csound is dynamically linked to
>>>>>>> this library. Is there a way to set up cmake so that on Windows Csound
>>>>>>> links statically with this library? I've no experience whatsoever at
>>>>>>> tweaking cmake build settings. Don't even know where to start, but
>>>>>>> would love to see if this resolves the problem.
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> Slashdot TV.
>>>>> Video for Nerds.  Stuff that matters.
>>>>> http://tv.slashdot.org/
>>>>> _______________________________________________
>>>>> Csound-devel mailing list
>>>>> Csound-devel@lists.sourceforge.net
>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Slashdot TV.
>>>> Video for Nerds.  Stuff that matters.
>>>> http://tv.slashdot.org/
>>>> _______________________________________________
>>>> Csound-devel mailing list
>>>> Csound-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>> ------------------------------------------------------------------------------
>>> Slashdot TV.
>>> Video for Nerds.  Stuff that matters.
>>> http://tv.slashdot.org/
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>> ------------------------------------------------------------------------------
>> Slashdot TV.
>> Video for Nerds.  Stuff that matters.
>> http://tv.slashdot.org/
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel

------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Yes, I recently added static-libgcc to the csound~ windows build.
Maybe it is something we should maybe look at doing for the entire
windows build. I have this in
csound/frontends/max_csound_tilde/CMakLists.txt:

  set_target_properties(${MAX_OUTPUT_LIB}
      PROPERTIES LINK_FLAGS "-static-libstdc++ -static-libgcc")

You can add something similar in the main CMakeLists.txt for the
CSOUND_LIB target.  You could also try something like:

set(CMAKE_SHARED_LINKER_FLAGS "${CMAKE_SHARED_LINKER_FLAGS}
-static-libstdc++ -static-libgcc")

On Thu, Aug 28, 2014 at 10:02 AM, Rory Walsh  wrote:
> So it turns out that csound64.dll calls LIBGCC_S_DW2-1.DLL which then
> calls libwinpthread. I use the compile time flag '-static-libgcc' to
> statically link to libgcc? Any ideas how I do this in cmake?
>
> On 28 August 2014 15:09, Steven Yi  wrote:
>> I'd check that you don't have a libcsound64.dll somewhere in your PATH
>> that the csound.exe you just built is linking to instead of the one
>> you built.  Use dependency walker to see exactly what library you're
>> linking to.
>>
>> On Thu, Aug 28, 2014 at 9:04 AM, Rory Walsh  wrote:
>>> Hi Steven. These were the first things I tried. Everything continues
>>> to build Ok, but when I run Csound from the command line I keep
>>> getting 'error, libwinpthread-1.dll cannot be found'. My CMakeList.txt
>>> bits look like this:
>>>
>>> find_library(PTHREAD_LIBRARY pthread.a)
>>>
>>> if(NOT PTHREAD_LIBRARY AND WIN32)
>>>     find_library(PTHREAD_LIBRARY pthread.a)
>>> endif()
>>>
>>> if(NOT PTHREAD_LIBRARY AND NOT EMSCRIPTEN)
>>>     message(FATAL_ERROR "Csound requires the pthread library")
>>> endif()
>>>
>>> set(CMAKE_REQUIRED_INCLUDES pthread.h)
>>> set(CMAKE_REQUIRED_LIBRARIES pthread.a)
>>>
>>> And the cache file looks like this:
>>>
>>> //Path to a library.
>>> PTHREAD_LIBRARY:FILEPATH=C:/Users/RoryWalsh/Documents/SourceCode/pthreads/Pre-built/lib/libpthread.a
>>>
>>> Any further ideas?
>>>
>>>
>>> On 28 August 2014 14:33, Steven Yi  wrote:
>>>> You can try a couple of things:
>>>>
>>>> 1. Modify your CMakeCache.txt or use cmake-gui to edit the value for
>>>> PTHREAD_LIBRARY.  Have it point to a .a instead of whatever DLL it
>>>> finds.
>>>>
>>>> 2. If that doesn't work, you can modify csound's top-level
>>>> CMakeCache.txt and look for the lines:
>>>>
>>>> find_library(PTHREAD_LIBRARY pthread)
>>>>
>>>> if(NOT PTHREAD_LIBRARY AND WIN32)
>>>>     find_library(PTHREAD_LIBRARY pthreadGC2)
>>>> endif()
>>>>
>>>> and change that to something like:
>>>>
>>>> find_library(PTHREAD_LIBRARY pthread.a)
>>>>
>>>>
>>>> On Thu, Aug 28, 2014 at 8:23 AM, Rory Walsh  wrote:
>>>>> I was mistaken. It's there in the bin directory. So back to the first
>>>>> question, can I statically link Csound to pthread?
>>>>>
>>>>> On 28 August 2014 13:34, Rory Walsh  wrote:
>>>>>> I just took a look at Mike's latest Windows installer and he doesn't
>>>>>> include libpthread, so I might take a go at linking against his build
>>>>>> and see how it goes.
>>>>>>
>>>>>> On 28 August 2014 12:04, Rory Walsh  wrote:
>>>>>>> Myself and Oeyvind have been trying to track down an issue he and some
>>>>>>> other users are having with Cabbage on some versions of
>>>>>>> Windows/Ableton Live. For me and lots of users everything works fine,
>>>>>>> but for some users the Cabbage plugins are not seen at all. Note the
>>>>>>> similarity here to issues arising with the csound~. Anyhow, we created
>>>>>>> a bare bones mingw plugin(no Csound) and found we had the same
>>>>>>> problems, UNTIL I started to linking statically to the pthread library
>>>>>>> (perhaps Windows/Live is somehow flagging the pthread dll as
>>>>>>> malicious?). As soon as I start linking to Csound however the problem
>>>>>>> returns because, as far as I can tell, Csound is dynamically linked to
>>>>>>> this library. Is there a way to set up cmake so that on Windows Csound
>>>>>>> links statically with this library? I've no experience whatsoever at
>>>>>>> tweaking cmake build settings. Don't even know where to start, but
>>>>>>> would love to see if this resolves the problem.
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> Slashdot TV.
>>>>> Video for Nerds.  Stuff that matters.
>>>>> http://tv.slashdot.org/
>>>>> _______________________________________________
>>>>> Csound-devel mailing list
>>>>> Csound-devel@lists.sourceforge.net
>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Slashdot TV.
>>>> Video for Nerds.  Stuff that matters.
>>>> http://tv.slashdot.org/
>>>> _______________________________________________
>>>> Csound-devel mailing list
>>>> Csound-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>> ------------------------------------------------------------------------------
>>> Slashdot TV.
>>> Video for Nerds.  Stuff that matters.
>>> http://tv.slashdot.org/
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>> ------------------------------------------------------------------------------
>> Slashdot TV.
>> Video for Nerds.  Stuff that matters.
>> http://tv.slashdot.org/
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
> ------------------------------------------------------------------------------
> Slashdot TV.
> Video for Nerds.  Stuff that matters.
> http://tv.slashdot.org/
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Thanks, I'll try that now.

On 28 August 2014 16:12, Steven Yi  wrote:
> Yes, I recently added static-libgcc to the csound~ windows build.
> Maybe it is something we should maybe look at doing for the entire
> windows build. I have this in
> csound/frontends/max_csound_tilde/CMakLists.txt:
>
>   set_target_properties(${MAX_OUTPUT_LIB}
>       PROPERTIES LINK_FLAGS "-static-libstdc++ -static-libgcc")
>
> You can add something similar in the main CMakeLists.txt for the
> CSOUND_LIB target.  You could also try something like:
>
> set(CMAKE_SHARED_LINKER_FLAGS "${CMAKE_SHARED_LINKER_FLAGS}
> -static-libstdc++ -static-libgcc")
>
> On Thu, Aug 28, 2014 at 10:02 AM, Rory Walsh  wrote:
>> So it turns out that csound64.dll calls LIBGCC_S_DW2-1.DLL which then
>> calls libwinpthread. I use the compile time flag '-static-libgcc' to
>> statically link to libgcc? Any ideas how I do this in cmake?
>>
>> On 28 August 2014 15:09, Steven Yi  wrote:
>>> I'd check that you don't have a libcsound64.dll somewhere in your PATH
>>> that the csound.exe you just built is linking to instead of the one
>>> you built.  Use dependency walker to see exactly what library you're
>>> linking to.
>>>
>>> On Thu, Aug 28, 2014 at 9:04 AM, Rory Walsh  wrote:
>>>> Hi Steven. These were the first things I tried. Everything continues
>>>> to build Ok, but when I run Csound from the command line I keep
>>>> getting 'error, libwinpthread-1.dll cannot be found'. My CMakeList.txt
>>>> bits look like this:
>>>>
>>>> find_library(PTHREAD_LIBRARY pthread.a)
>>>>
>>>> if(NOT PTHREAD_LIBRARY AND WIN32)
>>>>     find_library(PTHREAD_LIBRARY pthread.a)
>>>> endif()
>>>>
>>>> if(NOT PTHREAD_LIBRARY AND NOT EMSCRIPTEN)
>>>>     message(FATAL_ERROR "Csound requires the pthread library")
>>>> endif()
>>>>
>>>> set(CMAKE_REQUIRED_INCLUDES pthread.h)
>>>> set(CMAKE_REQUIRED_LIBRARIES pthread.a)
>>>>
>>>> And the cache file looks like this:
>>>>
>>>> //Path to a library.
>>>> PTHREAD_LIBRARY:FILEPATH=C:/Users/RoryWalsh/Documents/SourceCode/pthreads/Pre-built/lib/libpthread.a
>>>>
>>>> Any further ideas?
>>>>
>>>>
>>>> On 28 August 2014 14:33, Steven Yi  wrote:
>>>>> You can try a couple of things:
>>>>>
>>>>> 1. Modify your CMakeCache.txt or use cmake-gui to edit the value for
>>>>> PTHREAD_LIBRARY.  Have it point to a .a instead of whatever DLL it
>>>>> finds.
>>>>>
>>>>> 2. If that doesn't work, you can modify csound's top-level
>>>>> CMakeCache.txt and look for the lines:
>>>>>
>>>>> find_library(PTHREAD_LIBRARY pthread)
>>>>>
>>>>> if(NOT PTHREAD_LIBRARY AND WIN32)
>>>>>     find_library(PTHREAD_LIBRARY pthreadGC2)
>>>>> endif()
>>>>>
>>>>> and change that to something like:
>>>>>
>>>>> find_library(PTHREAD_LIBRARY pthread.a)
>>>>>
>>>>>
>>>>> On Thu, Aug 28, 2014 at 8:23 AM, Rory Walsh  wrote:
>>>>>> I was mistaken. It's there in the bin directory. So back to the first
>>>>>> question, can I statically link Csound to pthread?
>>>>>>
>>>>>> On 28 August 2014 13:34, Rory Walsh  wrote:
>>>>>>> I just took a look at Mike's latest Windows installer and he doesn't
>>>>>>> include libpthread, so I might take a go at linking against his build
>>>>>>> and see how it goes.
>>>>>>>
>>>>>>> On 28 August 2014 12:04, Rory Walsh  wrote:
>>>>>>>> Myself and Oeyvind have been trying to track down an issue he and some
>>>>>>>> other users are having with Cabbage on some versions of
>>>>>>>> Windows/Ableton Live. For me and lots of users everything works fine,
>>>>>>>> but for some users the Cabbage plugins are not seen at all. Note the
>>>>>>>> similarity here to issues arising with the csound~. Anyhow, we created
>>>>>>>> a bare bones mingw plugin(no Csound) and found we had the same
>>>>>>>> problems, UNTIL I started to linking statically to the pthread library
>>>>>>>> (perhaps Windows/Live is somehow flagging the pthread dll as
>>>>>>>> malicious?). As soon as I start linking to Csound however the problem
>>>>>>>> returns because, as far as I can tell, Csound is dynamically linked to
>>>>>>>> this library. Is there a way to set up cmake so that on Windows Csound
>>>>>>>> links statically with this library? I've no experience whatsoever at
>>>>>>>> tweaking cmake build settings. Don't even know where to start, but
>>>>>>>> would love to see if this resolves the problem.
>>>>>>
>>>>>> ------------------------------------------------------------------------------
>>>>>> Slashdot TV.
>>>>>> Video for Nerds.  Stuff that matters.
>>>>>> http://tv.slashdot.org/
>>>>>> _______________________________________________
>>>>>> Csound-devel mailing list
>>>>>> Csound-devel@lists.sourceforge.net
>>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> Slashdot TV.
>>>>> Video for Nerds.  Stuff that matters.
>>>>> http://tv.slashdot.org/
>>>>> _______________________________________________
>>>>> Csound-devel mailing list
>>>>> Csound-devel@lists.sourceforge.net
>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Slashdot TV.
>>>> Video for Nerds.  Stuff that matters.
>>>> http://tv.slashdot.org/
>>>> _______________________________________________
>>>> Csound-devel mailing list
>>>> Csound-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>> ------------------------------------------------------------------------------
>>> Slashdot TV.
>>> Video for Nerds.  Stuff that matters.
>>> http://tv.slashdot.org/
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>> ------------------------------------------------------------------------------
>> Slashdot TV.
>> Video for Nerds.  Stuff that matters.
>> http://tv.slashdot.org/
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
> ------------------------------------------------------------------------------
> Slashdot TV.
> Video for Nerds.  Stuff that matters.
> http://tv.slashdot.org/
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

That got rid of the gcc dep, but Csound is still trying to find a
pthread library on startup. I don't get it. I'm specifically passing
pthread's .a files to cmake settings. I've tried each of the .a files
contained in the pthread lib dir, but each time I launch Csound in dep
walker it complains that PTHREADGCE2.DLL cannot be found. Arrghhhh.

On 28 August 2014 16:15, Rory Walsh  wrote:
> Thanks, I'll try that now.
>
> On 28 August 2014 16:12, Steven Yi  wrote:
>> Yes, I recently added static-libgcc to the csound~ windows build.
>> Maybe it is something we should maybe look at doing for the entire
>> windows build. I have this in
>> csound/frontends/max_csound_tilde/CMakLists.txt:
>>
>>   set_target_properties(${MAX_OUTPUT_LIB}
>>       PROPERTIES LINK_FLAGS "-static-libstdc++ -static-libgcc")
>>
>> You can add something similar in the main CMakeLists.txt for the
>> CSOUND_LIB target.  You could also try something like:
>>
>> set(CMAKE_SHARED_LINKER_FLAGS "${CMAKE_SHARED_LINKER_FLAGS}
>> -static-libstdc++ -static-libgcc")
>>
>> On Thu, Aug 28, 2014 at 10:02 AM, Rory Walsh  wrote:
>>> So it turns out that csound64.dll calls LIBGCC_S_DW2-1.DLL which then
>>> calls libwinpthread. I use the compile time flag '-static-libgcc' to
>>> statically link to libgcc? Any ideas how I do this in cmake?
>>>
>>> On 28 August 2014 15:09, Steven Yi  wrote:
>>>> I'd check that you don't have a libcsound64.dll somewhere in your PATH
>>>> that the csound.exe you just built is linking to instead of the one
>>>> you built.  Use dependency walker to see exactly what library you're
>>>> linking to.
>>>>
>>>> On Thu, Aug 28, 2014 at 9:04 AM, Rory Walsh  wrote:
>>>>> Hi Steven. These were the first things I tried. Everything continues
>>>>> to build Ok, but when I run Csound from the command line I keep
>>>>> getting 'error, libwinpthread-1.dll cannot be found'. My CMakeList.txt
>>>>> bits look like this:
>>>>>
>>>>> find_library(PTHREAD_LIBRARY pthread.a)
>>>>>
>>>>> if(NOT PTHREAD_LIBRARY AND WIN32)
>>>>>     find_library(PTHREAD_LIBRARY pthread.a)
>>>>> endif()
>>>>>
>>>>> if(NOT PTHREAD_LIBRARY AND NOT EMSCRIPTEN)
>>>>>     message(FATAL_ERROR "Csound requires the pthread library")
>>>>> endif()
>>>>>
>>>>> set(CMAKE_REQUIRED_INCLUDES pthread.h)
>>>>> set(CMAKE_REQUIRED_LIBRARIES pthread.a)
>>>>>
>>>>> And the cache file looks like this:
>>>>>
>>>>> //Path to a library.
>>>>> PTHREAD_LIBRARY:FILEPATH=C:/Users/RoryWalsh/Documents/SourceCode/pthreads/Pre-built/lib/libpthread.a
>>>>>
>>>>> Any further ideas?
>>>>>
>>>>>
>>>>> On 28 August 2014 14:33, Steven Yi  wrote:
>>>>>> You can try a couple of things:
>>>>>>
>>>>>> 1. Modify your CMakeCache.txt or use cmake-gui to edit the value for
>>>>>> PTHREAD_LIBRARY.  Have it point to a .a instead of whatever DLL it
>>>>>> finds.
>>>>>>
>>>>>> 2. If that doesn't work, you can modify csound's top-level
>>>>>> CMakeCache.txt and look for the lines:
>>>>>>
>>>>>> find_library(PTHREAD_LIBRARY pthread)
>>>>>>
>>>>>> if(NOT PTHREAD_LIBRARY AND WIN32)
>>>>>>     find_library(PTHREAD_LIBRARY pthreadGC2)
>>>>>> endif()
>>>>>>
>>>>>> and change that to something like:
>>>>>>
>>>>>> find_library(PTHREAD_LIBRARY pthread.a)
>>>>>>
>>>>>>
>>>>>> On Thu, Aug 28, 2014 at 8:23 AM, Rory Walsh  wrote:
>>>>>>> I was mistaken. It's there in the bin directory. So back to the first
>>>>>>> question, can I statically link Csound to pthread?
>>>>>>>
>>>>>>> On 28 August 2014 13:34, Rory Walsh  wrote:
>>>>>>>> I just took a look at Mike's latest Windows installer and he doesn't
>>>>>>>> include libpthread, so I might take a go at linking against his build
>>>>>>>> and see how it goes.
>>>>>>>>
>>>>>>>> On 28 August 2014 12:04, Rory Walsh  wrote:
>>>>>>>>> Myself and Oeyvind have been trying to track down an issue he and some
>>>>>>>>> other users are having with Cabbage on some versions of
>>>>>>>>> Windows/Ableton Live. For me and lots of users everything works fine,
>>>>>>>>> but for some users the Cabbage plugins are not seen at all. Note the
>>>>>>>>> similarity here to issues arising with the csound~. Anyhow, we created
>>>>>>>>> a bare bones mingw plugin(no Csound) and found we had the same
>>>>>>>>> problems, UNTIL I started to linking statically to the pthread library
>>>>>>>>> (perhaps Windows/Live is somehow flagging the pthread dll as
>>>>>>>>> malicious?). As soon as I start linking to Csound however the problem
>>>>>>>>> returns because, as far as I can tell, Csound is dynamically linked to
>>>>>>>>> this library. Is there a way to set up cmake so that on Windows Csound
>>>>>>>>> links statically with this library? I've no experience whatsoever at
>>>>>>>>> tweaking cmake build settings. Don't even know where to start, but
>>>>>>>>> would love to see if this resolves the problem.
>>>>>>>
>>>>>>> ------------------------------------------------------------------------------
>>>>>>> Slashdot TV.
>>>>>>> Video for Nerds.  Stuff that matters.
>>>>>>> http://tv.slashdot.org/
>>>>>>> _______________________________________________
>>>>>>> Csound-devel mailing list
>>>>>>> Csound-devel@lists.sourceforge.net
>>>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>>
>>>>>> ------------------------------------------------------------------------------
>>>>>> Slashdot TV.
>>>>>> Video for Nerds.  Stuff that matters.
>>>>>> http://tv.slashdot.org/
>>>>>> _______________________________________________
>>>>>> Csound-devel mailing list
>>>>>> Csound-devel@lists.sourceforge.net
>>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> Slashdot TV.
>>>>> Video for Nerds.  Stuff that matters.
>>>>> http://tv.slashdot.org/
>>>>> _______________________________________________
>>>>> Csound-devel mailing list
>>>>> Csound-devel@lists.sourceforge.net
>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Slashdot TV.
>>>> Video for Nerds.  Stuff that matters.
>>>> http://tv.slashdot.org/
>>>> _______________________________________________
>>>> Csound-devel mailing list
>>>> Csound-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>> ------------------------------------------------------------------------------
>>> Slashdot TV.
>>> Video for Nerds.  Stuff that matters.
>>> http://tv.slashdot.org/
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>> ------------------------------------------------------------------------------
>> Slashdot TV.
>> Video for Nerds.  Stuff that matters.
>> http://tv.slashdot.org/
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel

------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Are you positive the libcsound that csound.exe is linking to is the
one you just built and not another on the system?  (You should be able
to toggle full path in dep walker)

On Thu, Aug 28, 2014 at 11:26 AM, Rory Walsh  wrote:
> That got rid of the gcc dep, but Csound is still trying to find a
> pthread library on startup. I don't get it. I'm specifically passing
> pthread's .a files to cmake settings. I've tried each of the .a files
> contained in the pthread lib dir, but each time I launch Csound in dep
> walker it complains that PTHREADGCE2.DLL cannot be found. Arrghhhh.
>
> On 28 August 2014 16:15, Rory Walsh  wrote:
>> Thanks, I'll try that now.
>>
>> On 28 August 2014 16:12, Steven Yi  wrote:
>>> Yes, I recently added static-libgcc to the csound~ windows build.
>>> Maybe it is something we should maybe look at doing for the entire
>>> windows build. I have this in
>>> csound/frontends/max_csound_tilde/CMakLists.txt:
>>>
>>>   set_target_properties(${MAX_OUTPUT_LIB}
>>>       PROPERTIES LINK_FLAGS "-static-libstdc++ -static-libgcc")
>>>
>>> You can add something similar in the main CMakeLists.txt for the
>>> CSOUND_LIB target.  You could also try something like:
>>>
>>> set(CMAKE_SHARED_LINKER_FLAGS "${CMAKE_SHARED_LINKER_FLAGS}
>>> -static-libstdc++ -static-libgcc")
>>>
>>> On Thu, Aug 28, 2014 at 10:02 AM, Rory Walsh  wrote:
>>>> So it turns out that csound64.dll calls LIBGCC_S_DW2-1.DLL which then
>>>> calls libwinpthread. I use the compile time flag '-static-libgcc' to
>>>> statically link to libgcc? Any ideas how I do this in cmake?
>>>>
>>>> On 28 August 2014 15:09, Steven Yi  wrote:
>>>>> I'd check that you don't have a libcsound64.dll somewhere in your PATH
>>>>> that the csound.exe you just built is linking to instead of the one
>>>>> you built.  Use dependency walker to see exactly what library you're
>>>>> linking to.
>>>>>
>>>>> On Thu, Aug 28, 2014 at 9:04 AM, Rory Walsh  wrote:
>>>>>> Hi Steven. These were the first things I tried. Everything continues
>>>>>> to build Ok, but when I run Csound from the command line I keep
>>>>>> getting 'error, libwinpthread-1.dll cannot be found'. My CMakeList.txt
>>>>>> bits look like this:
>>>>>>
>>>>>> find_library(PTHREAD_LIBRARY pthread.a)
>>>>>>
>>>>>> if(NOT PTHREAD_LIBRARY AND WIN32)
>>>>>>     find_library(PTHREAD_LIBRARY pthread.a)
>>>>>> endif()
>>>>>>
>>>>>> if(NOT PTHREAD_LIBRARY AND NOT EMSCRIPTEN)
>>>>>>     message(FATAL_ERROR "Csound requires the pthread library")
>>>>>> endif()
>>>>>>
>>>>>> set(CMAKE_REQUIRED_INCLUDES pthread.h)
>>>>>> set(CMAKE_REQUIRED_LIBRARIES pthread.a)
>>>>>>
>>>>>> And the cache file looks like this:
>>>>>>
>>>>>> //Path to a library.
>>>>>> PTHREAD_LIBRARY:FILEPATH=C:/Users/RoryWalsh/Documents/SourceCode/pthreads/Pre-built/lib/libpthread.a
>>>>>>
>>>>>> Any further ideas?
>>>>>>
>>>>>>
>>>>>> On 28 August 2014 14:33, Steven Yi  wrote:
>>>>>>> You can try a couple of things:
>>>>>>>
>>>>>>> 1. Modify your CMakeCache.txt or use cmake-gui to edit the value for
>>>>>>> PTHREAD_LIBRARY.  Have it point to a .a instead of whatever DLL it
>>>>>>> finds.
>>>>>>>
>>>>>>> 2. If that doesn't work, you can modify csound's top-level
>>>>>>> CMakeCache.txt and look for the lines:
>>>>>>>
>>>>>>> find_library(PTHREAD_LIBRARY pthread)
>>>>>>>
>>>>>>> if(NOT PTHREAD_LIBRARY AND WIN32)
>>>>>>>     find_library(PTHREAD_LIBRARY pthreadGC2)
>>>>>>> endif()
>>>>>>>
>>>>>>> and change that to something like:
>>>>>>>
>>>>>>> find_library(PTHREAD_LIBRARY pthread.a)
>>>>>>>
>>>>>>>
>>>>>>> On Thu, Aug 28, 2014 at 8:23 AM, Rory Walsh  wrote:
>>>>>>>> I was mistaken. It's there in the bin directory. So back to the first
>>>>>>>> question, can I statically link Csound to pthread?
>>>>>>>>
>>>>>>>> On 28 August 2014 13:34, Rory Walsh  wrote:
>>>>>>>>> I just took a look at Mike's latest Windows installer and he doesn't
>>>>>>>>> include libpthread, so I might take a go at linking against his build
>>>>>>>>> and see how it goes.
>>>>>>>>>
>>>>>>>>> On 28 August 2014 12:04, Rory Walsh  wrote:
>>>>>>>>>> Myself and Oeyvind have been trying to track down an issue he and some
>>>>>>>>>> other users are having with Cabbage on some versions of
>>>>>>>>>> Windows/Ableton Live. For me and lots of users everything works fine,
>>>>>>>>>> but for some users the Cabbage plugins are not seen at all. Note the
>>>>>>>>>> similarity here to issues arising with the csound~. Anyhow, we created
>>>>>>>>>> a bare bones mingw plugin(no Csound) and found we had the same
>>>>>>>>>> problems, UNTIL I started to linking statically to the pthread library
>>>>>>>>>> (perhaps Windows/Live is somehow flagging the pthread dll as
>>>>>>>>>> malicious?). As soon as I start linking to Csound however the problem
>>>>>>>>>> returns because, as far as I can tell, Csound is dynamically linked to
>>>>>>>>>> this library. Is there a way to set up cmake so that on Windows Csound
>>>>>>>>>> links statically with this library? I've no experience whatsoever at
>>>>>>>>>> tweaking cmake build settings. Don't even know where to start, but
>>>>>>>>>> would love to see if this resolves the problem.
>>>>>>>>
>>>>>>>> ------------------------------------------------------------------------------
>>>>>>>> Slashdot TV.
>>>>>>>> Video for Nerds.  Stuff that matters.
>>>>>>>> http://tv.slashdot.org/
>>>>>>>> _______________________________________________
>>>>>>>> Csound-devel mailing list
>>>>>>>> Csound-devel@lists.sourceforge.net
>>>>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>>>
>>>>>>> ------------------------------------------------------------------------------
>>>>>>> Slashdot TV.
>>>>>>> Video for Nerds.  Stuff that matters.
>>>>>>> http://tv.slashdot.org/
>>>>>>> _______________________________________________
>>>>>>> Csound-devel mailing list
>>>>>>> Csound-devel@lists.sourceforge.net
>>>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>>
>>>>>> ------------------------------------------------------------------------------
>>>>>> Slashdot TV.
>>>>>> Video for Nerds.  Stuff that matters.
>>>>>> http://tv.slashdot.org/
>>>>>> _______________________________________________
>>>>>> Csound-devel mailing list
>>>>>> Csound-devel@lists.sourceforge.net
>>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> Slashdot TV.
>>>>> Video for Nerds.  Stuff that matters.
>>>>> http://tv.slashdot.org/
>>>>> _______________________________________________
>>>>> Csound-devel mailing list
>>>>> Csound-devel@lists.sourceforge.net
>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Slashdot TV.
>>>> Video for Nerds.  Stuff that matters.
>>>> http://tv.slashdot.org/
>>>> _______________________________________________
>>>> Csound-devel mailing list
>>>> Csound-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>> ------------------------------------------------------------------------------
>>> Slashdot TV.
>>> Video for Nerds.  Stuff that matters.
>>> http://tv.slashdot.org/
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
> ------------------------------------------------------------------------------
> Slashdot TV.
> Video for Nerds.  Stuff that matters.
> http://tv.slashdot.org/
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

I'm sure. Attached is a screenshot. Also attached are my cmake files
too in case perhaps you can spot something wrong there? I'm stumped.
Oddly enough it looks for pthreadGCE2.dll whether I link to pthread.a
or  pthreadGCE2.a.

On 28 August 2014 17:39, Steven Yi  wrote:
> Are you positive the libcsound that csound.exe is linking to is the
> one you just built and not another on the system?  (You should be able
> to toggle full path in dep walker)
>
> On Thu, Aug 28, 2014 at 11:26 AM, Rory Walsh  wrote:
>> That got rid of the gcc dep, but Csound is still trying to find a
>> pthread library on startup. I don't get it. I'm specifically passing
>> pthread's .a files to cmake settings. I've tried each of the .a files
>> contained in the pthread lib dir, but each time I launch Csound in dep
>> walker it complains that PTHREADGCE2.DLL cannot be found. Arrghhhh.
>>
>> On 28 August 2014 16:15, Rory Walsh  wrote:
>>> Thanks, I'll try that now.
>>>
>>> On 28 August 2014 16:12, Steven Yi  wrote:
>>>> Yes, I recently added static-libgcc to the csound~ windows build.
>>>> Maybe it is something we should maybe look at doing for the entire
>>>> windows build. I have this in
>>>> csound/frontends/max_csound_tilde/CMakLists.txt:
>>>>
>>>>   set_target_properties(${MAX_OUTPUT_LIB}
>>>>       PROPERTIES LINK_FLAGS "-static-libstdc++ -static-libgcc")
>>>>
>>>> You can add something similar in the main CMakeLists.txt for the
>>>> CSOUND_LIB target.  You could also try something like:
>>>>
>>>> set(CMAKE_SHARED_LINKER_FLAGS "${CMAKE_SHARED_LINKER_FLAGS}
>>>> -static-libstdc++ -static-libgcc")
>>>>
>>>> On Thu, Aug 28, 2014 at 10:02 AM, Rory Walsh  wrote:
>>>>> So it turns out that csound64.dll calls LIBGCC_S_DW2-1.DLL which then
>>>>> calls libwinpthread. I use the compile time flag '-static-libgcc' to
>>>>> statically link to libgcc? Any ideas how I do this in cmake?
>>>>>
>>>>> On 28 August 2014 15:09, Steven Yi  wrote:
>>>>>> I'd check that you don't have a libcsound64.dll somewhere in your PATH
>>>>>> that the csound.exe you just built is linking to instead of the one
>>>>>> you built.  Use dependency walker to see exactly what library you're
>>>>>> linking to.
>>>>>>
>>>>>> On Thu, Aug 28, 2014 at 9:04 AM, Rory Walsh  wrote:
>>>>>>> Hi Steven. These were the first things I tried. Everything continues
>>>>>>> to build Ok, but when I run Csound from the command line I keep
>>>>>>> getting 'error, libwinpthread-1.dll cannot be found'. My CMakeList.txt
>>>>>>> bits look like this:
>>>>>>>
>>>>>>> find_library(PTHREAD_LIBRARY pthread.a)
>>>>>>>
>>>>>>> if(NOT PTHREAD_LIBRARY AND WIN32)
>>>>>>>     find_library(PTHREAD_LIBRARY pthread.a)
>>>>>>> endif()
>>>>>>>
>>>>>>> if(NOT PTHREAD_LIBRARY AND NOT EMSCRIPTEN)
>>>>>>>     message(FATAL_ERROR "Csound requires the pthread library")
>>>>>>> endif()
>>>>>>>
>>>>>>> set(CMAKE_REQUIRED_INCLUDES pthread.h)
>>>>>>> set(CMAKE_REQUIRED_LIBRARIES pthread.a)
>>>>>>>
>>>>>>> And the cache file looks like this:
>>>>>>>
>>>>>>> //Path to a library.
>>>>>>> PTHREAD_LIBRARY:FILEPATH=C:/Users/RoryWalsh/Documents/SourceCode/pthreads/Pre-built/lib/libpthread.a
>>>>>>>
>>>>>>> Any further ideas?
>>>>>>>
>>>>>>>
>>>>>>> On 28 August 2014 14:33, Steven Yi  wrote:
>>>>>>>> You can try a couple of things:
>>>>>>>>
>>>>>>>> 1. Modify your CMakeCache.txt or use cmake-gui to edit the value for
>>>>>>>> PTHREAD_LIBRARY.  Have it point to a .a instead of whatever DLL it
>>>>>>>> finds.
>>>>>>>>
>>>>>>>> 2. If that doesn't work, you can modify csound's top-level
>>>>>>>> CMakeCache.txt and look for the lines:
>>>>>>>>
>>>>>>>> find_library(PTHREAD_LIBRARY pthread)
>>>>>>>>
>>>>>>>> if(NOT PTHREAD_LIBRARY AND WIN32)
>>>>>>>>     find_library(PTHREAD_LIBRARY pthreadGC2)
>>>>>>>> endif()
>>>>>>>>
>>>>>>>> and change that to something like:
>>>>>>>>
>>>>>>>> find_library(PTHREAD_LIBRARY pthread.a)
>>>>>>>>
>>>>>>>>
>>>>>>>> On Thu, Aug 28, 2014 at 8:23 AM, Rory Walsh  wrote:
>>>>>>>>> I was mistaken. It's there in the bin directory. So back to the first
>>>>>>>>> question, can I statically link Csound to pthread?
>>>>>>>>>
>>>>>>>>> On 28 August 2014 13:34, Rory Walsh  wrote:
>>>>>>>>>> I just took a look at Mike's latest Windows installer and he doesn't
>>>>>>>>>> include libpthread, so I might take a go at linking against his build
>>>>>>>>>> and see how it goes.
>>>>>>>>>>
>>>>>>>>>> On 28 August 2014 12:04, Rory Walsh  wrote:
>>>>>>>>>>> Myself and Oeyvind have been trying to track down an issue he and some
>>>>>>>>>>> other users are having with Cabbage on some versions of
>>>>>>>>>>> Windows/Ableton Live. For me and lots of users everything works fine,
>>>>>>>>>>> but for some users the Cabbage plugins are not seen at all. Note the
>>>>>>>>>>> similarity here to issues arising with the csound~. Anyhow, we created
>>>>>>>>>>> a bare bones mingw plugin(no Csound) and found we had the same
>>>>>>>>>>> problems, UNTIL I started to linking statically to the pthread library
>>>>>>>>>>> (perhaps Windows/Live is somehow flagging the pthread dll as
>>>>>>>>>>> malicious?). As soon as I start linking to Csound however the problem
>>>>>>>>>>> returns because, as far as I can tell, Csound is dynamically linked to
>>>>>>>>>>> this library. Is there a way to set up cmake so that on Windows Csound
>>>>>>>>>>> links statically with this library? I've no experience whatsoever at
>>>>>>>>>>> tweaking cmake build settings. Don't even know where to start, but
>>>>>>>>>>> would love to see if this resolves the problem.
>>>>>>>>>
>>>>>>>>> ------------------------------------------------------------------------------
>>>>>>>>> Slashdot TV.
>>>>>>>>> Video for Nerds.  Stuff that matters.
>>>>>>>>> http://tv.slashdot.org/
>>>>>>>>> _______________________________________________
>>>>>>>>> Csound-devel mailing list
>>>>>>>>> Csound-devel@lists.sourceforge.net
>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>>>>
>>>>>>>> ------------------------------------------------------------------------------
>>>>>>>> Slashdot TV.
>>>>>>>> Video for Nerds.  Stuff that matters.
>>>>>>>> http://tv.slashdot.org/
>>>>>>>> _______________________________________________
>>>>>>>> Csound-devel mailing list
>>>>>>>> Csound-devel@lists.sourceforge.net
>>>>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>>>
>>>>>>> ------------------------------------------------------------------------------
>>>>>>> Slashdot TV.
>>>>>>> Video for Nerds.  Stuff that matters.
>>>>>>> http://tv.slashdot.org/
>>>>>>> _______________________________________________
>>>>>>> Csound-devel mailing list
>>>>>>> Csound-devel@lists.sourceforge.net
>>>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>>
>>>>>> ------------------------------------------------------------------------------
>>>>>> Slashdot TV.
>>>>>> Video for Nerds.  Stuff that matters.
>>>>>> http://tv.slashdot.org/
>>>>>> _______________________________________________
>>>>>> Csound-devel mailing list
>>>>>> Csound-devel@lists.sourceforge.net
>>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> Slashdot TV.
>>>>> Video for Nerds.  Stuff that matters.
>>>>> http://tv.slashdot.org/
>>>>> _______________________________________________
>>>>> Csound-devel mailing list
>>>>> Csound-devel@lists.sourceforge.net
>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Slashdot TV.
>>>> Video for Nerds.  Stuff that matters.
>>>> http://tv.slashdot.org/
>>>> _______________________________________________
>>>> Csound-devel mailing list
>>>> Csound-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>> ------------------------------------------------------------------------------
>> Slashdot TV.
>> Video for Nerds.  Stuff that matters.
>> http://tv.slashdot.org/
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
> ------------------------------------------------------------------------------
> Slashdot TV.
> Video for Nerds.  Stuff that matters.
> http://tv.slashdot.org/
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

It looks like ws2_32.dll is what has the dependency on
pthreadGCE2.dll, no?  It's in the list of required dll's in
csound/CMakeLists.txt.  Maybe try removing that and seeing what
happens?  (I'll assume a compile failure but could give it a try.)

On Thu, Aug 28, 2014 at 1:13 PM, Rory Walsh  wrote:
> I'm sure. Attached is a screenshot. Also attached are my cmake files
> too in case perhaps you can spot something wrong there? I'm stumped.
> Oddly enough it looks for pthreadGCE2.dll whether I link to pthread.a
> or  pthreadGCE2.a.
>
> On 28 August 2014 17:39, Steven Yi  wrote:
>> Are you positive the libcsound that csound.exe is linking to is the
>> one you just built and not another on the system?  (You should be able
>> to toggle full path in dep walker)
>>
>> On Thu, Aug 28, 2014 at 11:26 AM, Rory Walsh  wrote:
>>> That got rid of the gcc dep, but Csound is still trying to find a
>>> pthread library on startup. I don't get it. I'm specifically passing
>>> pthread's .a files to cmake settings. I've tried each of the .a files
>>> contained in the pthread lib dir, but each time I launch Csound in dep
>>> walker it complains that PTHREADGCE2.DLL cannot be found. Arrghhhh.
>>>
>>> On 28 August 2014 16:15, Rory Walsh  wrote:
>>>> Thanks, I'll try that now.
>>>>
>>>> On 28 August 2014 16:12, Steven Yi  wrote:
>>>>> Yes, I recently added static-libgcc to the csound~ windows build.
>>>>> Maybe it is something we should maybe look at doing for the entire
>>>>> windows build. I have this in
>>>>> csound/frontends/max_csound_tilde/CMakLists.txt:
>>>>>
>>>>>   set_target_properties(${MAX_OUTPUT_LIB}
>>>>>       PROPERTIES LINK_FLAGS "-static-libstdc++ -static-libgcc")
>>>>>
>>>>> You can add something similar in the main CMakeLists.txt for the
>>>>> CSOUND_LIB target.  You could also try something like:
>>>>>
>>>>> set(CMAKE_SHARED_LINKER_FLAGS "${CMAKE_SHARED_LINKER_FLAGS}
>>>>> -static-libstdc++ -static-libgcc")
>>>>>
>>>>> On Thu, Aug 28, 2014 at 10:02 AM, Rory Walsh  wrote:
>>>>>> So it turns out that csound64.dll calls LIBGCC_S_DW2-1.DLL which then
>>>>>> calls libwinpthread. I use the compile time flag '-static-libgcc' to
>>>>>> statically link to libgcc? Any ideas how I do this in cmake?
>>>>>>
>>>>>> On 28 August 2014 15:09, Steven Yi  wrote:
>>>>>>> I'd check that you don't have a libcsound64.dll somewhere in your PATH
>>>>>>> that the csound.exe you just built is linking to instead of the one
>>>>>>> you built.  Use dependency walker to see exactly what library you're
>>>>>>> linking to.
>>>>>>>
>>>>>>> On Thu, Aug 28, 2014 at 9:04 AM, Rory Walsh  wrote:
>>>>>>>> Hi Steven. These were the first things I tried. Everything continues
>>>>>>>> to build Ok, but when I run Csound from the command line I keep
>>>>>>>> getting 'error, libwinpthread-1.dll cannot be found'. My CMakeList.txt
>>>>>>>> bits look like this:
>>>>>>>>
>>>>>>>> find_library(PTHREAD_LIBRARY pthread.a)
>>>>>>>>
>>>>>>>> if(NOT PTHREAD_LIBRARY AND WIN32)
>>>>>>>>     find_library(PTHREAD_LIBRARY pthread.a)
>>>>>>>> endif()
>>>>>>>>
>>>>>>>> if(NOT PTHREAD_LIBRARY AND NOT EMSCRIPTEN)
>>>>>>>>     message(FATAL_ERROR "Csound requires the pthread library")
>>>>>>>> endif()
>>>>>>>>
>>>>>>>> set(CMAKE_REQUIRED_INCLUDES pthread.h)
>>>>>>>> set(CMAKE_REQUIRED_LIBRARIES pthread.a)
>>>>>>>>
>>>>>>>> And the cache file looks like this:
>>>>>>>>
>>>>>>>> //Path to a library.
>>>>>>>> PTHREAD_LIBRARY:FILEPATH=C:/Users/RoryWalsh/Documents/SourceCode/pthreads/Pre-built/lib/libpthread.a
>>>>>>>>
>>>>>>>> Any further ideas?
>>>>>>>>
>>>>>>>>
>>>>>>>> On 28 August 2014 14:33, Steven Yi  wrote:
>>>>>>>>> You can try a couple of things:
>>>>>>>>>
>>>>>>>>> 1. Modify your CMakeCache.txt or use cmake-gui to edit the value for
>>>>>>>>> PTHREAD_LIBRARY.  Have it point to a .a instead of whatever DLL it
>>>>>>>>> finds.
>>>>>>>>>
>>>>>>>>> 2. If that doesn't work, you can modify csound's top-level
>>>>>>>>> CMakeCache.txt and look for the lines:
>>>>>>>>>
>>>>>>>>> find_library(PTHREAD_LIBRARY pthread)
>>>>>>>>>
>>>>>>>>> if(NOT PTHREAD_LIBRARY AND WIN32)
>>>>>>>>>     find_library(PTHREAD_LIBRARY pthreadGC2)
>>>>>>>>> endif()
>>>>>>>>>
>>>>>>>>> and change that to something like:
>>>>>>>>>
>>>>>>>>> find_library(PTHREAD_LIBRARY pthread.a)
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Thu, Aug 28, 2014 at 8:23 AM, Rory Walsh  wrote:
>>>>>>>>>> I was mistaken. It's there in the bin directory. So back to the first
>>>>>>>>>> question, can I statically link Csound to pthread?
>>>>>>>>>>
>>>>>>>>>> On 28 August 2014 13:34, Rory Walsh  wrote:
>>>>>>>>>>> I just took a look at Mike's latest Windows installer and he doesn't
>>>>>>>>>>> include libpthread, so I might take a go at linking against his build
>>>>>>>>>>> and see how it goes.
>>>>>>>>>>>
>>>>>>>>>>> On 28 August 2014 12:04, Rory Walsh  wrote:
>>>>>>>>>>>> Myself and Oeyvind have been trying to track down an issue he and some
>>>>>>>>>>>> other users are having with Cabbage on some versions of
>>>>>>>>>>>> Windows/Ableton Live. For me and lots of users everything works fine,
>>>>>>>>>>>> but for some users the Cabbage plugins are not seen at all. Note the
>>>>>>>>>>>> similarity here to issues arising with the csound~. Anyhow, we created
>>>>>>>>>>>> a bare bones mingw plugin(no Csound) and found we had the same
>>>>>>>>>>>> problems, UNTIL I started to linking statically to the pthread library
>>>>>>>>>>>> (perhaps Windows/Live is somehow flagging the pthread dll as
>>>>>>>>>>>> malicious?). As soon as I start linking to Csound however the problem
>>>>>>>>>>>> returns because, as far as I can tell, Csound is dynamically linked to
>>>>>>>>>>>> this library. Is there a way to set up cmake so that on Windows Csound
>>>>>>>>>>>> links statically with this library? I've no experience whatsoever at
>>>>>>>>>>>> tweaking cmake build settings. Don't even know where to start, but
>>>>>>>>>>>> would love to see if this resolves the problem.
>>>>>>>>>>
>>>>>>>>>> ------------------------------------------------------------------------------
>>>>>>>>>> Slashdot TV.
>>>>>>>>>> Video for Nerds.  Stuff that matters.
>>>>>>>>>> http://tv.slashdot.org/
>>>>>>>>>> _______________________________________________
>>>>>>>>>> Csound-devel mailing list
>>>>>>>>>> Csound-devel@lists.sourceforge.net
>>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>>>>>
>>>>>>>>> ------------------------------------------------------------------------------
>>>>>>>>> Slashdot TV.
>>>>>>>>> Video for Nerds.  Stuff that matters.
>>>>>>>>> http://tv.slashdot.org/
>>>>>>>>> _______________________________________________
>>>>>>>>> Csound-devel mailing list
>>>>>>>>> Csound-devel@lists.sourceforge.net
>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>>>>
>>>>>>>> ------------------------------------------------------------------------------
>>>>>>>> Slashdot TV.
>>>>>>>> Video for Nerds.  Stuff that matters.
>>>>>>>> http://tv.slashdot.org/
>>>>>>>> _______________________________________________
>>>>>>>> Csound-devel mailing list
>>>>>>>> Csound-devel@lists.sourceforge.net
>>>>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>>>
>>>>>>> ------------------------------------------------------------------------------
>>>>>>> Slashdot TV.
>>>>>>> Video for Nerds.  Stuff that matters.
>>>>>>> http://tv.slashdot.org/
>>>>>>> _______________________________________________
>>>>>>> Csound-devel mailing list
>>>>>>> Csound-devel@lists.sourceforge.net
>>>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>>
>>>>>> ------------------------------------------------------------------------------
>>>>>> Slashdot TV.
>>>>>> Video for Nerds.  Stuff that matters.
>>>>>> http://tv.slashdot.org/
>>>>>> _______________________________________________
>>>>>> Csound-devel mailing list
>>>>>> Csound-devel@lists.sourceforge.net
>>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> Slashdot TV.
>>>>> Video for Nerds.  Stuff that matters.
>>>>> http://tv.slashdot.org/
>>>>> _______________________________________________
>>>>> Csound-devel mailing list
>>>>> Csound-devel@lists.sourceforge.net
>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>> ------------------------------------------------------------------------------
>>> Slashdot TV.
>>> Video for Nerds.  Stuff that matters.
>>> http://tv.slashdot.org/
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>> ------------------------------------------------------------------------------
>> Slashdot TV.
>> Video for Nerds.  Stuff that matters.
>> http://tv.slashdot.org/
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
> ------------------------------------------------------------------------------
> Slashdot TV.
> Video for Nerds.  Stuff that matters.
> http://tv.slashdot.org/
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>

------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Thanks Steven I didn't notice that. I'll try tomorrow.

Looks like that particular dll has to do with winsock. Iäll see if I
can disable the building of any opcodes that use them. I fear Mike is
right. Once I start removing one Iäll need to remove another and so
on. It's worth a shot however.

On 28 August 2014 22:46, Rory Walsh  wrote:
> Thanks Steven I didn't notice that. I'll try tomorrow.
>
> On 28 Aug 2014 19:29, "Steven Yi"  wrote:
>>
>> It looks like ws2_32.dll is what has the dependency on
>> pthreadGCE2.dll, no?  It's in the list of required dll's in
>> csound/CMakeLists.txt.  Maybe try removing that and seeing what
>> happens?  (I'll assume a compile failure but could give it a try.)
>>
>> On Thu, Aug 28, 2014 at 1:13 PM, Rory Walsh  wrote:
>> > I'm sure. Attached is a screenshot. Also attached are my cmake files
>> > too in case perhaps you can spot something wrong there? I'm stumped.
>> > Oddly enough it looks for pthreadGCE2.dll whether I link to pthread.a
>> > or  pthreadGCE2.a.
>> >
>> > On 28 August 2014 17:39, Steven Yi  wrote:
>> >> Are you positive the libcsound that csound.exe is linking to is the
>> >> one you just built and not another on the system?  (You should be able
>> >> to toggle full path in dep walker)
>> >>
>> >> On Thu, Aug 28, 2014 at 11:26 AM, Rory Walsh  wrote:
>> >>> That got rid of the gcc dep, but Csound is still trying to find a
>> >>> pthread library on startup. I don't get it. I'm specifically passing
>> >>> pthread's .a files to cmake settings. I've tried each of the .a files
>> >>> contained in the pthread lib dir, but each time I launch Csound in dep
>> >>> walker it complains that PTHREADGCE2.DLL cannot be found. Arrghhhh.
>> >>>
>> >>> On 28 August 2014 16:15, Rory Walsh  wrote:
>> >>>> Thanks, I'll try that now.
>> >>>>
>> >>>> On 28 August 2014 16:12, Steven Yi  wrote:
>> >>>>> Yes, I recently added static-libgcc to the csound~ windows build.
>> >>>>> Maybe it is something we should maybe look at doing for the entire
>> >>>>> windows build. I have this in
>> >>>>> csound/frontends/max_csound_tilde/CMakLists.txt:
>> >>>>>
>> >>>>>   set_target_properties(${MAX_OUTPUT_LIB}
>> >>>>>       PROPERTIES LINK_FLAGS "-static-libstdc++ -static-libgcc")
>> >>>>>
>> >>>>> You can add something similar in the main CMakeLists.txt for the
>> >>>>> CSOUND_LIB target.  You could also try something like:
>> >>>>>
>> >>>>> set(CMAKE_SHARED_LINKER_FLAGS "${CMAKE_SHARED_LINKER_FLAGS}
>> >>>>> -static-libstdc++ -static-libgcc")
>> >>>>>
>> >>>>> On Thu, Aug 28, 2014 at 10:02 AM, Rory Walsh 
>> >>>>> wrote:
>> >>>>>> So it turns out that csound64.dll calls LIBGCC_S_DW2-1.DLL which
>> >>>>>> then
>> >>>>>> calls libwinpthread. I use the compile time flag '-static-libgcc'
>> >>>>>> to
>> >>>>>> statically link to libgcc? Any ideas how I do this in cmake?
>> >>>>>>
>> >>>>>> On 28 August 2014 15:09, Steven Yi  wrote:
>> >>>>>>> I'd check that you don't have a libcsound64.dll somewhere in your
>> >>>>>>> PATH
>> >>>>>>> that the csound.exe you just built is linking to instead of the
>> >>>>>>> one
>> >>>>>>> you built.  Use dependency walker to see exactly what library
>> >>>>>>> you're
>> >>>>>>> linking to.
>> >>>>>>>
>> >>>>>>> On Thu, Aug 28, 2014 at 9:04 AM, Rory Walsh 
>> >>>>>>> wrote:
>> >>>>>>>> Hi Steven. These were the first things I tried. Everything
>> >>>>>>>> continues
>> >>>>>>>> to build Ok, but when I run Csound from the command line I keep
>> >>>>>>>> getting 'error, libwinpthread-1.dll cannot be found'. My
>> >>>>>>>> CMakeList.txt
>> >>>>>>>> bits look like this:
>> >>>>>>>>
>> >>>>>>>> find_library(PTHREAD_LIBRARY pthread.a)
>> >>>>>>>>
>> >>>>>>>> if(NOT PTHREAD_LIBRARY AND WIN32)
>> >>>>>>>>     find_library(PTHREAD_LIBRARY pthread.a)
>> >>>>>>>> endif()
>> >>>>>>>>
>> >>>>>>>> if(NOT PTHREAD_LIBRARY AND NOT EMSCRIPTEN)
>> >>>>>>>>     message(FATAL_ERROR "Csound requires the pthread library")
>> >>>>>>>> endif()
>> >>>>>>>>
>> >>>>>>>> set(CMAKE_REQUIRED_INCLUDES pthread.h)
>> >>>>>>>> set(CMAKE_REQUIRED_LIBRARIES pthread.a)
>> >>>>>>>>
>> >>>>>>>> And the cache file looks like this:
>> >>>>>>>>
>> >>>>>>>> //Path to a library.
>> >>>>>>>>
>> >>>>>>>> PTHREAD_LIBRARY:FILEPATH=C:/Users/RoryWalsh/Documents/SourceCode/pthreads/Pre-built/lib/libpthread.a
>> >>>>>>>>
>> >>>>>>>> Any further ideas?
>> >>>>>>>>
>> >>>>>>>>
>> >>>>>>>> On 28 August 2014 14:33, Steven Yi  wrote:
>> >>>>>>>>> You can try a couple of things:
>> >>>>>>>>>
>> >>>>>>>>> 1. Modify your CMakeCache.txt or use cmake-gui to edit the value
>> >>>>>>>>> for
>> >>>>>>>>> PTHREAD_LIBRARY.  Have it point to a .a instead of whatever DLL
>> >>>>>>>>> it
>> >>>>>>>>> finds.
>> >>>>>>>>>
>> >>>>>>>>> 2. If that doesn't work, you can modify csound's top-level
>> >>>>>>>>> CMakeCache.txt and look for the lines:
>> >>>>>>>>>
>> >>>>>>>>> find_library(PTHREAD_LIBRARY pthread)
>> >>>>>>>>>
>> >>>>>>>>> if(NOT PTHREAD_LIBRARY AND WIN32)
>> >>>>>>>>>     find_library(PTHREAD_LIBRARY pthreadGC2)
>> >>>>>>>>> endif()
>> >>>>>>>>>
>> >>>>>>>>> and change that to something like:
>> >>>>>>>>>
>> >>>>>>>>> find_library(PTHREAD_LIBRARY pthread.a)
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>> On Thu, Aug 28, 2014 at 8:23 AM, Rory Walsh 
>> >>>>>>>>> wrote:
>> >>>>>>>>>> I was mistaken. It's there in the bin directory. So back to the
>> >>>>>>>>>> first
>> >>>>>>>>>> question, can I statically link Csound to pthread?
>> >>>>>>>>>>
>> >>>>>>>>>> On 28 August 2014 13:34, Rory Walsh  wrote:
>> >>>>>>>>>>> I just took a look at Mike's latest Windows installer and he
>> >>>>>>>>>>> doesn't
>> >>>>>>>>>>> include libpthread, so I might take a go at linking against
>> >>>>>>>>>>> his build
>> >>>>>>>>>>> and see how it goes.
>> >>>>>>>>>>>
>> >>>>>>>>>>> On 28 August 2014 12:04, Rory Walsh  wrote:
>> >>>>>>>>>>>> Myself and Oeyvind have been trying to track down an issue he
>> >>>>>>>>>>>> and some
>> >>>>>>>>>>>> other users are having with Cabbage on some versions of
>> >>>>>>>>>>>> Windows/Ableton Live. For me and lots of users everything
>> >>>>>>>>>>>> works fine,
>> >>>>>>>>>>>> but for some users the Cabbage plugins are not seen at all.
>> >>>>>>>>>>>> Note the
>> >>>>>>>>>>>> similarity here to issues arising with the csound~. Anyhow,
>> >>>>>>>>>>>> we created
>> >>>>>>>>>>>> a bare bones mingw plugin(no Csound) and found we had the
>> >>>>>>>>>>>> same
>> >>>>>>>>>>>> problems, UNTIL I started to linking statically to the
>> >>>>>>>>>>>> pthread library
>> >>>>>>>>>>>> (perhaps Windows/Live is somehow flagging the pthread dll as
>> >>>>>>>>>>>> malicious?). As soon as I start linking to Csound however the
>> >>>>>>>>>>>> problem
>> >>>>>>>>>>>> returns because, as far as I can tell, Csound is dynamically
>> >>>>>>>>>>>> linked to
>> >>>>>>>>>>>> this library. Is there a way to set up cmake so that on
>> >>>>>>>>>>>> Windows Csound
>> >>>>>>>>>>>> links statically with this library? I've no experience
>> >>>>>>>>>>>> whatsoever at
>> >>>>>>>>>>>> tweaking cmake build settings. Don't even know where to
>> >>>>>>>>>>>> start, but
>> >>>>>>>>>>>> would love to see if this resolves the problem.
>> >>>>>>>>>>
>> >>>>>>>>>>
>> >>>>>>>>>> ------------------------------------------------------------------------------
>> >>>>>>>>>> Slashdot TV.
>> >>>>>>>>>> Video for Nerds.  Stuff that matters.
>> >>>>>>>>>> http://tv.slashdot.org/
>> >>>>>>>>>> _______________________________________________
>> >>>>>>>>>> Csound-devel mailing list
>> >>>>>>>>>> Csound-devel@lists.sourceforge.net
>> >>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>> ------------------------------------------------------------------------------
>> >>>>>>>>> Slashdot TV.
>> >>>>>>>>> Video for Nerds.  Stuff that matters.
>> >>>>>>>>> http://tv.slashdot.org/
>> >>>>>>>>> _______________________________________________
>> >>>>>>>>> Csound-devel mailing list
>> >>>>>>>>> Csound-devel@lists.sourceforge.net
>> >>>>>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>> >>>>>>>>
>> >>>>>>>>
>> >>>>>>>> ------------------------------------------------------------------------------
>> >>>>>>>> Slashdot TV.
>> >>>>>>>> Video for Nerds.  Stuff that matters.
>> >>>>>>>> http://tv.slashdot.org/
>> >>>>>>>> _______________________________________________
>> >>>>>>>> Csound-devel mailing list
>> >>>>>>>> Csound-devel@lists.sourceforge.net
>> >>>>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>> >>>>>>>
>> >>>>>>>
>> >>>>>>> ------------------------------------------------------------------------------
>> >>>>>>> Slashdot TV.
>> >>>>>>> Video for Nerds.  Stuff that matters.
>> >>>>>>> http://tv.slashdot.org/
>> >>>>>>> _______________________________________________
>> >>>>>>> Csound-devel mailing list
>> >>>>>>> Csound-devel@lists.sourceforge.net
>> >>>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>> >>>>>>
>> >>>>>>
>> >>>>>> ------------------------------------------------------------------------------
>> >>>>>> Slashdot TV.
>> >>>>>> Video for Nerds.  Stuff that matters.
>> >>>>>> http://tv.slashdot.org/
>> >>>>>> _______________________________________________
>> >>>>>> Csound-devel mailing list
>> >>>>>> Csound-devel@lists.sourceforge.net
>> >>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>> >>>>>
>> >>>>>
>> >>>>> ------------------------------------------------------------------------------
>> >>>>> Slashdot TV.
>> >>>>> Video for Nerds.  Stuff that matters.
>> >>>>> http://tv.slashdot.org/
>> >>>>> _______________________________________________
>> >>>>> Csound-devel mailing list
>> >>>>> Csound-devel@lists.sourceforge.net
>> >>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>> >>>
>> >>>
>> >>> ------------------------------------------------------------------------------
>> >>> Slashdot TV.
>> >>> Video for Nerds.  Stuff that matters.
>> >>> http://tv.slashdot.org/
>> >>> _______________________________________________
>> >>> Csound-devel mailing list
>> >>> Csound-devel@lists.sourceforge.net
>> >>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>> >>
>> >>
>> >> ------------------------------------------------------------------------------
>> >> Slashdot TV.
>> >> Video for Nerds.  Stuff that matters.
>> >> http://tv.slashdot.org/
>> >> _______________________________________________
>> >> Csound-devel mailing list
>> >> Csound-devel@lists.sourceforge.net
>> >> https://lists.sourceforge.net/lists/listinfo/csound-devel
>> >
>> >
>> > ------------------------------------------------------------------------------
>> > Slashdot TV.
>> > Video for Nerds.  Stuff that matters.
>> > http://tv.slashdot.org/
>> > _______________________________________________
>> > Csound-devel mailing list
>> > Csound-devel@lists.sourceforge.net
>> > https://lists.sourceforge.net/lists/listinfo/csound-devel
>> >
>>
>>
>> ------------------------------------------------------------------------------
>> Slashdot TV.
>> Video for Nerds.  Stuff that matters.
>> http://tv.slashdot.org/
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel

------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/c

I think we are reading this wrong Steven. I can remove ws_2 without
any problems but the problem with pthreadGCE2.dll remains. I also
looked down the list at the other modules and if one module has a
dependency on another, then a connection is drawn under it and to the
next module. In this case(as far as I can tell) it's goes

csound64.dll->kernel32.dll
                     msvcrt.dll
                     user32.dll
                     ws_32.dll
                     pthreadGCE2.dll
                     libsndfile-1.dll

If I remove ws_32.dll I get:

csound64.dll->kernel32.dll
                     msvcrt.dll
                     user32.dll
                     pthreadGCE2.dll
                     libsndfile-1.dll

Also note that I actually link to ws_2.dll in my bare bones VST and it
does not have any dep on pthreadGCE2.dll, I'm thinking now that it
must be the build settings for csound64.dll?

------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Got it. I added the -static compiler flag and linked to the
libwinpthread-1.dll that ships with Mingw. That seems to have removed
the dep on pthread. Let's hope it resolves the other issue. I'll send
a package to Alfonsos to try with csound~ and see if that solves
anything there.

On 29 August 2014 10:35, Rory Walsh  wrote:
> I think we are reading this wrong Steven. I can remove ws_2 without
> any problems but the problem with pthreadGCE2.dll remains. I also
> looked down the list at the other modules and if one module has a
> dependency on another, then a connection is drawn under it and to the
> next module. In this case(as far as I can tell) it's goes
>
> csound64.dll->kernel32.dll
>                      msvcrt.dll
>                      user32.dll
>                      ws_32.dll
>                      pthreadGCE2.dll
>                      libsndfile-1.dll
>
> If I remove ws_32.dll I get:
>
> csound64.dll->kernel32.dll
>                      msvcrt.dll
>                      user32.dll
>                      pthreadGCE2.dll
>                      libsndfile-1.dll
>
> Also note that I actually link to ws_2.dll in my bare bones VST and it
> does not have any dep on pthreadGCE2.dll, I'm thinking now that it
> must be the build settings for csound64.dll?

------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

That's awesome, thanks!  Question: Does that end up linking statically
to csound too?  I'll also have to check about csound~ if it links to
pthread.

On Fri, Aug 29, 2014 at 5:21 AM, Rory Walsh  wrote:
> Got it. I added the -static compiler flag and linked to the
> libwinpthread-1.dll that ships with Mingw. That seems to have removed
> the dep on pthread. Let's hope it resolves the other issue. I'll send
> a package to Alfonsos to try with csound~ and see if that solves
> anything there.
>
> On 29 August 2014 10:35, Rory Walsh  wrote:
>> I think we are reading this wrong Steven. I can remove ws_2 without
>> any problems but the problem with pthreadGCE2.dll remains. I also
>> looked down the list at the other modules and if one module has a
>> dependency on another, then a connection is drawn under it and to the
>> next module. In this case(as far as I can tell) it's goes
>>
>> csound64.dll->kernel32.dll
>>                      msvcrt.dll
>>                      user32.dll
>>                      ws_32.dll
>>                      pthreadGCE2.dll
>>                      libsndfile-1.dll
>>
>> If I remove ws_32.dll I get:
>>
>> csound64.dll->kernel32.dll
>>                      msvcrt.dll
>>                      user32.dll
>>                      pthreadGCE2.dll
>>                      libsndfile-1.dll
>>
>> Also note that I actually link to ws_2.dll in my bare bones VST and it
>> does not have any dep on pthreadGCE2.dll, I'm thinking now that it
>> must be the build settings for csound64.dll?
>
> ------------------------------------------------------------------------------
> Slashdot TV.
> Video for Nerds.  Stuff that matters.
> http://tv.slashdot.org/
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

I think the -static flag will force mingw to use static libs whenever they are available. Just off a plane. I can check later about csound..

Dosn't look like Csound is statically linked by using this option. But
it does somehow get Oeyvind past Live's authorisation problem and he
can now use some of his Cabbage plugins again. The problem is he can
only use instruments that use a completely vanilla version of Csound,
i.e., csound64.dll and libsndfile-1. The next thing I would like to do
is build OSC without a dynamic link to pthread, but it looks like the
liblo-7.dll I have was built with a dynamic link to pthread. I can
have a good at building it myself I guess and then modifying the OSC
opcode build settings. Hmmm. This could take a while.

p.s. It hasn't seem to make any difference to the csound~ problem.

On 29 August 2014 16:04, Rory Walsh  wrote:
> I think the -static flag will force mingw to use static libs whenever they
> are available. Just off a plane. I can check later about csound..
>
> On 29 Aug 2014 14:04, "Steven Yi"  wrote:
>>
>> That's awesome, thanks!  Question: Does that end up linking statically
>> to csound too?  I'll also have to check about csound~ if it links to
>> pthread.
>>
>> On Fri, Aug 29, 2014 at 5:21 AM, Rory Walsh  wrote:
>> > Got it. I added the -static compiler flag and linked to the
>> > libwinpthread-1.dll that ships with Mingw. That seems to have removed
>> > the dep on pthread. Let's hope it resolves the other issue. I'll send
>> > a package to Alfonsos to try with csound~ and see if that solves
>> > anything there.
>> >
>> > On 29 August 2014 10:35, Rory Walsh  wrote:
>> >> I think we are reading this wrong Steven. I can remove ws_2 without
>> >> any problems but the problem with pthreadGCE2.dll remains. I also
>> >> looked down the list at the other modules and if one module has a
>> >> dependency on another, then a connection is drawn under it and to the
>> >> next module. In this case(as far as I can tell) it's goes
>> >>
>> >> csound64.dll->kernel32.dll
>> >>                      msvcrt.dll
>> >>                      user32.dll
>> >>                      ws_32.dll
>> >>                      pthreadGCE2.dll
>> >>                      libsndfile-1.dll
>> >>
>> >> If I remove ws_32.dll I get:
>> >>
>> >> csound64.dll->kernel32.dll
>> >>                      msvcrt.dll
>> >>                      user32.dll
>> >>                      pthreadGCE2.dll
>> >>                      libsndfile-1.dll
>> >>
>> >> Also note that I actually link to ws_2.dll in my bare bones VST and it
>> >> does not have any dep on pthreadGCE2.dll, I'm thinking now that it
>> >> must be the build settings for csound64.dll?
>> >
>> >
>> > ------------------------------------------------------------------------------
>> > Slashdot TV.
>> > Video for Nerds.  Stuff that matters.
>> > http://tv.slashdot.org/
>> > _______________________________________________
>> > Csound-devel mailing list
>> > Csound-devel@lists.sourceforge.net
>> > https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>>
>> ------------------------------------------------------------------------------
>> Slashdot TV.
>> Video for Nerds.  Stuff that matters.
>> http://tv.slashdot.org/
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel

------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Btw, if I drop y existing OSC.dll and liblo-7.dll into my plugin dir,
Cabbage, on startup, complains that libwinpthread is not found. But my
instrument doesn't use any OSC, So why is Csound trying to load this
plugin lib? The same goes for any plugins I drop into the plugin dir
that have not being statically linked to libwinpthread. I thought
these libs only get loaded if they are needed?

On 30 August 2014 11:28, Rory Walsh  wrote:
> Dosn't look like Csound is statically linked by using this option. But
> it does somehow get Oeyvind past Live's authorisation problem and he
> can now use some of his Cabbage plugins again. The problem is he can
> only use instruments that use a completely vanilla version of Csound,
> i.e., csound64.dll and libsndfile-1. The next thing I would like to do
> is build OSC without a dynamic link to pthread, but it looks like the
> liblo-7.dll I have was built with a dynamic link to pthread. I can
> have a good at building it myself I guess and then modifying the OSC
> opcode build settings. Hmmm. This could take a while.
>
> p.s. It hasn't seem to make any difference to the csound~ problem.
>
> On 29 August 2014 16:04, Rory Walsh  wrote:
>> I think the -static flag will force mingw to use static libs whenever they
>> are available. Just off a plane. I can check later about csound..
>>
>> On 29 Aug 2014 14:04, "Steven Yi"  wrote:
>>>
>>> That's awesome, thanks!  Question: Does that end up linking statically
>>> to csound too?  I'll also have to check about csound~ if it links to
>>> pthread.
>>>
>>> On Fri, Aug 29, 2014 at 5:21 AM, Rory Walsh  wrote:
>>> > Got it. I added the -static compiler flag and linked to the
>>> > libwinpthread-1.dll that ships with Mingw. That seems to have removed
>>> > the dep on pthread. Let's hope it resolves the other issue. I'll send
>>> > a package to Alfonsos to try with csound~ and see if that solves
>>> > anything there.
>>> >
>>> > On 29 August 2014 10:35, Rory Walsh  wrote:
>>> >> I think we are reading this wrong Steven. I can remove ws_2 without
>>> >> any problems but the problem with pthreadGCE2.dll remains. I also
>>> >> looked down the list at the other modules and if one module has a
>>> >> dependency on another, then a connection is drawn under it and to the
>>> >> next module. In this case(as far as I can tell) it's goes
>>> >>
>>> >> csound64.dll->kernel32.dll
>>> >>                      msvcrt.dll
>>> >>                      user32.dll
>>> >>                      ws_32.dll
>>> >>                      pthreadGCE2.dll
>>> >>                      libsndfile-1.dll
>>> >>
>>> >> If I remove ws_32.dll I get:
>>> >>
>>> >> csound64.dll->kernel32.dll
>>> >>                      msvcrt.dll
>>> >>                      user32.dll
>>> >>                      pthreadGCE2.dll
>>> >>                      libsndfile-1.dll
>>> >>
>>> >> Also note that I actually link to ws_2.dll in my bare bones VST and it
>>> >> does not have any dep on pthreadGCE2.dll, I'm thinking now that it
>>> >> must be the build settings for csound64.dll?
>>> >
>>> >
>>> > ------------------------------------------------------------------------------
>>> > Slashdot TV.
>>> > Video for Nerds.  Stuff that matters.
>>> > http://tv.slashdot.org/
>>> > _______________________________________________
>>> > Csound-devel mailing list
>>> > Csound-devel@lists.sourceforge.net
>>> > https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Slashdot TV.
>>> Video for Nerds.  Stuff that matters.
>>> http://tv.slashdot.org/
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel

------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Thanks John. I guess it makes no difference to this problem. I'm going
to have to start looking at removing the dynamic linking of pthread to
any number of plugin opcodes.

On 30 August 2014 12:15,   wrote:
>
> Quoting Rory Walsh :
>
>> I thought
>> these libs only get loaded if they are needed?
>
> Tha6t wa my original design, but other decided to load everything that
> could be found.
>
> ==John
>
>
>
>
> ------------------------------------------------------------------------------
> Slashdot TV.
> Video for Nerds.  Stuff that matters.
> http://tv.slashdot.org/
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net