leopard.sh and tiger.sh

[TheBeeDev]

To install versions below py313, you may need to add into the portfile this:

compiler.c_standard 2011
build.cmd-prepend CFLAGS=-Wno-incompatible-pointer-types

The first line should apply to all versions, the second only to py27 block, I guess.

Anyway, py27-game with SDL1 also built fine after these minor fixes.

Aaaa sorry, i missed this when i replied, how would i go about adding that?

 

[barracuda156]

Aaaa sorry, i missed this when i replied, how would i go about adding that?

Something like this.

If you plan to actually use this port, it may be worth checking which was the last version to support SDL1. Current one does not seem to, judging from setup.py at least. I am not gonna dig into this myself. You may check through commit history of pygame itself, or/and its port, or perhaps just ask developers to help you, they probably know when support was dropped. Once you know, then either pick an older portfile from history, for that specific version, and make sure to set it to use SDL1, or edit the current portfile (possibly replacing version and checksums can work). In the worst case I can handle a portfile for you, provided you find out which exactly version you need.

 

[TheBeeDev]

Something like this.

If you plan to actually use this port, it may be worth checking which was the last version to support SDL1. Current one does not seem to, judging from setup.py at least. I am not gonna dig into this myself. You may check through commit history of pygame itself, or/and its port, or perhaps just ask developers to help you, they probably know when support was dropped. Once you know, then either pick an older portfile from history, for that specific version, and make sure to set it to use SDL1, or edit the current portfile (possibly replacing version and checksums can work). In the worst case I can handle a portfile for you, provided you find out which exactly version you need.

I think for me at my skill level with this kinda thing [0] i'll just stick with the one you reccomended, the only thing im a littttle confused with is how to i "tell" MacPorts to use the custom file?

 

[barracuda156]

I think for me at my skill level with this kinda thing [0] i'll just stick with the one you reccomended, the only thing im a littttle confused with is how to i "tell" MacPorts to use the custom file?

If you refer specifically to this instance, you do not need to keep a modified portfile, since it is a build fix. (Depending on whether MacPorts fixes this on their side, next update of the port may need this fix added over again.)

If you want to keep a portfile “permanently” (until you change it yourself), make an override repo and set it in sources.conf above the default one.
See: https://guide.macports.org/chunked/development.local-repositories.html

 

[TheBeeDev]

If you refer specifically to this instance, you do not need to keep a modified portfile, since it is a build fix. (Depending on whether MacPorts fixes this on their side, next update of the port may need this fix added over again.)

If you want to keep a portfile “permanently” (until you change it yourself), make an override repo and set it in sources.conf above the default one.
See: https://guide.macports.org/chunked/development.local-repositories.html

Im so sorry, im still a little confused :c
So for the temporary, i follow the steps in the link? or is that for the permanent?
[sorry again ;-; im new to PowerPC stuff]

 

[barracuda156]

Im so sorry, im still a little confused :c
So for the temporary, i follow the steps in the link? or is that for the permanent?
[sorry again ;-; im new to PowerPC stuff]

Yeah, okay, just make a local port as described, that’s perhaps less confusing.

P. S. What I meant is that if you already installed the port using a suggested fix, you do not need to keep a custom portfile. But indeed better make a local one as described.