I was hoping that Cabbage users could distribute plugins that will
work whether Csound is installed or not. Do you think dumping all the
necessary Csound source code into a Visual Studio project will
actually work? Sounds like a mighty task..


On 10 January 2013 12:38, michael.gogins@gmail.com
 wrote:
> Won't work.
>
> Put all the csound source.files you need into your msvc project. Don't
> bother with a library.
>
> Or if you anticipate more than one project, create your own msvc project for
> that.
>
> What exactly are you trying to make?
>
> T-Mobile. America’s First Nationwide 4G Network
>
>
> ----- Reply message -----
> From: "Rory Walsh" 
> To: 
> Subject: [Csnd] static link to Csound lib MSVC..
> Date: Thu, Jan 10, 2013 4:16 am
>
>
> I'm looking at statically linking to libcsound.a that ships with the
> windows package from MSVC. In the past I've always linking dynamically
> against the dll by creating an MSVC import lib from it and linking to
> that at runtime. I tried adding the libcsound.a file to the list of
> libraries to link to but I get error about it not being valid, or
> corrupted. I've never tried to do a static link to a MinGW library in
> MSVC before. Has anyone any suggestions? Mike?
>
>
> Send bugs reports to the Sourceforge bug tracker
>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"
>

Thanks Mike. So I'd need to add every thing in the following folders:

Engine
H
OOps
Opcodes

Does that look right?


 from I'll have to try this out on a sample project first and see how I get on!

On 10 January 2013 16:31, Michael Gogins  wrote:
> It is not a mighty task, but you will need to (a) define all the macros that
> are used when compiling Csound (including those just for MSVC compiling
> Csound, which would not be apparent from the existing build system) and (b)
> link also with any other libs Csound needs.
>
> It's the same things that need to be done whether to build an app this way
> or to build a library to be used to build an app.
>
>
> On Thu, Jan 10, 2013 at 6:57 AM, Rory Walsh  wrote:
>>
>> I was hoping that Cabbage users could distribute plugins that will
>> work whether Csound is installed or not. Do you think dumping all the
>> necessary Csound source code into a Visual Studio project will
>> actually work? Sounds like a mighty task..
>>
>>
>> On 10 January 2013 12:38, michael.gogins@gmail.com
>>  wrote:
>> > Won't work.
>> >
>> > Put all the csound source.files you need into your msvc project. Don't
>> > bother with a library.
>> >
>> > Or if you anticipate more than one project, create your own msvc project
>> > for
>> > that.
>> >
>> > What exactly are you trying to make?
>> >
>> > T-Mobile. America’s First Nationwide 4G Network
>> >
>> >
>> > ----- Reply message -----
>> > From: "Rory Walsh" 
>> > To: 
>> > Subject: [Csnd] static link to Csound lib MSVC..
>> > Date: Thu, Jan 10, 2013 4:16 am
>> >
>> >
>> > I'm looking at statically linking to libcsound.a that ships with the
>> > windows package from MSVC. In the past I've always linking dynamically
>> > against the dll by creating an MSVC import lib from it and linking to
>> > that at runtime. I tried adding the libcsound.a file to the list of
>> > libraries to link to but I get error about it not being valid, or
>> > corrupted. I've never tried to do a static link to a MinGW library in
>> > MSVC before. Has anyone any suggestions? Mike?
>> >
>> >
>> > Send bugs reports to the Sourceforge bug tracker
>> >            https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> > Discussions of bugs and features can be posted here
>> > To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> > csound"
>> >
>>
>>
>> Send bugs reports to the Sourceforge bug tracker
>>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>>
>
>
>
> --
> Michael Gogins
> Irreducible Productions
> http://www.michael-gogins.com
> Michael dot Gogins at gmail dot com

Hi Rory,

Couple ideas:

1. I know we had issues a while back building with CMake, but maybe
it's worth trying once again?  Should be able to generate a VS
project.  I don't have it installed in my Win7 VM at the moment, but
had planned to do that sometime soon to check on CS6.

2. You can find what files are necessary for a libcsound build by
looking at the CMakeFiles.txt in the main csound directory or looking
at the SConstruct file.

steven

