Csound Csound-dev Csound-tekno Search About

[Csnd] How can I create Microsoft C++ import libraries from Csound libs?

Date2013-05-19 03:01
FromMark Brophy
Subject[Csnd] How can I create Microsoft C++ import libraries from Csound libs?
I want to create a multi-touch app using C++ running on Windows 8. How can I create import libraries that the Microsoft linker will understand?


Date2013-05-19 03:05
FromJustin Smith
SubjectRe: [Csnd] How can I create Microsoft C++ import libraries from
Your best bet would be to use the C api, unless someone has a working visual studio build of a recent csound.

There is no compatibility between C++ implementations, you either have to compile everything with the same vendor's compiler, or use C interfaces to the libraries.


On Sat, May 18, 2013 at 7:01 PM, Mark Brophy <mark@brophyworld.com> wrote:
I want to create a multi-touch app using C++ running on Windows 8. How can I create import libraries that the Microsoft linker will understand?



Date2013-05-19 14:00
FromMark Brophy
SubjectRe: [Csnd] How can I create Microsoft C++ import libraries from
I decided to use the C interfaces with C++. How can I link to the libraries?


On Sat, May 18, 2013 at 9:05 PM, Justin Smith <noisesmith@gmail.com> wrote:
Your best bet would be to use the C api, unless someone has a working visual studio build of a recent csound.

There is no compatibility between C++ implementations, you either have to compile everything with the same vendor's compiler, or use C interfaces to the libraries.


On Sat, May 18, 2013 at 7:01 PM, Mark Brophy <mark@brophyworld.com> wrote:
I want to create a multi-touch app using C++ running on Windows 8. How can I create import libraries that the Microsoft linker will understand?




Date2013-05-19 14:52
Fromandy fillebrown
SubjectRe: [Csnd] How can I create Microsoft C++ import libraries from

and use it on the command line to create a csound .def file ...

pexports csound64.dll.5.2 > csound64.def

Then open up a MSVC command line and run the lib tool on the .def file ...

lib /machine:i386  /def:csound64.def

That will create a csound64.lib import library that you can link to with MSVC.

Cheers,
~ andy.f





On Sun, May 19, 2013 at 9:00 AM, Mark Brophy <mark@brophyworld.com> wrote:
I decided to use the C interfaces with C++. How can I link to the libraries?


On Sat, May 18, 2013 at 9:05 PM, Justin Smith <noisesmith@gmail.com> wrote:
Your best bet would be to use the C api, unless someone has a working visual studio build of a recent csound.

There is no compatibility between C++ implementations, you either have to compile everything with the same vendor's compiler, or use C interfaces to the libraries.


On Sat, May 18, 2013 at 7:01 PM, Mark Brophy <mark@brophyworld.com> wrote:
I want to create a multi-touch app using C++ running on Windows 8. How can I create import libraries that the Microsoft linker will understand?





Date2013-05-19 18:04
FromMark Brophy
SubjectRe: [Csnd] How can I create Microsoft C++ import libraries from
I get the error, "the program can't start because mspdb110.dll is missing" when I try to run the lib program. What environment variables do I need to set to make lib work?



On Sun, May 19, 2013 at 8:52 AM, andy fillebrown <andy.fillebrown@gmail.com> wrote:

and use it on the command line to create a csound .def file ...

pexports csound64.dll.5.2 > csound64.def

Then open up a MSVC command line and run the lib tool on the .def file ...

lib /machine:i386  /def:csound64.def

That will create a csound64.lib import library that you can link to with MSVC.

Cheers,
~ andy.f





On Sun, May 19, 2013 at 9:00 AM, Mark Brophy <mark@brophyworld.com> wrote:
I decided to use the C interfaces with C++. How can I link to the libraries?


On Sat, May 18, 2013 at 9:05 PM, Justin Smith <noisesmith@gmail.com> wrote:
Your best bet would be to use the C api, unless someone has a working visual studio build of a recent csound.

