macOS compilation about cnc_remastered_collection

[abergmeier]

Have a look here: #31
I could try to get/keep my code compiling on macOS as well; this only makes sense if we have a macOS CI to validate.

[connorhu]

I can help testing the code on mac.

[tsilcher]

@abergmeier Thanks a lot for your input. Having a common Makefile for Linux & Unix (macOS) sounds great. About the CI, I am not sure if you are referring to automated tests but we can always manually test this in order to assure it works on the latest macOS versions.

[abergmeier]

Having a common Makefile for Linux & Unix (macOS) sounds great.

Currently I use CMake, which should even enable native XCode projects.

About the CI, I am not sure if you are referring to automated tests

For now automated tests would be that it at least compiles on macOS ;)

[trulyspinach]

What are you expecting to achieve behind this? To compile and execute on macOS? You can't without modifying the source code and remove win32 dependencies.

[abergmeier]

What are you expecting to achieve behind this?

I think there are a lot of different goals for different people. See below for me.

To compile and execute on macOS?

For me to compile and link on macOS.

You can't without modifying the source code

Yes. That is what we need to do.

and remove win32 dependencies.

Since most of the non-basic Windows APIs are in WIN32LIB we need to create something along MACOSLIB. For the rest making headers for Windows compat is not that hard.

All work that is currently going on in https://github.com/abergmeier/CnC_Remastered_Multiplatform

[ccg301]

missing a memory.h header file. Unable to compile.

[OmniBlade]

As an alternative fork working on standalone classic builds might I offer https://github.com/hifi/Vanilla-Conquer. Myself and a few other people already did some of the heavy lifting needed for this as part of the https://github.com/TheAssemblyArmada/Chronoshift project which is been rendered a bit moot by this source drop.