I set up a new API project using MS Visual Express. I then copied
project settings from a previous MSVE Csound host application and went
to build. As soon as I include csound.hpp and try to build it
complains about not recognising int32. In the past, because MSVC is
defined, I would have always commented the MSVC stuff from sysdep.h as
in:

#ifdef MSVC
/*
typedef __int32 int32;
typedef __int16 int16;
typedef unsigned __int32 uint32;
typedef unsigned __int16 uint16;
*/
#else
#include 
typedef int_least32_t int32;
typedef int_least16_t int16;
typedef uint_least32_t uint32;
typedef uint_least16_t uint16;
#endif

Without these comments I get a load of errors about ambiguous symbol
int32 or something along those lines. Now however I'm getting a whole
new list of error all related to int32 and uint32. If I take out the
comments I get even worse errors:

1>c:\program files\microsoft visual studio 9.0\vc\include\ivec.h(96) :
warning C4190: '&' has C-linkage specified, but returns UDT 'M64'
which is incompatible with C
1>        c:\program files\microsoft visual studio
9.0\vc\include\ivec.h(77) : see declaration of 'M64'
1>c:\program files\microsoft visual studio 9.0\vc\include\ivec.h(97) :
warning C4190: '|' has C-linkage specified, but returns UDT 'M64'
which is incompatible with C
1>        c:\program files\microsoft visual studio
9.0\vc\include\ivec.h(77) : see declaration of 'M64'
(etc...)

The odd thing is, and wait for it, my old build still work fine. Both
projects link to the same libs and use the same header files. I've
even done comparisons of the project settings from the two projects
and apart from project name differences everything else is the same.
I'm at a lose to explain this, can anyone think of any reason this may
be happening or any way I can try to resolve this?

Rory.

------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

You are not using MSVC 2010, it may now have stdint.h, I will check on
that when I get home this evening.

Is this a native code project? It should be. If so, is it compiling C
or C++ code? Maybe it should be C++ code (that is, compile "C" as if
it were "C++"). THIS IS PROBABLY IT.

You may inadvertently be including some header that redefines things
you don't want redefined, try to simplify your problem with a stub
test file.

There also may be new int32 etc. definitions somwhere in the Microsoft
headers, as they gradually are becoming more and more "standard"
whatever that is.

Hope this helps,
Mike

On Thu, Sep 30, 2010 at 9:20 AM, Rory Walsh  wrote:
> I set up a new API project using MS Visual Express. I then copied
> project settings from a previous MSVE Csound host application and went
> to build. As soon as I include csound.hpp and try to build it
> complains about not recognising int32. In the past, because MSVC is
> defined, I would have always commented the MSVC stuff from sysdep.h as
> in:
>
> #ifdef MSVC
> /*
> typedef __int32 int32;
> typedef __int16 int16;
> typedef unsigned __int32 uint32;
> typedef unsigned __int16 uint16;
> */
> #else
> #include 
> typedef int_least32_t int32;
> typedef int_least16_t int16;
> typedef uint_least32_t uint32;
> typedef uint_least16_t uint16;
> #endif
>
> Without these comments I get a load of errors about ambiguous symbol
> int32 or something along those lines. Now however I'm getting a whole
> new list of error all related to int32 and uint32. If I take out the
> comments I get even worse errors:
>
> 1>c:\program files\microsoft visual studio 9.0\vc\include\ivec.h(96) :
> warning C4190: '&' has C-linkage specified, but returns UDT 'M64'
> which is incompatible with C
> 1>        c:\program files\microsoft visual studio
> 9.0\vc\include\ivec.h(77) : see declaration of 'M64'
> 1>c:\program files\microsoft visual studio 9.0\vc\include\ivec.h(97) :
> warning C4190: '|' has C-linkage specified, but returns UDT 'M64'
> which is incompatible with C
> 1>        c:\program files\microsoft visual studio
> 9.0\vc\include\ivec.h(77) : see declaration of 'M64'
> (etc...)
>
> The odd thing is, and wait for it, my old build still work fine. Both
> projects link to the same libs and use the same header files. I've
> even done comparisons of the project settings from the two projects
> and apart from project name differences everything else is the same.
> I'm at a lose to explain this, can anyone think of any reason this may
> be happening or any way I can try to resolve this?
>
> Rory.
>
> ------------------------------------------------------------------------------
> Start uncovering the many advantages of virtual appliances
> and start using them to simplify application deployment and
> accelerate your shift to cloud computing.
> http://p.sf.net/sfu/novell-sfdev2dev
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>



-- 
Michael Gogins
Irreducible Productions
http://www.michael-gogins.com
Michael dot Gogins at gmail dot com

------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Thanks Mike, I'll try to see this is the problem. I'll also try to
create a smaller sample project and see if I can spot what's up.
Hopefully you've given me enough info to figure out the problem!

Rory.


> Is this a native code project? It should be. If so, is it compiling C
> or C++ code? Maybe it should be C++ code (that is, compile "C" as if
> it were "C++"). THIS IS PROBABLY IT.

> You may inadvertently be including some header that redefines things
> you don't want redefined, try to simplify your problem with a stub
> test file.
>
> There also may be new int32 etc. definitions somwhere in the Microsoft
> headers, as they gradually are becoming more and more "standard"
> whatever that is.
>
> Hope this helps,
> Mike
>
> On Thu, Sep 30, 2010 at 9:20 AM, Rory Walsh  wrote:
>> I set up a new API project using MS Visual Express. I then copied
>> project settings from a previous MSVE Csound host application and went
>> to build. As soon as I include csound.hpp and try to build it
>> complains about not recognising int32. In the past, because MSVC is
>> defined, I would have always commented the MSVC stuff from sysdep.h as
>> in:
>>
>> #ifdef MSVC
>> /*
>> typedef __int32 int32;
>> typedef __int16 int16;
>> typedef unsigned __int32 uint32;
>> typedef unsigned __int16 uint16;
>> */
>> #else
>> #include 
>> typedef int_least32_t int32;
>> typedef int_least16_t int16;
>> typedef uint_least32_t uint32;
>> typedef uint_least16_t uint16;
>> #endif
>>
>> Without these comments I get a load of errors about ambiguous symbol
>> int32 or something along those lines. Now however I'm getting a whole
>> new list of error all related to int32 and uint32. If I take out the
>> comments I get even worse errors:
>>
>> 1>c:\program files\microsoft visual studio 9.0\vc\include\ivec.h(96) :
>> warning C4190: '&' has C-linkage specified, but returns UDT 'M64'
>> which is incompatible with C
>> 1>        c:\program files\microsoft visual studio
>> 9.0\vc\include\ivec.h(77) : see declaration of 'M64'
>> 1>c:\program files\microsoft visual studio 9.0\vc\include\ivec.h(97) :
>> warning C4190: '|' has C-linkage specified, but returns UDT 'M64'
>> which is incompatible with C
>> 1>        c:\program files\microsoft visual studio
>> 9.0\vc\include\ivec.h(77) : see declaration of 'M64'
>> (etc...)
>>
>> The odd thing is, and wait for it, my old build still work fine. Both
>> projects link to the same libs and use the same header files. I've
>> even done comparisons of the project settings from the two projects
>> and apart from project name differences everything else is the same.
>> I'm at a lose to explain this, can anyone think of any reason this may
>> be happening or any way I can try to resolve this?
>>
>> Rory.
>>
>> ------------------------------------------------------------------------------
>> Start uncovering the many advantages of virtual appliances
>> and start using them to simplify application deployment and
>> accelerate your shift to cloud computing.
>> http://p.sf.net/sfu/novell-sfdev2dev
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>
>
>
> --
> Michael Gogins
> Irreducible Productions
> http://www.michael-gogins.com
> Michael dot Gogins at gmail dot com
>
> ------------------------------------------------------------------------------
> Start uncovering the many advantages of virtual appliances
> and start using them to simplify application deployment and
> accelerate your shift to cloud computing.
> http://p.sf.net/sfu/novell-sfdev2dev
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>

------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

I'm trying again today to resolve this problem. Unfortunately a few
hours on Thursday is all I have to work on my own projects this
semester so I'm keen to find a fix if anyone can help. I've done as
Mike suggested and simplified the program completely. All I'm trying
to do now is to get the following lines of code to compile:

#include 
#include 

int main(){
return 0;
}

At this stage I'm not even linking to csound.lib. Compiling gives me a
load of errors regarding int32 in csound.h. As I mentioned previously,
I have working Csound projects but all my new projects suffer from the
same fate outlined above, I just can't see what the problem is?

Rory.





On 30 September 2010 16:34, Rory Walsh  wrote:
> Thanks Mike, I'll try to see this is the problem. I'll also try to
> create a smaller sample project and see if I can spot what's up.
> Hopefully you've given me enough info to figure out the problem!
>
> Rory.
>
>
>> Is this a native code project? It should be. If so, is it compiling C
>> or C++ code? Maybe it should be C++ code (that is, compile "C" as if
>> it were "C++"). THIS IS PROBABLY IT.
>
>> You may inadvertently be including some header that redefines things
>> you don't want redefined, try to simplify your problem with a stub
>> test file.
>>
>> There also may be new int32 etc. definitions somwhere in the Microsoft
>> headers, as they gradually are becoming more and more "standard"
>> whatever that is.
>>
>> Hope this helps,
>> Mike
>>
>> On Thu, Sep 30, 2010 at 9:20 AM, Rory Walsh  wrote:
>>> I set up a new API project using MS Visual Express. I then copied
>>> project settings from a previous MSVE Csound host application and went
>>> to build. As soon as I include csound.hpp and try to build it
>>> complains about not recognising int32. In the past, because MSVC is
>>> defined, I would have always commented the MSVC stuff from sysdep.h as
>>> in:
>>>
>>> #ifdef MSVC
>>> /*
>>> typedef __int32 int32;
>>> typedef __int16 int16;
>>> typedef unsigned __int32 uint32;
>>> typedef unsigned __int16 uint16;
>>> */
>>> #else
>>> #include 
>>> typedef int_least32_t int32;
>>> typedef int_least16_t int16;
>>> typedef uint_least32_t uint32;
>>> typedef uint_least16_t uint16;
>>> #endif
>>>
>>> Without these comments I get a load of errors about ambiguous symbol
>>> int32 or something along those lines. Now however I'm getting a whole
>>> new list of error all related to int32 and uint32. If I take out the
>>> comments I get even worse errors:
>>>
>>> 1>c:\program files\microsoft visual studio 9.0\vc\include\ivec.h(96) :
>>> warning C4190: '&' has C-linkage specified, but returns UDT 'M64'
>>> which is incompatible with C
>>> 1>        c:\program files\microsoft visual studio
>>> 9.0\vc\include\ivec.h(77) : see declaration of 'M64'
>>> 1>c:\program files\microsoft visual studio 9.0\vc\include\ivec.h(97) :
>>> warning C4190: '|' has C-linkage specified, but returns UDT 'M64'
>>> which is incompatible with C
>>> 1>        c:\program files\microsoft visual studio
>>> 9.0\vc\include\ivec.h(77) : see declaration of 'M64'
>>> (etc...)
>>>
>>> The odd thing is, and wait for it, my old build still work fine. Both
>>> projects link to the same libs and use the same header files. I've
>>> even done comparisons of the project settings from the two projects
>>> and apart from project name differences everything else is the same.
>>> I'm at a lose to explain this, can anyone think of any reason this may
>>> be happening or any way I can try to resolve this?
>>>
>>> Rory.
>>>
>>> ------------------------------------------------------------------------------
>>> Start uncovering the many advantages of virtual appliances
>>> and start using them to simplify application deployment and
>>> accelerate your shift to cloud computing.
>>> http://p.sf.net/sfu/novell-sfdev2dev
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>
>>
>>
>> --
>> Michael Gogins
>> Irreducible Productions
>> http://www.michael-gogins.com
>> Michael dot Gogins at gmail dot com
>>
>> ------------------------------------------------------------------------------
>> Start uncovering the many advantages of virtual appliances
>> and start using them to simplify application deployment and
>> accelerate your shift to cloud computing.
>> http://p.sf.net/sfu/novell-sfdev2dev
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>

------------------------------------------------------------------------------
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
Spend less time writing and  rewriting code and more time creating great
experiences on the web. Be a part of the beta today.
http://p.sf.net/sfu/beautyoftheweb
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

In fact, i seemed to have got around the problem with int 32, now I
get a load of error about ivec.h? I think this is to do with what Mike
mentioned about compiling C as if it were C++, here's the error:

1>c:\program files\microsoft visual studio 9.0\vc\include\ivec.h(96) :
warning C4190: '&' has C-linkage specified, but returns UDT 'M64'
which is incompatible with C
1>        c:\program files\microsoft visual studio
9.0\vc\include\ivec.h(77) : see declaration of 'M64'

There are hundreds of similar errors all relating to ivec.h, anyone
know how do I change it from C-linkage specified to C++-linkage
specifed?


On 7 October 2010 11:45, Rory Walsh  wrote:
> I'm trying again today to resolve this problem. Unfortunately a few
> hours on Thursday is all I have to work on my own projects this
> semester so I'm keen to find a fix if anyone can help. I've done as
> Mike suggested and simplified the program completely. All I'm trying
> to do now is to get the following lines of code to compile:
>
> #include 
> #include 
>
> int main(){
> return 0;
> }
>
> At this stage I'm not even linking to csound.lib. Compiling gives me a
> load of errors regarding int32 in csound.h. As I mentioned previously,
> I have working Csound projects but all my new projects suffer from the
> same fate outlined above, I just can't see what the problem is?
>
> Rory.
>
>
>
>
>
> On 30 September 2010 16:34, Rory Walsh  wrote:
>> Thanks Mike, I'll try to see this is the problem. I'll also try to
>> create a smaller sample project and see if I can spot what's up.
>> Hopefully you've given me enough info to figure out the problem!
>>
>> Rory.
>>
>>
>>> Is this a native code project? It should be. If so, is it compiling C
>>> or C++ code? Maybe it should be C++ code (that is, compile "C" as if
>>> it were "C++"). THIS IS PROBABLY IT.
>>
>>> You may inadvertently be including some header that redefines things
>>> you don't want redefined, try to simplify your problem with a stub
>>> test file.
>>>
>>> There also may be new int32 etc. definitions somwhere in the Microsoft
>>> headers, as they gradually are becoming more and more "standard"
>>> whatever that is.
>>>
>>> Hope this helps,
>>> Mike
>>>
>>> On Thu, Sep 30, 2010 at 9:20 AM, Rory Walsh  wrote:
>>>> I set up a new API project using MS Visual Express. I then copied
>>>> project settings from a previous MSVE Csound host application and went
>>>> to build. As soon as I include csound.hpp and try to build it
>>>> complains about not recognising int32. In the past, because MSVC is
>>>> defined, I would have always commented the MSVC stuff from sysdep.h as
>>>> in:
>>>>
>>>> #ifdef MSVC
>>>> /*
>>>> typedef __int32 int32;
>>>> typedef __int16 int16;
>>>> typedef unsigned __int32 uint32;
>>>> typedef unsigned __int16 uint16;
>>>> */
>>>> #else
>>>> #include 
>>>> typedef int_least32_t int32;
>>>> typedef int_least16_t int16;
>>>> typedef uint_least32_t uint32;
>>>> typedef uint_least16_t uint16;
>>>> #endif
>>>>
>>>> Without these comments I get a load of errors about ambiguous symbol
>>>> int32 or something along those lines. Now however I'm getting a whole
>>>> new list of error all related to int32 and uint32. If I take out the
>>>> comments I get even worse errors:
>>>>
>>>> 1>c:\program files\microsoft visual studio 9.0\vc\include\ivec.h(96) :
>>>> warning C4190: '&' has C-linkage specified, but returns UDT 'M64'
>>>> which is incompatible with C
>>>> 1>        c:\program files\microsoft visual studio
>>>> 9.0\vc\include\ivec.h(77) : see declaration of 'M64'
>>>> 1>c:\program files\microsoft visual studio 9.0\vc\include\ivec.h(97) :
>>>> warning C4190: '|' has C-linkage specified, but returns UDT 'M64'
>>>> which is incompatible with C
>>>> 1>        c:\program files\microsoft visual studio
>>>> 9.0\vc\include\ivec.h(77) : see declaration of 'M64'
>>>> (etc...)
>>>>
>>>> The odd thing is, and wait for it, my old build still work fine. Both
>>>> projects link to the same libs and use the same header files. I've
>>>> even done comparisons of the project settings from the two projects
>>>> and apart from project name differences everything else is the same.
>>>> I'm at a lose to explain this, can anyone think of any reason this may
>>>> be happening or any way I can try to resolve this?
>>>>
>>>> Rory.
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Start uncovering the many advantages of virtual appliances
>>>> and start using them to simplify application deployment and
>>>> accelerate your shift to cloud computing.
>>>> http://p.sf.net/sfu/novell-sfdev2dev
>>>> _______________________________________________
>>>> Csound-devel mailing list
>>>> Csound-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>
>>>
>>>
>>>
>>> --
>>> Michael Gogins
>>> Irreducible Productions
>>> http://www.michael-gogins.com
>>> Michael dot Gogins at gmail dot com
>>>
>>> ------------------------------------------------------------------------------
>>> Start uncovering the many advantages of virtual appliances
>>> and start using them to simplify application deployment and
>>> accelerate your shift to cloud computing.
>>> http://p.sf.net/sfu/novell-sfdev2dev
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>
>

------------------------------------------------------------------------------
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
Spend less time writing and  rewriting code and more time creating great
experiences on the web. Be a part of the beta today.
http://p.sf.net/sfu/beautyoftheweb
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Sorry, my previous post only showed the warning I'm getting, here are
some of the associated errors:

1>c:\program files\microsoft visual studio 9.0\vc\include\ivec.h(233)
: error C2733: second C linkage of overloaded function 'cmpeq' not
allowed
1>        c:\program files\microsoft visual studio
9.0\vc\include\ivec.h(233) : see declaration of 'cmpeq'
1>c:\program files\microsoft visual studio 9.0\vc\include\ivec.h(234)
: warning C4190: 'cmpneq' has C-linkage specified, but returns UDT
'Is32vec2' which is incompatible with C
1>        c:\program files\microsoft visual studio
9.0\vc\include\ivec.h(171) : see declaration of 'Is32vec2'
1>c:\program files\microsoft visual studio 9.0\vc\include\ivec.h(234)
: error C2733: second C linkage of overloaded function 'cmpneq' not
allowed
1>        c:\program files\microsoft visual studio
9.0\vc\include\ivec.h(234) : see declaration of 'cmpneq'
1>c:\program files\microsoft visual studio 9.0\vc\include\ivec.h(235)
: warning C4190: 'cmpgt' has C-linkage specified, but returns UDT
'Is32vec2' which is incompatible with C
1>        c:\program files\microsoft visual studio
9.0\vc\include\ivec.h(171) : see declaration of 'Is32vec2'


On 7 October 2010 11:51, Rory Walsh  wrote:
> In fact, i seemed to have got around the problem with int 32, now I
> get a load of error about ivec.h? I think this is to do with what Mike
> mentioned about compiling C as if it were C++, here's the error:
>
> 1>c:\program files\microsoft visual studio 9.0\vc\include\ivec.h(96) :
> warning C4190: '&' has C-linkage specified, but returns UDT 'M64'
> which is incompatible with C
> 1>        c:\program files\microsoft visual studio
> 9.0\vc\include\ivec.h(77) : see declaration of 'M64'
>
> There are hundreds of similar errors all relating to ivec.h, anyone
> know how do I change it from C-linkage specified to C++-linkage
> specifed?
>
>
> On 7 October 2010 11:45, Rory Walsh  wrote:
>> I'm trying again today to resolve this problem. Unfortunately a few
>> hours on Thursday is all I have to work on my own projects this
>> semester so I'm keen to find a fix if anyone can help. I've done as
>> Mike suggested and simplified the program completely. All I'm trying
>> to do now is to get the following lines of code to compile:
>>
>> #include 
>> #include 
>>
>> int main(){
>> return 0;
>> }
>>
>> At this stage I'm not even linking to csound.lib. Compiling gives me a
>> load of errors regarding int32 in csound.h. As I mentioned previously,
>> I have working Csound projects but all my new projects suffer from the
>> same fate outlined above, I just can't see what the problem is?
>>
>> Rory.
>>
>>
>>
>>
>>
>> On 30 September 2010 16:34, Rory Walsh  wrote:
>>> Thanks Mike, I'll try to see this is the problem. I'll also try to
>>> create a smaller sample project and see if I can spot what's up.
>>> Hopefully you've given me enough info to figure out the problem!
>>>
>>> Rory.
>>>
>>>
>>>> Is this a native code project? It should be. If so, is it compiling C
>>>> or C++ code? Maybe it should be C++ code (that is, compile "C" as if
>>>> it were "C++"). THIS IS PROBABLY IT.
>>>
>>>> You may inadvertently be including some header that redefines things
>>>> you don't want redefined, try to simplify your problem with a stub
>>>> test file.
>>>>
>>>> There also may be new int32 etc. definitions somwhere in the Microsoft
>>>> headers, as they gradually are becoming more and more "standard"
>>>> whatever that is.
>>>>
>>>> Hope this helps,
>>>> Mike
>>>>
>>>> On Thu, Sep 30, 2010 at 9:20 AM, Rory Walsh  wrote:
>>>>> I set up a new API project using MS Visual Express. I then copied
>>>>> project settings from a previous MSVE Csound host application and went
>>>>> to build. As soon as I include csound.hpp and try to build it
>>>>> complains about not recognising int32. In the past, because MSVC is
>>>>> defined, I would have always commented the MSVC stuff from sysdep.h as
>>>>> in:
>>>>>
>>>>> #ifdef MSVC
>>>>> /*
>>>>> typedef __int32 int32;
>>>>> typedef __int16 int16;
>>>>> typedef unsigned __int32 uint32;
>>>>> typedef unsigned __int16 uint16;
>>>>> */
>>>>> #else
>>>>> #include 
>>>>> typedef int_least32_t int32;
>>>>> typedef int_least16_t int16;
>>>>> typedef uint_least32_t uint32;
>>>>> typedef uint_least16_t uint16;
>>>>> #endif
>>>>>
>>>>> Without these comments I get a load of errors about ambiguous symbol
>>>>> int32 or something along those lines. Now however I'm getting a whole
>>>>> new list of error all related to int32 and uint32. If I take out the
>>>>> comments I get even worse errors:
>>>>>
>>>>> 1>c:\program files\microsoft visual studio 9.0\vc\include\ivec.h(96) :
>>>>> warning C4190: '&' has C-linkage specified, but returns UDT 'M64'
>>>>> which is incompatible with C
>>>>> 1>        c:\program files\microsoft visual studio
>>>>> 9.0\vc\include\ivec.h(77) : see declaration of 'M64'
>>>>> 1>c:\program files\microsoft visual studio 9.0\vc\include\ivec.h(97) :
>>>>> warning C4190: '|' has C-linkage specified, but returns UDT 'M64'
>>>>> which is incompatible with C
>>>>> 1>        c:\program files\microsoft visual studio
>>>>> 9.0\vc\include\ivec.h(77) : see declaration of 'M64'
>>>>> (etc...)
>>>>>
>>>>> The odd thing is, and wait for it, my old build still work fine. Both
>>>>> projects link to the same libs and use the same header files. I've
>>>>> even done comparisons of the project settings from the two projects
>>>>> and apart from project name differences everything else is the same.
>>>>> I'm at a lose to explain this, can anyone think of any reason this may
>>>>> be happening or any way I can try to resolve this?
>>>>>
>>>>> Rory.
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> Start uncovering the many advantages of virtual appliances
>>>>> and start using them to simplify application deployment and
>>>>> accelerate your shift to cloud computing.
>>>>> http://p.sf.net/sfu/novell-sfdev2dev
>>>>> _______________________________________________
>>>>> Csound-devel mailing list
>>>>> Csound-devel@lists.sourceforge.net
>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Michael Gogins
>>>> Irreducible Productions
>>>> http://www.michael-gogins.com
>>>> Michael dot Gogins at gmail dot com
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Start uncovering the many advantages of virtual appliances
>>>> and start using them to simplify application deployment and
>>>> accelerate your shift to cloud computing.
>>>> http://p.sf.net/sfu/novell-sfdev2dev
>>>> _______________________________________________
>>>> Csound-devel mailing list
>>>> Csound-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>
>>>
>>
>

------------------------------------------------------------------------------
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
Spend less time writing and  rewriting code and more time creating great
experiences on the web. Be a part of the beta today.
http://p.sf.net/sfu/beautyoftheweb
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Do you get the ivec.h errors when linking the same little program as before? Here's my workaround for the int32 issue, and this compiles nicely with no further errors.

#include 
typedef __int32 int32;
typedef unsigned __int32 uint32;
#include 

int main(){
 return 0;
}


Sigurd


-----Original Message-----
From: Rory Walsh [mailto:rorywalsh@ear.ie] 
Sent: 7. oktober 2010 12:52
To: Developer discussions
Subject: Re: [Cs-dev] help needed...MS Visual Express..int32...

In fact, i seemed to have got around the problem with int 32, now I
get a load of error about ivec.h? I think this is to do with what Mike
mentioned about compiling C as if it were C++, here's the error:

1>c:\program files\microsoft visual studio 9.0\vc\include\ivec.h(96) :
warning C4190: '&' has C-linkage specified, but returns UDT 'M64'
which is incompatible with C
1>        c:\program files\microsoft visual studio
9.0\vc\include\ivec.h(77) : see declaration of 'M64'

There are hundreds of similar errors all relating to ivec.h, anyone
know how do I change it from C-linkage specified to C++-linkage
specifed?