There is no compatibility between C++ implementations, you either have to compile everything with the same vendor's compiler, or use C interfaces to the libraries.


On Sat, May 18, 2013 at 7:01 PM, Mark Brophy <mark@brophyworld.com> wrote:
I want to create a multi-touch app using C++ running on Windows 8. How can I create import libraries that the Microsoft linker will understand?






Date2013-05-19 18:07
FromRory Walsh
SubjectRe: [Csnd] How can I create Microsoft C++ import libraries from
You need to run it within the MSVC command line environment. It should
be accessible from your programs menu.

On 19 May 2013 18:04, Mark Brophy  wrote:
> I get the error, "the program can't start because mspdb110.dll is missing"
> when I try to run the lib program. What environment variables do I need to
> set to make lib work?
>
>
>
> On Sun, May 19, 2013 at 8:52 AM, andy fillebrown 
> wrote:
>>
>>
>> Get pexports from
>> http://sourceforge.net/projects/mingw/files/MinGW/Extension/pexports/pexports-0.44-1/pexports-0.44-1-mingw32-bin.tar.lzma/download
>> and use it on the command line to create a csound .def file ...
>>
>> pexports csound64.dll.5.2 > csound64.def
>>
>> Then open up a MSVC command line and run the lib tool on the .def file ...
>>
>> lib /machine:i386  /def:csound64.def
>>
>> That will create a csound64.lib import library that you can link to with
>> MSVC.
>>
>> Cheers,
>> ~ andy.f
>>
>>
>>
>>
>>
>> On Sun, May 19, 2013 at 9:00 AM, Mark Brophy  wrote:
>>>
>>> I decided to use the C interfaces with C++. How can I link to the
>>> libraries?
>>>
>>>
>>> On Sat, May 18, 2013 at 9:05 PM, Justin Smith 
>>> wrote:
>>>>
>>>> Your best bet would be to use the C api, unless someone has a working
>>>> visual studio build of a recent csound.
>>>>
>>>> There is no compatibility between C++ implementations, you either have
>>>> to compile everything with the same vendor's compiler, or use C interfaces
>>>> to the libraries.
>>>>
>>>>
>>>> On Sat, May 18, 2013 at 7:01 PM, Mark Brophy 
>>>> wrote:
>>>>>
>>>>> I want to create a multi-touch app using C++ running on Windows 8. How
>>>>> can I create import libraries that the Microsoft linker will understand?
>>>>>
>>>>
>>>
>>
>

Date2013-05-19 20:37
FromMark Brophy
SubjectRe: [Csnd] How can I create Microsoft C++ import libraries from
I ran lib from the command line, producing csound64.lib and csound64.exp; so I copied those to the Visual Studio lib directory and tried to build my project. I received "unresolved symbol" errors for each of the Csound calls, csoundCreate, csoundDestroy, csoundCompile, and csoundPerform. How do I tell Visual Studio that csound64.lib is related to csound64.dll.5.2?



On Sun, May 19, 2013 at 12:07 PM, Rory Walsh <rorywalsh@ear.ie> wrote:
You need to run it within the MSVC command line environment. It should
be accessible from your programs menu.

