Skip to content

Oricutron integration - #3

Open
seclorum wants to merge 25 commits into
Oric-Software-Development-Kit:masterfrom
seclorum:oricutron-integration
Open

Oricutron integration#3
seclorum wants to merge 25 commits into
Oric-Software-Development-Kit:masterfrom
seclorum:oricutron-integration

Conversation

@seclorum

@seclorum seclorum commented Aug 6, 2026

Copy link
Copy Markdown

This PR cleans up the inclusion of Oricutron in the OSDK, such that:

  1. Untrusted pre-built binaries are not part of the repository - Oricutron is always built from source natively for the users' platform - the bins have been removed from the final resource directory, which should only contain the binaries (roms/images) assets required by Oricutron.
  2. Oricutron is packaged into the OSDK2.0 destination folder alongside its default .cfg and images/roms directories.

This makes Oricutron a standard native tool for OSDK2.0.

Note: Oricutron is added as a submodule to OSDK 2.0, so don't forget to "git submodule update --init --recursive".

Note: For now, the oricutron submodule repo is set to https://github.com/seclorum/oricutron.seclorum - this fork of petegordon's upstream repo contains bugfixes to the CMakeLists.txt file for modern MacOS/Linux dependency detection. Once those fixes make it upstream I will revert to petegordon's canonical repo for this submodule.

seclorum and others added 25 commits July 31, 2026 21:40
…n), fix ask_name() functions to not be Windows-only, update FloppyBuilder to remove c++-20-style code (only one line!)
…on time, with these priorities: DESTINATION= > OSDK= > CMAKE_INSTALL_PREFIX=; e.g. OSDK=~/Desktop/custom-local-osdk-install/ cmake --build <cmake-build-dir> --target build_and_install
…igures and builds every istalled sample using the install prefix; installed CMake helper now automatically OSDK_ROOT from its own sample/cmake location, so standalone installed samples no longer require OSDK_ROOT or OSDK to be set. ; DESTINATION=/private/tmp/osdk-all-samples-final cmake --build /private/tmp/osdk-all-samples-build --target samples
… a means to get the OSDK built, then the samples built.
…e builds, or CMake, depending on their preferences. The older Makefiles' still produce the same build products as before - CMake does not replace it - it is rather an additional feature for devs who prefer CMake for their projects.
… destination of the OSDK distributable directory, the distributable will be placed in /distributable/OSDK2.0/ by default.
…tively built oricutron during the OSDK build. Note: oricutron.seclorum is only temporary until petegordon accepts the PR modifying oricutrons' CMakeLlist.txt, which brings it up to date with building on modern MacOS.
…on this fork, Oricutron is built from source and packaged into the OSDK properly.
…ination directory properly, remove pre-built untrusted binaries from repo.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant