Re: [pjsip] Win32 build doesn't build because of stddef.h
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
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
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
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
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, 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
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
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
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
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
On 11/8/07, Eagle I Martin Baranski eagle3386@googlemail.com wrote:
Alright, got the checkout done. What next? :)
Well, describe what you do to try to compile it in Code::Blocks. And then
post any errors here. I know you have posted some errors before but we're
not clear on the steps you have taken to reach it.
Cheers,
--
Perry Ismangil
2007/11/8, Perry Ismangil perry@pjsip.org:
On 11/8/07, Eagle I Martin Baranski eagle3386@googlemail.com wrote:
Alright, got the checkout done. What next? :)
Well, describe what you do to try to compile it in Code::Blocks. And then
post any errors here. I know you have posted some errors before but we're
not clear on the steps you have taken to reach it.
Cheers,
Nothing easier than that..
At first, I rename the "config_site_sample.h" within the path
"pjlib\include\pj" to "config_site.h".
Then, I launch Code::Blocks (the devs their suggest using the latest
SVN-build, others won't work under Vista and are totally outdated),
open the "pjproject-vs8.sln"-file and then click 2 times "Yes",
because I want to compile PJSIP with my default set compiler and all
configuration data shall be imported.
After some waiting, I single-click the "pjsua"-item within the
project-management-tree at the left, choose "Debug Win32" from the
drop-down menu above the project-management, then a right-click at the
"pjsua"-item and a left-click at the context-menu-option called
"Build".
So, the building goes and and soon will fail and then, the message-box
at the bottom will jump to the "Build messages"-tab. But because I
want the whole log, I click the "Build log"-tab and the box then gives
me:
-------------- Build: Debug Win32 in pjsua ---------------
[ 33.3%] mingw32-c++.exe -D_DEBUG -DPJ_WIN32=1 -DPJ_M_I386=1 -DWIN32
-D_CONSOLE -Wall -g -O0 -march=athlon64 -O2 -O1 -O -Wmain -Wall
-DNDEBUG -DPJ_WIN32=1 -DPJ_M_I386=1 -DWIN32 -D_CONSOLE
-I....\pjsip\include -I....\pjlib\include -I....\pjlib-util\include
-I....\pjmedia\include -I....\pjnath\include -IC:\MinGW\include
-IC:\MinGW\include\c++\3.4.5 -IC:\MinGW\include\c++\3.4.5\backward
-IC:\MinGW\include\c++\3.4.5\mingw32
-IC:\MinGW\lib\gcc\mingw32\3.4.5\include -I"C:\Program
Files\System\Platform SDK\Windows\Include"
-IM:\pj-sip\pjsip-apps\src\pjsua -IM:\pj-sip\pjsip-apps -c
M:\pj-sip\pjsip-apps\src\pjsua\pjsua_app.c -o
output\pjsua-i386-win32-vc8-debug\src\pjsua\pjsua_app.o
cc1plus.exe: warning: command line option "-Wmain" is valid for C/ObjC
but not for C++
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*' M:\pj-sip\pjsip-apps\src\pjsua\pjsua_app.c: In function void
change_online_status()':
M:\pj-sip\pjsip-apps\src\pjsua\pjsua_app.c:2257: warning: comparison
between signed and unsigned integer expressions
Process terminated with status 1 (0 minutes, 0 seconds)
2 errors, 2 warnings
And that's all, the compiler says to me..
But to get that far, I had to add some stuff to the compiler settings,
which I'm going to describe for you now (I'm assuming you've installed
MinGW directly below the "C:"-root because of problems between Vista
and MinGW when using long pathnames):
Click "Settings" -> "Compiler and debugger..." -> "#defines"-tab (make
sure, the selected compiler is set to "GNU GCC Compiler") -> enter the
following into the box:
NDEBUG
PJ_WIN32=1
PJ_M_I386=1
WIN32
_CONSOLE
Then, click the "Toolchain"-tab -> "Auto-detect" (make sure, the path
to the left does NOT contain "\bin", e. g. "C:\MinGW", NOT
"C:\MinGW\bin")
Afterwards, click the "Additional Paths"-tab -> add
"C:\MinGW\libexec\gcc\mingw32\3.4.5"
After that, click the "Search directories"-tab, and below the
"Compiler"-sub-tab, there should be the following:
C:\MinGW\include
C:\MinGW\include\c++\3.4.5
C:\MinGW\include\c++\3.4.5\backward
C:\MinGW\include\c++\3.4.5\mingw32
C:\MinGW\lib\gcc\mingw32\3.4.5\include
C:\Program Files\System\Platform SDK\Windows\Include
Same goes for the "Linker"-sub-tab:
C:\MinGW\lib
C:\MinGW\lib\gcc\mingw32\3.4.5
And the "Resource"-sub-tab has just this:
C:\MinGW\include
Finally, click that tiny little arrow pointing to the right in the
upper window-part to get to the "Other settings"-tab. There, set the
following:
Compiler logging: Full command line
Check both entries starting with "Explicitely add..." and also both
entries starting with "Display build".
That's it - click OK and then that tiny blue gear at the upper-left window-part.
=====================
= ~ Code is poetry ~
= Martin Baranski
= Eagle | Eagle3386
= www.troublezone.net
= eagle3386@gmail.com
= +49 (0)160 93317843
Hi,
It looks to me that CodeBlocks is trying to compile PJSIP as a C++ project,
while it's a C project. Try to change the configurations so that it's
compiled as C project.
Thanks.
Best Regards,
Hitesh
----- 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 9:09 PM
Subject: Re: [pjsip] Win32 build doesn't build because of stddef.h
2007/11/8, Perry Ismangil perry@pjsip.org:
On 11/8/07, Eagle I Martin Baranski eagle3386@googlemail.com wrote:
Alright, got the checkout done. What next? :)
Well, describe what you do to try to compile it in Code::Blocks. And then
post any errors here. I know you have posted some errors before but we're
not clear on the steps you have taken to reach it.
Cheers,
Nothing easier than that..
At first, I rename the "config_site_sample.h" within the path
"pjlib\include\pj" to "config_site.h".
Then, I launch Code::Blocks (the devs their suggest using the latest
SVN-build, others won't work under Vista and are totally outdated),
open the "pjproject-vs8.sln"-file and then click 2 times "Yes",
because I want to compile PJSIP with my default set compiler and all
configuration data shall be imported.
After some waiting, I single-click the "pjsua"-item within the
project-management-tree at the left, choose "Debug Win32" from the
drop-down menu above the project-management, then a right-click at the
"pjsua"-item and a left-click at the context-menu-option called
"Build".
So, the building goes and and soon will fail and then, the message-box
at the bottom will jump to the "Build messages"-tab. But because I
want the whole log, I click the "Build log"-tab and the box then gives
me:
-------------- Build: Debug Win32 in pjsua ---------------
[ 33.3%] mingw32-c++.exe -D_DEBUG -DPJ_WIN32=1 -DPJ_M_I386=1 -DWIN32
-D_CONSOLE -Wall -g -O0 -march=athlon64 -O2 -O1 -O -Wmain -Wall
-DNDEBUG -DPJ_WIN32=1 -DPJ_M_I386=1 -DWIN32 -D_CONSOLE
-I....\pjsip\include -I....\pjlib\include -I....\pjlib-util\include
-I....\pjmedia\include -I....\pjnath\include -IC:\MinGW\include
-IC:\MinGW\include\c++\3.4.5 -IC:\MinGW\include\c++\3.4.5\backward
-IC:\MinGW\include\c++\3.4.5\mingw32
-IC:\MinGW\lib\gcc\mingw32\3.4.5\include -I"C:\Program
Files\System\Platform SDK\Windows\Include"
-IM:\pj-sip\pjsip-apps\src\pjsua -IM:\pj-sip\pjsip-apps -c
M:\pj-sip\pjsip-apps\src\pjsua\pjsua_app.c -o
output\pjsua-i386-win32-vc8-debug\src\pjsua\pjsua_app.o
cc1plus.exe: warning: command line option "-Wmain" is valid for C/ObjC
but not for C++
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*' M:\pj-sip\pjsip-apps\src\pjsua\pjsua_app.c: In function void
change_online_status()':
M:\pj-sip\pjsip-apps\src\pjsua\pjsua_app.c:2257: warning: comparison
between signed and unsigned integer expressions
Process terminated with status 1 (0 minutes, 0 seconds)
2 errors, 2 warnings
And that's all, the compiler says to me..
But to get that far, I had to add some stuff to the compiler settings,
which I'm going to describe for you now (I'm assuming you've installed
MinGW directly below the "C:"-root because of problems between Vista
and MinGW when using long pathnames):
Click "Settings" -> "Compiler and debugger..." -> "#defines"-tab (make
sure, the selected compiler is set to "GNU GCC Compiler") -> enter the
following into the box:
NDEBUG
PJ_WIN32=1
PJ_M_I386=1
WIN32
_CONSOLE
Then, click the "Toolchain"-tab -> "Auto-detect" (make sure, the path
to the left does NOT contain "\bin", e. g. "C:\MinGW", NOT
"C:\MinGW\bin")
Afterwards, click the "Additional Paths"-tab -> add
"C:\MinGW\libexec\gcc\mingw32\3.4.5"
After that, click the "Search directories"-tab, and below the
"Compiler"-sub-tab, there should be the following:
C:\MinGW\include
C:\MinGW\include\c++\3.4.5
C:\MinGW\include\c++\3.4.5\backward
C:\MinGW\include\c++\3.4.5\mingw32
C:\MinGW\lib\gcc\mingw32\3.4.5\include
C:\Program Files\System\Platform SDK\Windows\Include
Same goes for the "Linker"-sub-tab:
C:\MinGW\lib
C:\MinGW\lib\gcc\mingw32\3.4.5
And the "Resource"-sub-tab has just this:
C:\MinGW\include
Finally, click that tiny little arrow pointing to the right in the
upper window-part to get to the "Other settings"-tab. There, set the
following:
Compiler logging: Full command line
Check both entries starting with "Explicitely add..." and also both
entries starting with "Display build".
That's it - click OK and then that tiny blue gear at the upper-left
window-part.
=====================
= ~ 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
2007/11/8, logan logan04x@gmail.com:
Hi,
It looks to me that CodeBlocks is trying to compile PJSIP as a C++ project,
while it's a C project. Try to change the configurations so that it's
compiled as C project.
Thanks.
Hi,
thanks for that hint.. Although Code::Blocks normally determines the
needed compiler by looking at the file's extension (.c = C, .cpp =
C++), there seem to be some problems..
Therefore I did 2 things:
-
Go into the compiler-settings once again (Settings -> Compiler and
debugger... -> "Toolchain"-tab -> the item for "C compiler" and
"Linker for dynamic libs" should be "mingw32-gcc.exe" ("C++ compiler"
should be "mingw32-g++.exe") and nothing else.. -
Right-click at the pjsua-project and select "Build options..." ->
"Other options"-tab -> enter "-x c" (that forces gcc to explicitly
compile C instead of C++)
The correctness of the changes can be checked by checking "Enable
warnings demanded by strict ISO C and ISO C++ [-pedantic]" at the
"Compiler flags"-tab, because that gives some warnings about
C++-styled comments in some files.. ;)
Anyway, after all that, I still got errors:
[100.0%] mingw32-gcc.exe -LC:\MinGW\lib
-LC:\MinGW\lib\gcc\mingw32\3.4.5 -o ..\bin\pjsua_vc8d.exe
output\pjsua-i386-win32-vc8-debug\src\pjsua\pjsua_app.o
output\pjsua-i386-win32-vc8-debug\src\pjsua\main.o -s -s -lIphlpapi
-ldsound -ldxguid -lnetapi32 -lmswsock -lws2_32 -lodbc32 -lodbccp32
-lole32 -luser32
output\pjsua-i386-win32-vc8-debug\src\pjsua\pjsua_app.o: In function my_atoi': M:/pj-sip/pjsip-apps/src/pjsua/pjsua_app.c:359: undefined reference to pj_strtoul'
M:/pj-sip/pjsip-apps/src/pjsua/pjsua_app.c:354: undefined reference to
pj_strtoul' output\pjsua-i386-win32-vc8-debug\src\pjsua\pjsua_app.o: In function write_settings':
M:/pj-sip/pjsip-apps/src/pjsua/pjsua_app.c:1128: undefined reference
to pj_strcat2' M:/pj-sip/pjsip-apps/src/pjsua/pjsua_app.c:1131: undefined reference to pj_strcat2'
M:/pj-sip/pjsip-apps/src/pjsua/pjsua_app.c:1135: undefined reference
to pj_strcat2' M:/pj-sip/pjsip-apps/src/pjsua/pjsua_app.c:1042: undefined reference to pj_strcat2'
M:/pj-sip/pjsip-apps/src/pjsua/pjsua_app.c:1105: undefined reference
to pj_strcat2' output\pjsua-i386-win32-vc8-debug\src\pjsua\pjsua_app.o:M:/pj-sip/pjsip-apps/src/pjsua/pjsua_app.c:1087: more undefined references to pj_strcat2' follow
(There are more, but I got told that the first error often involves
more errors and so fixing the first might fix others as well..)
--
= ~ Code is poetry ~
= Martin Baranski
= Eagle | Eagle3386
= www.troublezone.net
= eagle3386@gmail.com
= +49 (0)160 93317843
On 11/8/07, Eagle I Martin Baranski eagle3386@googlemail.com wrote:
[100.0%] mingw32-gcc.exe -LC:\MinGW\lib
-LC:\MinGW\lib\gcc\mingw32\3.4.5 -o ..\bin\pjsua_vc8d.exe
output\pjsua-i386-win32-vc8-debug\src\pjsua\pjsua_app.o
output\pjsua-i386-win32-vc8-debug\src\pjsua\main.o -s -s -lIphlpapi
-ldsound -ldxguid -lnetapi32 -lmswsock -lws2_32 -lodbc32 -lodbccp32
-lole32 -luser32
output\pjsua-i386-win32-vc8-debug\src\pjsua\pjsua_app.o: In function my_atoi': M:/pj-sip/pjsip-apps/src/pjsua/pjsua_app.c:359: undefined reference to pj_strtoul'
Ok, you're past compile problems now and on to linking problems. So
'undefined reference' errors are usually to do with the libraries you
have compiled not being referenced.
You can see the '-l' arguments does not specify pjxxxx libraries anywhere.
On http://www.pjsip.org/trac/wiki/Getting_Started_Using there are some
hints on what libraries are needed. You need to add those somewhere in
your IDE to the libraries that needs to be linked.
Cheers,
--
Perry Ismangil
2007/11/9, Perry Ismangil perry@pjsip.org:
On 11/8/07, Eagle I Martin Baranski eagle3386@googlemail.com wrote:
[100.0%] mingw32-gcc.exe -LC:\MinGW\lib
-LC:\MinGW\lib\gcc\mingw32\3.4.5 -o ..\bin\pjsua_vc8d.exe
output\pjsua-i386-win32-vc8-debug\src\pjsua\pjsua_app.o
output\pjsua-i386-win32-vc8-debug\src\pjsua\main.o -s -s -lIphlpapi
-ldsound -ldxguid -lnetapi32 -lmswsock -lws2_32 -lodbc32 -lodbccp32
-lole32 -luser32
output\pjsua-i386-win32-vc8-debug\src\pjsua\pjsua_app.o: In function my_atoi': M:/pj-sip/pjsip-apps/src/pjsua/pjsua_app.c:359: undefined reference to pj_strtoul'
Ok, you're past compile problems now and on to linking problems. So
'undefined reference' errors are usually to do with the libraries you
have compiled not being referenced.
You can see the '-l' arguments does not specify pjxxxx libraries anywhere.
On http://www.pjsip.org/trac/wiki/Getting_Started_Using there are some
hints on what libraries are needed. You need to add those somewhere in
your IDE to the libraries that needs to be linked.
Alright, looked at the link you gave me.. IMHO, I need to add
pjlib/lib, pjlib-util/lib, pjmedia/lib and pjsip/lib..
So, I've added their paths to the linker's search-paths.. But as that
failed (and because you talked about "-l" and the log talked about e.
g. "-L....\pjlib\lib"), I took some time, reading the trac-ticket
once more and then got the thought that I might need to add
-lpjsua-${TARGET_NAME}
-lpjsip-ua-${TARGET_NAME}
-lpjsip-simple-${TARGET_NAME}
-lpjsip-${TARGET_NAME}
-lpjmedia-codec-${TARGET_NAME}
-lpjmedia-${TARGET_NAME}
-lpjmedia-codec-${TARGET_NAME}
-lpjlib-util-${TARGET_NAME}
-lpj-${TARGET_NAME}
-lm
-lpthread
-lasound
-lssl
to the linker's options (instead of adding some paths to search for
libraries) and so I did that.. But GCC then told me:
[100.0%] mingw32-gcc.exe -L....\pjlib\lib -LC:\MinGW\lib
-LC:\MinGW\lib\gcc\mingw32\3.4.5 -o ..\bin\pjsua_vc8d.exe
output\pjsua-i386-win32-vc8-debug\src\pjsua\pjsua_app.o
output\pjsua-i386-win32-vc8-debug\src\pjsua\main.o -s -lpjsua-Debug
Win32\ -lpjsip-ua-Debug Win32\ -lpjsip-simple-Debug Win32
-lpjsip-Debug Win32\ -lpjmedia-codec-Debug Win32\ -lpjmedia-Debug
Win32\ -lpjmedia-codec-Debug Win32\ -lpjlib-util-Debug Win32
-lpj-Debug Win32\ -lm\ -lpthread\ -lasound\ -lssl -s -lIphlpapi
-ldsound -ldxguid -lnetapi32 -lmswsock -lws2_32 -lodbc32 -lodbccp32
-lole32 -luser32
mingw32-gcc.exe: Win32: No such file or directory
mingw32-gcc.exe: Win32: No such file or directory
mingw32-gcc.exe: Win32: No such file or directory
mingw32-gcc.exe: Win32: No such file or directory
mingw32-gcc.exe: Win32: No such file or directory
mingw32-gcc.exe: Win32: No such file or directory
mingw32-gcc.exe: Win32: No such file or directory
mingw32-gcc.exe: Win32: No such file or directory
mingw32-gcc.exe: Win32: No such file or directory
Process terminated with status 1 (0 minutes, 2 seconds)
0 errors, 0 warnings
("Debug Win32" is how Code::Blocks calls my build target - the other
option would be "Release Win32"..)
But I refused to give up, so I tried the linker's options without that
"-${TARGET_NAME}"-stuff (e. g. "-lpjsua" instead of
"-lpjsua-${TARGET_NAME}") which seemed to work until.. Well..
[100.0%] mingw32-gcc.exe -L....\pjlib\lib -LC:\MinGW\lib
-LC:\MinGW\lib\gcc\mingw32\3.4.5 -o ..\bin\pjsua_vc8d.exe
output\pjsua-i386-win32-vc8-debug\src\pjsua\pjsua_app.o
output\pjsua-i386-win32-vc8-debug\src\pjsua\main.o -s -lpjsua
-lpjsip-ua\ -lpjsip-simple\ -lpjsip\ -lpjmedia-codec\ -lpjmedia
-lpjmedia-codec\ -lpjlib-util\ -lpj\ -lm\ -lpthread\ -lasound\ -lssl
-s -lIphlpapi -ldsound -ldxguid -lnetapi32 -lmswsock -lws2_32
-lodbc32 -lodbccp32 -lole32 -luser32
C:\MinGW\bin..\lib\gcc\mingw32\3.4.5........\mingw32\bin\ld.exe:
cannot find -lpjsua
collect2: ld returned 1 exit status
Process terminated with status 1 (0 minutes, 1 seconds)
1 errors, 0 warnings
Is that because PJSIP is stored on M:, but MinGW is on the C:-drive?
Regards,
Martin.. :)
=====================
= ~ Code is poetry ~
= Martin Baranski
= Eagle | Eagle3386
= www.troublezone.net
= eagle3386@gmail.com
= +49 (0)160 93317843
On 11/9/07, Eagle I Martin Baranski eagle3386@googlemail.com wrote:
Is that because PJSIP is stored on M:, but MinGW is on the C:-drive?
No, it's not. '-l' takes an actual library name. '-L' is library path.
Let's start from the bottom:
- Don't build pjsua just yet, it is too big with too many libraries
- Start by building pjlib.
- Then we will know the actual physical name of pjlib
- report any errors
Cheers,
--
Perry Ismangil
2007/11/9, Perry Ismangil perry@pjsip.org:
On 11/9/07, Eagle I Martin Baranski eagle3386@googlemail.com wrote:
Is that because PJSIP is stored on M:, but MinGW is on the C:-drive?
No, it's not. '-l' takes an actual library name. '-L' is library path.
Let's start from the bottom:
- Don't build pjsua just yet, it is too big with too many libraries
- Start by building pjlib.
- Then we will know the actual physical name of pjlib
- report any errors
Good, then my second thought was right.. I did think about that PJSIP
needs to build its own library before the actual application can be
compiled.. ;)
Anyway, the compiling of pjlib worked just fine - last command was:
ar.exe: creating ..\lib\libpjlib-i386-win32-vc8-debug.a
Output size is 2.87 MB
Process terminated with status 0 (0 minutes, 7 seconds)
0 errors, 0 warnings
That's an amazing feeling.. No errors, no warnings - great! :D
Regards,
Martin.. :)
=====================
= ~ Code is poetry ~
= Martin Baranski
= Eagle | Eagle3386
= www.troublezone.net
= eagle3386@gmail.com
= +49 (0)160 93317843
Excellent!
Now we know the name of pjlib file on disk. That name will need to be
referenced on applications that use pjlib.
Next, try to build pjlib-test. If it complains of unreferenced stuff
put the pjlib already build as -l.
On 11/9/07, Eagle I Martin Baranski eagle3386@googlemail.com wrote:
2007/11/9, Perry Ismangil perry@pjsip.org:
On 11/9/07, Eagle I Martin Baranski eagle3386@googlemail.com wrote:
Is that because PJSIP is stored on M:, but MinGW is on the C:-drive?
No, it's not. '-l' takes an actual library name. '-L' is library path.
Let's start from the bottom:
- Don't build pjsua just yet, it is too big with too many libraries
- Start by building pjlib.
- Then we will know the actual physical name of pjlib
- report any errors
Good, then my second thought was right.. I did think about that PJSIP
needs to build its own library before the actual application can be
compiled.. ;)
Anyway, the compiling of pjlib worked just fine - last command was:
ar.exe: creating ..\lib\libpjlib-i386-win32-vc8-debug.a
Output size is 2.87 MB
Process terminated with status 0 (0 minutes, 7 seconds)
0 errors, 0 warnings
That's an amazing feeling.. No errors, no warnings - great! :D
Regards,
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
--
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
2007/11/10, perry@pjsip.org perry@pjsip.org:
Excellent!
Now we know the name of pjlib file on disk. That name will need to be
referenced on applications that use pjlib.
Next, try to build pjlib-test. If it complains of unreferenced stuff
put the pjlib already build as -l.
Thanks! :)
Yes, it complains about unreferenced stuff.. Therefore, I've added
"-lM:\pj-sip\pjlib\lib\libpjlib-i386-win32-vc8-debug.a" to the
linker's options, but that didn't solve the problem (even just adding
"-llibpjlib-i386-win32-vc8-debug.a" didn't help.. Full error:
[100.0%] mingw32-gcc.exe -LC:\MinGW\lib
-LC:\MinGW\lib\gcc\mingw32\3.4.5 -o
..\bin\pjlib-test-i386-win32-vc8-debug.exe
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\atomic.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\echo_clt.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\errno.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\exception.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\fifobuf.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\file.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\ioq_perf.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\ioq_tcp.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\ioq_udp.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\ioq_unreg.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\list.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\main.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\mutex.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\os.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\pool.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\pool_perf.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\rand.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\rbtree.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\select.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\sleep.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\sock.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\sock_perf.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\string.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\test.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\thread.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\timer.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\timestamp.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\udp_echo_srv_ioqueue.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\udp_echo_srv_sync.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\util.o
-lM:\pj-sip\pjlib\lib\libpjlib-i386-win32-vc8-debug.a -s -lnetapi32
-lmswsock -lws2_32 -lodbc32 -lodbccp32 -loleaut32 -lole32
C:\MinGW\bin..\lib\gcc\mingw32\3.4.5........\mingw32\bin\ld.exe:
cannot find -lM:\pj-sip\pjlib\lib\libpjlib-i386-win32-vc8-debug.a
collect2: ld returned 1 exit status
Process terminated with status 1 (0 minutes, 8 seconds)
1 errors, 0 warnings
Did I miss something? - Since I want to fix as much stuff as possible
by my own, I played a bit around with the linker's settings (there's
list with libraries at the left and a textarea for entering custom
options at the right - the "-l"-stuff goes into that textarea) and
added the "libpjlib-i386-win32-vc8-debug.a"-file to the list at the
left - that seemed to work a bit better, but I then got this:
[100.0%] mingw32-gcc.exe -LC:\MinGW\lib
-LC:\MinGW\lib\gcc\mingw32\3.4.5 -o
..\bin\pjlib-test-i386-win32-vc8-debug.exe
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\atomic.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\echo_clt.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\errno.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\exception.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\fifobuf.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\file.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\ioq_perf.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\ioq_tcp.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\ioq_udp.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\ioq_unreg.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\list.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\main.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\mutex.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\os.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\pool.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\pool_perf.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\rand.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\rbtree.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\select.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\sleep.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\sock.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\sock_perf.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\string.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\test.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\thread.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\timer.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\timestamp.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\udp_echo_srv_ioqueue.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\udp_echo_srv_sync.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\util.o -s
-lnetapi32 -lmswsock -lws2_32 -lodbc32 -lodbccp32 -loleaut32 -lole32
M:\pj-sip\pjlib\lib\libpjlib-i386-win32-vc8-debug.a
M:\pj-sip\pjlib\lib\libpjlib-i386-win32-vc8-debug.a(os_core_win32.o):
In function pj_init': M:/pj-sip/pjlib/src/pj/os_core_win32.c:134: undefined reference to WSAStartup@8'
M:/pj-sip/pjlib/src/pj/os_core_win32.c:135: undefined reference to
WSAGetLastError@0' M:/pj-sip/pjlib/src/pj/os_core_win32.c:135: undefined reference to WSAGetLastError@0'
M:/pj-sip/pjlib/src/pj/os_core_win32.c:135: undefined reference to
`WSAGetLastError@0'
So, although there's no "-l" before the absolute path to the
pjlib-file, it seems to work, because the linker doesn't complain
about "file not found"..
=====================
= ~ Code is poetry ~
= Martin Baranski
= Eagle | Eagle3386
= www.troublezone.net
= eagle3386@gmail.com
= +49 (0)160 93317843
M:/pj-sip/pjlib/src/pj/os_core_win32.c:134: undefined reference to
WSAStartup@8' M:/pj-sip/pjlib/src/pj/os_core_win32.c:135: undefined reference to WSAGetLastError@0'
M:/pj-sip/pjlib/src/pj/os_core_win32.c:135: undefined reference to
WSAGetLastError@0' M:/pj-sip/pjlib/src/pj/os_core_win32.c:135: undefined reference to WSAGetLastError@0'
You need to link the winsocket library.
----- Original Message -----
From: "Eagle I Martin Baranski" eagle3386@googlemail.com
To: "pjsip embedded/DSP SIP discussion" pjsip@lists.pjsip.org
Sent: Saturday, November 10, 2007 3:05 PM
Subject: Re: [pjsip] Win32 build doesn't build because of stddef.h
2007/11/10, perry@pjsip.org perry@pjsip.org:
Excellent!
Now we know the name of pjlib file on disk. That name will need to be
referenced on applications that use pjlib.
Next, try to build pjlib-test. If it complains of unreferenced stuff
put the pjlib already build as -l.
Thanks! :)
Yes, it complains about unreferenced stuff.. Therefore, I've added
"-lM:\pj-sip\pjlib\lib\libpjlib-i386-win32-vc8-debug.a" to the
linker's options, but that didn't solve the problem (even just adding
"-llibpjlib-i386-win32-vc8-debug.a" didn't help.. Full error:
[100.0%] mingw32-gcc.exe -LC:\MinGW\lib
-LC:\MinGW\lib\gcc\mingw32\3.4.5 -o
..\bin\pjlib-test-i386-win32-vc8-debug.exe
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\atomic.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\echo_clt.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\errno.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\exception.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\fifobuf.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\file.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\ioq_perf.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\ioq_tcp.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\ioq_udp.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\ioq_unreg.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\list.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\main.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\mutex.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\os.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\pool.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\pool_perf.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\rand.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\rbtree.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\select.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\sleep.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\sock.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\sock_perf.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\string.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\test.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\thread.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\timer.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\timestamp.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\udp_echo_srv_ioqueue.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\udp_echo_srv_sync.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\util.o
-lM:\pj-sip\pjlib\lib\libpjlib-i386-win32-vc8-debug.a -s -lnetapi32
-lmswsock -lws2_32 -lodbc32 -lodbccp32 -loleaut32 -lole32
C:\MinGW\bin..\lib\gcc\mingw32\3.4.5........\mingw32\bin\ld.exe:
cannot find -lM:\pj-sip\pjlib\lib\libpjlib-i386-win32-vc8-debug.a
collect2: ld returned 1 exit status
Process terminated with status 1 (0 minutes, 8 seconds)
1 errors, 0 warnings
Did I miss something? - Since I want to fix as much stuff as possible
by my own, I played a bit around with the linker's settings (there's
list with libraries at the left and a textarea for entering custom
options at the right - the "-l"-stuff goes into that textarea) and
added the "libpjlib-i386-win32-vc8-debug.a"-file to the list at the
left - that seemed to work a bit better, but I then got this:
[100.0%] mingw32-gcc.exe -LC:\MinGW\lib
-LC:\MinGW\lib\gcc\mingw32\3.4.5 -o
..\bin\pjlib-test-i386-win32-vc8-debug.exe
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\atomic.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\echo_clt.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\errno.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\exception.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\fifobuf.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\file.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\ioq_perf.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\ioq_tcp.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\ioq_udp.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\ioq_unreg.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\list.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\main.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\mutex.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\os.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\pool.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\pool_perf.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\rand.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\rbtree.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\select.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\sleep.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\sock.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\sock_perf.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\string.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\test.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\thread.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\timer.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\timestamp.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\udp_echo_srv_ioqueue.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\udp_echo_srv_sync.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\util.o -s
-lnetapi32 -lmswsock -lws2_32 -lodbc32 -lodbccp32 -loleaut32 -lole32
M:\pj-sip\pjlib\lib\libpjlib-i386-win32-vc8-debug.a
M:\pj-sip\pjlib\lib\libpjlib-i386-win32-vc8-debug.a(os_core_win32.o):
In function pj_init': M:/pj-sip/pjlib/src/pj/os_core_win32.c:134: undefined reference to WSAStartup@8'
M:/pj-sip/pjlib/src/pj/os_core_win32.c:135: undefined reference to
WSAGetLastError@0' M:/pj-sip/pjlib/src/pj/os_core_win32.c:135: undefined reference to WSAGetLastError@0'
M:/pj-sip/pjlib/src/pj/os_core_win32.c:135: undefined reference to
`WSAGetLastError@0'
So, although there's no "-l" before the absolute path to the
pjlib-file, it seems to work, because the linker doesn't complain
about "file not found"..
=====================
= ~ 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
2007/11/10, Roland Klabunde roland.klabunde@freenet.de:
M:/pj-sip/pjlib/src/pj/os_core_win32.c:134: undefined reference to
WSAStartup@8' M:/pj-sip/pjlib/src/pj/os_core_win32.c:135: undefined reference to WSAGetLastError@0'
M:/pj-sip/pjlib/src/pj/os_core_win32.c:135: undefined reference to
WSAGetLastError@0' M:/pj-sip/pjlib/src/pj/os_core_win32.c:135: undefined reference to WSAGetLastError@0'
You need to link the winsocket library.
I thought that is linked by "mswsock"? - Because that one is already linked:
-lM:\pj-sip\pjlib\lib\libpjlib-i386-win32-vc8-debug.a -s -lnetapi32
-lmswsock -lws2_32 -lodbc32 -lodbccp32 -loleaut32 -lole32
^^^^^^^^^^^^^^^^^^^^
=====================
= ~ Code is poetry ~
= Martin Baranski
= Eagle | Eagle3386
= www.troublezone.net
= eagle3386@gmail.com
= +49 (0)160 93317843
Note the namings. Obviously your lib cannot resolve the functions.
----- Original Message -----
From: "Eagle I Martin Baranski" eagle3386@googlemail.com
To: "pjsip embedded/DSP SIP discussion" pjsip@lists.pjsip.org
Sent: Saturday, November 10, 2007 8:34 PM
Subject: Re: [pjsip] Win32 build doesn't build because of stddef.h
2007/11/10, Roland Klabunde roland.klabunde@freenet.de:
M:/pj-sip/pjlib/src/pj/os_core_win32.c:134: undefined reference to
WSAStartup@8' M:/pj-sip/pjlib/src/pj/os_core_win32.c:135: undefined reference to WSAGetLastError@0'
M:/pj-sip/pjlib/src/pj/os_core_win32.c:135: undefined reference to
WSAGetLastError@0' M:/pj-sip/pjlib/src/pj/os_core_win32.c:135: undefined reference to WSAGetLastError@0'
You need to link the winsocket library.
I thought that is linked by "mswsock"? - Because that one is already
linked:
-lM:\pj-sip\pjlib\lib\libpjlib-i386-win32-vc8-debug.a -s -lnetapi32
-lmswsock -lws2_32 -lodbc32 -lodbccp32 -loleaut32 -lole32
^^^^^^^^^^^^^^^^^^^^
=====================
= ~ 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
Hi,
Try wsock32.lib, look for it on your disk and include the path in your
linker directories. If you can't find it then it's available with the MS
Platform SDK.
Thanks.
Best Regards,
Hitesh
----- Original Message -----
From: "Eagle I Martin Baranski" eagle3386@googlemail.com
To: "pjsip embedded/DSP SIP discussion" pjsip@lists.pjsip.org
Sent: Sunday, November 11, 2007 1:04 AM
Subject: Re: [pjsip] Win32 build doesn't build because of stddef.h
2007/11/10, Roland Klabunde roland.klabunde@freenet.de:
M:/pj-sip/pjlib/src/pj/os_core_win32.c:134: undefined reference to
WSAStartup@8' M:/pj-sip/pjlib/src/pj/os_core_win32.c:135: undefined reference to WSAGetLastError@0'
M:/pj-sip/pjlib/src/pj/os_core_win32.c:135: undefined reference to
WSAGetLastError@0' M:/pj-sip/pjlib/src/pj/os_core_win32.c:135: undefined reference to WSAGetLastError@0'
You need to link the winsocket library.
I thought that is linked by "mswsock"? - Because that one is already
linked:
-lM:\pj-sip\pjlib\lib\libpjlib-i386-win32-vc8-debug.a -s -lnetapi32
-lmswsock -lws2_32 -lodbc32 -lodbccp32 -loleaut32 -lole32
^^^^^^^^^^^^^^^^^^^^
=====================
= ~ 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
Doesn't anyone else feel that this thread is getting way way much
longer that it really should? I know everyone is keen to help, but
instructions have been clearly given in the website, we don't need
to repeat it here.
IMO this discussion has less to do to pjsip, but rather more to do
with applying pjsip build settings to your favorite IDE (which is
not supported by pjsip anyway), so it's probably best to take it to
the IDE's forum.
cheers,
-benny
Benny, I already wanted to say three and a half postings before: Man, change
your signature. Cod(ing) MUST be PAIN for you...:)
Of course, I'm with you. Close this topic..
Regards
----- Original Message -----
From: "Benny Prijono" bennylp@pjsip.org
To: "pjsip embedded/DSP SIP discussion" pjsip@lists.pjsip.org
Sent: Sunday, November 11, 2007 1:09 AM
Subject: Re: [pjsip] Win32 build doesn't build because of stddef.h
Doesn't anyone else feel that this thread is getting way way much
longer that it really should? I know everyone is keen to help, but
instructions have been clearly given in the website, we don't need
to repeat it here.
IMO this discussion has less to do to pjsip, but rather more to do
with applying pjsip build settings to your favorite IDE (which is
not supported by pjsip anyway), so it's probably best to take it to
the IDE's forum.
cheers,
-benny
Visit our blog: http://blog.pjsip.org
pjsip mailing list
pjsip@lists.pjsip.org
http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
2007/11/10, logan logan04x@gmail.com:
Hi,
Try wsock32.lib, look for it on your disk and include the path in your
linker directories. If you can't find it then it's available with the MS
Platform SDK.
Thanks.
Hi Hitesh,
thanks for your hint - got it insert (although I additionally had to
insert the absolute path of the library into the linker's options,
too)..
So now, I only remain with 2 errors (instead of more than 50):
M:\pj-sip\pjlib\lib\libpjlib-i386-win32-vc8-debug.a(sock_bsd.o): In
function pj_sock_socket': M:/pj-sip/pjlib/src/pj/sock_bsd.c:347: undefined reference to WSASocketA@24'
M:\pj-sip\pjlib\lib\libpjlib-i386-win32-vc8-debug.a(guid_win32.o): In
function pj_generate_unique_string': M:/pj-sip/pjlib/src/pj/guid_win32.c:69: undefined reference to CoCreateGuid@4'
collect2: ld returned 1 exit status
Process terminated with status 1 (0 minutes, 8 seconds)
2 errors, 0 warnings
Benny,
I'm just thinking that the GCC should be supported, because that's
definitely a better compiler than MS' one.. I'm saying this, because I
had to work with VS 2003 .NET some time ago and especially the linker
was pure pain to me.. It threw errors where GCC worked just fine - and
GCC is stricter than MS' linker..
And since the compiler works fine and the IDE does what it's meant to
be, I don't see any reason for switching over to the
Code::Blocks-forums.
Instead, IMHO it's more a putting-pjsip-into-a-gcc-compatible-form-stuff.. ;)
Roland,
although this might be hard to understand, I want to say that this is
what makes me still saying "code is poetry" - all this hard work will
finally work and then, there's kind of silence and pleasure and what
I'm feeling in that moment is just awesome..
You know, that's this "still standing, fighting with the code and
finally win the battle"..
So, why close this topic as the final step is already in sight?
Regards,
Martin..
=====================
= ~ Code is poetry ~
= Martin Baranski
= Eagle | Eagle3386
= www.troublezone.net
= eagle3386@gmail.com
= +49 (0)160 93317843
Hi,
Ahh, I'm sorry for my ignorance, the library for Winsock 2 is ws2_32.lib.
The first error should go with this. For the second one make sure you are
linking to ole32.lib (Hmm, I wonder why you didn't get errors for
CoCreateInstance and other COM API's before this, maybe the linker didn't
try further after getting this error?).
As of closing the thread, I guess road blocks like this happen with
everyone, so we can try to help a bit. But, as a side note you should try to
use the tools that are meant to be used with a particular library.
And, VC++ 2005 is a standard C++ compilant compiler. You should be able to
build all standard C++ projects with it. Maybe you were just getting some
weird errors that needed subtle changes in configuration of VC++ 2003.
Thanks.
Best Regards,
Hitesh
----- Original Message -----
From: "Eagle I Martin Baranski" eagle3386@googlemail.com
To: "pjsip embedded/DSP SIP discussion" pjsip@lists.pjsip.org
Sent: Sunday, November 11, 2007 1:10 PM
Subject: Re: [pjsip] Win32 build doesn't build because of stddef.h
2007/11/10, logan logan04x@gmail.com:
Hi,
Try wsock32.lib, look for it on your disk and include the path in your
linker directories. If you can't find it then it's available with the MS
Platform SDK.
Thanks.
Hi Hitesh,
thanks for your hint - got it insert (although I additionally had to
insert the absolute path of the library into the linker's options,
too)..
So now, I only remain with 2 errors (instead of more than 50):
M:\pj-sip\pjlib\lib\libpjlib-i386-win32-vc8-debug.a(sock_bsd.o): In
function pj_sock_socket': M:/pj-sip/pjlib/src/pj/sock_bsd.c:347: undefined reference to WSASocketA@24'
M:\pj-sip\pjlib\lib\libpjlib-i386-win32-vc8-debug.a(guid_win32.o): In
function pj_generate_unique_string': M:/pj-sip/pjlib/src/pj/guid_win32.c:69: undefined reference to CoCreateGuid@4'
collect2: ld returned 1 exit status
Process terminated with status 1 (0 minutes, 8 seconds)
2 errors, 0 warnings
Benny,
I'm just thinking that the GCC should be supported, because that's
definitely a better compiler than MS' one.. I'm saying this, because I
had to work with VS 2003 .NET some time ago and especially the linker
was pure pain to me.. It threw errors where GCC worked just fine - and
GCC is stricter than MS' linker..
And since the compiler works fine and the IDE does what it's meant to
be, I don't see any reason for switching over to the
Code::Blocks-forums.
Instead, IMHO it's more a putting-pjsip-into-a-gcc-compatible-form-stuff..
;)
Roland,
although this might be hard to understand, I want to say that this is
what makes me still saying "code is poetry" - all this hard work will
finally work and then, there's kind of silence and pleasure and what
I'm feeling in that moment is just awesome..
You know, that's this "still standing, fighting with the code and
finally win the battle"..
So, why close this topic as the final step is already in sight?
Regards,
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
Eagle I Martin Baranski wrote:
Benny,
I'm just thinking that the GCC should be supported, because that's
definitely a better compiler than MS' one.. I'm saying this, because I
had to work with VS 2003 .NET some time ago and especially the linker
was pure pain to me.. It threw errors where GCC worked just fine - and
GCC is stricter than MS' linker..
And since the compiler works fine and the IDE does what it's meant to
be, I don't see any reason for switching over to the
Code::Blocks-forums.
Instead, IMHO it's more a putting-pjsip-into-a-gcc-compatible-form-stuff.. ;)
Thanks for the suggestion to support gcc, and I've added support for
gcc in pjsip... four years ago! You really really need to read the
Getting Started page to help you with building pjsip and avoid this
misconception.
Lets put this thread to rest already.
-benny
Instead, IMHO it's more a
putting-pjsip-into-a-gcc-compatible-form-stuff.. ;)
Thanks for the suggestion to support gcc, and I've added support for
gcc in pjsip... four years ago! You really really need to read the
Getting Started page to help you with building pjsip and avoid this
misconception.
Congratulation. I know Benny since years and I didn't manage to upset him
seriously. Martin, please consider to stop annoying the community with
precocious postings and stealing us time, nerves and mailbox space!
Regards
2007/11/11, logan logan04x@gmail.com:
Hi,
Ahh, I'm sorry for my ignorance, the library for Winsock 2 is ws2_32.lib.
The first error should go with this. For the second one make sure you are
linking to ole32.lib (Hmm, I wonder why you didn't get errors for
CoCreateInstance and other COM API's before this, maybe the linker didn't
try further after getting this error?).
As of closing the thread, I guess road blocks like this happen with
everyone, so we can try to help a bit. But, as a side note you should try to
use the tools that are meant to be used with a particular library.
And, VC++ 2005 is a standard C++ compilant compiler. You should be able to
build all standard C++ projects with it. Maybe you were just getting some
weird errors that needed subtle changes in configuration of VC++ 2003.
Thanks.
Hitesh,
thanks, man! You're one of those guys that support my way of thinking
that there's NO stupid question, but maybe answers which won't help..
Regarding your hint, I'm asking myself why I should add it once more,
because there's already a command-line argument "-ws2_32".. - Here's
the error's full log:
[100.0%] mingw32-gcc.exe -LC:\MinGW\lib
-LC:\MinGW\lib\gcc\mingw32\3.4.5 -L"C:\Program Files\System\Platform
SDK\Windows\Lib" -o ..\bin\pjlib-test-i386-win32-vc8-debug.exe
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\atomic.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\echo_clt.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\errno.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\exception.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\fifobuf.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\file.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\ioq_perf.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\ioq_tcp.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\ioq_udp.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\ioq_unreg.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\list.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\main.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\mutex.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\os.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\pool.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\pool_perf.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\rand.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\rbtree.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\select.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\sleep.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\sock.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\sock_perf.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\string.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\test.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\thread.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\timer.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\timestamp.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\udp_echo_srv_ioqueue.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\udp_echo_srv_sync.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\util.o -s
-lnetapi32 -lmswsock -lws2_32 -lodbc32 -lodbccp32 -loleaut32 -lole32
M:\pj-sip\pjlib\lib\libpjlib-i386-win32-vc8-debug.a "C:\Program
Files\System\Platform SDK\Windows\Lib\WSock32.Lib"
M:\pj-sip\pjlib\lib\libpjlib-i386-win32-vc8-debug.a(sock_bsd.o): In
function pj_sock_socket': M:/pj-sip/pjlib/src/pj/sock_bsd.c:347: undefined reference to WSASocketA@24'
M:\pj-sip\pjlib\lib\libpjlib-i386-win32-vc8-debug.a(guid_win32.o): In
function pj_generate_unique_string': M:/pj-sip/pjlib/src/pj/guid_win32.c:69: undefined reference to CoCreateGuid@4'
collect2: ld returned 1 exit status
Process terminated with status 1 (0 minutes, 9 seconds)
2 errors, 0 warnings
So, as you can see, there's a part talking about "-lmswsock -lws2_32
-lodbc32 -lodbccp32 -loleaut32 -lole32".. Or do I have to setup the
absolute path for all of them?
Benny,
I didn't want to, but now I have to - let's get this straight, once and for all:
The only chapter that include the letters "GCC" is this one:
Building Linux, *nix, *BSD, and MacOS X Targets with GNU Build Systems
So, let me explain this a little bit further.. The non-professional
developer, i. e. a guy who develops stuff for fun in his spare time,
will visit the page http://www.pjsip.org/using.htm and look for
information about building the SIP-library he thinks would suit
perfectly in a new, free open-source SIP-software for people looking
for something not bloated and kept simple.. Something like KPhone on
Linux maybe..
Therefore, this guy - after managing SVN-installation and shortly
learning its syntax - downloads the SVN-files and gets a first look
into the architecture of the library..
Afterwards, he reads on at the page I've linked to above. But soon, he
will notice that the guide talks about Visual Studio from Microsoft
which normal people maybe don't want to buy. Just think about this:
free, open-source software - built via a commercial IDE from a company
which is heavily involved in commercial stuff.
Wouldn't it be just nicer to build a free software based upon free
library-files and all built with a free IDE using a free compiler?
But this is, where the problem(s) come in.. Even if such a guy would
read the Linux-part of the guide (after he had read the whole guide
about 2 or 3 times - just to make sure nothing has been left hidden
from his eyes), he would come across the part that talks about
Cygwin.. And now think about what well-informed guys talk about Cygwin
and efficiency and stuff like that.. - That's just what I've read and
heard.. I, myself, never tried Cygwin because of those reasons..
So please, explain a stupid guy like me why the hell I should reinvent
the wheel instead of using the ported GCC for Windows together with a
free IDE that supports GCC and throws an app right into my face if the
compiling would one day run without any errors? I just don't get it,
but that's maybe because I'm just too stupid.. - Roland surely knows
more as he thinks that way about me since his very first reply..
(To Roland: Super Hilfe von dir, Landsmann! - Das ich nicht lache.. -.-)
Honestly guys, this isn't helpful!! I'm just doing everything to get
this working (so that others later might do the same way, but faster
and without such pain) and you're talking about ridiculous stuff like
closing the thread or kicking me over to the Code::Blocks-forums..
What's this? Shunt me off so that your "problem" has pissed off and
that "it" must fight all alone?
If I'm such an annoying, stupid guy, put me into your spam-filter so
that (as Roland said) "stealing us time, nerves and mailbox space"
doesn't happen to you and guys like Hitesh or Perry can concentrate on
my problem and helping me through..
Lastly, I'm wishing you all the best and that guys like me never
discover the idea of running a SIP-software built around the
PJSIP-library, because if this happens one day again, you will have
the "pain" and "loss of nerves" just once again!
Best regards from a guy, living in Germany who lost his trust in
helpful developers..
=====================
= ~ Code is poetry ~
= Martin Baranski
= Eagle | Eagle3386
= www.troublezone.net
= eagle3386@gmail.com
= +49 (0)160 93317843
Hi,
It seems that you are now able to build and link pjlib, and your IDE
found it. The problem now is how your IDE deals with Platform SDK, so
I'm afraid I can't help you further.
As others have suggested, maybe try the Code::Blocks forum or look at
networking/socket samples.
Regards,
On 11/11/07, Eagle I Martin Baranski eagle3386@googlemail.com wrote:
2007/11/11, logan logan04x@gmail.com:
Hi,
Ahh, I'm sorry for my ignorance, the library for Winsock 2 is ws2_32.lib.
The first error should go with this. For the second one make sure you are
linking to ole32.lib (Hmm, I wonder why you didn't get errors for
CoCreateInstance and other COM API's before this, maybe the linker didn't
try further after getting this error?).
As of closing the thread, I guess road blocks like this happen with
everyone, so we can try to help a bit. But, as a side note you should try
to
use the tools that are meant to be used with a particular library.
And, VC++ 2005 is a standard C++ compilant compiler. You should be able to
build all standard C++ projects with it. Maybe you were just getting some
weird errors that needed subtle changes in configuration of VC++ 2003.
Thanks.
Hitesh,
thanks, man! You're one of those guys that support my way of thinking
that there's NO stupid question, but maybe answers which won't help..
Regarding your hint, I'm asking myself why I should add it once more,
because there's already a command-line argument "-ws2_32".. - Here's
the error's full log:
[100.0%] mingw32-gcc.exe -LC:\MinGW\lib
-LC:\MinGW\lib\gcc\mingw32\3.4.5 -L"C:\Program Files\System\Platform
SDK\Windows\Lib" -o ..\bin\pjlib-test-i386-win32-vc8-debug.exe
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\atomic.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\echo_clt.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\errno.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\exception.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\fifobuf.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\file.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\ioq_perf.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\ioq_tcp.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\ioq_udp.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\ioq_unreg.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\list.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\main.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\mutex.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\os.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\pool.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\pool_perf.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\rand.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\rbtree.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\select.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\sleep.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\sock.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\sock_perf.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\string.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\test.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\thread.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\timer.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\timestamp.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\udp_echo_srv_ioqueue.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\udp_echo_srv_sync.o
output\pjlib-test-i386-win32-vc8-debug\src\pjlib-test\util.o -s
-lnetapi32 -lmswsock -lws2_32 -lodbc32 -lodbccp32 -loleaut32 -lole32
M:\pj-sip\pjlib\lib\libpjlib-i386-win32-vc8-debug.a "C:\Program
Files\System\Platform SDK\Windows\Lib\WSock32.Lib"
M:\pj-sip\pjlib\lib\libpjlib-i386-win32-vc8-debug.a(sock_bsd.o): In
function pj_sock_socket': M:/pj-sip/pjlib/src/pj/sock_bsd.c:347: undefined reference to WSASocketA@24'
M:\pj-sip\pjlib\lib\libpjlib-i386-win32-vc8-debug.a(guid_win32.o): In
function pj_generate_unique_string': M:/pj-sip/pjlib/src/pj/guid_win32.c:69: undefined reference to CoCreateGuid@4'
collect2: ld returned 1 exit status
Process terminated with status 1 (0 minutes, 9 seconds)
2 errors, 0 warnings
So, as you can see, there's a part talking about "-lmswsock -lws2_32
-lodbc32 -lodbccp32 -loleaut32 -lole32".. Or do I have to setup the
absolute path for all of them?
Benny,
I didn't want to, but now I have to - let's get this straight, once and for
all:
The only chapter that include the letters "GCC" is this one:
Building Linux, *nix, *BSD, and MacOS X Targets with GNU Build Systems
So, let me explain this a little bit further.. The non-professional
developer, i. e. a guy who develops stuff for fun in his spare time,
will visit the page http://www.pjsip.org/using.htm and look for
information about building the SIP-library he thinks would suit
perfectly in a new, free open-source SIP-software for people looking
for something not bloated and kept simple.. Something like KPhone on
Linux maybe..
Therefore, this guy - after managing SVN-installation and shortly
learning its syntax - downloads the SVN-files and gets a first look
into the architecture of the library..
Afterwards, he reads on at the page I've linked to above. But soon, he
will notice that the guide talks about Visual Studio from Microsoft
which normal people maybe don't want to buy. Just think about this:
free, open-source software - built via a commercial IDE from a company
which is heavily involved in commercial stuff.
Wouldn't it be just nicer to build a free software based upon free
library-files and all built with a free IDE using a free compiler?
But this is, where the problem(s) come in.. Even if such a guy would
read the Linux-part of the guide (after he had read the whole guide
about 2 or 3 times - just to make sure nothing has been left hidden
from his eyes), he would come across the part that talks about
Cygwin.. And now think about what well-informed guys talk about Cygwin
and efficiency and stuff like that.. - That's just what I've read and
heard.. I, myself, never tried Cygwin because of those reasons..
So please, explain a stupid guy like me why the hell I should reinvent
the wheel instead of using the ported GCC for Windows together with a
free IDE that supports GCC and throws an app right into my face if the
compiling would one day run without any errors? I just don't get it,
but that's maybe because I'm just too stupid.. - Roland surely knows
more as he thinks that way about me since his very first reply..
(To Roland: Super Hilfe von dir, Landsmann! - Das ich nicht lache.. -.-)
Honestly guys, this isn't helpful!! I'm just doing everything to get
this working (so that others later might do the same way, but faster
and without such pain) and you're talking about ridiculous stuff like
closing the thread or kicking me over to the Code::Blocks-forums..
What's this? Shunt me off so that your "problem" has pissed off and
that "it" must fight all alone?
If I'm such an annoying, stupid guy, put me into your spam-filter so
that (as Roland said) "stealing us time, nerves and mailbox space"
doesn't happen to you and guys like Hitesh or Perry can concentrate on
my problem and helping me through..
Lastly, I'm wishing you all the best and that guys like me never
discover the idea of running a SIP-software built around the
PJSIP-library, because if this happens one day again, you will have
the "pain" and "loss of nerves" just once again!
Best regards from a guy, living in Germany who lost his trust in
helpful developers..
=====================
= ~ 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