On 19 May 2013 18:04, Mark Brophy <mark@brophyworld.com> wrote:
> I get the error, "the program can't start because mspdb110.dll is missing"
> when I try to run the lib program. What environment variables do I need to
> set to make lib work?
>
>
>
> On Sun, May 19, 2013 at 8:52 AM, andy fillebrown <andy.fillebrown@gmail.com>
> wrote:
>>
>>
>> Get pexports from
>> http://sourceforge.net/projects/mingw/files/MinGW/Extension/pexports/pexports-0.44-1/pexports-0.44-1-mingw32-bin.tar.lzma/download
>> and use it on the command line to create a csound .def file ...
>>
>> pexports csound64.dll.5.2 > csound64.def
>>
>> Then open up a MSVC command line and run the lib tool on the .def file ...
>>
>> lib /machine:i386  /def:csound64.def
>>
>> That will create a csound64.lib import library that you can link to with
>> MSVC.
>>
>> Cheers,
>> ~ andy.f
>>
>>
>>
>>
>>
>> On Sun, May 19, 2013 at 9:00 AM, Mark Brophy <mark@brophyworld.com> wrote:
>>>
>>> I decided to use the C interfaces with C++. How can I link to the
>>> libraries?
>>>
>>>
>>> On Sat, May 18, 2013 at 9:05 PM, Justin Smith <noisesmith@gmail.com>
>>> wrote:
>>>>
>>>> Your best bet would be to use the C api, unless someone has a working
>>>> visual studio build of a recent csound.
>>>>
>>>> There is no compatibility between C++ implementations, you either have
>>>> to compile everything with the same vendor's compiler, or use C interfaces
>>>> to the libraries.
>>>>
>>>>
>>>> On Sat, May 18, 2013 at 7:01 PM, Mark Brophy <mark@brophyworld.com>
>>>> wrote:
>>>>>
>>>>> I want to create a multi-touch app using C++ running on Windows 8. How
>>>>> can I create import libraries that the Microsoft linker will understand?
>>>>>
>>>>
>>>
>>
>


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"



Date2013-05-19 21:39
FromRory Walsh
SubjectRe: [Csnd] How can I create Microsoft C++ import libraries from

You don't need to move the files. You can leave them in the csound bin dir if you like, but you do need to link to them. Do this through your project settings in msvc. I'm not at a pc right now but it should be clear enough what to do.

sent from a mobile device...

On 19 May 2013 20:37, "Mark Brophy" <mark@brophyworld.com> wrote:
I ran lib from the command line, producing csound64.lib and csound64.exp; so I copied those to the Visual Studio lib directory and tried to build my project. I received "unresolved symbol" errors for each of the Csound calls, csoundCreate, csoundDestroy, csoundCompile, and csoundPerform. How do I tell Visual Studio that csound64.lib is related to csound64.dll.5.2?



On Sun, May 19, 2013 at 12:07 PM, Rory Walsh <rorywalsh@ear.ie> wrote:
You need to run it within the MSVC command line environment. It should
be accessible from your programs menu.

On 19 May 2013 18:04, Mark Brophy <mark@brophyworld.com> wrote:
> I get the error, "the program can't start because mspdb110.dll is missing"
> when I try to run the lib program. What environment variables do I need to
> set to make lib work?
>
>
>
> On Sun, May 19, 2013 at 8:52 AM, andy fillebrown <andy.fillebrown@gmail.com>
> wrote:
>>
>>
>> Get pexports from
>> http://sourceforge.net/projects/mingw/files/MinGW/Extension/pexports/pexports-0.44-1/pexports-0.44-1-mingw32-bin.tar.lzma/download
>> and use it on the command line to create a csound .def file ...
>>
>> pexports csound64.dll.5.2 > csound64.def
>>
>> Then open up a MSVC command line and run the lib tool on the .def file ...
>>
>> lib /machine:i386  /def:csound64.def
>>
>> That will create a csound64.lib import library that you can link to with
>> MSVC.
>>
>> Cheers,
>> ~ andy.f
>>
>>
>>
>>
>>
>> On Sun, May 19, 2013 at 9:00 AM, Mark Brophy <mark@brophyworld.com> wrote:
>>>
>>> I decided to use the C interfaces with C++. How can I link to the
>>> libraries?
>>>
>>>
>>> On Sat, May 18, 2013 at 9:05 PM, Justin Smith <noisesmith@gmail.com>
>>> wrote:
>>>>
>>>> Your best bet would be to use the C api, unless someone has a working
>>>> visual studio build of a recent csound.
>>>>
>>>> There is no compatibility between C++ implementations, you either have
>>>> to compile everything with the same vendor's compiler, or use C interfaces
>>>> to the libraries.
>>>>
>>>>
>>>> On Sat, May 18, 2013 at 7:01 PM, Mark Brophy <mark@brophyworld.com>
>>>> wrote:
>>>>>
>>>>> I want to create a multi-touch app using C++ running on Windows 8. How
>>>>> can I create import libraries that the Microsoft linker will understand?
>>>>>
>>>>
>>>
>>
>


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"



