Re: [pjsip] Win32 build doesn't build because of stddef.h

DS
darmawan salihun
Thu, Nov 8, 2007 2:28 AM

another note is, you don't need mingw to compile pjsip.Visual studio and platform sdk is enough.Also make sure you downloaded all of the needed source code from the repository.

  • original message -
    Subject: Re: [pjsip] Win32 build doesn't build because of stddef.h
    From: "Perry Ismangil" perry@pjsip.org
    Date: 07/11/2007 23:30

There seems to be a huge gap here...

  • You can't #include  lib file. Include is for other text files,
    usually header  files.
  • lib files are binary files which will be linked to the application,
    not compiled.

I suggest you start with something smaller than pjsip to get the
basics on building C applications that uses external libraries.

Cheers,

On 11/7/07, Eagle I Martin Baranski eagle3386@googlemail.com wrote:

2007/11/6, Eagle I Martin Baranski eagle3386@googlemail.com:

2007/11/6, Perry Ismangil perry@pjsip.org:

On 11/6/07, Eagle I Martin Baranski eagle3386@googlemail.com wrote:

Though, since I neither installed Visual Studio nor the Platform SDK,
is this the only step I need to do or do I have to install Visual
Studio and/or the Platform SDK, too?

Although you are not using Visual Studio, you will still need all the
SDK mentioned on the building pjsip docs.

Hope this helps.

It helped a lot - thanks for clearing this completing out! :)

I'm now installing the SDK and setting up everything.. - I'll let you
all know if it worked afterwards.. ;)

Alright, got the Platform SDK installed, but it still didn't work.. So
I did some research again and finally found out, that the stddef.h is
within MinGW's directories..

Now, the problem is, that although I've specified the proper
search-path (C:\MinGW\include), the compiler (or Code::Blocks, don't
know for sure) wants the exact path
(C:\MinGW\lib\gcc\mingw32\3.4.5\include), too.

So, I've added that one and finally there were a lot of errors gone

  • though, it didn't found pjsua.h (although "....\pjsip\include" is
    specified, it additionally needed "....\pjsip\include\pjsua-lib" to
    find the header-file)..

Then, everything seemed to work fine, but it didn't.. The compiler
complained about "#include expects "FILENAME" or <FILENAME>", but I'm
not that stupid, so I fixed it by adding Platform SDK's lib-path to
the search-paths and also by adding quotes:

#include <pjlib.h>
#include <pjlib-util.h>
#include <pjnath.h>
#include <pjsip.h>
#include <pjsip_ua.h>
#include <pjsip_simple.h>
#include <pjsua.h>
#include <pjmedia.h>
#include <pjmedia-codec.h>
#include "wsock32.lib"
#include "ws2_32.lib"
#include "ole32.lib"
#include "dsound.lib"

But this is where I go crackers.. Since the compiler now finds what he
needs, I got again about 50 errors and 74 warnings.. - and they all
complain about wsock32.lib:

-------------- Build: Release Win32 in pjsua ---------------
[ 50.0%] Compiling: ..\src\pjsua\main.c
In file included from M:\Coding\pj-sip\pjsip-apps\src\pjsua\main.c:44:
C:/Program Files/System/Platform SDK/Windows/Lib/wsock32.lib:1: error:
syntax error before '!' token
C:/Program Files/System/Platform SDK/Windows/Lib/wsock32.lib:2: error:
stray '`' in program
In file included from M:\Coding\pj-sip\pjsip-apps\src\pjsua\main.c:44:
C:/Program Files/System/Platform SDK/Windows/Lib/wsock32.lib:3:1:
warning: null character(s) ignored
C:/Program Files/System/Platform SDK/Windows/Lib/wsock32.lib:3: error:
stray '\141' in program

So, I looked into that file - and this is all I could find:

