[Csnd-dev] can we still link dynamically to third party libs on Windows?

Date	2016-05-09 19:23
From	Rory Walsh
Subject	[Csnd-dev] can we still link dynamically to third party libs on Windows?
	Is there a way to link dynamically to libsndfile and such using the new msys2 build system? I'm having an issue with my Csound build for Unity. The builds I do with my old mingw64 system seem to run Ok, but the new msys2 build crashes Unity as soon as I start my game. I thought the first thing to do would be to disable all features and build with dynamic linking as this is how my old mingw64 build worked. It's not an easy one to debug and the C# compiler won't give me any info about the dll it's calling using invoke.

Date	2016-05-09 23:12
From	Michael Gogins
Subject	Re: [Csnd-dev] can we still link dynamically to third party libs on Windows?
	I think it does support dynamic linking. Regards, Mike ----------------------------------------------------- Michael Gogins Irreducible Productions http://michaelgogins.tumblr.com Michael dot Gogins at gmail dot com On Mon, May 9, 2016 at 2:23 PM, Rory Walsh wrote: > Is there a way to link dynamically to libsndfile and such using the new > msys2 build system? I'm having an issue with my Csound build for Unity. The > builds I do with my old mingw64 system seem to run Ok, but the new msys2 > build crashes Unity as soon as I start my game. I thought the first thing to > do would be to disable all features and build with dynamic linking as this > is how my old mingw64 build worked. It's not an easy one to debug and the C#

Date	2016-05-09 23:47
From	Rory Walsh
Subject	Re: [Csnd-dev] can we still link dynamically to third party libs on Windows?
	Thanks Mike. The next question is how? Should I select the .dll.a libs instead of the .a ones? Sorry, I'm not very au fait with how this is done.. On 9 May 2016 at 23:12, Michael Gogins <michael.gogins@gmail.com> wrote: I think it does support dynamic linking. Regards, Mike ----------------------------------------------------- Michael Gogins Irreducible Productions http://michaelgogins.tumblr.com Michael dot Gogins at gmail dot com On Mon, May 9, 2016 at 2:23 PM, Rory Walsh <rorywalsh@ear.ie> wrote: > Is there a way to link dynamically to libsndfile and such using the new > msys2 build system? I'm having an issue with my Csound build for Unity. The > builds I do with my old mingw64 system seem to run Ok, but the new msys2 > build crashes Unity as soon as I start my game. I thought the first thing to > do would be to disable all features and build with dynamic linking as this > is how my old mingw64 build worked. It's not an easy one to debug and the C# > compiler won't give me any info about the dll it's calling using invoke.

Date	2016-05-10 00:01
From	Michael Gogins
Subject	Re: [Csnd-dev] can we still link dynamically to third party libs on Windows?
	Yes. ----------------------------------------------------- Michael Gogins Irreducible Productions http://michaelgogins.tumblr.com Michael dot Gogins at gmail dot com On Mon, May 9, 2016 at 6:47 PM, Rory Walsh wrote: > Thanks Mike. The next question is how? Should I select the .dll.a libs > instead of the .a ones? Sorry, I'm not very au fait with how this is done.. > > On 9 May 2016 at 23:12, Michael Gogins wrote: >> >> I think it does support dynamic linking. >> >> Regards, >> Mike >> >> ----------------------------------------------------- >> Michael Gogins >> Irreducible Productions >> http://michaelgogins.tumblr.com >> Michael dot Gogins at gmail dot com >> >> >> On Mon, May 9, 2016 at 2:23 PM, Rory Walsh wrote: >> > Is there a way to link dynamically to libsndfile and such using the new >> > msys2 build system? I'm having an issue with my Csound build for Unity. >> > The >> > builds I do with my old mingw64 system seem to run Ok, but the new msys2 >> > build crashes Unity as soon as I start my game. I thought the first >> > thing to >> > do would be to disable all features and build with dynamic linking as >> > this >> > is how my old mingw64 build worked. It's not an easy one to debug and >> > the C# >> > compiler won't give me any info about the dll it's calling using invoke. >