Support for Raspian Stretch Lite

[ira...@gmail.com]

Hello,

I installed simple2d on a Raspberry Pi 3 Model B. The Pi is running the latest version of Raspian Stretch Lite (the non-Desktop version). When I try to build the example file, I get the following:

pi@raspberrypi:~ $ simple2d build triangle.c

/usr/bin/ld: cannot find -lGLESv2

/usr/bin/ld: cannot find -lsmpeg2

collect2: error: ld returned 1 exit status

pi@raspberrypi:~ $ cc triangle.c `simple2d --libs` -o triangle

/usr/bin/ld: cannot find -lGLESv2

/usr/bin/ld: cannot find -lsmpeg2

collect2: error: ld returned 1 exit status

Do I need to download the desktop version of Raspian instead?

Thanks

[Tom Black]

Hi there,

The Raspian folks changed the location of stuff in Stretch. I've made some updates to fix those, and a few other weird things. Everything should work fine in Lite and Desktop. I haven't published a new release yet, but you can either clone the repo (from the master branch) or use the install script from the web running `simple2d.sh install --HEAD` (the option will install from the master branch). I've also updated the version of SDL in the script, so you may want to uninstall first using `simple2d.sh uninstall --sdl` or just use a clean SD card.

Hope that helps, let me know if you still run into issues.

Tom

[ira...@gmail.com]

Wow, thank you for the prompt response!

So that worked, but I'm having an issue running auto.c. I cloned the git repos in /home/pi/. When I run auto, it can't find the image assets.

==> Running test (S2D_CreateImage) bad image file path

Error: (S2D_CreateImage) Image file not found

Error: (S2D_CreateImage) Image file not found

Error: (S2D_CreateImage) Image file not found

I know everything compiled, because triangle works fine. I've tried running auto from the test/ directory and changing the image path to an absolute path. Nothing seems to work. Any ideas?

[Tom Black]

Of course, happy to help!

Could be that you cloned with out the `--recursive` flag? The test media is in a submodule, so you'll need those for the tests (you can run `git submodule init && git submodule update --remote` in the repo without re-cloning the whole thing).

If the test media is there and `make auto` and `make testcard` fail, then we'll have to dig deeper.

[Tom Black]

Oh, duh, I just realized that's expected in the automated tests. When bad file paths are given to media creation functions, errors are suppose to be reported, I should make that more clear. Hopefully at the end of all the output, you should see:

All tests passed!

26 examples, 0 failures