I am having a problem with fpc picking up linking directories on my
Raspberry Pi.
I have a this lib:
/opt/vc/lib/libGLESv2.so
When I execute "ldconfig -v" it shows both "/opt/vc/lib/" as a ld link
directory, and the file libGLESv2.so as a linkable library.
But when I use this code in a unit:
Thanks for the explanation.
I guess I'll create symlinks in the standard locations (/usr/lib) for these
libraries and put that in an install script. Either that or add to fpc.cfg,
I'm not sure which is better.
Explanation: I'm creating a series of Pi examples for GLES2 and SDL2 along
the lines
On 12/11/2015 09:50 AM, Anthony Walter wrote:
I am having a problem with fpc picking up linking directories on my
Raspberry Pi.
I have a this lib:
/opt/vc/lib/libGLESv2.so
I get this linker error during compile:
/usr/lib/ld: cannot lind -lGLESv2
But when I compile adding -Fl/opt/vc/lib
Anthony Walter wrote on Fri, 11 Dec 2015:
I am having a problem with fpc picking up linking directories on my
Raspberry Pi.
It's unrelated to FPC. The same will happen with GCC or Clang.
I have a this lib:
/opt/vc/lib/libGLESv2.so
When I execute "ldconfig -v" it shows both "/opt/vc/lib/"
On 11/12/15 17:44, Anthony Walter wrote:
I guess I'll create symlinks in the standard locations (/usr/lib) for
these libraries and put that in an install script. Either that or add to
fpc.cfg, I'm not sure which is better.
Definitely the latter. Everything under /usr belongs exclusively to the
Jonas, well the thing is on Raspbian the GLESv2 implementation, which works
with the Pi GPU, is at /opt/vc/lib by default. It's owned by root and there
is no install. The install I was referring to is building and installing of
SDL2 from sources. I already have to tell SDL2 build to find the
On 11/12/15 18:44, Anthony Walter wrote:
Jonas, well the thing is on Raspbian the GLESv2 implementation, which
works with the Pi GPU, is at /opt/vc/lib by default. It's owned by root
and there is no install. The install I was referring to is building and
installing of SDL2 from sources. I
