linphone-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Linphone-users] Compile on Windows fails: (belle-sip/dict.h: No suc


From: Angelo
Subject: Re: [Linphone-users] Compile on Windows fails: (belle-sip/dict.h: No such file or directory)
Date: Mon, 23 Dec 2013 18:46:10 +0100
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0

Hi

This time I compiled a tagged version (3.6.99)
submodules were at:
$ git submodule
c516f225bea6ac2132f3468235138e2dde6cfcda mediastreamer2 (2.9.1-46-gc516f22)
 706f0b59f818a69c673053e831fa1f19a855f80b oRTP (0.22.0-7-g706f0b5)

I performed a git clean -fdx in the repo and each submodules repo prior to running

./autogen.sh && ./configure --prefix=/usr --enable-shared --disable-static && make

This time compilation went a little further, but I still encountered an error:
  CC     sal_op_call.lo
  CC     sal_op_registration.lo
bellesip_sal/sal_op_registration.c: In function 'sal_register':
bellesip_sal/sal_op_registration.c:92:2: error: passing argument 4 of
'sal_op_se
nd_and_create_refresher' from incompatible pointer type [-Werror]
  return
sal_op_send_and_create_refresher(op,req,expires,register_refresher_list
ener);
  ^
In file included from bellesip_sal/sal_op_registration.c:19:0:
bellesip_sal/sal_impl.h:119:5: note: expected
'belle_sip_refresher_listener_t' b
ut argument is of type 'void (*)(const struct belle_sip_refresher_t *,
void *, u
nsigned int,  const char *)'
 int sal_op_send_and_create_refresher(SalOp* op,belle_sip_request_t*
req, int ex
pires,belle_sip_refresher_listener_t listener );
     ^
cc1.exe: all warnings being treated as errors
make[4]: *** [sal_op_registration.lo] Error 1



 (On 12/23/2013 6:31 PM, Angelo wrote:
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)


_______________________________________________
Linphone-users mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/linphone-users




reply via email to

[Prev in Thread] Current Thread [Next in Thread]