Csound Csound-dev Csound-tekno Search About

[Csnd] Conflict between CsoundLib64 and Vuo

Date2020-03-16 18:02
FromSyl Morrison
Subject[Csnd] Conflict between CsoundLib64 and Vuo
Hi all, realise this might be more of a general c++ problem, but I've been using the Vuo API for graphics, and wanting to use Csound as the backend audio engine for it. I've included both frameworks in my project, and it compiles fine with one or the other of the frameworks, but together it throws "/Users/sylmorrison/Apps/Kalide-clwtapgpaygtnkgmyqyagctbsorr/Build/Products/Debug/Vuo.framework/Frameworks/llvm.framework/Headers/Support/PrettyStackTrace.h:56:47: Member initializer 'csoundLocalizeString' does not name a non-static data member or base class", I'm trying to work out what the conflict is, and if anyone has come across this with Csound and other libs, any suggestions would be amazing!
Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date2020-03-16 18:18
FromSyl Morrison
SubjectRe: [Csnd] Conflict between CsoundLib64 and Vuo
Seemed to be the definition of Str that was conflicting, solved by doing #undef Str after including both headers, my bad!

On Mon, Mar 16, 2020 at 6:02 PM Syl Morrison <honoonu@gmail.com> wrote:
Hi all, realise this might be more of a general c++ problem, but I've been using the Vuo API for graphics, and wanting to use Csound as the backend audio engine for it. I've included both frameworks in my project, and it compiles fine with one or the other of the frameworks, but together it throws "/Users/sylmorrison/Apps/Kalide-clwtapgpaygtnkgmyqyagctbsorr/Build/Products/Debug/Vuo.framework/Frameworks/llvm.framework/Headers/Support/PrettyStackTrace.h:56:47: Member initializer 'csoundLocalizeString' does not name a non-static data member or base class", I'm trying to work out what the conflict is, and if anyone has come across this with Csound and other libs, any suggestions would be amazing!
Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date2020-03-16 18:29
FromMichael Gogins
SubjectRe: [Csnd] Conflict between CsoundLib64 and Vuo
When you #include header files that define namespaces, do you use "using namespace <name>;"? If so try not doing that, and qualifying all symbols by namespace. This is the best practice and is why namespaces were created in the first place.

This won't help if "Str" is defined using a macro. In that case, you may try changing the order of #includes in your source code.

Regards,
Mike

-----------------------------------------------------
Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com


On Mon, Mar 16, 2020 at 7:18 PM Syl Morrison <honoonu@gmail.com> wrote:
Seemed to be the definition of Str that was conflicting, solved by doing #undef Str after including both headers, my bad!

On Mon, Mar 16, 2020 at 6:02 PM Syl Morrison <honoonu@gmail.com> wrote:
Hi all, realise this might be more of a general c++ problem, but I've been using the Vuo API for graphics, and wanting to use Csound as the backend audio engine for it. I've included both frameworks in my project, and it compiles fine with one or the other of the frameworks, but together it throws "/Users/sylmorrison/Apps/Kalide-clwtapgpaygtnkgmyqyagctbsorr/Build/Products/Debug/Vuo.framework/Frameworks/llvm.framework/Headers/Support/PrettyStackTrace.h:56:47: Member initializer 'csoundLocalizeString' does not name a non-static data member or base class", I'm trying to work out what the conflict is, and if anyone has come across this with Csound and other libs, any suggestions would be amazing!
Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here
Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date2020-03-16 18:38
FromSyl Morrison
SubjectRe: [Csnd] Conflict between CsoundLib64 and Vuo
Nah I always use the "::" operator, but neither framework seems to need namespace qualifiers to actually work, like I can just call Csound(), and VuoRunner(), but yeah, #undef seemed to do the trick, though I'm not 100% how hahhaha

On Mon, Mar 16, 2020 at 6:30 PM Michael Gogins <michael.gogins@gmail.com> wrote:
When you #include header files that define namespaces, do you use "using namespace <name>;"? If so try not doing that, and qualifying all symbols by namespace. This is the best practice and is why namespaces were created in the first place.

This won't help if "Str" is defined using a macro. In that case, you may try changing the order of #includes in your source code.

Regards,
Mike

-----------------------------------------------------
Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com


On Mon, Mar 16, 2020 at 7:18 PM Syl Morrison <honoonu@gmail.com> wrote:
Seemed to be the definition of Str that was conflicting, solved by doing #undef Str after including both headers, my bad!

On Mon, Mar 16, 2020 at 6:02 PM Syl Morrison <honoonu@gmail.com> wrote:
Hi all, realise this might be more of a general c++ problem, but I've been using the Vuo API for graphics, and wanting to use Csound as the backend audio engine for it. I've included both frameworks in my project, and it compiles fine with one or the other of the frameworks, but together it throws "/Users/sylmorrison/Apps/Kalide-clwtapgpaygtnkgmyqyagctbsorr/Build/Products/Debug/Vuo.framework/Frameworks/llvm.framework/Headers/Support/PrettyStackTrace.h:56:47: Member initializer 'csoundLocalizeString' does not name a non-static data member or base class", I'm trying to work out what the conflict is, and if anyone has come across this with Csound and other libs, any suggestions would be amazing!
Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here
Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here
Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here