2 ms·

Good news, there's a project that ported NES Screen Tool to cross-platform Qt, called "NESTool": https://github.com/jpwhiting/nestool https://github.com/jpwhit

Good news, there's a project that ported NES Screen Tool to cross-platform Qt, called "NESTool": https://github.com/jpwhiting/nestool https://github.com/jpwhiting/nestool I made Mac and Windows builds, but I'm not sure yet how best to pre-compile a Linux version that works across distributions - any advice would be appreciated. I assume users can install Qt on their own, so I don't need to do static linking, but I'm not sure what needs to happen beyond that. I'm in the process of updating the parts of the book that are already there to use it instead of NES Screen Tool. Looking at a few replacements for FamiTracker as well, so no one will need to use WINE to do NES development.

jordigh 7y ago
Personally, I'm happy building from source, especially for niche software. Just give me a working CMake or Qt .pro file and I can figure out the rest. I in fact rather dislike pre-built binaries. I don't trust them to work well and I don't trust them to work for a long time if they happen to rely on libraries that one day change (even the most statically compiled of static binaries still usually rely on libc). And if your software ever gets popular enough, I expect one day my distribution will just package it for me. I'm happy with this arrangement. Source for niche software, apt/rpm for well-established software. For my own Qt project, I decided to use PyQt so I could leverage fbs for distribution for Windows where they're not used to source code (Mac can rely on homebrew, as far as I'm concerned): https://build-system.fman.io/ https://build-system.fman.io/
AnIdiotOnTheNet 7y ago
> but I'm not sure yet how best to pre-compile a Linux version that works across distributions - any advice would be appreciated. I like AppImage. Self-contained portable application bundles that should work on most Linux distros. https://docs.appimage.org/packaging-guide/index.html https://docs.appimage.org/packaging-guide/index.html

jordigh 7y ago

Personally, I'm happy building from source, especially for niche software. Just give me a working CMake or Qt .pro file and I can figure out the rest. I in fact rather dislike pre-built binaries. I don't trust them to work well and I don't trust them to work for a long time if they happen to rely on libraries that one day change (even the most statically compiled of static binaries still usually rely on libc). And if your software ever gets popular enough, I expect one day my distribution will just package it for me. I'm happy with this arrangement. Source for niche software, apt/rpm for well-established software. For my own Qt project, I decided to use PyQt so I could leverage fbs for distribution for Windows where they're not used to source code (Mac can rely on homebrew, as far as I'm concerned): https://build-system.fman.io/ https://build-system.fman.io/

AnIdiotOnTheNet 7y ago

> but I'm not sure yet how best to pre-compile a Linux version that works across distributions - any advice would be appreciated. I like AppImage. Self-contained portable application bundles that should work on most Linux distros. https://docs.appimage.org/packaging-guide/index.html https://docs.appimage.org/packaging-guide/index.html