From: Vincent T. <vin...@gm...> - 2012-10-28 10:38:48
|
On Fri, Oct 26, 2012 at 3:04 PM, Vincent Torri <vin...@gm...> wrote: > On Fri, Oct 26, 2012 at 2:51 PM, LM <lm...@gm...> wrote: >> Vincent Torri wrote: >>>* about the build, there is a wiki page, but it's not up to date >>>(because of some move in the trunk). Before that move, i can build and >>>run the EFL on Windows XP. I've never tried with win > XP >> >> I read the wiki page. As you mentioned, it's not up-to-date. >> >> So, does this mean there's no place to submit patches and work-arounds >> for Windows developers? I've already spent quite a lot of time trying >> to track down why certain libraries wouldn't compile and coming up >> with patches. I have evil, eina, evas, ecore, eet, embryo compiling >> and building successfully with patches. Was looking into edje which >> also won't build on my system without patching. I thought standard >> procedure with Open Source projects was to contact the developers and >> share fixes needed to make them work on other platforms. > > send the patches on the ML, please. I'll take care of them (well i'll > be away for 5 days, so don't expect them to hit svn immediatly). I > prefer the ML instead of a private mail. > >>> * dlfcn-win32 is dead and the author does not want to add non POSIX >>>extension (like the GNU dladdr, which I have added). I have too less >>>time to fix that. If you can provide a patch that fix all the >>>problems, fine, otherwise, install the EFL in their own directory, it >>>will fix the problem >> >> MinGW project still recommends the dlfcn-win32 library. If you have >> something better, you should let them know about it. Thanks. > > I don't use MingW, I use mingw-w64. A LOT better. And as I said, just > install the EFL in their own dir, it's sufficient. > > I won't let MinGW devs know about that problem as they won't do > anything anyway about dlfcn-win32. I've already dealt with them, with > patches, etc... I have patches in their bugzilla that I sent 6 or 7 > years ago... So I gave up. > > The problem with Windows is that there is no centralized package > system. The only viable solution is to install a project, an > application, etc... in its own directory. also, for the current efl/ subdir, eina can not be compiled (eina_thread.c), I'm waiting for cedric to fix that code (it's his code..) Vincent |