On 7 October 2010 11:45, Rory Walsh  wrote:
> I'm trying again today to resolve this problem. Unfortunately a few
> hours on Thursday is all I have to work on my own projects this
> semester so I'm keen to find a fix if anyone can help. I've done as
> Mike suggested and simplified the program completely. All I'm trying
> to do now is to get the following lines of code to compile:
>
> #include 
> #include 
>
> int main(){
> return 0;
> }
>
> At this stage I'm not even linking to csound.lib. Compiling gives me a
> load of errors regarding int32 in csound.h. As I mentioned previously,
> I have working Csound projects but all my new projects suffer from the
> same fate outlined above, I just can't see what the problem is?
>
> Rory.
>
>
>
>
>
> On 30 September 2010 16:34, Rory Walsh  wrote:
>> Thanks Mike, I'll try to see this is the problem. I'll also try to
>> create a smaller sample project and see if I can spot what's up.
>> Hopefully you've given me enough info to figure out the problem!
>>
>> Rory.
>>
>>
>>> Is this a native code project? It should be. If so, is it compiling C
>>> or C++ code? Maybe it should be C++ code (that is, compile "C" as if
>>> it were "C++"). THIS IS PROBABLY IT.
>>
>>> You may inadvertently be including some header that redefines things
>>> you don't want redefined, try to simplify your problem with a stub
>>> test file.
>>>
>>> There also may be new int32 etc. definitions somwhere in the Microsoft
>>> headers, as they gradually are becoming more and more "standard"
>>> whatever that is.
>>>
>>> Hope this helps,
>>> Mike
>>>
>>> On Thu, Sep 30, 2010 at 9:20 AM, Rory Walsh  wrote:
>>>> I set up a new API project using MS Visual Express. I then copied
>>>> project settings from a previous MSVE Csound host application and went
>>>> to build. As soon as I include csound.hpp and try to build it
>>>> complains about not recognising int32. In the past, because MSVC is
>>>> defined, I would have always commented the MSVC stuff from sysdep.h as
>>>> in:
>>>>
>>>> #ifdef MSVC
>>>> /*
>>>> typedef __int32 int32;
>>>> typedef __int16 int16;
>>>> typedef unsigned __int32 uint32;
>>>> typedef unsigned __int16 uint16;
>>>> */
>>>> #else
>>>> #include 
>>>> typedef int_least32_t int32;
>>>> typedef int_least16_t int16;
>>>> typedef uint_least32_t uint32;
>>>> typedef uint_least16_t uint16;
>>>> #endif
>>>>
>>>> Without these comments I get a load of errors about ambiguous symbol
>>>> int32 or something along those lines. Now however I'm getting a whole
>>>> new list of error all related to int32 and uint32. If I take out the
>>>> comments I get even worse errors:
>>>>
>>>> 1>c:\program files\microsoft visual studio 9.0\vc\include\ivec.h(96) :
>>>> warning C4190: '&' has C-linkage specified, but returns UDT 'M64'
>>>> which is incompatible with C
>>>> 1>        c:\program files\microsoft visual studio
>>>> 9.0\vc\include\ivec.h(77) : see declaration of 'M64'
>>>> 1>c:\program files\microsoft visual studio 9.0\vc\include\ivec.h(97) :
>>>> warning C4190: '|' has C-linkage specified, but returns UDT 'M64'
>>>> which is incompatible with C
>>>> 1>        c:\program files\microsoft visual studio
>>>> 9.0\vc\include\ivec.h(77) : see declaration of 'M64'
>>>> (etc...)
>>>>
>>>> The odd thing is, and wait for it, my old build still work fine. Both
>>>> projects link to the same libs and use the same header files. I've
>>>> even done comparisons of the project settings from the two projects
>>>> and apart from project name differences everything else is the same.
>>>> I'm at a lose to explain this, can anyone think of any reason this may
>>>> be happening or any way I can try to resolve this?
>>>>
>>>> Rory.
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Start uncovering the many advantages of virtual appliances
>>>> and start using them to simplify application deployment and
>>>> accelerate your shift to cloud computing.
>>>> http://p.sf.net/sfu/novell-sfdev2dev
>>>> _______________________________________________
>>>> Csound-devel mailing list
>>>> Csound-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>
>>>
>>>
>>>
>>> --
>>> Michael Gogins
>>> Irreducible Productions
>>> http://www.michael-gogins.com
>>> Michael dot Gogins at gmail dot com
>>>
>>> ------------------------------------------------------------------------------
>>> Start uncovering the many advantages of virtual appliances
>>> and start using them to simplify application deployment and
>>> accelerate your shift to cloud computing.
>>> http://p.sf.net/sfu/novell-sfdev2dev
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>
>

------------------------------------------------------------------------------
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
Spend less time writing and  rewriting code and more time creating great
experiences on the web. Be a part of the beta today.
http://p.sf.net/sfu/beautyoftheweb
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel


------------------------------------------------------------------------------
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
Spend less time writing and  rewriting code and more time creating great
experiences on the web. Be a part of the beta today.
http://p.sf.net/sfu/beautyoftheweb
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

The ivec.h errors are coming during the build process. I've been
trawling through forums in a bid to find the solution but I can't seem
to find anything concrete. According to Microsoft the error occurs
when: More than one overloaded function is declared with C linkage.
The version of VE I use on this machine is slightly newer than the one
I had on my laptop. It was on my laptop that I created all the Csound
project that work.It could be something to do with new headers, as
Mike had already suggested. I will try a simple test project on my
older version of Visual Express 2008 and see if it builds there.
Thanks for your reply.

Rory.


On 7 October 2010 13:12, Sigurd Saue  wrote:
> Do you get the ivec.h errors when linking the same little program as before? Here's my workaround for the int32 issue, and this compiles nicely with no further errors.
>
> #include 
> typedef __int32 int32;
> typedef unsigned __int32 uint32;
> #include 
>
> int main(){
>  return 0;
> }
>
>
> Sigurd
>
>
> -----Original Message-----
> From: Rory Walsh [mailto:rorywalsh@ear.ie]
> Sent: 7. oktober 2010 12:52
> To: Developer discussions
> Subject: Re: [Cs-dev] help needed...MS Visual Express..int32...
>
> In fact, i seemed to have got around the problem with int 32, now I
> get a load of error about ivec.h? I think this is to do with what Mike
> mentioned about compiling C as if it were C++, here's the error:
>
> 1>c:\program files\microsoft visual studio 9.0\vc\include\ivec.h(96) :
> warning C4190: '&' has C-linkage specified, but returns UDT 'M64'
> which is incompatible with C
> 1>        c:\program files\microsoft visual studio
> 9.0\vc\include\ivec.h(77) : see declaration of 'M64'
>
> There are hundreds of similar errors all relating to ivec.h, anyone
> know how do I change it from C-linkage specified to C++-linkage
> specifed?
>
>
> On 7 October 2010 11:45, Rory Walsh  wrote:
>> I'm trying again today to resolve this problem. Unfortunately a few
>> hours on Thursday is all I have to work on my own projects this
>> semester so I'm keen to find a fix if anyone can help. I've done as
>> Mike suggested and simplified the program completely. All I'm trying
>> to do now is to get the following lines of code to compile:
>>
>> #include 
>> #include 
>>
>> int main(){
>> return 0;
>> }
>>
>> At this stage I'm not even linking to csound.lib. Compiling gives me a
>> load of errors regarding int32 in csound.h. As I mentioned previously,
>> I have working Csound projects but all my new projects suffer from the
>> same fate outlined above, I just can't see what the problem is?
>>
>> Rory.
>>
>>
>>
>>
>>
>> On 30 September 2010 16:34, Rory Walsh  wrote:
>>> Thanks Mike, I'll try to see this is the problem. I'll also try to
>>> create a smaller sample project and see if I can spot what's up.
>>> Hopefully you've given me enough info to figure out the problem!
>>>
>>> Rory.
>>>
>>>
>>>> Is this a native code project? It should be. If so, is it compiling C
>>>> or C++ code? Maybe it should be C++ code (that is, compile "C" as if
>>>> it were "C++"). THIS IS PROBABLY IT.
>>>
>>>> You may inadvertently be including some header that redefines things
>>>> you don't want redefined, try to simplify your problem with a stub
>>>> test file.
>>>>
>>>> There also may be new int32 etc. definitions somwhere in the Microsoft
>>>> headers, as they gradually are becoming more and more "standard"
>>>> whatever that is.
>>>>
>>>> Hope this helps,
>>>> Mike
>>>>
>>>> On Thu, Sep 30, 2010 at 9:20 AM, Rory Walsh  wrote:
>>>>> I set up a new API project using MS Visual Express. I then copied
>>>>> project settings from a previous MSVE Csound host application and went
>>>>> to build. As soon as I include csound.hpp and try to build it
>>>>> complains about not recognising int32. In the past, because MSVC is
>>>>> defined, I would have always commented the MSVC stuff from sysdep.h as
>>>>> in:
>>>>>
>>>>> #ifdef MSVC
>>>>> /*
>>>>> typedef __int32 int32;
>>>>> typedef __int16 int16;
>>>>> typedef unsigned __int32 uint32;
>>>>> typedef unsigned __int16 uint16;
>>>>> */
>>>>> #else
>>>>> #include 
>>>>> typedef int_least32_t int32;
>>>>> typedef int_least16_t int16;
>>>>> typedef uint_least32_t uint32;
>>>>> typedef uint_least16_t uint16;
>>>>> #endif
>>>>>
>>>>> Without these comments I get a load of errors about ambiguous symbol
>>>>> int32 or something along those lines. Now however I'm getting a whole
>>>>> new list of error all related to int32 and uint32. If I take out the
>>>>> comments I get even worse errors:
>>>>>
>>>>> 1>c:\program files\microsoft visual studio 9.0\vc\include\ivec.h(96) :
>>>>> warning C4190: '&' has C-linkage specified, but returns UDT 'M64'
>>>>> which is incompatible with C
>>>>> 1>        c:\program files\microsoft visual studio
>>>>> 9.0\vc\include\ivec.h(77) : see declaration of 'M64'
>>>>> 1>c:\program files\microsoft visual studio 9.0\vc\include\ivec.h(97) :
>>>>> warning C4190: '|' has C-linkage specified, but returns UDT 'M64'
>>>>> which is incompatible with C
>>>>> 1>        c:\program files\microsoft visual studio
>>>>> 9.0\vc\include\ivec.h(77) : see declaration of 'M64'
>>>>> (etc...)
>>>>>
>>>>> The odd thing is, and wait for it, my old build still work fine. Both
>>>>> projects link to the same libs and use the same header files. I've
>>>>> even done comparisons of the project settings from the two projects
>>>>> and apart from project name differences everything else is the same.
>>>>> I'm at a lose to explain this, can anyone think of any reason this may
>>>>> be happening or any way I can try to resolve this?
>>>>>
>>>>> Rory.
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> Start uncovering the many advantages of virtual appliances
>>>>> and start using them to simplify application deployment and
>>>>> accelerate your shift to cloud computing.
>>>>> http://p.sf.net/sfu/novell-sfdev2dev
>>>>> _______________________________________________
>>>>> Csound-devel mailing list
>>>>> Csound-devel@lists.sourceforge.net
>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Michael Gogins
>>>> Irreducible Productions
>>>> http://www.michael-gogins.com
>>>> Michael dot Gogins at gmail dot com
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Start uncovering the many advantages of virtual appliances
>>>> and start using them to simplify application deployment and
>>>> accelerate your shift to cloud computing.
>>>> http://p.sf.net/sfu/novell-sfdev2dev
>>>> _______________________________________________
>>>> Csound-devel mailing list
>>>> Csound-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>
>>>
>>
>
> ------------------------------------------------------------------------------
> Beautiful is writing same markup. Internet Explorer 9 supports
> standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
> Spend less time writing and  rewriting code and more time creating great
> experiences on the web. Be a part of the beta today.
> http://p.sf.net/sfu/beautyoftheweb
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
> ------------------------------------------------------------------------------
> Beautiful is writing same markup. Internet Explorer 9 supports
> standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
> Spend less time writing and  rewriting code and more time creating great
> experiences on the web. Be a part of the beta today.
> http://p.sf.net/sfu/beautyoftheweb
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>

------------------------------------------------------------------------------
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
Spend less time writing and  rewriting code and more time creating great
experiences on the web. Be a part of the beta today.
http://p.sf.net/sfu/beautyoftheweb
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

#define MSVC should fix it.

Regards,
Mike

