Hi,
Ethan C wrote:
Provided that the code does not use GNUstep-only libraries or APIs
(such as GNUstep-only APIs in Base or Gui), it should be possible to
compile any GNUstep application for macOS if you generate a new Xcode
project. You should use the native macOS APIs (Foundation and AppKit)
or else the application will not behave like other Mac apps.
I stand to that answer. Concerning AppKit code, if it works on GNUstep
and does not use any of its extensions, it *should* compile and work the
same on Mac. You might get into the issue that some APIs were deprecated
in Mac. Usually, however, they just work. You can also try to use MacOS
compatibility target and lower it and/or use an older SDK and see if you
get it running that way, then think about upgrading later. MacOS version
macros are handy for that in case you intend to preserve extended support.
The API is intentionally architecture neutral!
This applies to Objective-C code using "NS" classes and Kits. For
platform specific code, dependencies and other things, one by one needs
to be analyzed.
Riccardo