On Thu, Jan 10, 2013 at 3:40 PM, Rory Walsh  wrote:
> Thanks Mike. So I'd need to add every thing in the following folders:
>
> Engine
> H
> OOps
> Opcodes
>
> Does that look right?
>
>
>  from I'll have to try this out on a sample project first and see how I get on!
>
> On 10 January 2013 16:31, Michael Gogins  wrote:
>> It is not a mighty task, but you will need to (a) define all the macros that
>> are used when compiling Csound (including those just for MSVC compiling
>> Csound, which would not be apparent from the existing build system) and (b)
>> link also with any other libs Csound needs.
>>
>> It's the same things that need to be done whether to build an app this way
>> or to build a library to be used to build an app.
>>
>>
>> On Thu, Jan 10, 2013 at 6:57 AM, Rory Walsh  wrote:
>>>
>>> I was hoping that Cabbage users could distribute plugins that will
>>> work whether Csound is installed or not. Do you think dumping all the
>>> necessary Csound source code into a Visual Studio project will
>>> actually work? Sounds like a mighty task..
>>>
>>>
>>> On 10 January 2013 12:38, michael.gogins@gmail.com
>>>  wrote:
>>> > Won't work.
>>> >
>>> > Put all the csound source.files you need into your msvc project. Don't
>>> > bother with a library.
>>> >
>>> > Or if you anticipate more than one project, create your own msvc project
>>> > for
>>> > that.
>>> >
>>> > What exactly are you trying to make?
>>> >
>>> > T-Mobile. America’s First Nationwide 4G Network
>>> >
>>> >
>>> > ----- Reply message -----
>>> > From: "Rory Walsh" 
>>> > To: 
>>> > Subject: [Csnd] static link to Csound lib MSVC..
>>> > Date: Thu, Jan 10, 2013 4:16 am
>>> >
>>> >
>>> > I'm looking at statically linking to libcsound.a that ships with the
>>> > windows package from MSVC. In the past I've always linking dynamically
>>> > against the dll by creating an MSVC import lib from it and linking to
>>> > that at runtime. I tried adding the libcsound.a file to the list of
>>> > libraries to link to but I get error about it not being valid, or
>>> > corrupted. I've never tried to do a static link to a MinGW library in
>>> > MSVC before. Has anyone any suggestions? Mike?
>>> >
>>> >
>>> > Send bugs reports to the Sourceforge bug tracker
>>> >            https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>> > Discussions of bugs and features can be posted here
>>> > To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>> > csound"
>>> >
>>>
>>>
>>> Send bugs reports to the Sourceforge bug tracker
>>>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>> Discussions of bugs and features can be posted here
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>> csound"
>>>
>>
>>
>>
>> --
>> Michael Gogins
>> Irreducible Productions
>> http://www.michael-gogins.com
>> Michael dot Gogins at gmail dot com
>
>
> Send bugs reports to the Sourceforge bug tracker
>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>

This would be great!

Sent from my iPhone.

On Jan 10, 2013, at 6:57 AM, Rory Walsh  wrote:

> I was hoping that Cabbage users could distribute plugins that will
> work whether Csound is installed or not. Do you think dumping all the
> necessary Csound source code into a Visual Studio project will
> actually work? Sounds like a mighty task..
> 
> 
> On 10 January 2013 12:38, michael.gogins@gmail.com
>  wrote:
>> Won't work.
>> 
>> Put all the csound source.files you need into your msvc project. Don't
>> bother with a library.
>> 
>> Or if you anticipate more than one project, create your own msvc project for
>> that.
>> 
>> What exactly are you trying to make?
>> 
>> T-Mobile. America’s First Nationwide 4G Network
>> 
>> 
>> ----- Reply message -----
>> From: "Rory Walsh" 
>> To: 
>> Subject: [Csnd] static link to Csound lib MSVC..
>> Date: Thu, Jan 10, 2013 4:16 am
>> 
>> 
>> I'm looking at statically linking to libcsound.a that ships with the
>> windows package from MSVC. In the past I've always linking dynamically
>> against the dll by creating an MSVC import lib from it and linking to
>> that at runtime. I tried adding the libcsound.a file to the list of
>> libraries to link to but I get error about it not being valid, or
>> corrupted. I've never tried to do a static link to a MinGW library in
>> MSVC before. Has anyone any suggestions? Mike?
>> 
>> 
>> Send bugs reports to the Sourceforge bug tracker
>>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
> 
> 
> Send bugs reports to the Sourceforge bug tracker
>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
> 

