Re: NEW: games/tic80

[Charlene Wendling]

On Tue, 29 Jun 2021 17:54:56 +
Brian Callahan  wrote:

> Hi ports --
> 
> Attached is a new port, TIC-80. TIC-80 is a fantasy computer to make, 
> play and share tiny games.
> For those of you familiar with PICO-8, TIC-80 is an open source 
> alternative.

[...] 

> TIC-80 works well for me on amd64. I am interested in hearing about
> big endian systems.

I've tested on macppc.

It builds but does not work. There is no sound, the welcome
screen is red, carts either segfault or display a white window.

Big endian support has been refused upstream [0], the code has
never been written to do so and would need a major refactoring to
make things maintainable. The PR code is interesting to fix
similar issues in other ports though.

Meanwhile, it builds and works fine on amd64, testing in an
empty chroot revealed no missing depends.

> OK?

OK cwen@, but as you probably guessed with NOT_FOR_ARCHS=${BE_ARCHS}

> ~Brian

[0] https://github.com/nesbox/TIC-80/pull/1057/

NEW: games/tic80

[Brian Callahan]

Hi ports --

Attached is a new port, TIC-80. TIC-80 is a fantasy computer to make, 
play and share tiny games.
For those of you familiar with PICO-8, TIC-80 is an open source 
alternative.


---
pkg/DESCR:
TIC-80 is a fantasy computer for making, playing and sharing tiny games.

There are built-in tools for development: code, sprites, maps, sound
editors and the command line, which is enough to create a mini retro
game. You will get a cartridge file, which can be stored and played
locally, or uploaded to the TIC-80 website to be shared and played
online.

Also, the game can be packed into a player that works on all popular
platforms and distributed as you wish. To make a retro styled game the
whole process of creation takes place under some technical limitations:
240x136 pixel display, 16 color palette, 256 8x8 color sprites and 4
channel sound.
---

I did a good bit of massaging to make the TIC-80 build more suitable for 
ports.


First, upstream does not appear to offer their own source tarballs, 
relying on GitHub auto-generated tarballs. Unfortunately, TIC-80 also 
insists on building all its direct dependencies, and expects those 
direct dependencies to be a part of the build tree, none of which you 
get with the auto-generated tarball. Because of this, I made my own 
source tarball that includes the dependencies we need.


Second, I have chosen to use the ports versions of all the direct 
dependencies that are available in ports. This is similar to what I did 
with HandBrake. I have not experienced any issues with doing this, and I 
think that it overall makes TIC-80 fit better in the ports tree. So the 
tarball I made with contains TIC-80 and only the dependencies not 
already available in ports.


Third, I chose to build the "PRO" version rather than the normal 
version. It offers a few more features, and appears to be donations 
requested not donations required. And in any event, the one additional 
source file compiled for PRO mode is licensed under the same MIT license 
as the rest of TIC-80. The AUR package also builds the PRO version.


TIC-80 works well for me on amd64. I am interested in hearing about big 
endian systems.


OK?

~Brian


tic80.tgz
Description: GNU Zip compressed data