zerojay / RetroPie-Extra

A collection of unofficial scripts for adding more emulators/ports/games to RetroPie.
MIT License
309 stars 101 forks source link

Crispy DOOM will not compile. #276

Closed XD3l closed 6 years ago

XD3l commented 6 years ago

Retropie is fully and freshly updated and I am getting this message when compiling:

COuld not successfully build crispy-doom - Crispy Doom - Enhanced port of (blah blah blah)

(/home/pi/RetroPie-Setup/tmp/build/crispy-doom/src/crispy-doom not found).

zerojay commented 6 years ago

I need the log for your compilation attempt.

On Thu, Mar 15, 2018, 04:31 XD3l, notifications@github.com wrote:

Retropie is fully and freshly updated and I am getting this message when compiling:

COuld not successfully build crispy-doom - Crispy Doom - Enhanced port of (blah blah blah)

(/home/pi/RetroPie-Setup/tmp/build/crispy-doom/src/crispy-doom not found).

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/zerojay/RetroPie-Extra/issues/276, or mute the thread https://github.com/notifications/unsubscribe-auth/AAmdndv-KG_xQnAO2Hht1L60DP1_NBHFks5teibXgaJpZM4SrvDz .

XD3l commented 6 years ago

Sorry, it has been FOREVER since I've dove into all of this. What is the command to run your Crispy script by hand again? If I recall correctly, that is how I went about getting a lot proper last time.

Do not let your theoretically benevolent care takers delude you into naive faith. - Jordan Peterson

On Thu, Mar 15, 2018 at 11:55 AM, zerojay notifications@github.com wrote:

I need the log for your compilation attempt.

On Thu, Mar 15, 2018, 04:31 XD3l, notifications@github.com wrote:

Retropie is fully and freshly updated and I am getting this message when compiling:

COuld not successfully build crispy-doom - Crispy Doom - Enhanced port of (blah blah blah)

(/home/pi/RetroPie-Setup/tmp/build/crispy-doom/src/crispy-doom not found).

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/zerojay/RetroPie-Extra/issues/276, or mute the thread https://github.com/notifications/unsubscribe-auth/AAmdndv-KG_ xQnAO2Hht1L60DP1_NBHFks5teibXgaJpZM4SrvDz .

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/zerojay/RetroPie-Extra/issues/276#issuecomment-373426437, or mute the thread https://github.com/notifications/unsubscribe-auth/AQ83qDqaSOsXvPyMv65aYAQQWgk1QEcmks5teo7VgaJpZM4SrvDz .

symbios24 commented 6 years ago

Install Chocolate doom is way better and faster.

XD3l commented 6 years ago

Thank you for your opinion, but I'd still like to know the command to run the Crispy DOOM install script individually so that I can provide Zero with the log he needs.

Do not let your theoretically benevolent care takers delude you into naive faith. - Jordan Peterson

On Thu, Mar 15, 2018 at 3:59 PM, symbios24 notifications@github.com wrote:

Install Chocolate doom is way better and faster.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/zerojay/RetroPie-Extra/issues/276#issuecomment-373504067, or mute the thread https://github.com/notifications/unsubscribe-auth/AQ83qBk45WYZoPgmn2fTxM-n1EkMoFyqks5tesgZgaJpZM4SrvDz .

symbios24 commented 6 years ago

good luck with that the command to run the script manual is sh crispy-doom.sh

you can compile it your self like this:

sudo apt-get install build-essential automake sudo apt-get build-dep chocolate-doom

cd crispy-doom autoreconf -vif ./configure make

i forgot to mention crispy doom has merged with chocolate doom

XD3l commented 6 years ago

sh crispy-doom.sh yields nothing from within the Retropie-Setup folder.

Chocolate compiles and runs fine... but has zero Crispy config options, so I'm confused about the two being merged...

Do not let your theoretically benevolent care takers delude you into naive faith. - Jordan Peterson

On Fri, Mar 16, 2018 at 3:39 AM, symbios24 notifications@github.com wrote:

good luck with that the command to run the script manual is sh crispy-doom.sh

you can compile it your self like this:

sudo apt-get install build-essential automake sudo apt-get build-dep chocolate-doom

cd crispy-doom autoreconf -vif ./configure make

i forgot to mention crispy doom has merged with chocolate doom

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/zerojay/RetroPie-Extra/issues/276#issuecomment-373629189, or mute the thread https://github.com/notifications/unsubscribe-auth/AQ83qPj1og1e7jisYml8JkR4cP11BDccks5te2xEgaJpZM4SrvDz .

XD3l commented 6 years ago

Turns out it compiles fine with the old apt-get command. Must be the script itself.

Do not let your theoretically benevolent care takers delude you into naive faith. - Jordan Peterson

On Fri, Mar 16, 2018 at 10:18 AM, Christopher advertandentice@gmail.com wrote:

sh crispy-doom.sh yields nothing from within the Retropie-Setup folder.

Chocolate compiles and runs fine... but has zero Crispy config options, so I'm confused about the two being merged...

Do not let your theoretically benevolent care takers delude you into naive faith. - Jordan Peterson

On Fri, Mar 16, 2018 at 3:39 AM, symbios24 notifications@github.com wrote:

good luck with that the command to run the script manual is sh crispy-doom.sh

you can compile it your self like this:

sudo apt-get install build-essential automake sudo apt-get build-dep chocolate-doom

cd crispy-doom autoreconf -vif ./configure make

i forgot to mention crispy doom has merged with chocolate doom

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/zerojay/RetroPie-Extra/issues/276#issuecomment-373629189, or mute the thread https://github.com/notifications/unsubscribe-auth/AQ83qPj1og1e7jisYml8JkR4cP11BDccks5te2xEgaJpZM4SrvDz .

zerojay commented 6 years ago

Crispy Doom is a fork off of Chocolate Doom.

Chocolate Doom recently made the jump from SDL1 to SDL2 and as such, so did Crispy Doom. This could have been fixed a long time ago if anyone posted the compilation logs as previously asked.