!<arch>
/              1132304112              0      3410      `

Three lines of code are all that file handles? Hum, did I miss something?
The wsock32.lib inside the sub-directory called "x64" has the same
content, except the first number which is different there..

--
Perry Ismangil
Mobile: +44 7761 179 575
http://www.pjsip.org

PJSIP LLP
23 Langdon Street, Sheffield S11 8BH, United Kingdom
T +44 114 299 8883 F +44 7092 216 3097
Registered in England no. OC323977


Visit our blog: http://blog.pjsip.org

pjsip mailing list
pjsip@lists.pjsip.org
http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org

--

= ~ Code is poetry ~

= Martin Baranski
= Eagle | Eagle3386
= www.troublezone.net
= eagle3386@gmail.com
= +49 (0)160 93317843

--

= ~ Code is poetry ~

= Martin Baranski
= Eagle | Eagle3386
= www.troublezone.net
= eagle3386@gmail.com
= +49 (0)160 93317843


Visit our blog: http://blog.pjsip.org

pjsip mailing list
pjsip@lists.pjsip.org
http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org

--
Perry Ismangil
Mobile: +44 7761 179 575
http://www.pjsip.org

PJSIP LLP
23 Langdon Street, Sheffield S11 8BH, United Kingdom
T +44 114 299 8883 F +44 7092 216 3097
Registered in England no. OC323977


Visit our blog: http://blog.pjsip.org

pjsip mailing list
pjsip@lists.pjsip.org
http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org

another note is, you don't need mingw to compile pjsip.Visual studio and platform sdk is enough.Also make sure you downloaded all of the needed source code from the repository. - original message - Subject: Re: [pjsip] Win32 build doesn't build because of stddef.h From: "Perry Ismangil" <perry@pjsip.org> Date: 07/11/2007 23:30 There seems to be a huge gap here... - You can't #include lib file. Include is for other text files, usually header files. - lib files are binary files which will be linked to the application, not compiled. I suggest you start with something smaller than pjsip to get the basics on building C applications that uses external libraries. Cheers, On 11/7/07, Eagle I Martin Baranski <eagle3386@googlemail.com> wrote: > 2007/11/6, Eagle I Martin Baranski <eagle3386@googlemail.com>: > > 2007/11/6, Perry Ismangil <perry@pjsip.org>: > > > On 11/6/07, Eagle I Martin Baranski <eagle3386@googlemail.com> wrote: > > > > > > > > Though, since I neither installed Visual Studio nor the Platform SDK, > > > > is this the only step I need to do or do I have to install Visual > > > > Studio and/or the Platform SDK, too? > > > > > > > > > > Although you are not using Visual Studio, you will still need all the > > > SDK mentioned on the building pjsip docs. > > > > > > Hope this helps. > > > > It helped _a lot_ - thanks for clearing this completing out! :) > > > > I'm now installing the SDK and setting up everything.. - I'll let you > > all know if it worked afterwards.. ;) > > Alright, got the Platform SDK installed, but it still didn't work.. So > I did some research again and finally found out, that the stddef.h is > within MinGW's directories.. > > Now, the problem is, that although I've specified the proper > search-path (C:\MinGW\include), the compiler (or Code::Blocks, don't > know for sure) wants the exact path > (C:\MinGW\lib\gcc\mingw32\3.4.5\include), too. > > So, I've added that one and finally there were _a lot_ of errors gone > - though, it didn't found pjsua.h (although "..\..\pjsip\include" is > specified, it additionally needed "..\..\pjsip\include\pjsua-lib" to > find the header-file).. > > Then, everything seemed to work fine, but it didn't.. The compiler > complained about "#include expects "FILENAME" or <FILENAME>", but I'm > not that stupid, so I fixed it by adding Platform SDK's lib-path to > the search-paths and also by adding quotes: > > #include <pjlib.h> > #include <pjlib-util.h> > #include <pjnath.h> > #include <pjsip.h> > #include <pjsip_ua.h> > #include <pjsip_simple.h> > #include <pjsua.h> > #include <pjmedia.h> > #include <pjmedia-codec.h> > #include "wsock32.lib" > #include "ws2_32.lib" > #include "ole32.lib" > #include "dsound.lib" > > But this is where I go crackers.. Since the compiler now finds what he > needs, I got again about 50 errors and 74 warnings.. - and they _all_ > complain about wsock32.lib: > > -------------- Build: Release Win32 in pjsua --------------- > [ 50.0%] Compiling: ..\src\pjsua\main.c > In file included from M:\Coding\pj-sip\pjsip-apps\src\pjsua\main.c:44: > C:/Program Files/System/Platform SDK/Windows/Lib/wsock32.lib:1: error: > syntax error before '!' token > C:/Program Files/System/Platform SDK/Windows/Lib/wsock32.lib:2: error: > stray '`' in program > In file included from M:\Coding\pj-sip\pjsip-apps\src\pjsua\main.c:44: > C:/Program Files/System/Platform SDK/Windows/Lib/wsock32.lib:3:1: > warning: null character(s) ignored > C:/Program Files/System/Platform SDK/Windows/Lib/wsock32.lib:3: error: > stray '\141' in program > > So, I looked into that file - and this is all I could find: > > !<arch> > / 1132304112 0 3410 ` > > > Three lines of code are all that file handles? Hum, did I miss something? > The wsock32.lib inside the sub-directory called "x64" has the same > content, except the first number which is different there.. > > > > -- > > > Perry Ismangil > > > Mobile: +44 7761 179 575 > > > http://www.pjsip.org > > > > > > PJSIP LLP > > > 23 Langdon Street, Sheffield S11 8BH, United Kingdom > > > T +44 114 299 8883 F +44 7092 216 3097 > > > Registered in England no. OC323977 > > > > > > _______________________________________________ > > > Visit our blog: http://blog.pjsip.org > > > > > > pjsip mailing list > > > pjsip@lists.pjsip.org > > > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org > > > > > > > > > -- > > ===================== > > = ~ Code is poetry ~ > > ===================== > > = Martin Baranski > > = Eagle | Eagle3386 > > = www.troublezone.net > > = eagle3386@gmail.com > > = +49 (0)160 93317843 > > ===================== > > > > > -- > ===================== > = ~ Code is poetry ~ > ===================== > = Martin Baranski > = Eagle | Eagle3386 > = www.troublezone.net > = eagle3386@gmail.com > = +49 (0)160 93317843 > ===================== > > _______________________________________________ > Visit our blog: http://blog.pjsip.org > > pjsip mailing list > pjsip@lists.pjsip.org > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org > -- Perry Ismangil Mobile: +44 7761 179 575 http://www.pjsip.org PJSIP LLP 23 Langdon Street, Sheffield S11 8BH, United Kingdom T +44 114 299 8883 F +44 7092 216 3097 Registered in England no. OC323977 _______________________________________________ Visit our blog: http://blog.pjsip.org pjsip mailing list pjsip@lists.pjsip.org http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
EI
Eagle I Martin Baranski
Thu, Nov 8, 2007 11:09 AM

