Lameguy64 / PSn00bSDK

The most powerful open source SDK for the PS1 (as far as open source PS1 SDKs go). Not recommended for beginner use.
Other
819 stars 66 forks source link

Could not find _gcc using the following names: mipsel-none-elf-gcc #65

Closed Lufims closed 1 year ago

Lufims commented 1 year ago

I'm almost giving up on compiling this, can someone help

I think the cause of this errors, is because during the instalation appeared a warning saying that it could not edit the path, because it was too long, so, if someone post the path entries (I think is that what is called), I could edit it mannualy. Screenshot_1

spicyjpeg commented 1 year ago

The NSIS installer for version 0.19 seems to be broken. You can get around it by downloading the prebuilt v0.21 zip from my fork and extracting/installing it manually as detailed here (yes, it involves setting a couple of environment variables including the one I mentioned in the other issue you opened). You will have to invoke CMake from the command line, as the GUI does not fully support the Ninja generator backend.

By the way, please avoid opening multiple GitHub issues for the same reason (difficulties with installing the SDK in your case). Cluttering the issue tracker does not help anybody.

Lufims commented 1 year ago

The NSIS installer for version 0.19 seems to be broken. You can get around it by downloading the prebuilt v0.21 zip from my fork and extracting/installing it manually as detailed here (yes, it involves setting a couple of environment variables including the one I mentioned in the other issue you opened). You will have to invoke CMake from the command line, as the GUI does not fully support the Ninja generator backend.

By the way, please avoid opening multiple GitHub issues for the same reason (difficulties with installing the SDK in your case). Cluttering the issue tracker does not help anybody.

I can't believe that was just setting the path environment variable, it worked now, and sorry for opening two issues, I thought I could not put different issues on the same issue, but now I need help with other thing, I'm using Visual Studio 16 2019 as a compiler, and the build folder just have this things, and not the .bin or .cue (sorry for that, there was only one other time that I tried to compile a program, so, i'm new with this) Screenshot_2

spicyjpeg commented 1 year ago

You cannot use VS/MSBuild at all since it does not support the custom toolchain required to compile PS1 code; you need to use Ninja (included with the SDK) or one of CMake's Makefile generators instead. The default preset is already set up to use Ninja, so if you run the commands listed here the project should build correctly.

Lufims commented 1 year ago

You cannot use VS/MSBuild at all since it does not support the custom toolchain required to compile PS1 code; you need to use Ninja (included with the SDK) or one of CMake's Makefile generators instead. The default preset is already set up to use Ninja, so if you run the commands listed here the project should build correctly.

I tried to install Ninja, but it says an error when I try to compile with cmake, and somehow a was able to create a CUE file with visual studio, but just the cue file was created. Screenshot_6 Screenshot_5 Screenshot_7

spicyjpeg commented 1 year ago

Ninja is bundled with the 0.21 release I linked before, just extract that in place of your existing installation. Also, I already told you not to use the CMake GUI and to run CMake from the command line instead, since the GUI does not support Ninja. I'd suggest you to avoid using VS as well, since configuring it to use PSn00bSDK's compiler instead of MSVC involves a significant number of configuration tweaks; use VS Code or a simple text editor instead and build from the command line.

Lufims commented 1 year ago

Ninja is bundled with the 0.21 release I linked before, just extract that in place of your existing installation. Also, I already told you not to use the CMake GUI and to run CMake from the command line instead, since the GUI does not support Ninja. I'd suggest you to avoid using VS as well, since configuring it to use PSn00bSDK's compiler instead of MSVC involves a significant number of configuration tweaks; use VS Code or a simple text editor instead and build from the command line.

Ok, the Ninja worked, now I can't set the preset for the cmake, I'm using the command prompt now. Screenshot_9

Lufims commented 1 year ago

Ninja is bundled with the 0.21 release I linked before, just extract that in place of your existing installation. Also, I already told you not to use the CMake GUI and to run CMake from the command line instead, since the GUI does not support Ninja. I'd suggest you to avoid using VS as well, since configuring it to use PSn00bSDK's compiler instead of MSVC involves a significant number of configuration tweaks; use VS Code or a simple text editor instead and build from the command line.

I figured out how to use the command, i'm very dumb, it took me a long time to figure out. Now what I do with these files, I couldn't find the CUE or BIN. Screenshot_10 Screenshot_11

Lufims commented 1 year ago

Ninja is bundled with the 0.21 release I linked before, just extract that in place of your existing installation. Also, I already told you not to use the CMake GUI and to run CMake from the command line instead, since the GUI does not support Ninja. I'd suggest you to avoid using VS as well, since configuring it to use PSn00bSDK's compiler instead of MSVC involves a significant number of configuration tweaks; use VS Code or a simple text editor instead and build from the command line.

I finnaly did it, but the emulator is not recognizing it Screenshot_12

Lufims commented 1 year ago

Ninja is bundled with the 0.21 release I linked before, just extract that in place of your existing installation. Also, I already told you not to use the CMake GUI and to run CMake from the command line instead, since the GUI does not support Ninja. I'd suggest you to avoid using VS as well, since configuring it to use PSn00bSDK's compiler instead of MSVC involves a significant number of configuration tweaks; use VS Code or a simple text editor instead and build from the command line.

I finnaly did it, but the emulator is not recognizing it Screenshot_12

I fixed it, I think Screenshot_14

spicyjpeg commented 1 year ago

Use a different emulator, as PCSXR is known to be highly inaccurate and additionally lacks debugging functionality. The following emulators are recommended for development:

If you are still getting stuck with building, try copying the project template as explained by the installation guide and building it as-is, without modifying anything (other than the path to the toolchain file if necessary). That should not give you any issues.

Lufims commented 1 year ago

Use a different emulator, as PCSXR is known to be highly inaccurate and additionally lacks debugging functionality. The following emulators are recommended for development:

If you are still getting stuck with building, try copying the project template as explained by the installation guide and building it as-is, without modifying anything (other than the path to the toolchain file if necessary). That should not give you any issues.

I just found out what was the issue, I was trying to PutDrawEnv with the &disp[db] argument (PutDrawEnv(&disp[db]), but now it's working fine Screenshot_15