Date2013-05-20 00:26
FromMark Brophy
SubjectRe: [Csnd] How can I create Microsoft C++ import libraries from
OK, that worked; I'm compiled and linked. I can't run it, though, because Microsoft is complaining that it is "unable to activate Windows Store app"; so I'll try to find out how to build a version that runs only on my machine.


On Sun, May 19, 2013 at 3:39 PM, Rory Walsh <rorywalsh@ear.ie> wrote:

You don't need to move the files. You can leave them in the csound bin dir if you like, but you do need to link to them. Do this through your project settings in msvc. I'm not at a pc right now but it should be clear enough what to do.

sent from a mobile device...

On 19 May 2013 20:37, "Mark Brophy" <mark@brophyworld.com> wrote:
I ran lib from the command line, producing csound64.lib and csound64.exp; so I copied those to the Visual Studio lib directory and tried to build my project. I received "unresolved symbol" errors for each of the Csound calls, csoundCreate, csoundDestroy, csoundCompile, and csoundPerform. How do I tell Visual Studio that csound64.lib is related to csound64.dll.5.2?



On Sun, May 19, 2013 at 12:07 PM, Rory Walsh <rorywalsh@ear.ie> wrote:
You need to run it within the MSVC command line environment. It should
be accessible from your programs menu.

On 19 May 2013 18:04, Mark Brophy <mark@brophyworld.com> wrote:
> I get the error, "the program can't start because mspdb110.dll is missing"
> when I try to run the lib program. What environment variables do I need to
> set to make lib work?
>
>
>
> On Sun, May 19, 2013 at 8:52 AM, andy fillebrown <andy.fillebrown@gmail.com>
> wrote:
>>
>>
>> Get pexports from
>> http://sourceforge.net/projects/mingw/files/MinGW/Extension/pexports/pexports-0.44-1/pexports-0.44-1-mingw32-bin.tar.lzma/download
>> and use it on the command line to create a csound .def file ...
>>
>> pexports csound64.dll.5.2 > csound64.def
>>
>> Then open up a MSVC command line and run the lib tool on the .def file ...
>>
>> lib /machine:i386  /def:csound64.def
>>
>> That will create a csound64.lib import library that you can link to with
>> MSVC.
>>
>> Cheers,
>> ~ andy.f
>>
>>
>>
>>
>>
>> On Sun, May 19, 2013 at 9:00 AM, Mark Brophy <mark@brophyworld.com> wrote:
>>>
>>> I decided to use the C interfaces with C++. How can I link to the
>>> libraries?
>>>
>>>
>>> On Sat, May 18, 2013 at 9:05 PM, Justin Smith <noisesmith@gmail.com>
>>> wrote:
>>>>
>>>> Your best bet would be to use the C api, unless someone has a working
>>>> visual studio build of a recent csound.
>>>>
>>>> There is no compatibility between C++ implementations, you either have
>>>> to compile everything with the same vendor's compiler, or use C interfaces
>>>> to the libraries.
>>>>
>>>>
>>>> On Sat, May 18, 2013 at 7:01 PM, Mark Brophy <mark@brophyworld.com>
>>>> wrote:
>>>>>
>>>>> I want to create a multi-touch app using C++ running on Windows 8. How
>>>>> can I create import libraries that the Microsoft linker will understand?
>>>>>
>>>>
>>>
>>
>


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"




Date2013-05-20 02:03
FromRory Walsh
SubjectRe: [Csnd] How can I create Microsoft C++ import libraries from
Let us know how you get on. I've never developed anything for Windows
8 so I've no idea about the windows app store.