On Thu, Oct 7, 2010 at 8:25 AM, Rory Walsh  wrote:
> The ivec.h errors are coming during the build process. I've been
> trawling through forums in a bid to find the solution but I can't seem
> to find anything concrete. According to Microsoft the error occurs
> when: More than one overloaded function is declared with C linkage.
> The version of VE I use on this machine is slightly newer than the one
> I had on my laptop. It was on my laptop that I created all the Csound
> project that work.It could be something to do with new headers, as
> Mike had already suggested. I will try a simple test project on my
> older version of Visual Express 2008 and see if it builds there.
> Thanks for your reply.
>
> Rory.
>
>
> On 7 October 2010 13:12, Sigurd Saue  wrote:
>> Do you get the ivec.h errors when linking the same little program as before? Here's my workaround for the int32 issue, and this compiles nicely with no further errors.
>>
>> #include 
>> typedef __int32 int32;
>> typedef unsigned __int32 uint32;
>> #include 
>>
>> int main(){
>>  return 0;
>> }
>>
>>
>> Sigurd
>>
>>
>> -----Original Message-----
>> From: Rory Walsh [mailto:rorywalsh@ear.ie]
>> Sent: 7. oktober 2010 12:52
>> To: Developer discussions
>> Subject: Re: [Cs-dev] help needed...MS Visual Express..int32...
>>
>> In fact, i seemed to have got around the problem with int 32, now I
>> get a load of error about ivec.h? I think this is to do with what Mike
>> mentioned about compiling C as if it were C++, here's the error:
>>
>> 1>c:\program files\microsoft visual studio 9.0\vc\include\ivec.h(96) :
>> warning C4190: '&' has C-linkage specified, but returns UDT 'M64'
>> which is incompatible with C
>> 1>        c:\program files\microsoft visual studio
>> 9.0\vc\include\ivec.h(77) : see declaration of 'M64'
>>
>> There are hundreds of similar errors all relating to ivec.h, anyone
>> know how do I change it from C-linkage specified to C++-linkage
>> specifed?
>>
>>
>> On 7 October 2010 11:45, Rory Walsh  wrote:
>>> I'm trying again today to resolve this problem. Unfortunately a few
>>> hours on Thursday is all I have to work on my own projects this
>>> semester so I'm keen to find a fix if anyone can help. I've done as
>>> Mike suggested and simplified the program completely. All I'm trying
>>> to do now is to get the following lines of code to compile:
>>>
>>> #include 
>>> #include 
>>>
>>> int main(){
>>> return 0;
>>> }
>>>
>>> At this stage I'm not even linking to csound.lib. Compiling gives me a
>>> load of errors regarding int32 in csound.h. As I mentioned previously,
>>> I have working Csound projects but all my new projects suffer from the
>>> same fate outlined above, I just can't see what the problem is?
>>>
>>> Rory.
>>>
>>>
>>>
>>>
>>>
>>> On 30 September 2010 16:34, Rory Walsh  wrote:
>>>> Thanks Mike, I'll try to see this is the problem. I'll also try to
>>>> create a smaller sample project and see if I can spot what's up.
>>>> Hopefully you've given me enough info to figure out the problem!
>>>>
>>>> Rory.
>>>>
>>>>
>>>>> Is this a native code project? It should be. If so, is it compiling C
>>>>> or C++ code? Maybe it should be C++ code (that is, compile "C" as if
>>>>> it were "C++"). THIS IS PROBABLY IT.
>>>>
>>>>> You may inadvertently be including some header that redefines things
>>>>> you don't want redefined, try to simplify your problem with a stub
>>>>> test file.
>>>>>
>>>>> There also may be new int32 etc. definitions somwhere in the Microsoft
>>>>> headers, as they gradually are becoming more and more "standard"
>>>>> whatever that is.
>>>>>
>>>>> Hope this helps,
>>>>> Mike
>>>>>
>>>>> On Thu, Sep 30, 2010 at 9:20 AM, Rory Walsh  wrote:
>>>>>> I set up a new API project using MS Visual Express. I then copied
>>>>>> project settings from a previous MSVE Csound host application and went
>>>>>> to build. As soon as I include csound.hpp and try to build it
>>>>>> complains about not recognising int32. In the past, because MSVC is
>>>>>> defined, I would have always commented the MSVC stuff from sysdep.h as
>>>>>> in:
>>>>>>
>>>>>> #ifdef MSVC
>>>>>> /*
>>>>>> typedef __int32 int32;
>>>>>> typedef __int16 int16;
>>>>>> typedef unsigned __int32 uint32;
>>>>>> typedef unsigned __int16 uint16;
>>>>>> */
>>>>>> #else
>>>>>> #include 
>>>>>> typedef int_least32_t int32;
>>>>>> typedef int_least16_t int16;
>>>>>> typedef uint_least32_t uint32;
>>>>>> typedef uint_least16_t uint16;
>>>>>> #endif
>>>>>>
>>>>>> Without these comments I get a load of errors about ambiguous symbol
>>>>>> int32 or something along those lines. Now however I'm getting a whole
>>>>>> new list of error all related to int32 and uint32. If I take out the
>>>>>> comments I get even worse errors:
>>>>>>
>>>>>> 1>c:\program files\microsoft visual studio 9.0\vc\include\ivec.h(96) :
>>>>>> warning C4190: '&' has C-linkage specified, but returns UDT 'M64'
>>>>>> which is incompatible with C
>>>>>> 1>        c:\program files\microsoft visual studio
>>>>>> 9.0\vc\include\ivec.h(77) : see declaration of 'M64'
>>>>>> 1>c:\program files\microsoft visual studio 9.0\vc\include\ivec.h(97) :
>>>>>> warning C4190: '|' has C-linkage specified, but returns UDT 'M64'
>>>>>> which is incompatible with C
>>>>>> 1>        c:\program files\microsoft visual studio
>>>>>> 9.0\vc\include\ivec.h(77) : see declaration of 'M64'
>>>>>> (etc...)
>>>>>>
>>>>>> The odd thing is, and wait for it, my old build still work fine. Both
>>>>>> projects link to the same libs and use the same header files. I've
>>>>>> even done comparisons of the project settings from the two projects
>>>>>> and apart from project name differences everything else is the same.
>>>>>> I'm at a lose to explain this, can anyone think of any reason this may
>>>>>> be happening or any way I can try to resolve this?
>>>>>>
>>>>>> Rory.
>>>>>>
>>>>>> ------------------------------------------------------------------------------
>>>>>> Start uncovering the many advantages of virtual appliances
>>>>>> and start using them to simplify application deployment and
>>>>>> accelerate your shift to cloud computing.
>>>>>> http://p.sf.net/sfu/novell-sfdev2dev
>>>>>> _______________________________________________
>>>>>> Csound-devel mailing list
>>>>>> Csound-devel@lists.sourceforge.net
>>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Michael Gogins
>>>>> Irreducible Productions
>>>>> http://www.michael-gogins.com
>>>>> Michael dot Gogins at gmail dot com
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> Start uncovering the many advantages of virtual appliances
>>>>> and start using them to simplify application deployment and
>>>>> accelerate your shift to cloud computing.
>>>>> http://p.sf.net/sfu/novell-sfdev2dev
>>>>> _______________________________________________
>>>>> Csound-devel mailing list
>>>>> Csound-devel@lists.sourceforge.net
>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>
>>>>
>>>
>>
>> ------------------------------------------------------------------------------
>> Beautiful is writing same markup. Internet Explorer 9 supports
>> standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
>> Spend less time writing and  rewriting code and more time creating great
>> experiences on the web. Be a part of the beta today.
>> http://p.sf.net/sfu/beautyoftheweb
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>>
>> ------------------------------------------------------------------------------
>> Beautiful is writing same markup. Internet Explorer 9 supports
>> standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
>> Spend less time writing and  rewriting code and more time creating great
>> experiences on the web. Be a part of the beta today.
>> http://p.sf.net/sfu/beautyoftheweb
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>
> ------------------------------------------------------------------------------
> Beautiful is writing same markup. Internet Explorer 9 supports
> standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
> Spend less time writing and  rewriting code and more time creating great
> experiences on the web. Be a part of the beta today.
> http://p.sf.net/sfu/beautyoftheweb
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>



-- 
Michael Gogins
Irreducible Productions
http://www.michael-gogins.com
Michael dot Gogins at gmail dot com

------------------------------------------------------------------------------
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
Spend less time writing and  rewriting code and more time creating great
experiences on the web. Be a part of the beta today.
http://p.sf.net/sfu/beautyoftheweb
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

By the way: Some issue with ivec.h was discussed on this list a long time ago:
http://csound.1045644.n5.nabble.com/MSVC-build-issue-td1130778.html

Could that be related?

Sigurd


-----Original Message-----
From: Rory Walsh [mailto:rorywalsh@ear.ie] 
Sent: 7. oktober 2010 14:26
To: Developer discussions
Subject: Re: [Cs-dev] help needed...MS Visual Express..int32...

The ivec.h errors are coming during the build process. I've been
trawling through forums in a bid to find the solution but I can't seem
to find anything concrete. According to Microsoft the error occurs
when: More than one overloaded function is declared with C linkage.
The version of VE I use on this machine is slightly newer than the one
I had on my laptop. It was on my laptop that I created all the Csound
project that work.It could be something to do with new headers, as
Mike had already suggested. I will try a simple test project on my
older version of Visual Express 2008 and see if it builds there.
Thanks for your reply.

Rory.


On 7 October 2010 13:12, Sigurd Saue  wrote:
> Do you get the ivec.h errors when linking the same little program as before? Here's my workaround for the int32 issue, and this compiles nicely with no further errors.
>
> #include 
> typedef __int32 int32;
> typedef unsigned __int32 uint32;
> #include 
>
> int main(){
>  return 0;
> }
>
>
> Sigurd
>
>
> -----Original Message-----
> From: Rory Walsh [mailto:rorywalsh@ear.ie]
> Sent: 7. oktober 2010 12:52
> To: Developer discussions
> Subject: Re: [Cs-dev] help needed...MS Visual Express..int32...
>
> In fact, i seemed to have got around the problem with int 32, now I
> get a load of error about ivec.h? I think this is to do with what Mike
> mentioned about compiling C as if it were C++, here's the error:
>
> 1>c:\program files\microsoft visual studio 9.0\vc\include\ivec.h(96) :
> warning C4190: '&' has C-linkage specified, but returns UDT 'M64'
> which is incompatible with C
> 1>        c:\program files\microsoft visual studio
> 9.0\vc\include\ivec.h(77) : see declaration of 'M64'
>
> There are hundreds of similar errors all relating to ivec.h, anyone
> know how do I change it from C-linkage specified to C++-linkage
> specifed?
>
>
> On 7 October 2010 11:45, Rory Walsh  wrote:
>> I'm trying again today to resolve this problem. Unfortunately a few
>> hours on Thursday is all I have to work on my own projects this
>> semester so I'm keen to find a fix if anyone can help. I've done as
>> Mike suggested and simplified the program completely. All I'm trying
>> to do now is to get the following lines of code to compile:
>>
>> #include 
>> #include 
>>
>> int main(){
>> return 0;
>> }
>>
>> At this stage I'm not even linking to csound.lib. Compiling gives me a
>> load of errors regarding int32 in csound.h. As I mentioned previously,
>> I have working Csound projects but all my new projects suffer from the
>> same fate outlined above, I just can't see what the problem is?
>>
>> Rory.
>>
>>
>>
>>
>>
>> On 30 September 2010 16:34, Rory Walsh  wrote:
>>> Thanks Mike, I'll try to see this is the problem. I'll also try to
>>> create a smaller sample project and see if I can spot what's up.
>>> Hopefully you've given me enough info to figure out the problem!
>>>
>>> Rory.
>>>
>>>
>>>> Is this a native code project? It should be. If so, is it compiling C
>>>> or C++ code? Maybe it should be C++ code (that is, compile "C" as if
>>>> it were "C++"). THIS IS PROBABLY IT.
>>>
>>>> You may inadvertently be including some header that redefines things
>>>> you don't want redefined, try to simplify your problem with a stub
>>>> test file.
>>>>
>>>> There also may be new int32 etc. definitions somwhere in the Microsoft
>>>> headers, as they gradually are becoming more and more "standard"
>>>> whatever that is.
>>>>
>>>> Hope this helps,
>>>> Mike
>>>>
>>>> On Thu, Sep 30, 2010 at 9:20 AM, Rory Walsh  wrote:
>>>>> I set up a new API project using MS Visual Express. I then copied
>>>>> project settings from a previous MSVE Csound host application and went
>>>>> to build. As soon as I include csound.hpp and try to build it
>>>>> complains about not recognising int32. In the past, because MSVC is
>>>>> defined, I would have always commented the MSVC stuff from sysdep.h as
>>>>> in:
>>>>>
>>>>> #ifdef MSVC
>>>>> /*
>>>>> typedef __int32 int32;
>>>>> typedef __int16 int16;
>>>>> typedef unsigned __int32 uint32;
>>>>> typedef unsigned __int16 uint16;
>>>>> */
>>>>> #else
>>>>> #include 
>>>>> typedef int_least32_t int32;
>>>>> typedef int_least16_t int16;
>>>>> typedef uint_least32_t uint32;
>>>>> typedef uint_least16_t uint16;
>>>>> #endif
>>>>>
>>>>> Without these comments I get a load of errors about ambiguous symbol
>>>>> int32 or something along those lines. Now however I'm getting a whole
>>>>> new list of error all related to int32 and uint32. If I take out the
>>>>> comments I get even worse errors:
>>>>>
>>>>> 1>c:\program files\microsoft visual studio 9.0\vc\include\ivec.h(96) :
>>>>> warning C4190: '&' has C-linkage specified, but returns UDT 'M64'
>>>>> which is incompatible with C
>>>>> 1>        c:\program files\microsoft visual studio
>>>>> 9.0\vc\include\ivec.h(77) : see declaration of 'M64'
>>>>> 1>c:\program files\microsoft visual studio 9.0\vc\include\ivec.h(97) :
>>>>> warning C4190: '|' has C-linkage specified, but returns UDT 'M64'
>>>>> which is incompatible with C
>>>>> 1>        c:\program files\microsoft visual studio
>>>>> 9.0\vc\include\ivec.h(77) : see declaration of 'M64'
>>>>> (etc...)
>>>>>
>>>>> The odd thing is, and wait for it, my old build still work fine. Both
>>>>> projects link to the same libs and use the same header files. I've
>>>>> even done comparisons of the project settings from the two projects
>>>>> and apart from project name differences everything else is the same.
>>>>> I'm at a lose to explain this, can anyone think of any reason this may
>>>>> be happening or any way I can try to resolve this?
>>>>>
>>>>> Rory.
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> Start uncovering the many advantages of virtual appliances
>>>>> and start using them to simplify application deployment and
>>>>> accelerate your shift to cloud computing.
>>>>> http://p.sf.net/sfu/novell-sfdev2dev
>>>>> _______________________________________________
>>>>> Csound-devel mailing list
>>>>> Csound-devel@lists.sourceforge.net
>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Michael Gogins
>>>> Irreducible Productions
>>>> http://www.michael-gogins.com
>>>> Michael dot Gogins at gmail dot com
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Start uncovering the many advantages of virtual appliances
>>>> and start using them to simplify application deployment and
>>>> accelerate your shift to cloud computing.
>>>> http://p.sf.net/sfu/novell-sfdev2dev
>>>> _______________________________________________
>>>> Csound-devel mailing list
>>>> Csound-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>
>>>
>>
>
> ------------------------------------------------------------------------------
> Beautiful is writing same markup. Internet Explorer 9 supports
> standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
> Spend less time writing and  rewriting code and more time creating great
> experiences on the web. Be a part of the beta today.
> http://p.sf.net/sfu/beautyoftheweb
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
> ------------------------------------------------------------------------------
> Beautiful is writing same markup. Internet Explorer 9 supports
> standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
> Spend less time writing and  rewriting code and more time creating great
> experiences on the web. Be a part of the beta today.
> http://p.sf.net/sfu/beautyoftheweb
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>

