library project for macos/ios about miniaudio HOT 5 CLOSED

I'm developing audio analysis programs using Embarcadero C++builder for cross platform development. Actually I'm re-writing such programs and making them cross platform. It's a very big project that started using Borland C++Builder in 1995 and that since then absorbed a lot of my work. The problem is that I can compile the single file source "mini_al.h" for windows, but when I switch to ios or macos the .h file won't compile in c++ (in your description you say it must be compiled as objective C, and the compiler bccosx I use manages only C++. I tried but it would need too many changes to the source. So my idea was to create a library for macos and ios and link to it. Frankly speaking I have little or no experience with xcode, and even compiling a very simple program in it including mini_al.h was not successful. I have problems linking frameworks or resolving path issues for inclusion. Is there an example project that actually works in xcode? I'm sure that you have since you develop the library! Thank you in any case for your software! Ing. Daniele Zingoni email: [email protected] From: David Reid Date: 2018-08-31 23:27 To: dr-soft/mini_al CC: dzing63; Author Subject: Re: [dr-soft/mini_al] library project for macos/ios (#31) mini_al was never designed to be compiled as a shared object as it doesn't mark any functions for exporting and has transparent types which means it will never have a stable ABI. Typically with single file libraries, people just put a copy of it directly into their project's source tree. I won't ever be doing pre-compiled builds. That's one of the reasons I've put so much work into simplifying mini_al's build system - so I don't have to spend time compile stuff :) Just out of curiosity, what is your use case that requires mini_al as a shared object? You should know that mini_al does not currently have a stable API and will probably never have a stable ABI, so upgrading your mini_al shared object will require recompiling all of your programs that use it. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

Yes, I can compile for macos, I got a dylib. I did not test it. For ios I get stuck in compiling errors, when including AVFoundation or even another NCSsomething include..... I tried a little, then stopped. My problem is actually the need to use Objective C, otherwise I'm sure a could compile it even out of xcode. Thank you. Ing. Daniele Zingoni email: [email protected] From: David Reid Date: 2018-09-01 11:33 To: dr-soft/mini_al CC: dzing63; Author Subject: Re: [dr-soft/mini_al] library project for macos/ios (#31) What errors are you getting when compiling for macOS? It should still work as C++ with macOS (it won't work on iOS though because it requires Objective-C). — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.