was able to build Icon manually for MacOS on arm; can the Icon port be fixed accordingly?

[Kenneth Wolcott]

Hi;

  I think using Icon on MacOS (arm64) via MacPorts would be really nice.
Since it is currently not working, I looked into installing it manually.
Seemed to go fine.  Perhaps it used gcc instead of clang?  I don't remember
now after having removed the GitGub clone directory from which I built
Icon.  I don't recall the steps that I followed exactly, but it seemed
simple enough (I was able to do it, so must have been simple!!) to just
follow the instructions on the web site on building from source, making a
guess here and there.

  A side note: I'm downloading, by hand, each of the Icon Project Library
files using wget.  It seems as though the library is provided in such a way
that using it is deliberately made difficult.  I guess that reduces the
amount of people wanting to use the library which reduces the maintenance
load.  I agree that such a conclusion is a negative/sarcastic one, but it
really looks that way.

https://www2.cs.arizona.edu/icon/

https://trac.macports.org/ticket/71944
https://trac.macports.org/ticket/71946

Thanks,
Ken Wolcott
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-users/attachments/20250211/b3742bb3/attachment.htm>