Thanks Steven, Mike. I'll give it a whirl when I get a chance.

Rory.

sent from a mobile device...

But since Csound is written in C, wouldn't it be possible to
distribute a static library for windows as well?

Cheers,
Andrés

On Thu, Jan 10, 2013 at 1:35 PM, Rory Walsh  wrote:
> Thanks Steven, Mike. I'll give it a whirl when I get a chance.
>
> Rory.
>
> sent from a mobile device...
>
> On 10 Jan 2013 16:05, "Steven Yi"  wrote:
>>
>> Hi Rory,
>>
>> Couple ideas:
>>
>> 1. I know we had issues a while back building with CMake, but maybe
>> it's worth trying once again?  Should be able to generate a VS
>> project.  I don't have it installed in my Win7 VM at the moment, but
>> had planned to do that sometime soon to check on CS6.
>>
>> 2. You can find what files are necessary for a libcsound build by
>> looking at the CMakeFiles.txt in the main csound directory or looking
>> at the SConstruct file.
>>
>> steven
>>
>> On Thu, Jan 10, 2013 at 3:40 PM, Rory Walsh  wrote:
>> > Thanks Mike. So I'd need to add every thing in the following folders:
>> >
>> > Engine
>> > H
>> > OOps
>> > Opcodes
>> >
>> > Does that look right?
>> >
>> >
>> >  from I'll have to try this out on a sample project first and see how I
>> > get on!
>> >
>> > On 10 January 2013 16:31, Michael Gogins 
>> > wrote:
>> >> It is not a mighty task, but you will need to (a) define all the macros
>> >> that
>> >> are used when compiling Csound (including those just for MSVC compiling
>> >> Csound, which would not be apparent from the existing build system) and
>> >> (b)
>> >> link also with any other libs Csound needs.
>> >>
>> >> It's the same things that need to be done whether to build an app this
>> >> way
>> >> or to build a library to be used to build an app.
>> >>
>> >>
>> >> On Thu, Jan 10, 2013 at 6:57 AM, Rory Walsh  wrote:
>> >>>
>> >>> I was hoping that Cabbage users could distribute plugins that will
>> >>> work whether Csound is installed or not. Do you think dumping all the
>> >>> necessary Csound source code into a Visual Studio project will
>> >>> actually work? Sounds like a mighty task..
>> >>>
>> >>>
>> >>> On 10 January 2013 12:38, michael.gogins@gmail.com
>> >>>  wrote:
>> >>> > Won't work.
>> >>> >
>> >>> > Put all the csound source.files you need into your msvc project.
>> >>> > Don't
>> >>> > bother with a library.
>> >>> >
>> >>> > Or if you anticipate more than one project, create your own msvc
>> >>> > project
>> >>> > for
>> >>> > that.
>> >>> >
>> >>> > What exactly are you trying to make?
>> >>> >
>> >>> > T-Mobile. America’s First Nationwide 4G Network
>> >>> >
>> >>> >
>> >>> > ----- Reply message -----
>> >>> > From: "Rory Walsh" 
>> >>> > To: 
>> >>> > Subject: [Csnd] static link to Csound lib MSVC..
>> >>> > Date: Thu, Jan 10, 2013 4:16 am
>> >>> >
>> >>> >
>> >>> > I'm looking at statically linking to libcsound.a that ships with the
>> >>> > windows package from MSVC. In the past I've always linking
>> >>> > dynamically
>> >>> > against the dll by creating an MSVC import lib from it and linking
>> >>> > to
>> >>> > that at runtime. I tried adding the libcsound.a file to the list of
>> >>> > libraries to link to but I get error about it not being valid, or
>> >>> > corrupted. I've never tried to do a static link to a MinGW library
>> >>> > in
>> >>> > MSVC before. Has anyone any suggestions? Mike?
>> >>> >
>> >>> >
>> >>> > Send bugs reports to the Sourceforge bug tracker
>> >>> >
>> >>> > https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> >>> > Discussions of bugs and features can be posted here
>> >>> > To unsubscribe, send email sympa@lists.bath.ac.uk with body
>> >>> > "unsubscribe
>> >>> > csound"
>> >>> >
>> >>>
>> >>>
>> >>> Send bugs reports to the Sourceforge bug tracker
>> >>>
>> >>> https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> >>> Discussions of bugs and features can be posted here
>> >>> To unsubscribe, send email sympa@lists.bath.ac.uk with body
>> >>> "unsubscribe
>> >>> csound"
>> >>>
>> >>
>> >>
>> >>
>> >> --
>> >> Michael Gogins
>> >> Irreducible Productions
>> >> http://www.michael-gogins.com
>> >> Michael dot Gogins at gmail dot com
>> >
>> >
>> > Send bugs reports to the Sourceforge bug tracker
>> >             https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> > Discussions of bugs and features can be posted here
>> > To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> > csound"
>> >
>>
>>
>> Send bugs reports to the Sourceforge bug tracker
>>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>>
>

A completely different thought: Isn't it possible to solve the original problem just by forcing the Cabbage plugin to look for the csound dll's in a specific location using SetDllDirectory and then package the csound dll's with the plugin. That is how Hadron works and we've had no complaints so far.

Sigurd

-----Original Message-----
From: Andres Cabrera [mailto:mantaraya36@gmail.com] 
Sent: Friday, January 11, 2013 2:46 AM
To: csound@lists.bath.ac.uk
Subject: Re: [Csnd] static link to Csound lib MSVC..

But since Csound is written in C, wouldn't it be possible to distribute a static library for windows as well?

Cheers,
Andrés

On Thu, Jan 10, 2013 at 1:35 PM, Rory Walsh  wrote:
> Thanks Steven, Mike. I'll give it a whirl when I get a chance.
>
> Rory.
>
> sent from a mobile device...
>
> On 10 Jan 2013 16:05, "Steven Yi"  wrote:
>>
>> Hi Rory,
>>
>> Couple ideas:
>>
>> 1. I know we had issues a while back building with CMake, but maybe 
>> it's worth trying once again?  Should be able to generate a VS 
>> project.  I don't have it installed in my Win7 VM at the moment, but 
>> had planned to do that sometime soon to check on CS6.
>>
>> 2. You can find what files are necessary for a libcsound build by 
>> looking at the CMakeFiles.txt in the main csound directory or looking 
>> at the SConstruct file.
>>
>> steven
>>
>> On Thu, Jan 10, 2013 at 3:40 PM, Rory Walsh  wrote:
>> > Thanks Mike. So I'd need to add every thing in the following folders:
>> >
>> > Engine
>> > H
>> > OOps
>> > Opcodes
>> >
>> > Does that look right?
>> >
>> >
>> >  from I'll have to try this out on a sample project first and see 
>> > how I get on!
>> >
>> > On 10 January 2013 16:31, Michael Gogins 
>> > wrote:
>> >> It is not a mighty task, but you will need to (a) define all the 
>> >> macros that are used when compiling Csound (including those just 
>> >> for MSVC compiling Csound, which would not be apparent from the 
>> >> existing build system) and
>> >> (b)
>> >> link also with any other libs Csound needs.
>> >>
>> >> It's the same things that need to be done whether to build an app 
>> >> this way or to build a library to be used to build an app.
>> >>
>> >>
>> >> On Thu, Jan 10, 2013 at 6:57 AM, Rory Walsh  wrote:
>> >>>
>> >>> I was hoping that Cabbage users could distribute plugins that 
>> >>> will work whether Csound is installed or not. Do you think 
>> >>> dumping all the necessary Csound source code into a Visual Studio 
>> >>> project will actually work? Sounds like a mighty task..
>> >>>
>> >>>
>> >>> On 10 January 2013 12:38, michael.gogins@gmail.com 
>> >>>  wrote:
>> >>> > Won't work.
>> >>> >
>> >>> > Put all the csound source.files you need into your msvc project.
>> >>> > Don't
>> >>> > bother with a library.
>> >>> >
>> >>> > Or if you anticipate more than one project, create your own 
>> >>> > msvc project for that.
>> >>> >
>> >>> > What exactly are you trying to make?
>> >>> >
>> >>> > T-Mobile. America’s First Nationwide 4G Network
>> >>> >
>> >>> >
>> >>> > ----- Reply message -----
>> >>> > From: "Rory Walsh" 
>> >>> > To: 
>> >>> > Subject: [Csnd] static link to Csound lib MSVC..
>> >>> > Date: Thu, Jan 10, 2013 4:16 am
>> >>> >
>> >>> >
>> >>> > I'm looking at statically linking to libcsound.a that ships 
>> >>> > with the windows package from MSVC. In the past I've always 
>> >>> > linking dynamically against the dll by creating an MSVC import 
>> >>> > lib from it and linking to that at runtime. I tried adding the 
>> >>> > libcsound.a file to the list of libraries to link to but I get 
>> >>> > error about it not being valid, or corrupted. I've never tried 
>> >>> > to do a static link to a MinGW library in MSVC before. Has 
>> >>> > anyone any suggestions? Mike?
>> >>> >
>> >>> >
>> >>> > Send bugs reports to the Sourceforge bug tracker
>> >>> >
>> >>> > https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> >>> > Discussions of bugs and features can be posted here To 
>> >>> > unsubscribe, send email sympa@lists.bath.ac.uk with body 
>> >>> > "unsubscribe csound"
>> >>> >
>> >>>
>> >>>
>> >>> Send bugs reports to the Sourceforge bug tracker
>> >>>
>> >>> https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> >>> Discussions of bugs and features can be posted here
>> >>> To unsubscribe, send email sympa@lists.bath.ac.uk with body
>> >>> "unsubscribe
>> >>> csound"
>> >>>
>> >>
>> >>
>> >>
>> >> --
>> >> Michael Gogins
>> >> Irreducible Productions
>> >> http://www.michael-gogins.com
>> >> Michael dot Gogins at gmail dot com
>> >
>> >
>> > Send bugs reports to the Sourceforge bug tracker
>> >             https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> > Discussions of bugs and features can be posted here
>> > To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> > csound"
>> >
>>
>>
>> Send bugs reports to the Sourceforge bug tracker
>>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>>
>


Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