2007/11/8, darmawan salihun darmawan.salihun@gmail.com:

another note is, you don't need mingw to compile pjsip.Visual studio
and platform sdk is enough.Also make sure you downloaded all of
the needed source code from the repository.

I do need MinGW as this is the only way I know off to get things
compiled by GCC and I can't download more than what a checkout gives
me..

2007/11/8, Roland Klabunde roland.klabunde@freenet.de:

I suggest you start with something smaller than pjsip to get the
basics on building C applications that uses external libraries.

Yeah. Try

#include <stdio.h>

void main() {
printf("Hello World\n");
}

rofl :)

Seriously, I'm aware of how to compile/build programs.. I did
C-programming when I was at the university of cooperative education..
So, come on, don't laugh at me while I'm just reporting what the
compiler says! I don't find it very funny.. :(

2007/11/8, Perry Ismangil perry@pjsip.org:

There seems to be a huge gap here...

  • You can't #include  lib file. Include is for other text files,
    usually header  files.
  • lib files are binary files which will be linked to the application,
    not compiled.

I suggest you start with something smaller than pjsip to get the
basics on building C applications that uses external libraries.

Cheers,

That might be / is true, but the file "pjsua\main.c" that my checkout
brought me clearly said/says:

#include <pjlib.h>

(...)

#include <pjmedia-codec.h>
#include wsock32.lib
#include ws2_32.lib
#include ole32.lib
#include dsound.lib

So, if libraries can't be included and/or compiled, why did the source
code tell my GCC to do so?
I didn't say that I do those includes - instead, I reported that the
source code requests this..

Again, I'm sorry if I missed anything.. I'm neither God nor Richard
Stallman, so I won't be perfect and so, I'm bound to make mistakes.
Though, I'd be glad if you guys can push my knowledge in this case
(and in general, too)..

Thanks in advance,
Martin..

=====================
= ~ Code is poetry ~

= Martin Baranski
= Eagle | Eagle3386
= www.troublezone.net
= eagle3386@gmail.com
= +49 (0)160 93317843

2007/11/8, darmawan salihun <darmawan.salihun@gmail.com>: > another note is, you don't need mingw to compile pjsip.Visual studio > and platform sdk is enough.Also make sure you downloaded all of > the needed source code from the repository. I _do_ need MinGW as this is the only way I know off to get things compiled by GCC and I can't download more than what a checkout gives me.. 2007/11/8, Roland Klabunde <roland.klabunde@freenet.de>: > > I suggest you start with something smaller than pjsip to get the > > basics on building C applications that uses external libraries. > > Yeah. Try > > #include <stdio.h> > > void main() { > printf("Hello World\n"); > } > > > rofl :) Seriously, I'm aware of how to compile/build programs.. I did C-programming when I was at the university of cooperative education.. So, come on, don't laugh at me while I'm just reporting what the compiler says! I don't find it very funny.. :( 2007/11/8, Perry Ismangil <perry@pjsip.org>: > There seems to be a huge gap here... > > - You can't #include lib file. Include is for other text files, > usually header files. > - lib files are binary files which will be linked to the application, > not compiled. > > I suggest you start with something smaller than pjsip to get the > basics on building C applications that uses external libraries. > > Cheers, That might be / is true, but the file "pjsua\main.c" that my checkout brought me clearly said/says: #include <pjlib.h> (...) #include <pjmedia-codec.h> #include wsock32.lib #include ws2_32.lib #include ole32.lib #include dsound.lib So, if libraries can't be included and/or compiled, why did the source code tell my GCC to do so? I didn't say that _I_ do those includes - instead, I reported that the _source code_ requests this.. Again, I'm sorry if I missed anything.. I'm neither God nor Richard Stallman, so I won't be perfect and so, I'm bound to make mistakes. Though, I'd be glad if you guys can push my knowledge in this case (and in general, too).. Thanks in advance, Martin.. -- ===================== = ~ Code is poetry ~ ===================== = Martin Baranski = Eagle | Eagle3386 = www.troublezone.net = eagle3386@gmail.com = +49 (0)160 93317843 =====================
RK
Roland Klabunde
Thu, Nov 8, 2007 11:25 AM

So, come on, don't laugh at me while I'm just reporting what the
compiler says! I don't find it very funny.. :(

That wasn't my intention. It just sprang into my mind when I saw

#include wsock32.lib
#include ws2_32.lib
#include ole32.lib
#include dsound.lib

That is not really sophisticated programming, neither for a amateur nor for
a diploma holder.

And - I don't know where you got your sources from --- my latest SVN
snapshot does not have such a pjlib.h.

If you didn't add that "inlcude lib" stuff you should quickly check, who the
heck did change the files on your computer :)

#include <pjmedia-codec.h>
#include wsock32.lib
#include ws2_32.lib
#include ole32.lib
#include dsound.lib

So, if libraries can't be included and/or compiled, why did the source
code tell my GCC to do so?
I didn't say that I do those includes - instead, I reported that the
source code requests this..

Sorry, that's really nonsens. Check it out again and start from scratch.

----- Original Message -----
From: "Eagle I Martin Baranski" eagle3386@googlemail.com
To: "pjsip embedded/DSP SIP discussion" pjsip@lists.pjsip.org
Sent: Thursday, November 08, 2007 12:09 PM
Subject: Re: [pjsip] Win32 build doesn't build because of stddef.h

2007/11/8, darmawan salihun darmawan.salihun@gmail.com:

another note is, you don't need mingw to compile pjsip.Visual studio
and platform sdk is enough.Also make sure you downloaded all of
the needed source code from the repository.

I do need MinGW as this is the only way I know off to get things
compiled by GCC and I can't download more than what a checkout gives
me..

2007/11/8, Roland Klabunde roland.klabunde@freenet.de:

I suggest you start with something smaller than pjsip to get the
basics on building C applications that uses external libraries.

Yeah. Try

#include <stdio.h>

void main() {
printf("Hello World\n");
}

rofl :)

Seriously, I'm aware of how to compile/build programs.. I did
C-programming when I was at the university of cooperative education..
So, come on, don't laugh at me while I'm just reporting what the
compiler says! I don't find it very funny.. :(

2007/11/8, Perry Ismangil perry@pjsip.org:

There seems to be a huge gap here...

  • You can't #include  lib file. Include is for other text files,
    usually header  files.
  • lib files are binary files which will be linked to the application,
    not compiled.

I suggest you start with something smaller than pjsip to get the
basics on building C applications that uses external libraries.

Cheers,

