b13dfbffd7
This makes it possible to compile on the bots without hardcoding paths to Ant, Java and ffmpeg deep into the Python scripts (hardcoded paths exists only in the buildbot configuration). For bots, the ANT_HOME, JAVA_HOME and FFMPEG_HOME environment variables must be set to the install locations for each of these dependencies, for Windows. This CL also improves the return code handling to make failures easier to detect when things break. TEST=running build_zxing.py without Ant or Java in the PATH, but with ANT_HOME, JAVA_HOME and FFMPEG_HOME set. Running Chromium's src/chrome/test/functional/webrtc_video_quality.py. BUG=none Review URL: https://webrtc-codereview.appspot.com/1002005 git-svn-id: http://webrtc.googlecode.com/svn/trunk@3311 4adac7df-926f-26a2-2b94-8c16560cd09d |
||
---|---|---|
.. | ||
barcode_decoder.py | ||
barcode_encoder.py | ||
build_zxing.py | ||
DEPS | ||
helper_functions.py | ||
README | ||
yuv_cropper.py |
This file explains how to set up the Zebra Crossing (Zxing) library in order to use it in the barcode encoder and decoder tools. Zxing could be found at: https://code.google.com/p/zxing/ After checkout, the relevant files from Zxing should be in third_party/zxing, relative to this README. In order to run barcode_encoder.py and barcode_decoder.py we need to have build two jar files: zxing/core/core.jar and zxing/javase/javase.jar. In order to build these we have to have Ant already installed. Building is as simple as running the build_zxing.py script: ./build_zxing.py, which should automatically call ant with the respective build files from the Zxing checkout. For more information on how to run barcode_encoder.py and barcode_decoder.py check the documentation in the main functions inside these tools.