Their github wiki has some example tutorials that are imminently readible without any resorting to pointers or assembly.
I was a little shocked at how clean this could be for a 16bit era console. Having checked in periodically for such a thing on the SNES and found little promising in the short term that wasn’t heavily reliant on assembly. There are obviously some advantages to the fact that the Genesis uses a mainline motorolla still supported by GCC. Where as the SNES’s main processor didn’t have the same staying power outside of the SNES.
The only other things similar that I have tripped over this clean to me, are targetted at gameboy development or 32bit systems and newer. (And GBDK has be unmaintaned for a good long time, unless something’s changed recently.)
@trashHeap, proposal! Change the goal of this to create a data page about the SGDK, itself spawning conversations about what a dev kit is, how to categorize it, etc. And we can make a new “Build Hello World in SGDK” quest.
Or! Let’s get started. I’m game to play along at home.
Ill be honest Im trying not to create any new quests right now. But feel free to edit this / fork / or split this off into a new thread. I may join in as I have time/energy. Im unlikely to forget SGDK and its an easy enough quest to recreate.
Ive been in a weird headspace for most technical quests or thinking about such things for a bit.
Well if you are into more of a “fill out this survey” mood…
Status (Dead/Healthy/Abandoned/Maitenaned/Security Patches Only)
Is license OSI/FSF/DFSG approved ?
Runtime (Java / Electron / NodeJS / Native (or libc) / etc.)
Widgets ( Qt / Gtk / Coacoa / Windows Forms / Swing / etc. )
Function ( Text Editor / Compiler / Calculator / Emulator / etc.)
Decentralized / Centralized
Peer to Peer
Supported Web Servers
DRM & Type of DRM
Last known price
Studio / Lead Dev
Package types available ( DEB / RPM / Flatpak / Snap / MSI / Installshield-EXE etc. )
Initial year it became available.
Recommended by other Talkgroup/Mage party member
GCC RUNTIME LIBRARY EXCEPTION
Version 3.1, 31 March 2009
Copyright (C) 2009 Free Software Foundation, Inc. <http://fsf.org/>
Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.
This GCC Runtime Library Exception ("Exception") is an additional
permission under section 7 of the GNU General Public License, version
3 ("GPLv3"). It applies to a given file (the "Runtime Library") that
bears a notice placed by the copyright holder of the file stating that
the file is governed by GPLv3 along with this Exception.
This isn’t a dual license per se. Or atleast not in the normal FSF/OSI lingo.
What we have here is a project running a composite of compatible licenses. Without digging into the source code deeper, the final binaries are likely all GPLv3 or GPLV3 with some MIT libraries. (very likely the later).
Dual-licesning as a term is usually when the whole project is covered by multiple libraries entirely. Not just piecemeal. Usually because the single copyright holder over the entire codebase is trying to serve multiple audiences. You see this from time to time in vanilla floss projects but it also comes up with open-core stuff or people who dual license to commercial vendors who don’t want to GPL their changes.
Linking exceptions are pretty common when you get digging. Doubly so for compilers / programming languages. I’d recommend against tracking them mostly because it falls below the granluarity you see in most package managers.
They mostly exist to make sure the GPL isn’t infecting things you make with GPL licensed tools. OR when a GPL program needs to link to an incompatible library/license. (discouraged but sometimes done.)
Tracking the compile/linking exceptions… I dunno. I don’t think most of us would find it useful. It’s deffinitely below the threshhold of most package managers. Which makes me think tracking it is awfully niche.