On 20 May 2013 00:26, Mark Brophy  wrote:
> OK, that worked; I'm compiled and linked. I can't run it, though, because
> Microsoft is complaining that it is "unable to activate Windows Store app";
> so I'll try to find out how to build a version that runs only on my machine.
>
>
> On Sun, May 19, 2013 at 3:39 PM, Rory Walsh  wrote:
>>
>> You don't need to move the files. You can leave them in the csound bin dir
>> if you like, but you do need to link to them. Do this through your project
>> settings in msvc. I'm not at a pc right now but it should be clear enough
>> what to do.
>>
>> sent from a mobile device...
>>
>> On 19 May 2013 20:37, "Mark Brophy"  wrote:
>>>
>>> I ran lib from the command line, producing csound64.lib and csound64.exp;
>>> so I copied those to the Visual Studio lib directory and tried to build my
>>> project. I received "unresolved symbol" errors for each of the Csound calls,
>>> csoundCreate, csoundDestroy, csoundCompile, and csoundPerform. How do I tell
>>> Visual Studio that csound64.lib is related to csound64.dll.5.2?
>>>
>>>
>>>
>>> On Sun, May 19, 2013 at 12:07 PM, Rory Walsh  wrote:
>>>>
>>>> You need to run it within the MSVC command line environment. It should
>>>> be accessible from your programs menu.
>>>>
>>>> On 19 May 2013 18:04, Mark Brophy  wrote:
>>>> > I get the error, "the program can't start because mspdb110.dll is
>>>> > missing"
>>>> > when I try to run the lib program. What environment variables do I
>>>> > need to
>>>> > set to make lib work?
>>>> >
>>>> >
>>>> >
>>>> > On Sun, May 19, 2013 at 8:52 AM, andy fillebrown
>>>> > 
>>>> > wrote:
>>>> >>
>>>> >>
>>>> >> Get pexports from
>>>> >>
>>>> >> http://sourceforge.net/projects/mingw/files/MinGW/Extension/pexports/pexports-0.44-1/pexports-0.44-1-mingw32-bin.tar.lzma/download
>>>> >> and use it on the command line to create a csound .def file ...
>>>> >>
>>>> >> pexports csound64.dll.5.2 > csound64.def
>>>> >>
>>>> >> Then open up a MSVC command line and run the lib tool on the .def
>>>> >> file ...
>>>> >>
>>>> >> lib /machine:i386  /def:csound64.def
>>>> >>
>>>> >> That will create a csound64.lib import library that you can link to
>>>> >> with
>>>> >> MSVC.
>>>> >>
>>>> >> Cheers,
>>>> >> ~ andy.f
>>>> >>
>>>> >>
>>>> >>
>>>> >>
>>>> >>
>>>> >> On Sun, May 19, 2013 at 9:00 AM, Mark Brophy 
>>>> >> wrote:
>>>> >>>
>>>> >>> I decided to use the C interfaces with C++. How can I link to the
>>>> >>> libraries?
>>>> >>>
>>>> >>>
>>>> >>> On Sat, May 18, 2013 at 9:05 PM, Justin Smith 
>>>> >>> wrote:
>>>> >>>>
>>>> >>>> Your best bet would be to use the C api, unless someone has a
>>>> >>>> working
>>>> >>>> visual studio build of a recent csound.
>>>> >>>>
>>>> >>>> There is no compatibility between C++ implementations, you either
>>>> >>>> have
>>>> >>>> to compile everything with the same vendor's compiler, or use C
>>>> >>>> interfaces
>>>> >>>> to the libraries.
>>>> >>>>
>>>> >>>>
>>>> >>>> On Sat, May 18, 2013 at 7:01 PM, Mark Brophy 
>>>> >>>> wrote:
>>>> >>>>>
>>>> >>>>> I want to create a multi-touch app using C++ running on Windows 8.
>>>> >>>>> How
>>>> >>>>> can I create import libraries that the Microsoft linker will
>>>> >>>>> understand?
>>>> >>>>>
>>>> >>>>
>>>> >>>
>>>> >>
>>>> >
>>>>
>>>>
>>>> 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"
>>>>
>>>
>

Date2013-05-28 13:54
FromRichard Henninger
SubjectRe: [Csnd] How can I create Microsoft C++ import libraries from

Not so easily - if by Win8 app you mean a downloadable app.  ”Apps” need to be compliant with the new WinRT API or they cannot be accepted by and downloaded from the Windows App store.  The restrictions are meant to support multiple hardware platforms (intel and ARM currently), a multi-language ABI (enabling use of javascript, .NET and native C++ interchangeably), and  a strict sandboxing model that promotes device safety and security as well as ease of installation/updating/removal: a pretty cool design goal, but not trivial to obtain with platform independent code like csound aspires to be.

On the other hand, csound works like a champ for Windows 8 in desktop mode.  If multi-touch is all you are after, you can use it now in a desktop program running on an intel box or intel-based tablet installed and run the “old-fashioned” way.  There you have all the API’s (including midi - which WinRT doesn’t support) we are used to in regular Windows.  You should be able to use the csound API and dll just fine in this mode by using the pexports tool to get the def file as described by others. Create a regular (non-windows store: no /ZW switch) native c++ project to make that work.  While you could compile as a Win8 app, it will fall apart when you run it - as you’ve found.

I’ve played around with WinRT some and there are several obstacles that make creation of WinRT csound “apps” difficult.  These all stem from the architectural implications of the design of WinRT’s sandboxing and how that is at odds with csound’s classic unix architecture.  The problem is less severe for ios and android - neither of which are as radical a departure from their underlying unix architectural concepts.  Until there is a WinRT compliant compile of csound and supporting libraries (like ios and android have) nothing you create will launch as a Win8 “app”.

The first hurdle to address is that WinRT apps are fully self-contained and must be compiled to use WinRT and a subset of directX (for audio).  The compiler shuts off many classic CRT-lib functions like getenv.  The sandbox will not let you rely on previously installed libraries.  Any libraries you include with csound (libsndfile, portaudio, portmidi-were midi supported) must also be re-compiled to be WinRT compliant and released with csound and your app as one.  Any app using csound must include its own copy of csound code and any supporting libraries.  Pretty tight sandbox, eh!

Another hurdle is file I/O.  Many csound opcodes and table types read data directly.  These would need a way to access permitted directories via WinRT’s agents. A simple fopen won’t work for files in your documents and music directories - even with permissions set right.  Accommodating this is doable, but csound itself would need some restructuring to pull this off.  Audio would have to use WASAPI rather than older audio api’s - I’m not sure portaudio works this way exclusively - all included code (even if you don’t use it in real time) must be compliant.  The old midi api’s are gone, but OSC and csound’s bus could be made to work for realtime interaction.  I could go on...

Given that the community is hard at work absorbing csound 6, I should think it unlikely that any changes for supporting WinRT could be incorporated any time soon.  It’s nice that many of 6’s enhancements would be helpful for such an effort - like compiling from strings rather than files.  Perhaps when 6 has settled down, we could make a WinRT branch in the code like was done for android and ios.

I’m certainly happy do my part in supporting such an effort when the time becomes right​​.

Richard Henninger

 
Sent from Windows 8 Mail
 
From: Rory Walsh
Sent: ‎Sunday‎, ‎May‎ ‎19‎, ‎2013 ‎9‎:‎04‎ ‎PM
To: csound@lists.bath.ac.uk
 
Let us know how you get on. I've never developed anything for Windows
8 so I've no idea about the windows app store.