That might be / is true, but the file "pjsua\main.c" that my checkout
brought me clearly said/says:

#include <pjlib.h>

(...)

#include <pjmedia-codec.h>
#include wsock32.lib
#include ws2_32.lib
#include ole32.lib
#include dsound.lib

So, if libraries can't be included and/or compiled, why did the source
code tell my GCC to do so?
I didn't say that I do those includes - instead, I reported that the
source code requests this..

Again, I'm sorry if I missed anything.. I'm neither God nor Richard
Stallman, so I won't be perfect and so, I'm bound to make mistakes.
Though, I'd be glad if you guys can push my knowledge in this case
(and in general, too)..

Thanks in advance,
Martin..

=====================
= ~ Code is poetry ~

= Martin Baranski
= Eagle | Eagle3386
= www.troublezone.net
= eagle3386@gmail.com
= +49 (0)160 93317843


Visit our blog: http://blog.pjsip.org

pjsip mailing list
pjsip@lists.pjsip.org
http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org

> So, come on, don't laugh at me while I'm just reporting what the > compiler says! I don't find it very funny.. :( That wasn't my intention. It just sprang into my mind when I saw > #include wsock32.lib > #include ws2_32.lib > #include ole32.lib > #include dsound.lib That is not really sophisticated programming, neither for a amateur nor for a diploma holder. And - I don't know where _you_ got your sources from --- my latest SVN snapshot does not have such a pjlib.h. If you didn't add that "inlcude lib" stuff you should quickly check, who the heck did change the files on your computer :) #include <pjmedia-codec.h> #include wsock32.lib #include ws2_32.lib #include ole32.lib #include dsound.lib > So, if libraries can't be included and/or compiled, why did the source > code tell my GCC to do so? > I didn't say that _I_ do those includes - instead, I reported that the > _source code_ requests this.. Sorry, that's really nonsens. Check it out again and start from scratch. ----- Original Message ----- From: "Eagle I Martin Baranski" <eagle3386@googlemail.com> To: "pjsip embedded/DSP SIP discussion" <pjsip@lists.pjsip.org> Sent: Thursday, November 08, 2007 12:09 PM Subject: Re: [pjsip] Win32 build doesn't build because of stddef.h > 2007/11/8, darmawan salihun <darmawan.salihun@gmail.com>: >> another note is, you don't need mingw to compile pjsip.Visual studio >> and platform sdk is enough.Also make sure you downloaded all of >> the needed source code from the repository. > > I _do_ need MinGW as this is the only way I know off to get things > compiled by GCC and I can't download more than what a checkout gives > me.. > > > 2007/11/8, Roland Klabunde <roland.klabunde@freenet.de>: >> > I suggest you start with something smaller than pjsip to get the >> > basics on building C applications that uses external libraries. >> >> Yeah. Try >> >> #include <stdio.h> >> >> void main() { >> printf("Hello World\n"); >> } >> >> >> rofl :) > > Seriously, I'm aware of how to compile/build programs.. I did > C-programming when I was at the university of cooperative education.. > So, come on, don't laugh at me while I'm just reporting what the > compiler says! I don't find it very funny.. :( > > > 2007/11/8, Perry Ismangil <perry@pjsip.org>: >> There seems to be a huge gap here... >> >> - You can't #include lib file. Include is for other text files, >> usually header files. >> - lib files are binary files which will be linked to the application, >> not compiled. >> >> I suggest you start with something smaller than pjsip to get the >> basics on building C applications that uses external libraries. >> >> Cheers, > > That might be / is true, but the file "pjsua\main.c" that my checkout > brought me clearly said/says: > > #include <pjlib.h> > > (...) > > #include <pjmedia-codec.h> > #include wsock32.lib > #include ws2_32.lib > #include ole32.lib > #include dsound.lib > > So, if libraries can't be included and/or compiled, why did the source > code tell my GCC to do so? > I didn't say that _I_ do those includes - instead, I reported that the > _source code_ requests this.. > > > Again, I'm sorry if I missed anything.. I'm neither God nor Richard > Stallman, so I won't be perfect and so, I'm bound to make mistakes. > Though, I'd be glad if you guys can push my knowledge in this case > (and in general, too).. > > Thanks in advance, > Martin.. > -- > ===================== > = ~ Code is poetry ~ > ===================== > = Martin Baranski > = Eagle | Eagle3386 > = www.troublezone.net > = eagle3386@gmail.com > = +49 (0)160 93317843 > ===================== > > _______________________________________________ > Visit our blog: http://blog.pjsip.org > > pjsip mailing list > pjsip@lists.pjsip.org > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org >
PI
Perry Ismangil
Thu, Nov 8, 2007 11:52 AM

