use `ctypes.util.find_library` to find library path, instead of loading from `pylibui/sharedlibs` ? about pylibui HOT 3 CLOSED

And there is another benefit of distributing the libui binary ourselves which is that we may decide to only distribute the libui binary that matches the current state of pylibui.. As long as libui binaries are smallish, this seems a good approach to me. :)

from pylibui.

It's a possibility, although I fear that it will force users to copy the library to some system folder and in most systems you do not have easy root access to do that (for instance, on OS X you cannot see system libraries by default in the file viewer app [Finder]).

As it is now, by forcing people to copy the shared library to a folder that we control we always know where it is, and in the future it will be easy for us to also distribute the libui binary with pylibui making pylibui completely transparent for users (specially for Windows users which usually do not have C compilers installed).. In other words, now we have to pip install pylibui and cmake libui, in the future I will probably distribute libui itself inside pylibui..

from pylibui.

We could allow developer possibility to either load system or package library (just by using a flag or else), as in
https://github.com/jamescook/libui-ruby/blob/master/lib/config.rb#L10

from pylibui.