[freeciv-dev] Re: Freeciv for macOS

  • From: Dean <ddeanbrown@xxxxxxxxxxx>
  • To: freeciv-dev@xxxxxxxxxxxxx
  • Date: Sun, 10 Apr 2022 00:49:54 -0400

On 4/10/22 12:13 AM, Marko Lindqvist wrote:

On Sun, 10 Apr 2022 at 06:55, Dean <ddeanbrown@xxxxxxxxxxx> wrote:

I expect you (meaning cazfi) are adept at writing unix scripts. I can
describe what needs to be done in sufficient detail that you can
hopefully translate that into scripting language. If you don't have
access to a Mac I can do the script testing myself. Does this sound do-able?

  That's the sensible way, at least to begin.

This would be a good thing if we can get it working, because my process
now is mostly manual each time, and takes me a fair bit of time.

  Manual processes are usually also prune to human errors.

So true.

The first issue I see is that there needs to be at least one file added
to the source tree - an Apple icon image file. It could go in a folder
called "mac", parallel to the "windows" folder. We might want to put
some other files in there too.

  How that relates to the icon files in data/ that my linux system
recognise as "MaxOS X Icon" (freeciv-client.icns &
freeciv-server.icns) - though I'm now not sure if they are in part of
the tarball distribution. or if they are in version control only.
  Is your icon derived from some of the other files (only different format)?

Those icns files are not in the tarball, but I found them in the source repo. They appear to be same format as mine, tho not identical. I just tried testing using the freeciv-client.icns and it works fine, so this is not a problem. In fact I prefer to switch to using that one.

  Do you currently provide repackaged freeciv source code matching your
binaries?

No, but I think we've resolved the icon issue.

 If not, that makes resolving things like this icon issue
necessary even if we don't get to the build script part.


  - ML


Curious about the CI thing, does it run on a Mac? I don't understand how it could produce a runnable Mac build if it doesn't. I can understand it could verify that a compile and link for the Mac works, but I wouldn't think it could produce something that could run on a Mac because of the packages thing. The packages thing is the next issue to deal with.

Do you have access to a Mac?

Other related posts: