TASEmulators / TASEmulators/BizHawk

[🐧] Core build/rebuild checklist for Linux port

Open
#2,423 11 comments 1 reaction 1 assignee View on GitHub

Nobody has claimed this yet.

Core: Handy Core: Octoshock Meta re: Multiplatform
Dominant language
C#
Stars
2.8k
Forks
468
PR merge metrics
No merged PRs in 30d

Description

update 2022-01: we have new cores also I haven't actually done any work on this oops
update 2021-02: I need to add something like the following to each unmanaged core's build scripts so they respect $BIZHAWK_HOME:

if [ -z "$BIZHAWK_HOME" ]; then
	export BIZHAWK_HOME="$PWD/../../BizHawk/submodule/output"
	# print a warning? haven't thought about it enough
fi

Looking to get these to "built recently" status or higher by 2.5.2:

Cygne (libbizswan.dll.so)

  • built
  • built recently
  • build scripts respect $BIZHAWK_HOME
  • automated
  • Nix derivations are pure and reproducible

Gambatte (libgambatte.dll.so)

  • built
  • built recently
  • build scripts respect $BIZHAWK_HOME
  • automated
  • Nix derivations are pure and reproducible

Handy (libbizlynx.dll.so)

  • built
  • built recently
  • build scripts respect $BIZHAWK_HOME
  • automated
  • Nix derivations are pure and reproducible

mGBA (libmgba.dll.so)

  • built
  • built recently
  • build scripts respect $BIZHAWK_HOME
  • automated
  • Nix derivations are pure and reproducible

Octoshock

  • built
  • built recently
  • build scripts respect $BIZHAWK_HOME
  • automated
  • Nix derivations are pure and reproducible

QuickNes (libquicknes.dll.so)

  • built
  • built recently
  • build scripts respect $BIZHAWK_HOME
  • automated
  • Nix derivations are pure and reproducible

And now for the moonshots:

Mupen64Plus

  • built
  • built recently
  • build scripts respect $BIZHAWK_HOME
  • automated
  • Nix derivations are pure and reproducible

Waterbox cores

  • built
  • built recently
  • build scripts respect $BIZHAWK_HOME
  • automated
  • Nix derivations are pure and reproducible

see also #990 re: Windows binaries

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.