Befoe this we always used the installed modules from the system. That is often
fine but there are cases we would need the local. un-installed, modules. The
coverage check is a example. The system modules normally don't had the options
for coverage enabled and thus would not produce anything for the modules.
Default still stays as it was. You would need to set an env var to use the
local modules.
SVN revision: 80670
Really free the list with sensor modules when shutting down. No idea how I
dropped that as I found it in one old local version I had. Thanks to Mike
for the notice and valgrind for the tooling.
Also make sure we don't corrupt the list before we can free it.
SVN revision: 77291
Some bigger leak is still going on there with the module unloading. I swear that
was all non-leaking before. I had valgrind on it. :)
SVN revision: 77290
No longer needed as it only contains the modules information that will be
used in the eeze_sensor core. All other important bits have found new homes
in other data structures.
SVN revision: 76969
Extend eeze to read out sensor data from various sources with a simple API to
access for application developers. The sensor backends are eina modules. For
now we support a tizen module as well as a fake module for testing.
Modules for plain sysfs on a desktop or other sensor frameworks could get
integrated.
The api is not fixed until 1.8 is out so let me know what you think. Having
small wrappers for all kind of infos like eeze_sensor_light_get or
eeze_sensor_proximity_get are possible but I did not want to bloat the api
from the beginning.
SVN revision: 76825
Stefan Schmidt