On 20 May 2013 00:26, Mark Brophy <mark@brophyworld.com> wrote:
> OK, that worked; I'm compiled and linked. I can't run it, though, because
> Microsoft is complaining that it is "unable to activate Windows Store app";
> so I'll try to find out how to build a version that runs only on my machine.
>
>
> On Sun, May 19, 2013 at 3:39 PM, Rory Walsh <rorywalsh@ear.ie> wrote:
>>
>> You don't need to move the files. You can leave them in the csound bin dir
>> if you like, but you do need to link to them. Do this through your project
>> settings in msvc. I'm not at a pc right now but it should be clear enough
>> what to do.
>>
>> sent from a mobile device...
>>
>> On 19 May 2013 20:37, "Mark Brophy" <mark@brophyworld.com> wrote:
>>>
>>> I ran lib from the command line, producing csound64.lib and csound64.exp;
>>> so I copied those to the Visual Studio lib directory and tried to build my
>>> project. I received "unresolved symbol" errors for each of the Csound calls,
>>> csoundCreate, csoundDestroy, csoundCompile, and csoundPerform. How do I tell
>>> Visual Studio that csound64.lib is related to csound64.dll.5.2?
>>>
>>>
>>>
>>> On Sun, May 19, 2013 at 12:07 PM, Rory Walsh <rorywalsh@ear.ie> wrote:
>>>>
>>>> You need to run it within the MSVC command line environment. It should
>>>> be accessible from your programs menu.
>>>>
>>>> On 19 May 2013 18:04, Mark Brophy <mark@brophyworld.com> wrote:
>>>> > I get the error, "the program can't start because mspdb110.dll is
>>>> > missing"
>>>> > when I try to run the lib program. What environment variables do I
>>>> > need to
>>>> > set to make lib work?
>>>> >
>>>> >
>>>> >
>>>> > On Sun, May 19, 2013 at 8:52 AM, andy fillebrown
>>>> > <andy.fillebrown@gmail.com>
>>>> > wrote:
>>>> >>
>>>> >>
>>>> >> Get pexports from
>>>> >>
>>>> >> http://sourceforge.net/projects/mingw/files/MinGW/Extension/pexports/pexports-0.44-1/pexports-0.44-1-mingw32-bin.tar.lzma/download
>>>> >> and use it on the command line to create a csound .def file ...
>>>> >>
>>>> >> pexports csound64.dll.5.2 > csound64.def
>>>> >>
>>>> >> Then open up a MSVC command line and run the lib tool on the .def
>>>> >> file ...
>>>> >>
>>>> >> lib /machine:i386  /def:csound64.def
>>>> >>
>>>> >> That will create a csound64.lib import library that you can link to
>>>> >> with
>>>> >> MSVC.
>>>> >>
>>>> >> Cheers,
>>>> >> ~ andy.f
>>>> >>
>>>> >>
>>>> >>
>>>> >>
>>>> >>
>>>> >> On Sun, May 19, 2013 at 9:00 AM, Mark Brophy <mark@brophyworld.com>
>>>> >> wrote:
>>>> >>>
>>>> >>> I decided to use the C interfaces with C++. How can I link to the
>>>> >>> libraries?
>>>> >>>
>>>> >>>
>>>> >>> On Sat, May 18, 2013 at 9:05 PM, Justin Smith <noisesmith@gmail.com>
>>>> >>> wrote:
>>>> >>>>
>>>> >>>> Your best bet would be to use the C api, unless someone has a
>>>> >>>> working
>>>> >>>> visual studio build of a recent csound.
>>>> >>>>
>>>> >>>> There is no compatibility between C++ implementations, you either
>>>> >>>> have
>>>> >>>> to compile everything with the same vendor's compiler, or use C
>>>> >>>> interfaces
>>>> >>>> to the libraries.
>>>> >>>>
>>>> >>>>
>>>> >>>> On Sat, May 18, 2013 at 7:01 PM, Mark Brophy <mark@brophyworld.com>
>>>> >>>> wrote:
>>>> >>>>>
>>>> >>>>> I want to create a multi-touch app using C++ running on Windows 8.
>>>> >>>>> How
>>>> >>>>> can I create import libraries that the Microsoft linker will
>>>> >>>>> understand?
>>>> >>>>>
>>>> >>>>
>>>> >>>
>>>> >>
>>>> >
>>>>
>>>>
>>>> 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"