Re: [E-devel] [PATCH] Only unlink the temporary file created in evas_object_image_memfile_set on cleanup (was evas_object_image_memfile_set is broken on non-Linux platforms)

2012-05-17 Thread Lucas De Marchi
On Wed, May 16, 2012 at 12:09 PM, Raphael Kubo da Costa rak...@freebsd.org wrote: Lucas De Marchi lucas.demar...@profusion.mobi writes: The renaming there is probably a hack so code paths that calls stat() to check if the file exists. If you know it exists, you could rename it to / for

Re: [E-devel] [PATCH] Only unlink the temporary file created in evas_object_image_memfile_set on cleanup (was evas_object_image_memfile_set is broken on non-Linux platforms)

2012-05-16 Thread Lucas De Marchi
On Tue, May 15, 2012 at 10:21 PM, Raphael Kubo da Costa rak...@freebsd.org wrote: Raphael Kubo da Costa rak...@freebsd.org writes: I was working on some code which uses evas_object_image_memfile_set here on FreeBSD, and it was failing. After some investigation, I found out that the problem

Re: [E-devel] [PATCH] Only unlink the temporary file created in evas_object_image_memfile_set on cleanup (was evas_object_image_memfile_set is broken on non-Linux platforms)

2012-05-16 Thread Raphael Kubo da Costa
Lucas De Marchi lucas.demar...@profusion.mobi writes: The renaming there is probably a hack so code paths that calls stat() to check if the file exists. If you know it exists, you could rename it to / for example or any path in put-here-your-choice-of-OS that is guaranteed to exist in the

[E-devel] [PATCH] Only unlink the temporary file created in evas_object_image_memfile_set on cleanup (was evas_object_image_memfile_set is broken on non-Linux platforms)

2012-05-15 Thread Raphael Kubo da Costa
Raphael Kubo da Costa rak...@freebsd.org writes: I was working on some code which uses evas_object_image_memfile_set here on FreeBSD, and it was failing. After some investigation, I found out that the problem was in the stat() call in evas_cache_image_request. On Linux, _create_tmpf()