Open yurivict opened 1 year ago
I wasn't aware of glinfo
is also being used by mesa. I was only aware of glxinfo
. As we don't want to provoke name clashes, we should rename our tools, including glinfo
.
However, I'm not sure which way of installing glbinding
you have used. Maybe you can provide some more details.
Usually, package maintainers just package the glbinding
and the glbinding-aux
library for their distributions.
I don't know any process to check whether an executable name is already taken for each distribution and package manager.
It seems as if you're working on FreeBSD, which is a platform we strive to support, but don't officially support at the moment.
Your input is appreciated, but I don't see a more constructive approach besides this trial and error process (https://github.com/cginternals/glbinding/issues/328, https://github.com/cginternals/glbinding/issues/299).
If you installed glbinding
yourself, you may want to install only parts of it.
In our CMake setup, we define several components and dependencies between them.
For example, you can install runtime
and dev
without tools
or examples_glfw
.
We use cmake to install glbinding.
I don't know any process to check whether an executable name is already taken for each distribution and package manager.
There is no such process. You should just rename the commands in question, for example add the glbinding-
prefix.
Could you please not install
bin/glinfo
, and any other files that conflict with anything else?