------------------------------------------------------------------------------
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
Spend less time writing and  rewriting code and more time creating great
experiences on the web. Be a part of the beta today.
http://p.sf.net/sfu/beautyoftheweb
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel


------------------------------------------------------------------------------
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
Spend less time writing and  rewriting code and more time creating great
experiences on the web. Be a part of the beta today.
http://p.sf.net/sfu/beautyoftheweb
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Indeed it is, I can't believe I didn't check the list for ivec.h!
Following Andy's advice allows me to build.

Rory.


On 7 October 2010 14:01, Sigurd Saue  wrote:
> By the way: Some issue with ivec.h was discussed on this list a long time ago:
> http://csound.1045644.n5.nabble.com/MSVC-build-issue-td1130778.html
>
> Could that be related?
>
> Sigurd
>
>
> -----Original Message-----
> From: Rory Walsh [mailto:rorywalsh@ear.ie]
> Sent: 7. oktober 2010 14:26
> To: Developer discussions
> Subject: Re: [Cs-dev] help needed...MS Visual Express..int32...
>
> The ivec.h errors are coming during the build process. I've been
> trawling through forums in a bid to find the solution but I can't seem
> to find anything concrete. According to Microsoft the error occurs
> when: More than one overloaded function is declared with C linkage.
> The version of VE I use on this machine is slightly newer than the one
> I had on my laptop. It was on my laptop that I created all the Csound
> project that work.It could be something to do with new headers, as
> Mike had already suggested. I will try a simple test project on my
> older version of Visual Express 2008 and see if it builds there.
> Thanks for your reply.
>
> Rory.
>
>
> On 7 October 2010 13:12, Sigurd Saue  wrote:
>> Do you get the ivec.h errors when linking the same little program as before? Here's my workaround for the int32 issue, and this compiles nicely with no further errors.
>>
>> #include 
>> typedef __int32 int32;
>> typedef unsigned __int32 uint32;
>> #include 
>>
>> int main(){
>>  return 0;
>> }
>>
>>
>> Sigurd
>>
>>
>> -----Original Message-----
>> From: Rory Walsh [mailto:rorywalsh@ear.ie]
>> Sent: 7. oktober 2010 12:52
>> To: Developer discussions
>> Subject: Re: [Cs-dev] help needed...MS Visual Express..int32...
>>
>> In fact, i seemed to have got around the problem with int 32, now I
>> get a load of error about ivec.h? I think this is to do with what Mike
>> mentioned about compiling C as if it were C++, here's the error:
>>
>> 1>c:\program files\microsoft visual studio 9.0\vc\include\ivec.h(96) :
>> warning C4190: '&' has C-linkage specified, but returns UDT 'M64'
>> which is incompatible with C
>> 1>        c:\program files\microsoft visual studio
>> 9.0\vc\include\ivec.h(77) : see declaration of 'M64'
>>
>> There are hundreds of similar errors all relating to ivec.h, anyone
>> know how do I change it from C-linkage specified to C++-linkage
>> specifed?
>>
>>
>> On 7 October 2010 11:45, Rory Walsh  wrote:
>>> I'm trying again today to resolve this problem. Unfortunately a few
>>> hours on Thursday is all I have to work on my own projects this
>>> semester so I'm keen to find a fix if anyone can help. I've done as
>>> Mike suggested and simplified the program completely. All I'm trying
>>> to do now is to get the following lines of code to compile:
>>>
>>> #include 
>>> #include 
>>>
>>> int main(){
>>> return 0;
>>> }
>>>
>>> At this stage I'm not even linking to csound.lib. Compiling gives me a
>>> load of errors regarding int32 in csound.h. As I mentioned previously,
>>> I have working Csound projects but all my new projects suffer from the
>>> same fate outlined above, I just can't see what the problem is?
>>>
>>> Rory.
>>>
>>>
>>>
>>>
>>>
>>> On 30 September 2010 16:34, Rory Walsh  wrote:
>>>> Thanks Mike, I'll try to see this is the problem. I'll also try to
>>>> create a smaller sample project and see if I can spot what's up.
>>>> Hopefully you've given me enough info to figure out the problem!
>>>>
>>>> Rory.
>>>>
>>>>
>>>>> Is this a native code project? It should be. If so, is it compiling C
>>>>> or C++ code? Maybe it should be C++ code (that is, compile "C" as if
>>>>> it were "C++"). THIS IS PROBABLY IT.
>>>>
>>>>> You may inadvertently be including some header that redefines things
>>>>> you don't want redefined, try to simplify your problem with a stub
>>>>> test file.
>>>>>
>>>>> There also may be new int32 etc. definitions somwhere in the Microsoft
>>>>> headers, as they gradually are becoming more and more "standard"
>>>>> whatever that is.
>>>>>
>>>>> Hope this helps,
>>>>> Mike
>>>>>
>>>>> On Thu, Sep 30, 2010 at 9:20 AM, Rory Walsh  wrote:
>>>>>> I set up a new API project using MS Visual Express. I then copied
>>>>>> project settings from a previous MSVE Csound host application and went
>>>>>> to build. As soon as I include csound.hpp and try to build it
>>>>>> complains about not recognising int32. In the past, because MSVC is
>>>>>> defined, I would have always commented the MSVC stuff from sysdep.h as
>>>>>> in:
>>>>>>
>>>>>> #ifdef MSVC
>>>>>> /*
>>>>>> typedef __int32 int32;
>>>>>> typedef __int16 int16;
>>>>>> typedef unsigned __int32 uint32;
>>>>>> typedef unsigned __int16 uint16;
>>>>>> */
>>>>>> #else
>>>>>> #include 
>>>>>> typedef int_least32_t int32;
>>>>>> typedef int_least16_t int16;
>>>>>> typedef uint_least32_t uint32;
>>>>>> typedef uint_least16_t uint16;
>>>>>> #endif
>>>>>>
>>>>>> Without these comments I get a load of errors about ambiguous symbol
>>>>>> int32 or something along those lines. Now however I'm getting a whole
>>>>>> new list of error all related to int32 and uint32. If I take out the
>>>>>> comments I get even worse errors:
>>>>>>
>>>>>> 1>c:\program files\microsoft visual studio 9.0\vc\include\ivec.h(96) :
>>>>>> warning C4190: '&' has C-linkage specified, but returns UDT 'M64'
>>>>>> which is incompatible with C
>>>>>> 1>        c:\program files\microsoft visual studio
>>>>>> 9.0\vc\include\ivec.h(77) : see declaration of 'M64'
>>>>>> 1>c:\program files\microsoft visual studio 9.0\vc\include\ivec.h(97) :
>>>>>> warning C4190: '|' has C-linkage specified, but returns UDT 'M64'
>>>>>> which is incompatible with C
>>>>>> 1>        c:\program files\microsoft visual studio
>>>>>> 9.0\vc\include\ivec.h(77) : see declaration of 'M64'
>>>>>> (etc...)
>>>>>>
>>>>>> The odd thing is, and wait for it, my old build still work fine. Both
>>>>>> projects link to the same libs and use the same header files. I've
>>>>>> even done comparisons of the project settings from the two projects
>>>>>> and apart from project name differences everything else is the same.
>>>>>> I'm at a lose to explain this, can anyone think of any reason this may
>>>>>> be happening or any way I can try to resolve this?
>>>>>>
>>>>>> Rory.
>>>>>>
>>>>>> ------------------------------------------------------------------------------
>>>>>> Start uncovering the many advantages of virtual appliances
>>>>>> and start using them to simplify application deployment and
>>>>>> accelerate your shift to cloud computing.
>>>>>> http://p.sf.net/sfu/novell-sfdev2dev
>>>>>> _______________________________________________
>>>>>> Csound-devel mailing list
>>>>>> Csound-devel@lists.sourceforge.net
>>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Michael Gogins
>>>>> Irreducible Productions
>>>>> http://www.michael-gogins.com
>>>>> Michael dot Gogins at gmail dot com
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> Start uncovering the many advantages of virtual appliances
>>>>> and start using them to simplify application deployment and
>>>>> accelerate your shift to cloud computing.
>>>>> http://p.sf.net/sfu/novell-sfdev2dev
>>>>> _______________________________________________
>>>>> Csound-devel mailing list
>>>>> Csound-devel@lists.sourceforge.net
>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>
>>>>
>>>
>>
>> ------------------------------------------------------------------------------
>> Beautiful is writing same markup. Internet Explorer 9 supports
>> standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
>> Spend less time writing and  rewriting code and more time creating great
>> experiences on the web. Be a part of the beta today.
>> http://p.sf.net/sfu/beautyoftheweb
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>>
>> ------------------------------------------------------------------------------
>> Beautiful is writing same markup. Internet Explorer 9 supports
>> standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
>> Spend less time writing and  rewriting code and more time creating great
>> experiences on the web. Be a part of the beta today.
>> http://p.sf.net/sfu/beautyoftheweb
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>
> ------------------------------------------------------------------------------
> Beautiful is writing same markup. Internet Explorer 9 supports
> standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
> Spend less time writing and  rewriting code and more time creating great
> experiences on the web. Be a part of the beta today.
> http://p.sf.net/sfu/beautyoftheweb
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
> ------------------------------------------------------------------------------
> Beautiful is writing same markup. Internet Explorer 9 supports
> standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
> Spend less time writing and  rewriting code and more time creating great
> experiences on the web. Be a part of the beta today.
> http://p.sf.net/sfu/beautyoftheweb
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>

------------------------------------------------------------------------------
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
Spend less time writing and  rewriting code and more time creating great
experiences on the web. Be a part of the beta today.
http://p.sf.net/sfu/beautyoftheweb
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Thanks Mike, I had that defined already. A post last year to this list
from Andy contains the solution. Thanks for everyone's help, hopefully
this is the end of it!