I had thought about that Sigurd, and in the short term it's probably
the easiest solution for anyone wishing to distribute plugins with
Cabbage. I guess the distribution would also come in at around the
same size regardless of which way it's put together? Do you do this on
OSX too? I assume it's quite easy to build statically on OSX as both
tools are compiled with the same compiler. The thing putting me off a
more complicated solution is having to update Csound myself with each
new release.

On 11 January 2013 08:06, Sigurd Saue  wrote:
> A completely different thought: Isn't it possible to solve the original problem just by forcing the Cabbage plugin to look for the csound dll's in a specific location using SetDllDirectory and then package the csound dll's with the plugin. That is how Hadron works and we've had no complaints so far.
>
> Sigurd
>
> -----Original Message-----
> From: Andres Cabrera [mailto:mantaraya36@gmail.com]
> Sent: Friday, January 11, 2013 2:46 AM
> To: csound@lists.bath.ac.uk
> Subject: Re: [Csnd] static link to Csound lib MSVC..
>
> But since Csound is written in C, wouldn't it be possible to distribute a static library for windows as well?
>
> Cheers,
> Andrés
>
> On Thu, Jan 10, 2013 at 1:35 PM, Rory Walsh  wrote:
>> Thanks Steven, Mike. I'll give it a whirl when I get a chance.
>>
>> Rory.
>>
>> sent from a mobile device...
>>
>> On 10 Jan 2013 16:05, "Steven Yi"  wrote:
>>>
>>> Hi Rory,
>>>
>>> Couple ideas:
>>>
>>> 1. I know we had issues a while back building with CMake, but maybe
>>> it's worth trying once again?  Should be able to generate a VS
>>> project.  I don't have it installed in my Win7 VM at the moment, but
>>> had planned to do that sometime soon to check on CS6.
>>>
>>> 2. You can find what files are necessary for a libcsound build by
>>> looking at the CMakeFiles.txt in the main csound directory or looking
>>> at the SConstruct file.
>>>
>>> steven
>>>
>>> On Thu, Jan 10, 2013 at 3:40 PM, Rory Walsh  wrote:
>>> > Thanks Mike. So I'd need to add every thing in the following folders:
>>> >
>>> > Engine
>>> > H
>>> > OOps
>>> > Opcodes
>>> >
>>> > Does that look right?
>>> >
>>> >
>>> >  from I'll have to try this out on a sample project first and see
>>> > how I get on!
>>> >
>>> > On 10 January 2013 16:31, Michael Gogins 
>>> > wrote:
>>> >> It is not a mighty task, but you will need to (a) define all the
>>> >> macros that are used when compiling Csound (including those just
>>> >> for MSVC compiling Csound, which would not be apparent from the
>>> >> existing build system) and
>>> >> (b)
>>> >> link also with any other libs Csound needs.
>>> >>
>>> >> It's the same things that need to be done whether to build an app
>>> >> this way or to build a library to be used to build an app.
>>> >>
>>> >>
>>> >> On Thu, Jan 10, 2013 at 6:57 AM, Rory Walsh  wrote:
>>> >>>
>>> >>> I was hoping that Cabbage users could distribute plugins that
>>> >>> will work whether Csound is installed or not. Do you think
>>> >>> dumping all the necessary Csound source code into a Visual Studio
>>> >>> project will actually work? Sounds like a mighty task..
>>> >>>
>>> >>>
>>> >>> On 10 January 2013 12:38, michael.gogins@gmail.com
>>> >>>  wrote:
>>> >>> > Won't work.
>>> >>> >
>>> >>> > Put all the csound source.files you need into your msvc project.
>>> >>> > Don't
>>> >>> > bother with a library.
>>> >>> >
>>> >>> > Or if you anticipate more than one project, create your own
>>> >>> > msvc project for that.
>>> >>> >
>>> >>> > What exactly are you trying to make?
>>> >>> >
>>> >>> > T-Mobile. America’s First Nationwide 4G Network
>>> >>> >
>>> >>> >
>>> >>> > ----- Reply message -----
>>> >>> > From: "Rory Walsh" 
>>> >>> > To: 
>>> >>> > Subject: [Csnd] static link to Csound lib MSVC..
>>> >>> > Date: Thu, Jan 10, 2013 4:16 am
>>> >>> >
>>> >>> >
>>> >>> > I'm looking at statically linking to libcsound.a that ships
>>> >>> > with the windows package from MSVC. In the past I've always
>>> >>> > linking dynamically against the dll by creating an MSVC import
>>> >>> > lib from it and linking to that at runtime. I tried adding the
>>> >>> > libcsound.a file to the list of libraries to link to but I get
>>> >>> > error about it not being valid, or corrupted. I've never tried
>>> >>> > to do a static link to a MinGW library in MSVC before. Has
>>> >>> > anyone any suggestions? Mike?
>>> >>> >
>>> >>> >
>>> >>> > Send bugs reports to the Sourceforge bug tracker
>>> >>> >
>>> >>> > https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>> >>> > Discussions of bugs and features can be posted here To
>>> >>> > unsubscribe, send email sympa@lists.bath.ac.uk with body
>>> >>> > "unsubscribe csound"
>>> >>> >
>>> >>>
>>> >>>
>>> >>> Send bugs reports to the Sourceforge bug tracker
>>> >>>
>>> >>> https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>> >>> Discussions of bugs and features can be posted here
>>> >>> To unsubscribe, send email sympa@lists.bath.ac.uk with body
>>> >>> "unsubscribe
>>> >>> csound"
>>> >>>
>>> >>
>>> >>
>>> >>
>>> >> --
>>> >> Michael Gogins
>>> >> Irreducible Productions
>>> >> http://www.michael-gogins.com
>>> >> Michael dot Gogins at gmail dot com
>>> >
>>> >
>>> > Send bugs reports to the Sourceforge bug tracker
>>> >             https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>> > Discussions of bugs and features can be posted here
>>> > To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>> > csound"
>>> >
>>>
>>>
>>> Send bugs reports to the Sourceforge bug tracker
>>>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>> Discussions of bugs and features can be posted here
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>> csound"
>>>
>>
>
>
> Send bugs reports to the Sourceforge bug tracker
>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>
>
> Send bugs reports to the Sourceforge bug tracker
>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>

