search

teaj / libjingle

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

could not build libjingle for win #438

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1.gclient config http://libjingle.googlecode.com/svn/trunk/ 
2.gclient sync --deps=win 
3.

What is the expected output? What do you see instead?
error-description:
-------------------
Call to '/bin/echo -n ${JAVA_HOME}' path not found

22>A    
X:\work\webrtc-test\v15.0\libjingle\trunk\third_party\icu\source\allinone\icuche
ck.bat
22>Checked out revision 199252.
Syncing projects:  97% (34/35), done.third_party\icu

________ running 'x:\work\webrtc\depot_tools\python_bin\python.exe 
trunk/tools/clang/scripts/update.py --mac-only' in 
'X:\work\webrtc-test\v15.0\libjingle'

________ running 'x:\work\webrtc\depot_tools\python_bin\python.exe 
trunk/build/win/setup_cygwin_mount.py --win-only' in 
'X:\work\webrtc-test\v15.0\libjingle'

________ running 'x:\work\webrtc\depot_tools\python_bin\python.exe 
trunk/build/gyp_chromium --depth=trunk trunk/talk/libjingle_all.gyp 
-Dextra_gyp_flag=0' in 'X:\work\web
rtc-test\v15.0\libjingle'
Updating projects from gyp files...
Das System kann den angegebenen Pfad nicht finden.
gyp: Call to '/bin/echo -n ${JAVA_HOME}' returned exit status 1. while loading 
dependencies of trunk\talk\libjingle_all.gyp while trying to load 
trunk\talk\libjingle_all.
gyp
Error: Command x:\work\webrtc\depot_tools\python_bin\python.exe 
trunk/build/gyp_chromium --depth=trunk trunk/talk/libjingle_all.gyp 
-Dextra_gyp_flag=0 returned non-zero e
xit status 1 in X:\work\webrtc-test\v15.0\libjingle

What version of the product are you using? On what operating system?
libjingle 326 , windows 7

Please provide any additional information below.

neu ab libjingle 326
     JAVA_HOME="C:\Program Files (x86)\Java\jdk1.7.0_07"

workaround:
------------
remove   /bin/echo -n 

X:\work\webrtc-test\v15.0\libjingle\trunk\talk\build\common.gypi

# This file contains common settings for building libjingle components.

{
  'variables': {
    # TODO(ronghuawu): Chromium build will need a different libjingle_root.
    'libjingle_root%': '<(DEPTH)',
    # TODO(ronghuawu): For now, disable the Chrome plugins, which causes a
    # flood of chromium-style warnings.
    'clang_use_chrome_plugins%': 0,
    'libpeer_target_type%': 'static_library',
    #'java_home%': '<!(/bin/echo -n ${JAVA_HOME})',
    'java_home%': '<$(JAVA_HOME)',
  },

Original issue reported on code.google.com by berthold...@googlemail.com on 29 May 2013 at 2:46

GoogleCodeExporter commented 9 years ago 
The proposed workaround doesn't work for linux/android, so is a non-starter.
You should be able to specify java_home explicitly to gyp (either via 
$GYP_DEFINES, or via -D on the gyp command-line, or via the windows version of 
~/.gyp/include.gypi) to avoid the fallback to env var here.

BTW I don't think anyone watches this /p/libjingle issue tracker; please use 
the webrtc tracker in future https://code.google.com/p/webrtc/issues/list

If this doesn't work for you, please open a webrtc issue and provide details on 
how you're passing java_home to gyp.

Original comment by fischman@google.com on 31 May 2013 at 7:39