Hi Shabeer,

Agar does not use Carbon at all. I think that definition was put there
either as a work around a bug in an older version of OSX or an SDL 1.2
specific issue.

Can you try removing -fpascal-strings and TARGET_API_MAC_CARBON from the
compilation flags? It should be on line 865 of CMakeChecks.cmake (in the
Check_Cocoa() macro).

I'll see if I can borrow a laptop with a more recent MacOS on it in the
next few days and test it myself (most of my Mac laptops are PowerPC and
my one Intel Mac has a blown video card) so I haven't tested the CMake
compilation method on recent MacOS yet.

By the way, I'm working on setting up the IRC channel and tunnel as
we've discussed, it should be ready in a couple of days.

Thanks!

On 3/16/24 05:42, Shabeer M wrote:
Since Apple has deprecated support for Carbon apps I guess it can no longer compile properly on macOS Catalina and above. This is some of the helpful tips I got from elsewhere online: > it's really old world stuff… after a quick check, it seems that catalina is 10.15.* and your are using sdk MacOSX11.1, the gap between versions may be too big and the compiler cant expand -fpascal-strings / TARGET_API_MAC_CARBON correctly > Many components were removed in recent versions of Xcode, the most notable being the Mac OS X 10.6 SDK, which is required to build software using the Carbon API (such as wxWidgets 2.8). ( https://github.com/devernay/xcodelegacy ) > macOS 10.14 Mojave is the newest system that can run 32-bit, let alone Carbon apps. Apple never offered Carbon for 64-bit, and by the time of Mojave it had been deprecated for years. ( https://ifnotnil.com/t/is-it-still-possible-to-run-app-that-use-carbon-api-in-the-latest-mac-os/3749 ). So perhaps for macOS the build system needs to be modified to detect what SDK is available and accordingly offer to compile ---with-carbon support or only compile --with-cocoa ?
11.03.2024, 11:54, "Shabeer M" <[email protected]>:

    I tried to build and compile the latest version and got some errors..
    Not sure if I did something wrong as I am not familiar with CMake.
    This is what I did after cloning the repository:
    1. Created a new directory called 'build' in the source directory.
    2. Ran cmake .. (in 'build' directory; it generated the makefiles
    and copied the source)
    3. Ran Make (in 'build' directory)
    4. Build failed with lots of warning and 6 errors (See here -
    https://bpa.st/2DLA <https://bpa.st/2DLA> - only copied the errors)..
    (I am on macOS Catalina 10.15.7, with cmake version 3.24.4 and Apple
    clang version 12.0.0 (clang-1200.0.32.29)).
    Thanks,
    Shabeer


--
Agar mailing list
[email protected]
http://mail123.csoft.net/mailman/listinfo/agar

Reply via email to