pthread manual says it is safe to destroy them after they are used
with pthread_create: "If the attributes specified by attr are modified
later, the thread���s attributes shall not be affected."
SVN revision: 34937
If we tried to create the new rw file, we must check if it was created
fine before continue, lots of errors are possible there, but mine was
creating the file inside an nonexistent directory.
SVN revision: 34928
The type "char" is not defined to have a sign or not, for performance
issue some platforms (ie: ARM) define it as unsigned. If we need to
rely on the sign, must say so.
SVN revision: 34924
It also add EET_G_VAR_ARRAY and EET_G_ARRAY thanks to
turran's (jorgeluis.zapata@gmail.com) last year patch.
Of course we have test code for it and eet_data.c code
is covered around 90.1%. We need to test with garbage
data for increasing it more.
WARNING: API of eet_data_descriptor_element_add is not
clean and we will need to break it, if we want a clean
API. So this is the plan for version 2.0.0.
SVN revision: 34919
EAPI int ecore_file_dir_is_empty(const char*dir)
Should we need to upgrade the ecore version? so apps that need this function can check for the right version?
Thanks
Dave
SVN revision: 34889
Currently debian/rules requires these dependancies to else
the following errors occur:
When automake is missing:
./autogen.sh
[...]
Running aclocal...
./autogen.sh: line 8: aclocal: command not found
make: *** [clean] Error 1
./autogen.sh
[...]
configure.in:20: error: possibly undefined macro: AC_LIBTOOL_WIN32_DLL
If this token and others are legitimate, please use m4_pattern_allow.
See the Autoconf documentation.
configure.in:23: error: possibly undefined macro: AC_PROG_LIBTOOL
make: *** [clean] Error 1
When pkg-config is missing:
./autogen.sh
[...]
configure: creating libtool
./configure: line 14491: PKG_PROG_PKG_CONFIG: command not found
./configure: line 14499: syntax error near unexpected token `EVIL,'
./configure: line 14499: ` PKG_CHECK_MODULES(EVIL, evil)'
make: *** [clean] Error 2
SVN revision: 34790