On 11/8/07, Eagle I Martin Baranski eagle3386@googlemail.com wrote:

That might be / is true, but the file "pjsua\main.c" that my checkout
brought me clearly said/says:

#include <pjlib.h>

(...)

#include <pjmedia-codec.h>
#include wsock32.lib
#include ws2_32.lib
#include ole32.lib
#include dsound.lib

Are we talking about the same file here? Is it this one:

http://svn.pjsip.org/repos/pjproject/trunk/pjsip-apps/src/pjsua/main.c

--
Perry Ismangil

On 11/8/07, Eagle I Martin Baranski <eagle3386@googlemail.com> wrote: > > > That might be / is true, but the file "pjsua\main.c" that my checkout > brought me clearly said/says: > > #include <pjlib.h> > > (...) > > #include <pjmedia-codec.h> > #include wsock32.lib > #include ws2_32.lib > #include ole32.lib > #include dsound.lib > > Are we talking about the same file here? Is it this one: http://svn.pjsip.org/repos/pjproject/trunk/pjsip-apps/src/pjsua/main.c -- Perry Ismangil
EI
Eagle I Martin Baranski
Thu, Nov 8, 2007 12:43 PM

2007/11/8, Roland Klabunde roland.klabunde@freenet.de:

So, come on, don't laugh at me while I'm just reporting what the
compiler says! I don't find it very funny.. :(

That wasn't my intention. It just sprang into my mind when I saw

#include wsock32.lib
#include ws2_32.lib
#include ole32.lib
#include dsound.lib

That is not really sophisticated programming, neither for a amateur nor for
a diploma holder.

And - I don't know where you got your sources from --- my latest SVN
snapshot does not have such a pjlib.h.

Correct.. Did a complete and fresh checkout.. Got the files as they're
supposed to be..

If you didn't add that "inlcude lib" stuff you should quickly check, who the
heck did change the files on your computer :)

From now on, I'm going to lock my computer everytime I leave the room.. ;)

Though, now GCC says:

M:\pj-sip\pjsip-apps\src\pjsua\pjsua_app.c: In function int read_config_file(pj_pool_t*, const char*, int*, char***)': M:\pj-sip\pjsip-apps\src\pjsua\pjsua_app.c:256: error: invalid conversion from void*' to char**' M:\pj-sip\pjsip-apps\src\pjsua\pjsua_app.c:317: error: invalid conversion from void*' to `char*'

How to fix the conversion? :)

=====================
= ~ Code is poetry ~

= Martin Baranski
= Eagle | Eagle3386
= www.troublezone.net
= eagle3386@gmail.com
= +49 (0)160 93317843

2007/11/8, Roland Klabunde <roland.klabunde@freenet.de>: > > So, come on, don't laugh at me while I'm just reporting what the > > compiler says! I don't find it very funny.. :( > > That wasn't my intention. It just sprang into my mind when I saw > > > #include wsock32.lib > > #include ws2_32.lib > > #include ole32.lib > > #include dsound.lib > > That is not really sophisticated programming, neither for a amateur nor for > a diploma holder. > > And - I don't know where _you_ got your sources from --- my latest SVN > snapshot does not have such a pjlib.h. Correct.. Did a complete and fresh checkout.. Got the files as they're supposed to be.. > If you didn't add that "inlcude lib" stuff you should quickly check, who the > heck did change the files on your computer :) >From now on, I'm going to lock my computer everytime I leave the room.. ;) Though, now GCC says: M:\pj-sip\pjsip-apps\src\pjsua\pjsua_app.c: In function `int read_config_file(pj_pool_t*, const char*, int*, char***)': M:\pj-sip\pjsip-apps\src\pjsua\pjsua_app.c:256: error: invalid conversion from `void*' to `char**' M:\pj-sip\pjsip-apps\src\pjsua\pjsua_app.c:317: error: invalid conversion from `void*' to `char*' How to fix the conversion? :) -- ===================== = ~ Code is poetry ~ ===================== = Martin Baranski = Eagle | Eagle3386 = www.troublezone.net = eagle3386@gmail.com = +49 (0)160 93317843 =====================
EI
Eagle I Martin Baranski
Thu, Nov 8, 2007 12:45 PM

