Together with eeze_sensor_module_register/unregister these are the functions
that are irrelevant for developer when they just want to use the eeze_sensor
API.
Still all three need to be marked with EAPI as they are used in the backend
modules and due to our visibility hidden usage the module loading would fail
if we remove EAPI from them.
Moving them into the private header should give an indication that these are
not meant for pure API users.
*/
EAPI Eina_Bool eeze_sensor_async_read(Eeze_Sensor_Obj *sens, void *user_data);
-/**
- * @brief Fetch the sensor object by type from the sensor object list
- * @param type Sensor type to fetch from the list of sensor objects.
- * @return The sensor object matching the given type
- *
- * @since 1.8
- */
-EAPI Eeze_Sensor_Obj *eeze_sensor_obj_get(Eeze_Sensor_Type type);
-
#ifdef __cplusplus
}
#endif
EAPI Eina_Bool eeze_sensor_module_unregister(const char *name);
/**
+ * @brief Fetch the sensor object by type from the sensor object list
+ * @param type Sensor type to fetch from the list of sensor objects.
+ * @return The sensor object matching the given type
+ *
+ * @since 1.8
+ */
+EAPI Eeze_Sensor_Obj *eeze_sensor_obj_get(Eeze_Sensor_Type type);
+
+/**
* @brief Initialize the Eeze sensor subsystem.
* @return EINA_TRUE for success and EINA_FALSE for failure
*
#include <Eeze_Net.h>
#include "eeze_udev_private.h"
+#include "eeze_sensor_private.h"
START_TEST(eeze_test_init)
{