search

kiwifig / libyuv

Automatically exported from code.google.com/p/libyuv
BSD 3-Clause "New" or "Revised" License
0 stars 0 forks source link

Error on synching libyuv #503

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Windows 7 64-bit, using Administrator cmd; on gclient sync I get the following 
error:

Updating projects from gyp files...
Traceback (most recent call last):
  File "libyuv/gyp_libyuv", line 89, in <module>
  File "I:\FPACH\p4\comms_all\comms\eng\vcp\main\pjsip\libyuv\tools\gyp\pylib\gyp\__init__.py", line 538, in main return gyp_main(args)
  File "I:\FPACH\p4\comms_all\comms\eng\vcp\main\pjsip\libyuv\tools\gyp\pylib\gyp\__init__.py", line 523, in gyp_main generator.GenerateOutput(flat_list, targets, data, params)
  File "I:\FPACH\p4\comms_all\comms\eng\vcp\main\pjsip\libyuv\tools\gyp\pylib\gyp\generator\ninja.py", line 2384, in GenerateOutput pool.map(CallGenerateOutputForConfig, arglists)
  File "I:\FPACH\p4\comms_all\comms\eng\vcp\main\pjsip\depot_tools\python276_bin\lib\multiprocessing\pool.py", line 250, in map return self.map_async(func, iterable, chunksize).get()
  File "I:\FPACH\p4\comms_all\comms\eng\vcp\main\pjsip\depot_tools\python276_bin\lib\multiprocessing\pool.py", line 554, in get raise self._value
Exception: Environment variable "SYSTEMROOT" required to be set to valid path
Error: Command 
'I:\\FPACH\\p4\\comms_all\\comms\\eng\\vcp\\main\\pjsip\\depot_tools\\python276_
bin\\python.exe libyuv/gyp_libyuv' returned non-zero exit status 1 in 
I:\FPACH\p4\comms_all\comms\eng\vcp\main\pjsip

SYSTEMROOT is correctly set to C:\Windows

Original issue reported on code.google.com by fp...@dolby.com on 9 Oct 2015 at 7:55

GoogleCodeExporter commented 9 years ago 
The depot moved to git recently.  Perhaps you havent synced since the move?

https://code.google.com/p/libyuv/wiki/GettingStarted

shows the new location under Getting the Code

c:\src>mkdir libyuv4

c:\src>cd libyuv4

c:\src\libyuv4>gclient config https://chromium.googlesource.com/libyuv/libyuv

c:\src\libyuv4>more .gclient
solutions = [
  { "name"        : "libyuv",
    "url"         : "https://chromium.googlesource.com/libyuv/libyuv",
    "deps_file"   : "DEPS",
    "managed"     : True,
    "custom_deps" : {
    },
    "safesync_url": "",
  },
]
cache_dir = None

c:\src\libyuv4>gclient sync
Syncing projects: 100% (1/1), done.

The slow part if pulling in chromium.  To avoid that glcient sync --nohooks
But you'll need the chromium bits for building.

You'll also need fairly new depot_tools.  Follow chromium instructions for 
getting those.

Original comment by fbarch...@chromium.org on 9 Oct 2015 at 6:15

GoogleCodeExporter commented 9 years ago 
It does not work...
I have installed the depot_tool without cygwin as described here: 
https://www.chromium.org/developers/how-tos/install-depot-tools

Downloaded the zip from this location: 
https://src.chromium.org/svn/trunk/tools/depot_tools.zip

I used "Extract all..." to unzip. Path does not contain blanks.

Opened Administrator cmd, added the path to PATH.

I ran gclient.

I ran gclient config https://chromium.googlesource.com/libyuv/libyuv.

I ran gtclient sync. Result is an error:

Traceback (most recent call last):
  File "src/build/landmines.py", line 136, in <module>
    sys.exit(main())
  File "src/build/landmines.py", line 123, in main
    gyp_environment.SetEnvironment()
  File "I:\FPACH\pjsip\libyuv\chromium\src\build\gyp_environment.py", line 33, in SetEnvironment
    vs_toolchain.SetEnvironmentAndGetRuntimeDllDirs()
  File "I:\FPACH\pjsip\libyuv\chromium\src\build\vs_toolchain.py", line 34, in SetEnvironmentAndGetRuntimeDllDirs
    Update()
  File "I:\FPACH\pjsip\libyuv\chromium\src\build\vs_toolchain.py", line 215, in Update
    subprocess.check_call(get_toolchain_args)
  File "I:\FPACH\pjsip\depot_tools\python276_bin\lib\subprocess.py", line 540, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command 
'['I:\\FPACH\\pjsip\\depot_tools\\python276_bin\\python.exe', 
'I:\\FPACH\\pjsip\\depot_tools\\win_toolchain\\get_toolchain_if_necessary.py', 
'--output-json', 
'I:\\FPACH\\pjsip\\libyuv\\chromium\\src\\build\\win_toolchain.json', 
'ee7d718ec60c2dc5d255bbe325909c2021a7efef']' returned non-zero exit status 1
Error: Command 'I:\\FPACH\\pjsip\\depot_tools\\python276_bin\\python.exe 
src/build/landmines.py' returned non-zero exit status 1 in 
I:\FPACH\pjsip\libyuv\chromium
Hook ''I:\FPACH\pjsip\depot_tools\python276_bin\python.exe' 
src/build/landmines.py' took 10.57 secs
Error: Command 'I:\\FPACH\\pjsip\\depot_tools\\python276_bin\\python.exe -u 
libyuv/sync_chromium.py --target-revision 
bfea27af55be979d8146ed4d225f07a9cf1fba8b' returned non-zero exit status 2 in 
I:\FPACH\pjsip
Hook ''I:\FPACH\pjsip\depot_tools\python276_bin\python.exe' -u 
libyuv/sync_chromium.py --target-revision 
bfea27af55be979d8146ed4d225f07a9cf1fba8b' took 4053.40 secs

Original comment by fp...@dolby.com on 12 Oct 2015 at 9:29

GoogleCodeExporter commented 9 years ago 
Is there any location to get binaries of libyuv for Windows?

Original comment by fp...@dolby.com on 12 Oct 2015 at 9:29

GoogleCodeExporter commented 9 years ago 
The issue looks similar to this:
http://stackoverflow.com/questions/27809193/webrtc-not-building-for-windows

No library binaries, I'm afraid.  Just the psnr.exe tool.
See if the above works for you.

Original comment by fbarch...@google.com on 14 Oct 2015 at 5:17

GoogleCodeExporter commented 9 years ago 
In general libyuv follows webrtc and chromium, so use the initial setup 
instructions from those.  If you can sync chrome and/or webrtc, you should be 
able to sync libyuv.

Original comment by fbarch...@google.com on 15 Oct 2015 at 9:35

GoogleCodeExporter commented 9 years ago 
marking invalid, as there doesnt appear to be anything fixable in libyuv.
see webrtc and chromium initial setup instructions.

Original comment by fbarch...@chromium.org on 22 Oct 2015 at 6:12