From: Andreas V. <li...@br...> - 2013-02-26 21:15:54
|
Am Tue, 26 Feb 2013 22:01:24 +0100 schrieb Andreas Volz: > Am Mon, 25 Feb 2013 23:24:53 +0100 schrieb Leif Middelschulte: > > > Am Montag, 25. Februar 2013 um 22:57 schrieb Andreas Volz: > > > Am Mon, 25 Feb 2013 11:47:21 +0900 (KST) schrieb ChunEon Park: > > > > > > > ah mistake. > > > > EINA_LOG_LEVEL=3 > > > > > > > > > > > > > As I said... no good chance to modify the C environment in > > > Android... > > > I hacked > > > > > > static Eina_Log_Level _log_level = EINA_LOG_LEVEL_DBG; > > > > > > in eina_log.c > > > > > > now it works :-) > > Android bionic's libc has setenv. Can't you call it to modify your > > env before you initialize eina? > > The problem is that I have to load C libs in reverse order in Java. > So I start with eina and end with my private C library that links > again all efl. So if it would be possible I need to write a shared > object ONLY to link against eina and modify environment to then > continue with rest of efl to enable logging early enough to trace > ecore_evas module loader debug messages. :-) > > In this case it's easier to modify eina code for me... After some minutes thinking about what I've written above I don't think it's true what I've written. :-( Loading the shared object wouldn't call the ecore_evas module loader! I'll later try to use setenv before I initialize EFL. This was somehow a black out... :-) -- Technical Blog <http://andreasvolz.wordpress.com/> |