You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 10, 2023. It is now read-only.
Ah, yes, now I am feeling your pain. I just made it possible to build the Closure Compiler using Buck, and I had to do some hacky things, as well (see /closure/closure-compiler/BUCK):
What about having a macro inside of the cmd string like "$(location //x:y)" to give you the location of a srcs entry named "//x:y". If //x:y is e.g. a java_library() this is the JAR it produces, if its a java_application() again its only the JAR it makes and not the execution command line, if its a genrule() its the out file. Such references in srcs should also automatically be added to the dep list so its not necessary to repeat them in deps.
Buck already seems to do this with ${//x:y} for the name of the tool to execute, but that expansion isn't suitable because it creates things like "java -classpath ..." or "PYTHONPATH= ..." which isn't suitable in all contexts. $(location //x:y) would expand only to the path of the source file.
The example for genrule() shows:
cmd = 'python $SRC_0 $SRC_1 > $OUT',
which does not work. $SRC_0 seems to be not implemented in BUCK. I suspect you meant:
cmd = 'python $SRCDIR/basic_to_full_manifest.py $SRCDIR/AndroidManifest.xml'
The text was updated successfully, but these errors were encountered: