JB Kim wrote: > Hi > > Been going through sigrok source code. It's really well written!
Thanks! > I got the impression that each plugin would be compiled as its own shared > lib and its symbol get imported and device_plugin struct initialized > during runtime. Is this something planned for the future? The hardware drivers actually used to be shared libs dynamically loaded at runtime, but they were recently changed to linked-in objects. As you noticed, they still sort of look like typical DL plugins. There really wasn't a very good reason to have them dynamically loaded, and what we want to avoid at all costs is people releasing binary-only drivers for hardware to work in sigrok. Indeed, opening up the proprietary/closed protocols and hardware is one of sigrok's specific goals. By linking the drivers into libsigrok as a whole, we make this a non-issue. > Also, what is the reason for removing dependency on glib? Just curious. Mostly that it's an extra dependency, and the little of glib functionality that we use (compared to the huge amount it offers) doesn't really justify having the dependency. Having said that, the windows port needs glib more than the various unix builds, because of some of the cross-platform functionality it offers. So we might keep it after all, now. -- Bert Vermeulen [email protected] email/xmpp ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ sigrok-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sigrok-devel
