| If you are working on MacOS, all you need is to link to an installed CsoundLib64.framework, which has everything you need to use the Csound API.
This should port directly to Linux and Windows, where you'd link to an installed Csound library.
Regarding CMake -- that is the build system for the Csound library (from sources), and it uses gcc/g++ and other tools. In general, you should not need to build the Csound lib yourself but use the built/released versions.
Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy
Maynooth University
Ireland
> On 13 Jul 2019, at 20:29, Patrick Hinkle wrote:
>
> I have heard from Victor that as far as software build systems go 'cmake' should be the main toolset for developing with Csound instead of, say, 'cc/gcc/g++' or any other development toolset. I am currently working with Mac OS X Mojave and would like to "embed" the Csound engine and fundamental technologies in the AUHAL and Core Audio technologies. This makes my app/plug-in NOT cross-platform by definition. Would 'cmake' still be the build system toolset for this type of application? I don't mind using 'cc/gcc/g++' for building as it seems to depend more on whether the source and header files compile rather than with cmake where much of the focus seems to be on generating and/or editing CMakeLists files.
> Any suggestions or pointers would be greatly appreciated.
> Thanks,
> Patrick
>
> 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 |