Yep, we do the same on OSX, but the details of that are taken care of by Bernt in our team. I assume it will be the same size, but don't know (our Csound package is slightly above 6 Mb, but we don't supply all the opcodes). We do build our own Csound with some minor tweaks, and to be absolutely sure that there is no mix-up with other Csound based plugins (e.g. Hadron and now Cabbage) we renamed the Csound dll.

It works fine and is probably much less work than your planned adventure.
 
Sigurd

-----Original Message-----
From: Rory Walsh [mailto:rorywalsh@ear.ie] 
Sent: Friday, January 11, 2013 1:04 PM
To: csound@lists.bath.ac.uk
Subject: Re: [Csnd] static link to Csound lib MSVC..

I had thought about that Sigurd, and in the short term it's probably the easiest solution for anyone wishing to distribute plugins with Cabbage. I guess the distribution would also come in at around the same size regardless of which way it's put together? Do you do this on OSX too? I assume it's quite easy to build statically on OSX as both tools are compiled with the same compiler. The thing putting me off a more complicated solution is having to update Csound myself with each new release.

On 11 January 2013 08:06, Sigurd Saue  wrote:
> A completely different thought: Isn't it possible to solve the original problem just by forcing the Cabbage plugin to look for the csound dll's in a specific location using SetDllDirectory and then package the csound dll's with the plugin. That is how Hadron works and we've had no complaints so far.
>
> Sigurd
>
> -----Original Message-----
> From: Andres Cabrera [mailto:mantaraya36@gmail.com]
> Sent: Friday, January 11, 2013 2:46 AM
> To: csound@lists.bath.ac.uk
> Subject: Re: [Csnd] static link to Csound lib MSVC..
>
> But since Csound is written in C, wouldn't it be possible to distribute a static library for windows as well?
>
> Cheers,
> Andrés
>
> On Thu, Jan 10, 2013 at 1:35 PM, Rory Walsh  wrote:
>> Thanks Steven, Mike. I'll give it a whirl when I get a chance.
>>
>> Rory.
>>
>> sent from a mobile device...
>>
>> On 10 Jan 2013 16:05, "Steven Yi"  wrote:
>>>
>>> Hi Rory,
>>>
>>> Couple ideas:
>>>
>>> 1. I know we had issues a while back building with CMake, but maybe 
>>> it's worth trying once again?  Should be able to generate a VS 
>>> project.  I don't have it installed in my Win7 VM at the moment, but 
>>> had planned to do that sometime soon to check on CS6.
>>>
>>> 2. You can find what files are necessary for a libcsound build by 
>>> looking at the CMakeFiles.txt in the main csound directory or 
>>> looking at the SConstruct file.
>>>
>>> steven
>>>
>>> On Thu, Jan 10, 2013 at 3:40 PM, Rory Walsh  wrote:
>>> > Thanks Mike. So I'd need to add every thing in the following folders:
>>> >
>>> > Engine
>>> > H
>>> > OOps
>>> > Opcodes
>>> >
>>> > Does that look right?
>>> >
>>> >
>>> >  from I'll have to try this out on a sample project first and see 
>>> > how I get on!
>>> >
>>> > On 10 January 2013 16:31, Michael Gogins 
>>> > 
>>> > wrote:
>>> >> It is not a mighty task, but you will need to (a) define all the 
>>> >> macros that are used when compiling Csound (including those just 
>>> >> for MSVC compiling Csound, which would not be apparent from the 
>>> >> existing build system) and
>>> >> (b)
>>> >> link also with any other libs Csound needs.
>>> >>
>>> >> It's the same things that need to be done whether to build an app 
>>> >> this way or to build a library to be used to build an app.
>>> >>
>>> >>
>>> >> On Thu, Jan 10, 2013 at 6:57 AM, Rory Walsh  wrote:
>>> >>>
>>> >>> I was hoping that Cabbage users could distribute plugins that 
>>> >>> will work whether Csound is installed or not. Do you think 
>>> >>> dumping all the necessary Csound source code into a Visual 
>>> >>> Studio project will actually work? Sounds like a mighty task..
>>> >>>
>>> >>>
>>> >>> On 10 January 2013 12:38, michael.gogins@gmail.com 
>>> >>>  wrote:
>>> >>> > Won't work.
>>> >>> >
>>> >>> > Put all the csound source.files you need into your msvc project.
>>> >>> > Don't
>>> >>> > bother with a library.
>>> >>> >
>>> >>> > Or if you anticipate more than one project, create your own 
>>> >>> > msvc project for that.
>>> >>> >
>>> >>> > What exactly are you trying to make?
>>> >>> >
>>> >>> > T-Mobile. America's First Nationwide 4G Network
>>> >>> >
>>> >>> >
>>> >>> > ----- Reply message -----
>>> >>> > From: "Rory Walsh" 
>>> >>> > To: 
>>> >>> > Subject: [Csnd] static link to Csound lib MSVC..
>>> >>> > Date: Thu, Jan 10, 2013 4:16 am
>>> >>> >
>>> >>> >
>>> >>> > I'm looking at statically linking to libcsound.a that ships 
>>> >>> > with the windows package from MSVC. In the past I've always 
>>> >>> > linking dynamically against the dll by creating an MSVC import 
>>> >>> > lib from it and linking to that at runtime. I tried adding the 
>>> >>> > libcsound.a file to the list of libraries to link to but I get 
>>> >>> > error about it not being valid, or corrupted. I've never tried 
>>> >>> > to do a static link to a MinGW library in MSVC before. Has 
>>> >>> > anyone any suggestions? Mike?
>>> >>> >
>>> >>> >
>>> >>> > Send bugs reports to the Sourceforge bug tracker
>>> >>> >
>>> >>> > https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>> >>> > Discussions of bugs and features can be posted here To 
>>> >>> > unsubscribe, send email sympa@lists.bath.ac.uk with body 
>>> >>> > "unsubscribe csound"
>>> >>> >
>>> >>>
>>> >>>
>>> >>> Send bugs reports to the Sourceforge bug tracker
>>> >>>
>>> >>> https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>> >>> Discussions of bugs and features can be posted here To 
>>> >>> unsubscribe, send email sympa@lists.bath.ac.uk with body 
>>> >>> "unsubscribe csound"
>>> >>>
>>> >>
>>> >>
>>> >>
>>> >> --
>>> >> Michael Gogins
>>> >> Irreducible Productions
>>> >> http://www.michael-gogins.com
>>> >> Michael dot Gogins at gmail dot com
>>> >
>>> >
>>> > Send bugs reports to the Sourceforge bug tracker
>>> >             
>>> > https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>> > Discussions of bugs and features can be posted here To 
>>> > unsubscribe, send email sympa@lists.bath.ac.uk with body 
>>> > "unsubscribe csound"
>>> >
>>>
>>>
>>> Send bugs reports to the Sourceforge bug tracker
>>>             
>>> https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>> Discussions of bugs and features can be posted here To unsubscribe, 
>>> send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>>
>>
>
>
> Send bugs reports to the Sourceforge bug tracker
>             
> https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here To unsubscribe, 
> send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>
>
> Send bugs reports to the Sourceforge bug tracker
>             
> https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here To unsubscribe, 
> send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>


Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

