pjsip linker problem

[Paul77]

Hi,
I'm using Visual Studio 2005 express to build the freeware pjsip SIP stack. I've pointed the project include and library settings at C:Program Files/Microsoft SDKs as 2005 express has no built-in SDK. So it now compiles
the solution project pjsua but when it links I get this error:-

LINK : fatal error LNK1104: cannot open file '..\..\lib\libpjproject-i386-win32-vc8-debug.lib'

which implies that there should be a general project library available - I don't think I've deleted this nor that the compiler whould be generating this lib?

Anyone got any ideas what the problem is here?

thanks
Paul

[helios]

Are there more than one projects included in the solution? There may be a specific build order and the developer failed to specify project dependencies.

[Paul77]

There is more than one project in the solution.

In the 'getting started' notes it says:-

For Visual Studio 8 (VS 2005): open pjproject-vs8.sln solution file.
Set pjsua as Active Project.
Set Win32 as the platform.
Select Debug or Release build as appropriate.
Build the project. This will build pjsua application and all libraries needed by pjsua.

Should this read 'Build Solution' as I have been building project pjsua and as you say
it may have to be done in a specific order so that the libpjproject is built before pjsua.

[helios]

If the dependencies were properly set, as the documentation appears to imply, building the project should be enough. Building the solution wouldn't change much, if anything.

[Paul77]

will have another look this evening, and check the project setting and see if its attempted
to build libpjproject-i386-win32-vc8-debug.lib

[Paul77]

Have checked the project dependencies and they look ok:
project pjsua depends on libpjproject only

The build order looks ok also in that libpjproject is above pjsua.

Looking at the build output - it looks like this at the top:-

I was expecting it to follow the build order which is:-

libportaudio
pjlib_util
pjmedia
pjmedia_codec
pjsip_core
.
.
.

but it starts with pjmedia.

It immediately runs into trouble when compiling the sdk files.

I currently have the project include and library paths pointing at
c:\program files\microsoft sdks\windows\v6.0a\include, which was already on my PC, so it could find all the includes.

2005 Express has no built-in sdk and I'm not sure there is one available on the web for Express
(visual studio 2005 v4.0 sdk I found appears to be only for the full version of visual studio)

So currently I appear to have an incompatible SDK problem.



1>------ Build started: Project: pjmedia, Configuration: Debug Win32 ------
2>------ Build started: Project: pjsip_core, Configuration: Debug Win32 ------
2>Compiling...
1>Compiling...
2>sip_transport_tls.c
1>stream.c
2>c:\program files\microsoft sdks\windows\v6.0a\include\ws2ipdef.h(157) : error C2061: syntax error : identifier 'ADDRESS_FAMILY'
2>c:\program files\microsoft sdks\windows\v6.0a\include\ws2ipdef.h(163) : error C2061: syntax error : identifier 'SCOPE_ID'
2>c:\program files\microsoft sdks\windows\v6.0a\include\ws2ipdef.h(164) : error C2059: syntax error : '}'
2>c:\program files\microsoft sdks\windows\v6.0a\include\ws2ipdef.h(165) : error C2059: syntax error : '}'

[helios]

Hm. Google doesn't give anything relevant for the error inside the SDK. I don't know what to tell you.
Some possible courses of action:
1. Try to see what's causing the error in ws2ipdef.h.
2. Update the Windows SDK.
3. Seek support from the developer.

[Paul77]

Have downloaded the Vista SDK 6.0 which is supposed to be okay for XP - but am still getting
the same error. Looking at the file ws2ipdef.h it uses ADDRESS_FAMILY but this is declared in
ws2def.h which ws2ipdef.h does not include!

This seems like a really basic problem - I can't figure why this is not in google as a known compatibility problem.

The only thing I notice on the download was that it said I have a slightly out of date
Microsoft .NET Framework 2.0 Service Pack 2 - tried to uninstall it so could down load
a new one and it would'nt allow it as it said it would affect other applications (something to do
with a pre-release of Microsoft .NET Framework 3.0 service pack)

I may try email Microsoft!