[Linphone-users] Compile on Windows fails: (belle-sip/dict.h: No such file or directory)

[Angelo]

Hi,

I'm trying to build linphone, but it seems I missed something or that 
the instructions are not complete (or both)
I would be thankful for any suggestion / feedback.


I installed mingw and msysgit
downloaded the linphone sources (HEAD) and followed the README.mingw 
instructions.

Finally I ended up with an error:
>         fi
> if test "`cat liblinphone_gitversion.h.tmp`" != "`cat 
> ./liblinphone_gitversion.h
> `" ; then \
>                 cp -f liblinphone_gitversion.h.tmp 
> ./liblinphone_gitversion.h ;
> \
>         fi
> rm -f liblinphone_gitversion.h.tmp ;
> make  all-recursive
> make[3]: Entering directory `/d/work//linphone/coreapi'
> Making all in .
> make[4]: Entering directory `/d/work//linphone/coreapi'
>   CC     linphonecore.lo
> In file included from linphonecore.c:22:0:
> linphonecore.h:36:28: fatal error: belle-sip/dict.h: No such file or 
> directory
>  #include <belle-sip/dict.h>

Well, Not sure what I'm missing.




Further minor observations:
The instructions fo compiling mingw are a little surprising:
- Why wget once to ~ (intltool_0.40.4-1_win32.zip) and once to / 
(GTK2-Outcrop.tar.gz)?

The url for the outcrop theme has changed:
http://ftp.gnome.org/pub/GNOME/teams/art.gnome.org/themes/gtk2/GTK2-Outcrop.tar.gz
The one in the documentation is outdated:

There were conflicts hwne unzipping:
It would be nice to say whether to skip / overwrite the conflicts.
The confilciting files were:
     bin/openssl.exe
     bin/certtool.exe
     bin/c_rehash.exe

A command line is indicated as
    tar -xvfz GTK2-Outcrop.tar.gz

but should probable be
    tar xvfz GTK2-Outcrop.tar.gz

I'm asked to remove three files from my MingW distribution (libintl.a 
libintl.la libintl.dll.a)
However I have only two files there.

I'd further be curious whether I break anything by removing these files. 
Did these files exist already before
I started following the instructions for setting up a linphone buiold 
environmment?
Wouldn't it be safer to just rename these files?


I'll try with the most recent tagged version to see whether the problem 
is version dependent (However my PC is quite slow, so I'll report back 
later in case this changes anything)