Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Compile #59

Open
stephaneickmann opened this issue Nov 11, 2020 · 8 comments
Open

Compile #59

stephaneickmann opened this issue Nov 11, 2020 · 8 comments

Comments

@stephaneickmann
Copy link

Hello. I want to compile a new kernal for my Ultimate 64.
With new f-Keys. What do i need for this? Sorry, its my first time.
Do i need a C Compiler?
Thx for your help.
Greetings Stephan

@FeralChild64
Copy link
Collaborator

  1. You need a Linux, with GIT, GCC, GNU make, and libpng development libraries (libpng-devel package on Debian, if I'm not mistaken). If you only have Windows - you can use Windows Subsystem for Linux, it should work. I'm not sure about Mac OS - I don't have a Mac.

  2. Clone the repository: git clone https://github.com/MEGA65/open-roms.git

  3. Edit the open-roms/src/,,config_ultimate64.s file, changing the strings near KEYCMD_F1, etc. If you don't need anything assigned to the key, put NO. If you want a string assigned, put the string in quotation marks. If you don't know how to type a given character, consult a PETSCII table here - take the hexadecimal code, and type it replacing dollar ($) with a backslash (), for example \5F is a CBM back-arrow sign (top left corner of C64 keyboard).

  4. In the open-roms directory, execute command make - afterwards fetch your ROMs from open-roms/build directory. Note: ALWAYS take the new BASIC ROM even if the only change in the Kernal was changed function key definitions - this is enough to trigger incompatibility, and for the custom build 'ROM mismatch' bluescreen will be displayed by Kernal!

  5. If you are not happy with the new function keys assignment - repeat starting from step 3 (no need to clone a new repository).

I'll keep this ticket open as a reminder to update documentation. We need:

  • a compilation guide
  • a link to the forum which is best to ask questions - this should be the best place.

@stephaneickmann
Copy link
Author

thank you. Trying Windows Sub for Linux

@stephaneickmann
Copy link
Author

hmmm...errormessage...
png.h file is missing in resp? File "pngprepare"
some tips for me?

@Compyx
Copy link

Compyx commented Nov 17, 2020

Install libpng, this depends on what distro you installed in the WSL. On my Debian box I have libpng-dev installed, so make works. On Fedora the development packages are usually called 'foo-devel'.

@stephaneickmann
Copy link
Author

Yeah. Runs fine now :-)))) First time on Linux ;-)
Thank you very much.

@Compyx
Copy link

Compyx commented Nov 17, 2020

You're welcome!

@stephaneickmann
Copy link
Author

By the way... Where can i modify the banner_fancy gfx? Special File? Thx.

@FeralChild64
Copy link
Collaborator

You mean the 'U' logo? Go to open-roms/src/basic/assets/startup_banner.s, for Ultimate 64 build modify values just after '!ifdef CONFIG_MB_U64 {' line. Everything is in PETSCII, has to be terminated by 0 (but I recommend putting BANNER_COLOR_0 before 0, this switches the color to white - for text display). BANNER_SPACING is an indentation for text, in case your new GFX is wider/narrower.

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

No branches or pull requests

3 participants