O$10.2 xcomps – constants
You most certainly need to recompile your components with the Studio 10.2 SDK and although the Mac build appears to work, I would recommend you rebuild them too as they now require to be compiled and linked with c11++ settings. You may run into difficulties with your components, eventually.
The specific Xcode settings that you must change are
C++ Language Dialect C++11 [C++11 [-std=c++11]
C++ Standard Library libc++ (LLVM C++ standard library with C++11 support)
There are other things you need to change but I don’t think they are essential, such as the Base SDK (I use 10.15) and macOS Deployment Target (I use 10.11).
That is all I can think of at the moment.
> On 26 Nov 2020, at 10:20, Phil (OmnisList) via omnisdev-en <firstname.lastname@example.org> wrote:
> Hi xcomp folk….
> I have some O$817 xcomps that have constants within them.
> Just putting them directly into the 10.2 xcomp folder, they work fine on Mac, but on windows, for some reason, the constants are missing the const prefix visible in the catalog.
> Is there something different I need to do to make these work on Windows now?
> Or is it simply a recompile with the latest OMNISu64.lib?
> Any insights?
> Phil Potter
> Based in Chester in the UK.
> Manage your list subscriptions at lists.omnis-dev.com
> Start a new message -> mailto:email@example.com