On 7 October 2010 14:00, Michael Gogins  wrote:
> #define MSVC should fix it.
>
> Regards,
> Mike
>
> On Thu, Oct 7, 2010 at 8:25 AM, Rory Walsh  wrote:
>> The ivec.h errors are coming during the build process. I've been
>> trawling through forums in a bid to find the solution but I can't seem
>> to find anything concrete. According to Microsoft the error occurs
>> when: More than one overloaded function is declared with C linkage.
>> The version of VE I use on this machine is slightly newer than the one
>> I had on my laptop. It was on my laptop that I created all the Csound
>> project that work.It could be something to do with new headers, as
>> Mike had already suggested. I will try a simple test project on my
>> older version of Visual Express 2008 and see if it builds there.
>> Thanks for your reply.
>>
>> Rory.
>>
>>
>> On 7 October 2010 13:12, Sigurd Saue  wrote:
>>> Do you get the ivec.h errors when linking the same little program as before? Here's my workaround for the int32 issue, and this compiles nicely with no further errors.
>>>
>>> #include 
>>> typedef __int32 int32;
>>> typedef unsigned __int32 uint32;
>>> #include 
>>>
>>> int main(){
>>>  return 0;
>>> }
>>>
>>>
>>> Sigurd
>>>
>>>
>>> -----Original Message-----
>>> From: Rory Walsh [mailto:rorywalsh@ear.ie]
>>> Sent: 7. oktober 2010 12:52
>>> To: Developer discussions
>>> Subject: Re: [Cs-dev] help needed...MS Visual Express..int32...
>>>
>>> In fact, i seemed to have got around the problem with int 32, now I
>>> get a load of error about ivec.h? I think this is to do with what Mike
>>> mentioned about compiling C as if it were C++, here's the error:
>>>
>>> 1>c:\program files\microsoft visual studio 9.0\vc\include\ivec.h(96) :
>>> warning C4190: '&' has C-linkage specified, but returns UDT 'M64'
>>> which is incompatible with C
>>> 1>        c:\program files\microsoft visual studio
>>> 9.0\vc\include\ivec.h(77) : see declaration of 'M64'
>>>
>>> There are hundreds of similar errors all relating to ivec.h, anyone
>>> know how do I change it from C-linkage specified to C++-linkage
>>> specifed?
>>>
>>>
>>> On 7 October 2010 11:45, Rory Walsh  wrote:
>>>> I'm trying again today to resolve this problem. Unfortunately a few
>>>> hours on Thursday is all I have to work on my own projects this
>>>> semester so I'm keen to find a fix if anyone can help. I've done as
>>>> Mike suggested and simplified the program completely. All I'm trying
>>>> to do now is to get the following lines of code to compile:
>>>>
>>>> #include 
>>>> #include 
>>>>
>>>> int main(){
>>>> return 0;
>>>> }
>>>>
>>>> At this stage I'm not even linking to csound.lib. Compiling gives me a
>>>> load of errors regarding int32 in csound.h. As I mentioned previously,
>>>> I have working Csound projects but all my new projects suffer from the
>>>> same fate outlined above, I just can't see what the problem is?
>>>>
>>>> Rory.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On 30 September 2010 16:34, Rory Walsh  wrote:
>>>>> Thanks Mike, I'll try to see this is the problem. I'll also try to
>>>>> create a smaller sample project and see if I can spot what's up.
>>>>> Hopefully you've given me enough info to figure out the problem!
>>>>>
>>>>> Rory.
>>>>>
>>>>>
>>>>>> Is this a native code project? It should be. If so, is it compiling C
>>>>>> or C++ code? Maybe it should be C++ code (that is, compile "C" as if
>>>>>> it were "C++"). THIS IS PROBABLY IT.
>>>>>
>>>>>> You may inadvertently be including some header that redefines things
>>>>>> you don't want redefined, try to simplify your problem with a stub
>>>>>> test file.
>>>>>>
>>>>>> There also may be new int32 etc. definitions somwhere in the Microsoft
>>>>>> headers, as they gradually are becoming more and more "standard"
>>>>>> whatever that is.
>>>>>>
>>>>>> Hope this helps,
>>>>>> Mike
>>>>>>
>>>>>> On Thu, Sep 30, 2010 at 9:20 AM, Rory Walsh  wrote:
>>>>>>> I set up a new API project using MS Visual Express. I then copied
>>>>>>> project settings from a previous MSVE Csound host application and went
>>>>>>> to build. As soon as I include csound.hpp and try to build it
>>>>>>> complains about not recognising int32. In the past, because MSVC is
>>>>>>> defined, I would have always commented the MSVC stuff from sysdep.h as
>>>>>>> in:
>>>>>>>
>>>>>>> #ifdef MSVC
>>>>>>> /*
>>>>>>> typedef __int32 int32;
>>>>>>> typedef __int16 int16;
>>>>>>> typedef unsigned __int32 uint32;
>>>>>>> typedef unsigned __int16 uint16;
>>>>>>> */
>>>>>>> #else
>>>>>>> #include 
>>>>>>> typedef int_least32_t int32;
>>>>>>> typedef int_least16_t int16;
>>>>>>> typedef uint_least32_t uint32;
>>>>>>> typedef uint_least16_t uint16;
>>>>>>> #endif
>>>>>>>
>>>>>>> Without these comments I get a load of errors about ambiguous symbol
>>>>>>> int32 or something along those lines. Now however I'm getting a whole
>>>>>>> new list of error all related to int32 and uint32. If I take out the
>>>>>>> comments I get even worse errors:
>>>>>>>
>>>>>>> 1>c:\program files\microsoft visual studio 9.0\vc\include\ivec.h(96) :
>>>>>>> warning C4190: '&' has C-linkage specified, but returns UDT 'M64'
>>>>>>> which is incompatible with C
>>>>>>> 1>        c:\program files\microsoft visual studio
>>>>>>> 9.0\vc\include\ivec.h(77) : see declaration of 'M64'
>>>>>>> 1>c:\program files\microsoft visual studio 9.0\vc\include\ivec.h(97) :
>>>>>>> warning C4190: '|' has C-linkage specified, but returns UDT 'M64'
>>>>>>> which is incompatible with C
>>>>>>> 1>        c:\program files\microsoft visual studio
>>>>>>> 9.0\vc\include\ivec.h(77) : see declaration of 'M64'
>>>>>>> (etc...)
>>>>>>>
>>>>>>> The odd thing is, and wait for it, my old build still work fine. Both
>>>>>>> projects link to the same libs and use the same header files. I've
>>>>>>> even done comparisons of the project settings from the two projects
>>>>>>> and apart from project name differences everything else is the same.
>>>>>>> I'm at a lose to explain this, can anyone think of any reason this may
>>>>>>> be happening or any way I can try to resolve this?
>>>>>>>
>>>>>>> Rory.
>>>>>>>
>>>>>>> ------------------------------------------------------------------------------
>>>>>>> Start uncovering the many advantages of virtual appliances
>>>>>>> and start using them to simplify application deployment and
>>>>>>> accelerate your shift to cloud computing.
>>>>>>> http://p.sf.net/sfu/novell-sfdev2dev
>>>>>>> _______________________________________________
>>>>>>> Csound-devel mailing list
>>>>>>> Csound-devel@lists.sourceforge.net
>>>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Michael Gogins
>>>>>> Irreducible Productions
>>>>>> http://www.michael-gogins.com
>>>>>> Michael dot Gogins at gmail dot com
>>>>>>
>>>>>> ------------------------------------------------------------------------------
>>>>>> Start uncovering the many advantages of virtual appliances
>>>>>> and start using them to simplify application deployment and
>>>>>> accelerate your shift to cloud computing.
>>>>>> http://p.sf.net/sfu/novell-sfdev2dev
>>>>>> _______________________________________________
>>>>>> Csound-devel mailing list
>>>>>> Csound-devel@lists.sourceforge.net
>>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>>
>>>>>
>>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Beautiful is writing same markup. Internet Explorer 9 supports
>>> standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
>>> Spend less time writing and  rewriting code and more time creating great
>>> experiences on the web. Be a part of the beta today.
>>> http://p.sf.net/sfu/beautyoftheweb
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Beautiful is writing same markup. Internet Explorer 9 supports
>>> standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
>>> Spend less time writing and  rewriting code and more time creating great
>>> experiences on the web. Be a part of the beta today.
>>> http://p.sf.net/sfu/beautyoftheweb
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>
>> ------------------------------------------------------------------------------
>> Beautiful is writing same markup. Internet Explorer 9 supports
>> standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
>> Spend less time writing and  rewriting code and more time creating great
>> experiences on the web. Be a part of the beta today.
>> http://p.sf.net/sfu/beautyoftheweb
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>
>
>
> --
> Michael Gogins
> Irreducible Productions
> http://www.michael-gogins.com
> Michael dot Gogins at gmail dot com
>
> ------------------------------------------------------------------------------
> Beautiful is writing same markup. Internet Explorer 9 supports
> standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
> Spend less time writing and  rewriting code and more time creating great
> experiences on the web. Be a part of the beta today.
> http://p.sf.net/sfu/beautyoftheweb
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>

------------------------------------------------------------------------------
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
Spend less time writing and  rewriting code and more time creating great
experiences on the web. Be a part of the beta today.
http://p.sf.net/sfu/beautyoftheweb
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Andy should go ahead and commit his fix. If he can't, he should email
his file to me and I will diff it and apply to the fix to the current
code.

Regards,
Mike