2007/11/8, Perry Ismangil perry@pjsip.org:

On 11/8/07, Eagle I Martin Baranski eagle3386@googlemail.com wrote:

That might be / is true, but the file "pjsua\main.c" that my checkout
brought me clearly said/says:

#include <pjlib.h>

(...)

#include <pjmedia-codec.h>
#include wsock32.lib
#include ws2_32.lib
#include ole32.lib
#include dsound.lib

Are we talking about the same file here? Is it this one:

http://svn.pjsip.org/repos/pjproject/trunk/pjsip-apps/src/pjsua/main.c

Yes, that file was the one I talked about.. And I don't even have a
clue who changed that file, because all I edited was removing a space
between "#" and "include" - and that was a completely different file..

=====================
= ~ Code is poetry ~

= Martin Baranski
= Eagle | Eagle3386
= www.troublezone.net
= eagle3386@gmail.com
= +49 (0)160 93317843

2007/11/8, Perry Ismangil <perry@pjsip.org>: > On 11/8/07, Eagle I Martin Baranski <eagle3386@googlemail.com> wrote: > > > > That might be / is true, but the file "pjsua\main.c" that my checkout > > brought me clearly said/says: > > > > #include <pjlib.h> > > > > (...) > > > > #include <pjmedia-codec.h> > > #include wsock32.lib > > #include ws2_32.lib > > #include ole32.lib > > #include dsound.lib > > > > > > Are we talking about the same file here? Is it this one: > > http://svn.pjsip.org/repos/pjproject/trunk/pjsip-apps/src/pjsua/main.c Yes, that file was the one I talked about.. And I don't even have a clue who changed that file, because all I edited was removing a space between "#" and "include" - and that was a completely different file.. -- ===================== = ~ Code is poetry ~ ===================== = Martin Baranski = Eagle | Eagle3386 = www.troublezone.net = eagle3386@gmail.com = +49 (0)160 93317843 =====================
PI
Perry Ismangil
Thu, Nov 8, 2007 1:08 PM

On 11/8/07, Eagle I Martin Baranski eagle3386@googlemail.com wrote:

Yes, that file was the one I talked about.. And I don't even have a
clue who changed that file, because all I edited was removing a space
between "#" and "include" - and that was a completely different file..

Right, let's start from the beginning then.

  • Delete your working directory.
  • Checkout a fresh copy from svn.pjsip.org

And we'll take it from there again. Although be aware there are limits to
our knowledge here as you are using an unsupported IDE.

--
Perry Ismangil

On 11/8/07, Eagle I Martin Baranski <eagle3386@googlemail.com> wrote: > > > Yes, that file was the one I talked about.. And I don't even have a > clue who changed that file, because all I edited was removing a space > between "#" and "include" - and that was a completely different file.. > Right, let's start from the beginning then. - Delete your working directory. - Checkout a fresh copy from svn.pjsip.org And we'll take it from there again. Although be aware there are limits to our knowledge here as you are using an unsupported IDE. -- Perry Ismangil
EI
Eagle I Martin Baranski
Thu, Nov 8, 2007 1:55 PM

2007/11/8, Perry Ismangil perry@pjsip.org:

On 11/8/07, Eagle I Martin Baranski eagle3386@googlemail.com wrote:

Yes, that file was the one I talked about.. And I don't even have a
clue who changed that file, because all I edited was removing a space
between "#" and "include" - and that was a completely different file..

Right, let's start from the beginning then.

  • Delete your working directory.
  • Checkout a fresh copy from svn.pjsip.org

And we'll take it from there again. Although be aware there are limits to
our knowledge here as you are using an unsupported IDE.

OK, did that.. But there's already a problem:

M:\pj-sip>svn co svn://svn.pjsip.org
svn: Kann nicht mit Host 'svn.pjsip.org' verbinden: Es konnte keine
Verbindung hergestellt werden, da der Zielcomputer die Verbindung
verweigerte.

Error message means in English "Can't connect to host 'svn.pjsip.org':
The connection couldn't be established because the target-computer
refused the connection"

Doing the checkout with the "http://"-prefix, gives me this:

