compiling for Mac

[Leopold]

Hello,who is willing to compile a programm for the MAC.Sorce code for windows is availible but I have no ideas on a Mac and would not be able to test it.

[Pl45m4]

@Leopold

What is your question?
If you don't use platform-specific things in your code, the same Qt app will compile just fine on Windows, Mac and Linux.

[SGaist]

Hi,

Depending on where you are hosting your code, there might be CI nodes that are macOS so you could do that there.

[Leopold]

I have no idea on Macs and on compiling for MAC . The source is written in "C" and runs for windows.It is open source and a lot of people use it but there are some MAC users who would like to use it too without converting , virtuall boxes and so on.
My question: is somebody willing to make a MAC-program out of it?

[mrdebug]

I normally compile my programs for mac too, for business and for free.
I suggest you to buy a mac. After compilation it is necessary to test it (gui, file system access, ...) and to crate a installer package.
Cross compile could not be enought.

[SGaist]

@Leopold Without even a link to that open source project nobody can tell what it amounts to to be able to build it on macOS.

[Leopold]

The source code is available at github.com/leopoldg
for windows you have to compile librosco first to get the librosco.dll
For the MAC i don't know!

[SGaist]

You need to do some cleanups, there are two rosco.h and the one used for compilation content is wrong.
You're forcing the use of .so extension everywhere. It should be left to CMake to handle since it knows how to build a library project.
And that's only for librosco4.
Also, why post the zip file on github rather than the source itself ?

[Leopold]

Thank you Sgaist
So I corrected the rosco.h files and replaced the zip files with the source.
How do I unforce the use of .so extensions?

[Christian Ehrlicher]

@Leopold said in compiling for Mac:

How do I unforce the use of .so extensions?

Simply don't add it in the first place as it is not needed.