I'd have to agree with you on the 'less work' comment. It certainly
sounds like it!

I also imagine that if users wish to distribute more than one plugin
they can just bundle a few of them together into the one folder
containing Csound so as not to duplicate lots of unnecessary files.

On 11 January 2013 12:35, Rory Walsh  wrote:
> I'd have to agree with you on the 'less work' comment. It certainly
> sounds like it!

Yes. It does have some additional advantages. So the choice is yours: "easy and flexible" or "difficult and inflexible". I leave it to you to decide :-)

Anyway, if you go with a dynamic Csound package I'm happy to help you sort out any difficulties.

Sigurd 

-----Original Message-----
From: Rory Walsh [mailto:rorywalsh@ear.ie] 
Sent: Friday, January 11, 2013 1:37 PM
To: csound@lists.bath.ac.uk
Subject: Re: [Csnd] static link to Csound lib MSVC..

I also imagine that if users wish to distribute more than one plugin they can just bundle a few of them together into the one folder containing Csound so as not to duplicate lots of unnecessary files.

On 11 January 2013 12:35, Rory Walsh  wrote:
> I'd have to agree with you on the 'less work' comment. It certainly 
> sounds like it!


Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Thanks Sigurd. One thing which I would love your help on is with MIDI
output. I've been looking at having plugins output MIDI but I couldn't
quite ever get it to work probably. Being able to build generative
MIDI plugins with Cabbage would be great. I can happily talk you
through my experiments so far if you wish to take a look. Feel free to
contact me off-list.