M:\pj-sip>svn co http://svn.pjsip.org
svn: PROPFIND Anfrage fehlgeschlagen auf '/'
svn: PROPFIND von '/': 405 Method Not Allowed (http://svn.pjsip.org)

"Anfrage fehlgeschlagen auf '/'" means "Request failed for '/'"

Why did you give me that URL? The one from the docs
(http://svn.pjsip.org/repos/pjproject/trunk/) worked fine for me..

Regards,
Martin

=====================
= ~ Code is poetry ~

= Martin Baranski
= Eagle | Eagle3386
= www.troublezone.net
= eagle3386@gmail.com
= +49 (0)160 93317843

2007/11/8, Perry Ismangil <perry@pjsip.org>: > On 11/8/07, Eagle I Martin Baranski <eagle3386@googlemail.com> wrote: > > > > Yes, that file was the one I talked about.. And I don't even have a > > clue who changed that file, because all I edited was removing a space > > between "#" and "include" - and that was a completely different file.. > > > > Right, let's start from the beginning then. > > - Delete your working directory. > - Checkout a fresh copy from svn.pjsip.org > > And we'll take it from there again. Although be aware there are limits to > our knowledge here as you are using an unsupported IDE. OK, did that.. But there's already a problem: M:\pj-sip>svn co svn://svn.pjsip.org svn: Kann nicht mit Host 'svn.pjsip.org' verbinden: Es konnte keine Verbindung hergestellt werden, da der Zielcomputer die Verbindung verweigerte. Error message means in English "Can't connect to host 'svn.pjsip.org': The connection couldn't be established because the target-computer refused the connection" Doing the checkout with the "http://"-prefix, gives me this: M:\pj-sip>svn co http://svn.pjsip.org svn: PROPFIND Anfrage fehlgeschlagen auf '/' svn: PROPFIND von '/': 405 Method Not Allowed (http://svn.pjsip.org) "Anfrage fehlgeschlagen auf '/'" means "Request failed for '/'" Why did you give me that URL? The one from the docs (http://svn.pjsip.org/repos/pjproject/trunk/) worked fine for me.. Regards, Martin -- ===================== = ~ Code is poetry ~ ===================== = Martin Baranski = Eagle | Eagle3386 = www.troublezone.net = eagle3386@gmail.com = +49 (0)160 93317843 =====================
PI
Perry Ismangil
Thu, Nov 8, 2007 2:14 PM

On 11/8/07, Eagle I Martin Baranski eagle3386@googlemail.com wrote:

Why did you give me that URL? The one from the docs
(http://svn.pjsip.org/repos/pjproject/trunk/) worked fine for me..

Because that wasn't supposed to be a URL, just a reference to the  svn
server. The URL you have is correct.

--
Perry Ismangil

On 11/8/07, Eagle I Martin Baranski <eagle3386@googlemail.com> wrote: > > > Why did you give me that URL? The one from the docs > (http://svn.pjsip.org/repos/pjproject/trunk/) worked fine for me.. Because that wasn't supposed to be a URL, just a reference to the svn server. The URL you have is correct. -- Perry Ismangil
EI
Eagle I Martin Baranski
Thu, Nov 8, 2007 2:21 PM

2007/11/8, Perry Ismangil perry@pjsip.org:

On 11/8/07, Eagle I Martin Baranski eagle3386@googlemail.com wrote:

Why did you give me that URL? The one from the docs
(http://svn.pjsip.org/repos/pjproject/trunk/) worked fine

for me..

Because that wasn't supposed to be a URL, just a reference to the  svn
server. The URL you have is correct.

Alright, got the checkout done. What next? :)

=====================
= ~ Code is poetry ~

= Martin Baranski
= Eagle | Eagle3386
= www.troublezone.net
= eagle3386@gmail.com
= +49 (0)160 93317843

2007/11/8, Perry Ismangil <perry@pjsip.org>: > On 11/8/07, Eagle I Martin Baranski <eagle3386@googlemail.com> wrote: > > > > Why did you give me that URL? The one from the docs > > (http://svn.pjsip.org/repos/pjproject/trunk/) worked fine > for me.. > > Because that wasn't supposed to be a URL, just a reference to the svn > server. The URL you have is correct. Alright, got the checkout done. What next? :) -- ===================== = ~ Code is poetry ~ ===================== = Martin Baranski = Eagle | Eagle3386 = www.troublezone.net = eagle3386@gmail.com = +49 (0)160 93317843 =====================