On Thu, Oct 7, 2010 at 9:20 AM, Rory Walsh  wrote:
> Thanks Mike, I had that defined already. A post last year to this list
> from Andy contains the solution. Thanks for everyone's help, hopefully
> this is the end of it!
>
> On 7 October 2010 14:00, Michael Gogins  wrote:
>> #define MSVC should fix it.
>>
>> Regards,
>> Mike
>>
>> On Thu, Oct 7, 2010 at 8:25 AM, Rory Walsh  wrote:
>>> The ivec.h errors are coming during the build process. I've been
>>> trawling through forums in a bid to find the solution but I can't seem
>>> to find anything concrete. According to Microsoft the error occurs
>>> when: More than one overloaded function is declared with C linkage.
>>> The version of VE I use on this machine is slightly newer than the one
>>> I had on my laptop. It was on my laptop that I created all the Csound
>>> project that work.It could be something to do with new headers, as
>>> Mike had already suggested. I will try a simple test project on my
>>> older version of Visual Express 2008 and see if it builds there.
>>> Thanks for your reply.
>>>
>>> Rory.
>>>
>>>
>>> On 7 October 2010 13:12, Sigurd Saue  wrote:
>>>> Do you get the ivec.h errors when linking the same little program as before? Here's my workaround for the int32 issue, and this compiles nicely with no further errors.
>>>>
>>>> #include 
>>>> typedef __int32 int32;
>>>> typedef unsigned __int32 uint32;
>>>> #include 
>>>>
>>>> int main(){
>>>>  return 0;
>>>> }
>>>>
>>>>
>>>> Sigurd
>>>>
>>>>
>>>> -----Original Message-----
>>>> From: Rory Walsh [mailto:rorywalsh@ear.ie]
>>>> Sent: 7. oktober 2010 12:52
>>>> To: Developer discussions
>>>> Subject: Re: [Cs-dev] help needed...MS Visual Express..int32...
>>>>
>>>> In fact, i seemed to have got around the problem with int 32, now I
>>>> get a load of error about ivec.h? I think this is to do with what Mike
>>>> mentioned about compiling C as if it were C++, here's the error:
>>>>
>>>> 1>c:\program files\microsoft visual studio 9.0\vc\include\ivec.h(96) :
>>>> warning C4190: '&' has C-linkage specified, but returns UDT 'M64'
>>>> which is incompatible with C
>>>> 1>        c:\program files\microsoft visual studio
>>>> 9.0\vc\include\ivec.h(77) : see declaration of 'M64'
>>>>
>>>> There are hundreds of similar errors all relating to ivec.h, anyone
>>>> know how do I change it from C-linkage specified to C++-linkage
>>>> specifed?
>>>>
>>>>
>>>> On 7 October 2010 11:45, Rory Walsh  wrote:
>>>>> I'm trying again today to resolve this problem. Unfortunately a few
>>>>> hours on Thursday is all I have to work on my own projects this
>>>>> semester so I'm keen to find a fix if anyone can help. I've done as
>>>>> Mike suggested and simplified the program completely. All I'm trying
>>>>> to do now is to get the following lines of code to compile:
>>>>>
>>>>> #include 
>>>>> #include 
>>>>>
>>>>> int main(){
>>>>> return 0;
>>>>> }
>>>>>
>>>>> At this stage I'm not even linking to csound.lib. Compiling gives me a
>>>>> load of errors regarding int32 in csound.h. As I mentioned previously,
>>>>> I have working Csound projects but all my new projects suffer from the
>>>>> same fate outlined above, I just can't see what the problem is?
>>>>>
>>>>> Rory.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On 30 September 2010 16:34, Rory Walsh  wrote:
>>>>>> Thanks Mike, I'll try to see this is the problem. I'll also try to
>>>>>> create a smaller sample project and see if I can spot what's up.
>>>>>> Hopefully you've given me enough info to figure out the problem!
>>>>>>
>>>>>> Rory.
>>>>>>
>>>>>>
>>>>>>> Is this a native code project? It should be. If so, is it compiling C
>>>>>>> or C++ code? Maybe it should be C++ code (that is, compile "C" as if
>>>>>>> it were "C++"). THIS IS PROBABLY IT.
>>>>>>
>>>>>>> You may inadvertently be including some header that redefines things
>>>>>>> you don't want redefined, try to simplify your problem with a stub
>>>>>>> test file.
>>>>>>>
>>>>>>> There also may be new int32 etc. definitions somwhere in the Microsoft
>>>>>>> headers, as they gradually are becoming more and more "standard"
>>>>>>> whatever that is.
>>>>>>>
>>>>>>> Hope this helps,
>>>>>>> Mike
>>>>>>>
>>>>>>> On Thu, Sep 30, 2010 at 9:20 AM, Rory Walsh  wrote:
>>>>>>>> I set up a new API project using MS Visual Express. I then copied
>>>>>>>> project settings from a previous MSVE Csound host application and went
>>>>>>>> to build. As soon as I include csound.hpp and try to build it
>>>>>>>> complains about not recognising int32. In the past, because MSVC is
>>>>>>>> defined, I would have always commented the MSVC stuff from sysdep.h as
>>>>>>>> in:
>>>>>>>>
>>>>>>>> #ifdef MSVC
>>>>>>>> /*
>>>>>>>> typedef __int32 int32;
>>>>>>>> typedef __int16 int16;
>>>>>>>> typedef unsigned __int32 uint32;
>>>>>>>> typedef unsigned __int16 uint16;
>>>>>>>> */
>>>>>>>> #else
>>>>>>>> #include 
>>>>>>>> typedef int_least32_t int32;
>>>>>>>> typedef int_least16_t int16;
>>>>>>>> typedef uint_least32_t uint32;
>>>>>>>> typedef uint_least16_t uint16;
>>>>>>>> #endif
>>>>>>>>
>>>>>>>> Without these comments I get a load of errors about ambiguous symbol
>>>>>>>> int32 or something along those lines. Now however I'm getting a whole
>>>>>>>> new list of error all related to int32 and uint32. If I take out the
>>>>>>>> comments I get even worse errors:
>>>>>>>>
>>>>>>>> 1>c:\program files\microsoft visual studio 9.0\vc\include\ivec.h(96) :
>>>>>>>> warning C4190: '&' has C-linkage specified, but returns UDT 'M64'
>>>>>>>> which is incompatible with C
>>>>>>>> 1>        c:\program files\microsoft visual studio
>>>>>>>> 9.0\vc\include\ivec.h(77) : see declaration of 'M64'
>>>>>>>> 1>c:\program files\microsoft visual studio 9.0\vc\include\ivec.h(97) :
>>>>>>>> warning C4190: '|' has C-linkage specified, but returns UDT 'M64'
>>>>>>>> which is incompatible with C
>>>>>>>> 1>        c:\program files\microsoft visual studio
>>>>>>>> 9.0\vc\include\ivec.h(77) : see declaration of 'M64'
>>>>>>>> (etc...)
>>>>>>>>
>>>>>>>> The odd thing is, and wait for it, my old build still work fine. Both
>>>>>>>> projects link to the same libs and use the same header files. I've
>>>>>>>> even done comparisons of the project settings from the two projects
>>>>>>>> and apart from project name differences everything else is the same.
>>>>>>>> I'm at a lose to explain this, can anyone think of any reason this may
>>>>>>>> be happening or any way I can try to resolve this?
>>>>>>>>
>>>>>>>> Rory.
>>>>>>>>
>>>>>>>> ------------------------------------------------------------------------------
>>>>>>>> Start uncovering the many advantages of virtual appliances
>>>>>>>> and start using them to simplify application deployment and
>>>>>>>> accelerate your shift to cloud computing.
>>>>>>>> http://p.sf.net/sfu/novell-sfdev2dev
>>>>>>>> _______________________________________________
>>>>>>>> Csound-devel mailing list
>>>>>>>> Csound-devel@lists.sourceforge.net
>>>>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Michael Gogins
>>>>>>> Irreducible Productions
>>>>>>> http://www.michael-gogins.com
>>>>>>> Michael dot Gogins at gmail dot com
>>>>>>>
>>>>>>> ------------------------------------------------------------------------------
>>>>>>> Start uncovering the many advantages of virtual appliances
>>>>>>> and start using them to simplify application deployment and
>>>>>>> accelerate your shift to cloud computing.
>>>>>>> http://p.sf.net/sfu/novell-sfdev2dev
>>>>>>> _______________________________________________
>>>>>>> Csound-devel mailing list
>>>>>>> Csound-devel@lists.sourceforge.net
>>>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Beautiful is writing same markup. Internet Explorer 9 supports
>>>> standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
>>>> Spend less time writing and  rewriting code and more time creating great
>>>> experiences on the web. Be a part of the beta today.
>>>> http://p.sf.net/sfu/beautyoftheweb
>>>> _______________________________________________
>>>> Csound-devel mailing list
>>>> Csound-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Beautiful is writing same markup. Internet Explorer 9 supports
>>>> standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
>>>> Spend less time writing and  rewriting code and more time creating great
>>>> experiences on the web. Be a part of the beta today.
>>>> http://p.sf.net/sfu/beautyoftheweb
>>>> _______________________________________________
>>>> Csound-devel mailing list
>>>> Csound-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Beautiful is writing same markup. Internet Explorer 9 supports
>>> standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
>>> Spend less time writing and  rewriting code and more time creating great
>>> experiences on the web. Be a part of the beta today.
>>> http://p.sf.net/sfu/beautyoftheweb
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>
>>
>>
>> --
>> Michael Gogins
>> Irreducible Productions
>> http://www.michael-gogins.com
>> Michael dot Gogins at gmail dot com
>>
>> ------------------------------------------------------------------------------
>> Beautiful is writing same markup. Internet Explorer 9 supports
>> standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
>> Spend less time writing and  rewriting code and more time creating great
>> experiences on the web. Be a part of the beta today.
>> http://p.sf.net/sfu/beautyoftheweb
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>
> ------------------------------------------------------------------------------
> Beautiful is writing same markup. Internet Explorer 9 supports
> standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
> Spend less time writing and  rewriting code and more time creating great
> experiences on the web. Be a part of the beta today.
> http://p.sf.net/sfu/beautyoftheweb
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>



-- 
Michael Gogins
Irreducible Productions
http://www.michael-gogins.com
Michael dot Gogins at gmail dot com

------------------------------------------------------------------------------
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
Spend less time writing and  rewriting code and more time creating great
experiences on the web. Be a part of the beta today.
http://p.sf.net/sfu/beautyoftheweb
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Good to hear. I hope this means that you are working with rather old CSound code, since Andy's fix was submitted December last year (csound.h revision 1.142).

Sigurd

-----Original Message-----
From: Rory Walsh [mailto:rorywalsh@ear.ie] 
Sent: 7. oktober 2010 15:20
To: Developer discussions
Subject: Re: [Cs-dev] help needed...MS Visual Express..int32...

Indeed it is, I can't believe I didn't check the list for ivec.h!
Following Andy's advice allows me to build.

Rory.


On 7 October 2010 14:01, Sigurd Saue  wrote:
> By the way: Some issue with ivec.h was discussed on this list a long time ago:
> http://csound.1045644.n5.nabble.com/MSVC-build-issue-td1130778.html
>
> Could that be related?
>
> Sigurd
>
>
> -----Original Message-----
> From: Rory Walsh [mailto:rorywalsh@ear.ie]
> Sent: 7. oktober 2010 14:26
> To: Developer discussions
> Subject: Re: [Cs-dev] help needed...MS Visual Express..int32...
>
> The ivec.h errors are coming during the build process. I've been
> trawling through forums in a bid to find the solution but I can't seem
> to find anything concrete. According to Microsoft the error occurs
> when: More than one overloaded function is declared with C linkage.
> The version of VE I use on this machine is slightly newer than the one
> I had on my laptop. It was on my laptop that I created all the Csound
> project that work.It could be something to do with new headers, as
> Mike had already suggested. I will try a simple test project on my
> older version of Visual Express 2008 and see if it builds there.
> Thanks for your reply.
>
> Rory.
>
>
> On 7 October 2010 13:12, Sigurd Saue  wrote:
>> Do you get the ivec.h errors when linking the same little program as before? Here's my workaround for the int32 issue, and this compiles nicely with no further errors.
>>
>> #include 
>> typedef __int32 int32;
>> typedef unsigned __int32 uint32;
>> #include 
>>
>> int main(){
>>  return 0;
>> }
>>
>>
>> Sigurd
>>
>>
>> -----Original Message-----
>> From: Rory Walsh [mailto:rorywalsh@ear.ie]
>> Sent: 7. oktober 2010 12:52
>> To: Developer discussions
>> Subject: Re: [Cs-dev] help needed...MS Visual Express..int32...
>>
>> In fact, i seemed to have got around the problem with int 32, now I
>> get a load of error about ivec.h? I think this is to do with what Mike
>> mentioned about compiling C as if it were C++, here's the error:
>>
>> 1>c:\program files\microsoft visual studio 9.0\vc\include\ivec.h(96) :
>> warning C4190: '&' has C-linkage specified, but returns UDT 'M64'
>> which is incompatible with C
>> 1>        c:\program files\microsoft visual studio
>> 9.0\vc\include\ivec.h(77) : see declaration of 'M64'
>>
>> There are hundreds of similar errors all relating to ivec.h, anyone
>> know how do I change it from C-linkage specified to C++-linkage
>> specifed?
>>
>>
>> On 7 October 2010 11:45, Rory Walsh  wrote:
>>> I'm trying again today to resolve this problem. Unfortunately a few
>>> hours on Thursday is all I have to work on my own projects this
>>> semester so I'm keen to find a fix if anyone can help. I've done as
>>> Mike suggested and simplified the program completely. All I'm trying
>>> to do now is to get the following lines of code to compile:
>>>
>>> #include 
>>> #include 
>>>
>>> int main(){
>>> return 0;
>>> }
>>>
>>> At this stage I'm not even linking to csound.lib. Compiling gives me a
>>> load of errors regarding int32 in csound.h. As I mentioned previously,
>>> I have working Csound projects but all my new projects suffer from the
>>> same fate outlined above, I just can't see what the problem is?
>>>
>>> Rory.
>>>
>>>
>>>
>>>
>>>
>>> On 30 September 2010 16:34, Rory Walsh  wrote:
>>>> Thanks Mike, I'll try to see this is the problem. I'll also try to
>>>> create a smaller sample project and see if I can spot what's up.
>>>> Hopefully you've given me enough info to figure out the problem!
>>>>
>>>> Rory.
>>>>
>>>>
>>>>> Is this a native code project? It should be. If so, is it compiling C
>>>>> or C++ code? Maybe it should be C++ code (that is, compile "C" as if
>>>>> it were "C++"). THIS IS PROBABLY IT.
>>>>
>>>>> You may inadvertently be including some header that redefines things
>>>>> you don't want redefined, try to simplify your problem with a stub
>>>>> test file.
>>>>>
>>>>> There also may be new int32 etc. definitions somwhere in the Microsoft
>>>>> headers, as they gradually are becoming more and more "standard"
>>>>> whatever that is.
>>>>>
>>>>> Hope this helps,
>>>>> Mike
>>>>>
>>>>> On Thu, Sep 30, 2010 at 9:20 AM, Rory Walsh  wrote:
>>>>>> I set up a new API project using MS Visual Express. I then copied
>>>>>> project settings from a previous MSVE Csound host application and went
>>>>>> to build. As soon as I include csound.hpp and try to build it
>>>>>> complains about not recognising int32. In the past, because MSVC is
>>>>>> defined, I would have always commented the MSVC stuff from sysdep.h as
>>>>>> in:
>>>>>>
>>>>>> #ifdef MSVC
>>>>>> /*
>>>>>> typedef __int32 int32;
>>>>>> typedef __int16 int16;
>>>>>> typedef unsigned __int32 uint32;
>>>>>> typedef unsigned __int16 uint16;
>>>>>> */
>>>>>> #else
>>>>>> #include 
>>>>>> typedef int_least32_t int32;
>>>>>> typedef int_least16_t int16;
>>>>>> typedef uint_least32_t uint32;
>>>>>> typedef uint_least16_t uint16;
>>>>>> #endif
>>>>>>
>>>>>> Without these comments I get a load of errors about ambiguous symbol
>>>>>> int32 or something along those lines. Now however I'm getting a whole
>>>>>> new list of error all related to int32 and uint32. If I take out the
>>>>>> comments I get even worse errors:
>>>>>>
>>>>>> 1>c:\program files\microsoft visual studio 9.0\vc\include\ivec.h(96) :
>>>>>> warning C4190: '&' has C-linkage specified, but returns UDT 'M64'
>>>>>> which is incompatible with C
>>>>>> 1>        c:\program files\microsoft visual studio
>>>>>> 9.0\vc\include\ivec.h(77) : see declaration of 'M64'
>>>>>> 1>c:\program files\microsoft visual studio 9.0\vc\include\ivec.h(97) :
>>>>>> warning C4190: '|' has C-linkage specified, but returns UDT 'M64'
>>>>>> which is incompatible with C
>>>>>> 1>        c:\program files\microsoft visual studio
>>>>>> 9.0\vc\include\ivec.h(77) : see declaration of 'M64'
>>>>>> (etc...)
>>>>>>
>>>>>> The odd thing is, and wait for it, my old build still work fine. Both
>>>>>> projects link to the same libs and use the same header files. I've
>>>>>> even done comparisons of the project settings from the two projects
>>>>>> and apart from project name differences everything else is the same.
>>>>>> I'm at a lose to explain this, can anyone think of any reason this may
>>>>>> be happening or any way I can try to resolve this?
>>>>>>
>>>>>> Rory.
>>>>>>
>>>>>> ------------------------------------------------------------------------------
>>>>>> Start uncovering the many advantages of virtual appliances
>>>>>> and start using them to simplify application deployment and
>>>>>> accelerate your shift to cloud computing.
>>>>>> http://p.sf.net/sfu/novell-sfdev2dev
>>>>>> _______________________________________________
>>>>>> Csound-devel mailing list
>>>>>> Csound-devel@lists.sourceforge.net
>>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Michael Gogins
>>>>> Irreducible Productions
>>>>> http://www.michael-gogins.com
>>>>> Michael dot Gogins at gmail dot com
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> Start uncovering the many advantages of virtual appliances
>>>>> and start using them to simplify application deployment and
>>>>> accelerate your shift to cloud computing.
>>>>> http://p.sf.net/sfu/novell-sfdev2dev
>>>>> _______________________________________________
>>>>> Csound-devel mailing list
>>>>> Csound-devel@lists.sourceforge.net
>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>
>>>>
>>>
>>
>> ------------------------------------------------------------------------------
>> Beautiful is writing same markup. Internet Explorer 9 supports
>> standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
>> Spend less time writing and  rewriting code and more time creating great
>> experiences on the web. Be a part of the beta today.
>> http://p.sf.net/sfu/beautyoftheweb
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>>
>> ------------------------------------------------------------------------------
>> Beautiful is writing same markup. Internet Explorer 9 supports
>> standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
>> Spend less time writing and  rewriting code and more time creating great
>> experiences on the web. Be a part of the beta today.
>> http://p.sf.net/sfu/beautyoftheweb
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>
> ------------------------------------------------------------------------------
> Beautiful is writing same markup. Internet Explorer 9 supports
> standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
> Spend less time writing and  rewriting code and more time creating great
> experiences on the web. Be a part of the beta today.
> http://p.sf.net/sfu/beautyoftheweb
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
> ------------------------------------------------------------------------------
> Beautiful is writing same markup. Internet Explorer 9 supports
> standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
> Spend less time writing and  rewriting code and more time creating great
> experiences on the web. Be a part of the beta today.
> http://p.sf.net/sfu/beautyoftheweb
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>

