From: Pat C. <pce...@at...> - 2002-03-08 00:27:31
|
This is mostly for other novices who run into 'problems' like I do. I fixed my problems with evas_test. evas_test was actually built correctly. I made the mistake of running evas_test before 'make install'. evas_test was looking for images in: /usr/local/e17/share/evas/img/ ...but since I hadn't run 'make install' none of the images could be loaded. As a side note, (I just updated from CVS about an hour ago) evas_test is one of the coolest demo's I've seen! I'm very excited about building the rest of e17 now. Excellent work and thanks to those who emailed me suggestions. ------------------------------------------------------ Pat Cevasco wrote: Hello, I'm building E17 from CVS I checked out about an hour ago and 'evas_test' segfault'd. I took the suggestion below and rebuilt imlib2 with --disable-mmx and it no longer segfaults. But, the window that appears just has a border and title bar. The internal window where evas should be doing it's stuff is just a copy of what's behind it. 'evas_test_old' seems to work fine. I did notice in the evas README file that Mesa 3.2 causes problems that were fixed in Mesa 3.3. Evidently Debian Woody (which I'm running) uses Mesa 3.1-17. Before I grab a new version of Mesa is there a version that's better suited for e17 than others? Should I grab 3.3 or should I go to 4.0? I'll also make note that I use a GeForce2 card with nvidia driver 1.0-1541. Thanks, Pat Christian Kreibich wrote: > David Coulson wrote: > >>Hi, >> >> I'm building E17 out of CVS (it's still going), but upon running >>'evas_test', just to try it out, it immediatly segfaults. It built >>cleanly and installed okay, so I'm not sure what the problem is with it. >> > > Have you tried compiling Imlib2 with --disable-mmx? > > Christian. > |