Build steps borked

[lifeforce-dev]

Hi!

So, trying to get the ygo sln up and running but I'm kind of stuck. Could someone update the build steps and fix the bootstrap scripts?

Symptom: ygo errors on startup due to being unable to initialize the irrlicht device engine

Potential causes based on my debugging

1) The quickrun.sh fails to execute properly

• I dug into this and it looks like the actual .conf files were moved from root and into their own "config" folder, and noone updated the quickrun script..

• I updated the script by changing the cp lines to cp ./config/*.conf $DESTINATION, but the scripts still don't copy properly. Though now it at least doesn't tell me the file doesn't exist.

  2) install-local-dependencies fail to install irrKlang by default. I ended up changing USE_IRRKLANG=${2:-""} to USE_IRRKLANG=true so it would at least download it. Though I'm not sure if this has anything to do with my issues.

  3) I built the .sln with premake5 vs2019 --no-direct3d. I was able to successfully open and build the .sln. Trying to run it presents the error mentioned above

  • I did some debugging, found out that ygo is still trying to initialize with direct3d. In fact, I can't see any code path where it doesn't do that. The build steps say direct3d is optional, is that still true?
  • I changed the init code to return irr::video::EDT_OPENGL and now the gui initializes successfully, however, now strings fail to load. Which is weird because its looking in L"./config/strings.conf" which definitely exists.

Anyway I think the crux of this problem is, someone changed things and didn't update your build scripts. Maybe try following your own build steps step by step from scratch and make sure they're correct? I'm probably the one at fault but I'm certain I've found at least one error so now I don't trust anything haha

[lifeforce-dev]

Eh, just read the contributing section. This probably falls into something you guys didn't want reported here. I'll just fix the bootstrapping setup myself and submit a pull request

[edo9300]

For the device initialization, that's fixed in https://github.com/edo9300/edopro/commit/9ec9bcf7cbeae09fcbcb689353c7c0ef0fde515a. For the rest, the wiki is very outdated, and the quickrun script is not being used since a long time, so it's expected to be not working. For now, what you can do is build the exe and use the released program to get the assets from. (If you've reached the point of getting the exe built, then you're fine.)