Hi, I recently sent a patch so the ctypes structures would have the right sizes on Solaris (thanks for merging!), but I was not sure what would be the best way for the libusb0 backend to handle the strange location of the shared object on Solaris. It's /usr/sfw/lib/libusb.so.1
Should that name just be added to the big list o' names already in libusb0.py _load_library()? Or check for sys.platform == 'sunos5' and define a different _load_library that knows the right path? Or some other approach? I also recently saw this blog post here: http://emergent.unpythonic.net/01330399156 where somebody wrote a C port of a Python script that was using pyusb because it was too slow. The post says that the compiler, objdump, and ldconfig were getting run when the Python script started up. I don't see that when I run it (same script, but I modified it to pass a find_library lambda that just returns the Solaris library path). So maybe the only time those expensive external processes get run are during the library search? In that case, maybe it's good to hardcode the path when known ... or fall back to the expensive way if the hardcoded path isn't found. -Chap ------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y _______________________________________________ pyusb-users mailing list pyusb-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pyusb-users
