I found my error. The eclipse implementation was looking in the wrong library directory '/usr/lib/' ad nthe evas folder in the directory only contained the buffer renderer. I had to configure my IDE to look in the /usr/local/lib where all the engines are installed.
Anyway, thanks for your quick replies! > From: [email protected] > To: [email protected] > Date: Tue, 15 Feb 2011 15:49:39 + > CC: [email protected] > Subject: Re: [E-devel] evas_render_method_lookup("software_x11") > > > EINA_LOG_LEVELS=3 ./you_app > > This was the way I ran the application in the console, but it makes no > difference. Is there some kind of log-file I should check? > > > Date: Tue, 15 Feb 2011 15:43:47 +0100 > > From: [email protected] > > To: [email protected] > > CC: [email protected] > > Subject: RE: [E-devel] evas_render_method_lookup("software_x11") > > > > > > > > On Tue, 15 Feb 2011, John Dovers wrote: > > > > > > > > I've checked the compiled modules and the software x11 is installed: > > > > > > /usr/local/lib/evas/modules/engines/software_x11/linux-gnu-i686-1.0.0$ ls > > > module.la module.so > > > > runs with > > > > EINA_LOG_LEVEL=3 your_app > > > > Vincent > > > > > > > >> Date: Tue, 15 Feb 2011 15:30:13 +0100 > > >> From: [email protected] > > >> To: [email protected] > > >> CC: [email protected] > > >> Subject: RE: [E-devel] evas_render_method_lookup("software_x11") > > >> > > >> > > >> > > >> On Tue, 15 Feb 2011, John Dovers wrote: > > >> > > >>> > > >>> Yes, I'm using c++ > > >> > > >> Maybe you don't know but there is a c++ binding > > >> > > >> Vincent > > >> > > >>> > > >>>> Date: Tue, 15 Feb 2011 15:08:48 +0100 > > >>>> From: [email protected] > > >>>> To: [email protected] > > >>>> CC: [email protected] > > >>>> Subject: Re: [E-devel] evas_render_method_lookup("software_x11") > > >>>> > > >>>> > > >>>> btw, you use c++ ? > > >>>> > > >>>> Vincent > > >>>> > > >>>> On Tue, 15 Feb 2011, Vincent Torri wrote: > > >>>> > > >>>>> > > >>>>> > > >>>>> On Tue, 15 Feb 2011, John Dovers wrote: > > >>>>> > > >>>>>> > > >>>>>> Hi, > > >>>>>> > > >>>>>> > > >>>>>> > > >>>>>> When I make the function call > > >>>>>> 'evas_render_method_lookup("software_x11")' the library returns an > > >>>>>> invalid id (= 0). I used the following code to print a list of the > > >>>>>> available render methods: > > >>>>>> > > >>>>>> Eina_List *engine_list, *l; > > >>>>>> char *engine_name; > > >>>>>> > > >>>>>> engine_list = evas_render_method_list(); > > >>>>>> > > >>>>>> if (!engine_list) > > >>>>>> { > > >>>>>> cerr << "ERROR: Evas supports no engines! Exit" << endl; > > >>>>>> exit(-1); > > >>>>>> } > > >>>>>> > > >>>>>> cout << "Availible Evas Engines:" << endl; > > >>>>>> l = engine_list; > > >>>>>> void* data = eina_list_data_get(l); > > >>>>>> > > >>>>>> while(l) { > > >>>>>> cout << (char*) data << endl; > > >>>>>> l = eina_list_next(l); > > >>>>>> data = eina_list_data_get(l); > > >>>>>> } > > >>>>>> > > >>>>>> evas_render_method_list_free(engine_list); > > >>>>>> > > >>>>>> and this was the output: > > >>>>>> > > >>>>>> Availible Evas Engines: > > >>>>>> > > >>>>>> software_x11 > > >>>>>> > > >>>>>> xrender_x11 > > >>>>>> > > >>>>>> gl_x11 > > >>>>>> > > >>>>>> fb > > >>>>>> > > >>>>>> buffer > > >>>>>> > > >>>>>> > > >>>>>> > > >>>>>> Although 'software_x11' is mentioned in the list, I'm not able to > > >>>>>> lookup this method. > > >>>>> > > >>>>> evas_render_method_lookup() does check if the module exists or not > > >>>>> > > >>>>> evas_render_method_list() has harcoded values according to what is > > >>>>> passed > > >>>>> to configure, hence does not check if the modules really exist. This > > >>>>> function should be fixed, imho. > > >>>>> > > >>>>> So does not rely on the results of evas_render_method_list(). If > > >>>>> evas_render_method_lookup() fails, then it certainly means that the > > >>>>> module is not compiled, or is disabled at configure time for some > > >>>>> reason. > > >>>>> > > >>>>> First check if the result of configure says that software x11 (xlib) > > >>>>> is > > >>>>> available, then be sure that the module is compiled and installed > > >>>>> > > >>>>> Vincent > > >>>>> > > >>>>> ------------------------------------------------------------------------------ > > >>>>> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio > > >>>>> XE: > > >>>>> Pinpoint memory and threading errors before they happen. > > >>>>> Find and fix more than 250 security defects in the development cycle. > > >>>>> Locate bottlenecks in serial and parallel code that limit performance. > > >>>>> http://p.sf.net/sfu/intel-dev2devfeb > > >>>>> _______________________________________________ > > >>>>> enlightenment-devel mailing list > > >>>>> [email protected] > > >>>>> https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > > >>>>> > > >>>>> > > >>> > > > > > ------------------------------------------------------------------------------ > The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: > Pinpoint memory and threading errors before they happen. > Find and fix more than 250 security defects in the development cycle. > Locate bottlenecks in serial and parallel code that limit performance. > http://p.sf.net/sfu/intel-dev2devfeb > _______________________________________________ > enlightenment-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
