Hey,

> After your recommendations, I did a new setup. I now used the following 
> versions:
>
> autoconf v2.61 (the newer versions 2.62 and 2.63 did not work)

for autoconf 2.63, unzip the m4 binary that you can find in the mingw 
sourceforge downlad section

http://sourceforge.net/project/downloading.php?group_id=2435&filename=m4-1.4.7-MSYS.tar.bz2&a=80911513

> automake 1.10.2
> libtool 2.2.6
>
> I had to do two modifications to the e source tree:
> evil : evil_pwd.c    add the line #include <ntsecapi.h> after the line 
> #include <windows.h>

Install w32api 3.13 and tell me if it solves the problem. One should not 
include that file (according to msdn documentation.

http://sourceforge.net/project/downloading.php?group_id=2435&filename=w32api-3.13-mingw32-dev.tar.gz&a=71315422

I have updated the wiki on trac for that.

> ecore : use the patch for the src/lib/ecore_evas/Makefile.am adding the 
> @EVIL_LIBS@ library.

it's strange that it fails with libtool 2.2.6. I cross compile, so maybe 
it could be the reason why it does not fail for me.

> I managed to build all libraries described in the Trac Windows XP description.
>
> I could not build EFREET.

it has been a long time since i didn't compile efreet on Windows

> My goal is to build EWL. Building EWL is not successful with this setup.

when i built efreet, ewl compiled finely and it worked more or less.

> I have some questions about EWL:
> Is it possible at this moment to build EWL on the Windows platform?
> While EWL is platform independent, why is it so that it is said the EWL 
> has bugs on the Microsoft platform? In my opinion if the EWL layer is 
> platform independent the bugs should be in platform dependent code. Can 
> someone explain this?

Porting to a platform like Windows is not an easy task. Ewl relies on a 
lot of efl. If these libraries are not working correctly, ewl will not 
work correctly.

in addittion, ewl has been written on linux, and can be compiled easily on 
other unices, but Windows is another beast.

> I have the following output from the EWL build which now needs to be 
> addressed:
>
> /bin/sh ../../libtool --tag=CC   --mode=compile gcc -std=gnu99 
> -DHAVE_CONFIG_H -I. -I../..  -I../.. -I../.. 
> -DPACKAGE_DATA_DIR=\"/usr/local/share\" -DPACKAGE_LIB_DIR=\"/usr/local/lib\" 
> -DPACKAGE_SYSCONF_DIR=\"/usr/local/etc\"  -IC:/msys/1.0/local/include 
> -IC:/msys/1.0/local/include/eina-0 -IC:/msys/1.0/local/include/eina-0/eina   
> -IC:/msys/1.0/local/include -IC:/msys/1.0/local/include/eina-0 
> -IC:/msys/1.0/local/include/eina-0/eina   -IC:/msys/1.0/local/include 
> -IC:/msys/1.0/local/include/eina-0 -IC:/msys/1.0/local/include/eina-0/eina    
>   -IC:/msys/1.0/local/include   -I/usr/local/include  -Wall -g -O0 -MT 
> libewl_la-ewl_filelist.lo -MD -MP -MF .deps/libewl_la-ewl_filelist.Tpo -c -o 
> libewl_la-ewl_filelist.lo `test -f 'ewl_filelist.c' || echo 
> './'`ewl_filelist.c
> libtool: compile:  gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I../.. -I../.. 
> -DPACKAGE_DATA_DIR=\"/usr/local/share\" -DPACKAGE_LIB_DIR=\"/usr/local/lib\" 
> -DPACKAGE_SYSCONF_DIR=\"/usr/local/etc\" -IC:/msys/1.0/local/include 
> -IC:/msys/1.0/local/include/eina-0 -IC:/msys/1.0/local/include/eina-0/eina 
> -IC:/msys/1.0/local/include -IC:/msys/1.0/local/include/eina-0 
> -IC:/msys/1.0/local/include/eina-0/eina -IC:/msys/1.0/local/include 
> -IC:/msys/1.0/local/include/eina-0 -IC:/msys/1.0/local/include/eina-0/eina 
> -IC:/msys/1.0/local/include -I/usr/local/include -Wall -g -O0 -MT 
> libewl_la-ewl_filelist.lo -MD -MP -MF .deps/libewl_la-ewl_filelist.Tpo -c 
> ewl_filelist.c  -DDLL_EXPORT -DPIC -o .libs/libewl_la-ewl_filelist.o
> In file included from ewl_filelist.c:3:


[snip]

> Someone has a hint?

well, i have to dig in that, I think. I'll check that soon (i don't have 
my desktop computer, where i have some local changes)

regards

Vincent

------------------------------------------------------------------------------
Stay on top of everything new and different, both inside and 
around Java (TM) technology - register by April 22, and save
$200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today. 
Use priority code J9JMT32. http://p.sf.net/sfu/p
_______________________________________________
enlightenment-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Reply via email to