search

edo9300 / edopro

A script engine for "yu-gi-oh!" and sample gui (former "ygopro")
Other
286 stars 76 forks source link

./travis/quickrun.sh debug|release command won't work #158

Closed Tsuyo99 closed 4 years ago

Tsuyo99 commented 4 years ago

Hey!

The "./travis/quickrun.sh debug|release" command doesnt work in step 4 of this tutorial: https://github.com/edo9300/edopro/wiki/4.-Running

Here is a screenshot of the problem: download

Also in text: $ ./travis/quickrun.sh release

$ ./travis/quickrun.sh debug

won't work with any of those commands :(

kevinlul commented 4 years ago

Quickrun is an outdated script that I haven't gotten around to updating

Tsuyo99 commented 4 years ago

Thanks for the fast response!

How will I resolve the issue?

Tsuyo99 commented 4 years ago

My vs2017 wont run the exe and I thought that the problem would probably revolve around the "./travis/quickrun.sh debug|release" command

kevinlul commented 4 years ago

image

Set this to your Project Ignis folder or equivalent. It's probably crashing due to missing fonts and configs.

Tsuyo99 commented 4 years ago

Output from vs2017 debug:

The thread 0x539c has exited with code 0 (0x0). Exception thrown at 0x76BC4192 in ygopro.exe: Microsoft C++ exception: nlohmann::detail::parse_error at memory location 0x021ABFDC. Exception thrown at 0x76BC4192 in ygopro.exe: Microsoft C++ exception: std::exception at memory location 0x021AD390. The thread 0x2818 has exited with code 1 (0x1). The thread 0x3ab4 has exited with code 1 (0x1). The program '[23100] ygopro.exe' has exited with code 1 (0x1).

Did as you said, that's what pops up once again :(

LordYuuma commented 4 years ago

Judging from the error, it seems that nlohmann barfs at either of your configuration JSONs (there should be one in config and one for Windbot). A working, albeit meaningless config/configs.json would be:

{
    "repos": [],
    "urls": [],
    "servers": []
}

You can safely delete/move away the WindBot JSON, it will only cause a warning if missing. Once you find out which of the files causes the error, you can try repairing that file.