------------------------------------------------------------------------------
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
Spend less time writing and  rewriting code and more time creating great
experiences on the web. Be a part of the beta today.
http://p.sf.net/sfu/beautyoftheweb
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel


------------------------------------------------------------------------------
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
Spend less time writing and  rewriting code and more time creating great
experiences on the web. Be a part of the beta today.
http://p.sf.net/sfu/beautyoftheweb
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Not really, I'm working with 5.11. I still have absolutely no idea why
some projects build fine, they all use the same include files and lib.
Either way, it seems to be building now. I'll try a few more tests to
make sure everything works Ok.

Rory.


On 7 October 2010 14:48, Sigurd Saue  wrote:
> Good to hear. I hope this means that you are working with rather old CSound code, since Andy's fix was submitted December last year (csound.h revision 1.142).
>
> Sigurd
>
> -----Original Message-----
> From: Rory Walsh [mailto:rorywalsh@ear.ie]
> Sent: 7. oktober 2010 15:20
> To: Developer discussions
> Subject: Re: [Cs-dev] help needed...MS Visual Express..int32...
>
> Indeed it is, I can't believe I didn't check the list for ivec.h!
> Following Andy's advice allows me to build.
>
> Rory.
>
>
> On 7 October 2010 14:01, Sigurd Saue  wrote:
>> By the way: Some issue with ivec.h was discussed on this list a long time ago:
>> http://csound.1045644.n5.nabble.com/MSVC-build-issue-td1130778.html
>>
>> Could that be related?
>>
>> Sigurd
>>
>>
>> -----Original Message-----
>> From: Rory Walsh [mailto:rorywalsh@ear.ie]
>> Sent: 7. oktober 2010 14:26
>> To: Developer discussions
>> Subject: Re: [Cs-dev] help needed...MS Visual Express..int32...
>>
>> The ivec.h errors are coming during the build process. I've been
>> trawling through forums in a bid to find the solution but I can't seem
>> to find anything concrete. According to Microsoft the error occurs
>> when: More than one overloaded function is declared with C linkage.
>> The version of VE I use on this machine is slightly newer than the one
>> I had on my laptop. It was on my laptop that I created all the Csound
>> project that work.It could be something to do with new headers, as
>> Mike had already suggested. I will try a simple test project on my
>> older version of Visual Express 2008 and see if it builds there.
>> Thanks for your reply.
>>
>> Rory.
>>
>>
>> On 7 October 2010 13:12, Sigurd Saue  wrote:
>>> Do you get the ivec.h errors when linking the same little program as before? Here's my workaround for the int32 issue, and this compiles nicely with no further errors.
>>>
>>> #include 
>>> typedef __int32 int32;
>>> typedef unsigned __int32 uint32;
>>> #include 
>>>
>>> int main(){
>>>  return 0;
>>> }
>>>
>>>
>>> Sigurd
>>>
>>>
>>> -----Original Message-----
>>> From: Rory Walsh [mailto:rorywalsh@ear.ie]
>>> Sent: 7. oktober 2010 12:52
>>> To: Developer discussions
>>> Subject: Re: [Cs-dev] help needed...MS Visual Express..int32...
>>>
>>> In fact, i seemed to have got around the problem with int 32, now I
>>> get a load of error about ivec.h? I think this is to do with what Mike
>>> mentioned about compiling C as if it were C++, here's the error:
>>>
>>> 1>c:\program files\microsoft visual studio 9.0\vc\include\ivec.h(96) :
>>> warning C4190: '&' has C-linkage specified, but returns UDT 'M64'
>>> which is incompatible with C
>>> 1>        c:\program files\microsoft visual studio
>>> 9.0\vc\include\ivec.h(77) : see declaration of 'M64'
>>>
>>> There are hundreds of similar errors all relating to ivec.h, anyone
>>> know how do I change it from C-linkage specified to C++-linkage
>>> specifed?
>>>
>>>
>>> On 7 October 2010 11:45, Rory Walsh  wrote:
>>>> I'm trying again today to resolve this problem. Unfortunately a few
>>>> hours on Thursday is all I have to work on my own projects this
>>>> semester so I'm keen to find a fix if anyone can help. I've done as
>>>> Mike suggested and simplified the program completely. All I'm trying
>>>> to do now is to get the following lines of code to compile:
>>>>
>>>> #include 
>>>> #include 
>>>>
>>>> int main(){
>>>> return 0;
>>>> }
>>>>
>>>> At this stage I'm not even linking to csound.lib. Compiling gives me a
>>>> load of errors regarding int32 in csound.h. As I mentioned previously,
>>>> I have working Csound projects but all my new projects suffer from the
>>>> same fate outlined above, I just can't see what the problem is?
>>>>
>>>> Rory.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On 30 September 2010 16:34, Rory Walsh  wrote:
>>>>> Thanks Mike, I'll try to see this is the problem. I'll also try to
>>>>> create a smaller sample project and see if I can spot what's up.
>>>>> Hopefully you've given me enough info to figure out the problem!
>>>>>
>>>>> Rory.
>>>>>
>>>>>
>>>>>> Is this a native code project? It should be. If so, is it compiling C
>>>>>> or C++ code? Maybe it should be C++ code (that is, compile "C" as if
>>>>>> it were "C++"). THIS IS PROBABLY IT.
>>>>>
>>>>>> You may inadvertently be including some header that redefines things
>>>>>> you don't want redefined, try to simplify your problem with a stub
>>>>>> test file.
>>>>>>
>>>>>> There also may be new int32 etc. definitions somwhere in the Microsoft
>>>>>> headers, as they gradually are becoming more and more "standard"
>>>>>> whatever that is.
>>>>>>
>>>>>> Hope this helps,
>>>>>> Mike
>>>>>>
>>>>>> On Thu, Sep 30, 2010 at 9:20 AM, Rory Walsh  wrote:
>>>>>>> I set up a new API project using MS Visual Express. I then copied
>>>>>>> project settings from a previous MSVE Csound host application and went
>>>>>>> to build. As soon as I include csound.hpp and try to build it
>>>>>>> complains about not recognising int32. In the past, because MSVC is
>>>>>>> defined, I would have always commented the MSVC stuff from sysdep.h as
>>>>>>> in:
>>>>>>>
>>>>>>> #ifdef MSVC
>>>>>>> /*
>>>>>>> typedef __int32 int32;
>>>>>>> typedef __int16 int16;
>>>>>>> typedef unsigned __int32 uint32;
>>>>>>> typedef unsigned __int16 uint16;
>>>>>>> */
>>>>>>> #else
>>>>>>> #include 
>>>>>>> typedef int_least32_t int32;
>>>>>>> typedef int_least16_t int16;
>>>>>>> typedef uint_least32_t uint32;
>>>>>>> typedef uint_least16_t uint16;
>>>>>>> #endif
>>>>>>>
>>>>>>> Without these comments I get a load of errors about ambiguous symbol
>>>>>>> int32 or something along those lines. Now however I'm getting a whole
>>>>>>> new list of error all related to int32 and uint32. If I take out the
>>>>>>> comments I get even worse errors:
>>>>>>>
>>>>>>> 1>c:\program files\microsoft visual studio 9.0\vc\include\ivec.h(96) :
>>>>>>> warning C4190: '&' has C-linkage specified, but returns UDT 'M64'
>>>>>>> which is incompatible with C
>>>>>>> 1>        c:\program files\microsoft visual studio
>>>>>>> 9.0\vc\include\ivec.h(77) : see declaration of 'M64'
>>>>>>> 1>c:\program files\microsoft visual studio 9.0\vc\include\ivec.h(97) :
>>>>>>> warning C4190: '|' has C-linkage specified, but returns UDT 'M64'
>>>>>>> which is incompatible with C
>>>>>>> 1>        c:\program files\microsoft visual studio
>>>>>>> 9.0\vc\include\ivec.h(77) : see declaration of 'M64'
>>>>>>> (etc...)
>>>>>>>
>>>>>>> The odd thing is, and wait for it, my old build still work fine. Both
>>>>>>> projects link to the same libs and use the same header files. I've
>>>>>>> even done comparisons of the project settings from the two projects
>>>>>>> and apart from project name differences everything else is the same.
>>>>>>> I'm at a lose to explain this, can anyone think of any reason this may
>>>>>>> be happening or any way I can try to resolve this?
>>>>>>>
>>>>>>> Rory.
>>>>>>>
>>>>>>> ------------------------------------------------------------------------------
>>>>>>> Start uncovering the many advantages of virtual appliances
>>>>>>> and start using them to simplify application deployment and
>>>>>>> accelerate your shift to cloud computing.
>>>>>>> http://p.sf.net/sfu/novell-sfdev2dev
>>>>>>> _______________________________________________
>>>>>>> Csound-devel mailing list
>>>>>>> Csound-devel@lists.sourceforge.net
>>>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Michael Gogins
>>>>>> Irreducible Productions
>>>>>> http://www.michael-gogins.com
>>>>>> Michael dot Gogins at gmail dot com
>>>>>>
>>>>>> ------------------------------------------------------------------------------
>>>>>> Start uncovering the many advantages of virtual appliances
>>>>>> and start using them to simplify application deployment and
>>>>>> accelerate your shift to cloud computing.
>>>>>> http://p.sf.net/sfu/novell-sfdev2dev
>>>>>> _______________________________________________
>>>>>> Csound-devel mailing list
>>>>>> Csound-devel@lists.sourceforge.net
>>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>>
>>>>>
>>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Beautiful is writing same markup. Internet Explorer 9 supports
>>> standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
>>> Spend less time writing and  rewriting code and more time creating great
>>> experiences on the web. Be a part of the beta today.
>>> http://p.sf.net/sfu/beautyoftheweb
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Beautiful is writing same markup. Internet Explorer 9 supports
>>> standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
>>> Spend less time writing and  rewriting code and more time creating great
>>> experiences on the web. Be a part of the beta today.
>>> http://p.sf.net/sfu/beautyoftheweb
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>
>> ------------------------------------------------------------------------------
>> Beautiful is writing same markup. Internet Explorer 9 supports
>> standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
>> Spend less time writing and  rewriting code and more time creating great
>> experiences on the web. Be a part of the beta today.
>> http://p.sf.net/sfu/beautyoftheweb
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>>
>> ------------------------------------------------------------------------------
>> Beautiful is writing same markup. Internet Explorer 9 supports
>> standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
>> Spend less time writing and  rewriting code and more time creating great
>> experiences on the web. Be a part of the beta today.
>> http://p.sf.net/sfu/beautyoftheweb
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>
> ------------------------------------------------------------------------------
> Beautiful is writing same markup. Internet Explorer 9 supports
> standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
> Spend less time writing and  rewriting code and more time creating great
> experiences on the web. Be a part of the beta today.
> http://p.sf.net/sfu/beautyoftheweb
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
> ------------------------------------------------------------------------------
> Beautiful is writing same markup. Internet Explorer 9 supports
> standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
> Spend less time writing and  rewriting code and more time creating great
> experiences on the web. Be a part of the beta today.
> http://p.sf.net/sfu/beautyoftheweb
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>

------------------------------------------------------------------------------
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
Spend less time writing and  rewriting code and more time creating great
experiences on the web. Be a part of the beta today.
http://p.sf.net/sfu/beautyoftheweb
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net