zcbsxb / libjingle

Automatically exported from code.google.com/p/libjingle
0 stars 0 forks source link

Libjingle doesn't complie on windows XP #89

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Follow steps as given in Readme file .
2. scon_dir path variable set.
3. replace srtp\crypto\include\config.h by config.hw

What is the expected output? What do you see instead?
It should produce the object file and libs compiling successfully but throws 
error stating missing files.

What version of the product are you using? On what operating system?
Visual Studio 2005 and windows XP.

Please provide any additional information below.

In the file session\phone\devicemanager.cc gives error stating missing file 
'mmdeviceapi.h'(error logs attched). This file looks like belonging to some 
Window Vista SDK.What are the dependencies libjingle having??What else i need 
to install except the things written in Readme file.

Original issue reported on code.google.com by sbhu...@gmail.com on 10 Nov 2010 at 3:55

Attachments:

GoogleCodeExporter commented 9 years ago
I'm looking into this.

Original comment by jun...@google.com on 10 Nov 2010 at 4:29

GoogleCodeExporter commented 9 years ago
Basically, what you need is to install the Microsoft Windows SDK. Here is the 
link:
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=E6E1C3DF-A74F-4207-8
586-711EBE331CDC
After that, you need to modify the libjingle.scons file to add reference path 
to the install location. We will make a fix in the near future on the .scons 
file. Meanwhile, you can try this workaround.

Original comment by jun...@google.com on 11 Nov 2010 at 12:56

GoogleCodeExporter commented 9 years ago
Issue 86 has been merged into this issue.

Original comment by jun...@google.com on 11 Nov 2010 at 12:57

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
I have successfully compiled this on Windows XP Pro 32 bit and Windows 7 64 
bit.  Here is the complete list of everything I had to do in order to get this 
to work on the x64 OS.

1. Extract libjingle-0.5.1.zip somewhere (I put it in c:\libjingle-0.5.1 for 
this)

2. Install Python-2.7.1.msi

3. Install pywin32-214.win32-py2.7.exe

4. Extract scons-local-2.0.1.zip to c:\libjingle-0.5.1\talk

5. Extract swtoolkit.0.9.1 into c:\libjingle-0.5.1\talk

6. Extract srtp-cvs into third-party renaming the folder to srtp

7. Extract expat-2.0.1 into third-party

8. set an environment variable SCONS_DIR, to point to the directory containing 
SCons

9. copy talk/third_party/srtp/config.hw to 
talk/third_party/srtp/crypto/include/config.h

10. Install Windows SDK, VS2008 Express, and MS Platform SDK

11a. In main.scons under in the CPPDEFINES section, uncomment the line 
'WIN32_LEAN_AND_MEAN' so that your CPPDEFINES section looks like this:

11b. Commented out or removed the line #define WIN32_LEAN_AND_MEAN from the 
following files:

talk\base\logging.cc
talk\base\common.cc
talk\base\helpers.cc
talk\base\httpcommon.cc
talk\base\physicalsocketserver.cc
talk\base\socketadapters.cc
talk\base\time.cc
expat\lib\winconfig.h

12. Added #include <mmsystem.h> to line 42 of 
talk\session\phone\devicemanager.cc (Just above the end of the windows tag)

13. Found out which version of atlbase.h the compiler was utilizing (In my 
case, because of the PATH that I set, the version I used was at c:\Program 
Files\Microsoft Platform SDK\Include\atl.  Edit that file and comment out the 
line #pragma comment(lib, "atlthunk.lib") which was on or around line 293.

14. Run a visual studio command prompt so that your PATH, LIB, and INCLUDE 
environment variables are set properly.  In our case, we had to also manually 
add python to our PATH, and also the Microsoft Platform SDK\Include\atl 
directory to our INCLUDE which ended up looking like this:

PATH
C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE;C:\Program Files 
(x86)\Microsoft Visual Studio 9.0\VC\BIN;C:\Program Files (x86)\Microsoft 
Visual Studio 9.0\Common7\Tools;C:\Program Files (x86)\Microsoft Visual Studio 
9.0\Common7\Tools\bin;C:\Windows\Microsoft.NET\Framework\;C:\Windows\Microsoft.N
ET\Framework\\Microsoft .NET Framework 3.5 (Pre-Release 
Version);C:\Windows\Microsoft.NET\Framework\v2.0.50727;C:\Program Files 
(x86)\Microsoft Visual Studio 9.0\VC\VCPackages;C:\Program Files\Microsoft 
SDKs\Windows\v6.0A\bin;C:\Program Files\Common Files\Microsoft Shared\Windows 
Live;C:\Program Files (x86)\Common Files\Microsoft Shared\Windows 
Live;C:\Applications\Xuggle\bin;C:\Windows\system32;C:\Windows;C:\Windows\System
32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Applications\Bitvise 
Tunnelier;C:\Applications\SlikSvn\bin\;C:\Applications\jEdit;C:\Program Files 
(x86)\Windows Live\Shared;C:\Applications\Python27 

INCLUDE
C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\ATLMFC\INCLUDE;C:\Program 
Files (x86)\Microsoft Visual Studio 9.0\VC\INCLUDE;C:\Program Files\Microsoft 
SDKs\Windows\v6.0A\include;C:\Program Files\Microsoft Platform SDK\Include\atl 

LIB
C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\ATLMFC\LIB;C:\Program 
Files (x86)\Microsoft Visual Studio 9.0\VC\LIB;C:\Program Files\Microsoft 
SDKs\Windows\v6.0A\lib; 

15. cd into the talk directory and execute the following command

scons-local-2.0.1\hammer.bat

Notes:

There will be differences on a 32 bit machine such as your path but all around 
this is more or less the same instructions I followed on the 32 bit machine.

According to some very brief research, Step 14 seems to be caused by 
atlthunk.lib being wanted for 32 bit SDK libraries only.  I have not verified 
this yet, but will be investigating this issue further so that perhaps we can 
rectify the situation instead of sweeping it under the rug.

I would like to hear any feedback on this if anyone has success or problems or 
has improvements on these instructions.

Original comment by atm7...@gmail.com on 7 Dec 2010 at 4:08

GoogleCodeExporter commented 9 years ago

Original comment by jun...@google.com on 9 Dec 2010 at 7:16