-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hard or impossible to compile under Windows with Buck? #117
Comments
hmmm...i've definitely been able to compile Plovr on windows w/ buck, but let me double-check tonight and get back to you |
hmm...I was not able to reproduce any of the problems you are having. Can you give more details? In particular,
|
Re-reading this exception, the error seems to be only related to Buck, so probably Android SDK as nothing to do with it.
Thanks! |
Ok I went a bit further and found this ticket on buck repo. I tried the environment variable NO_BUCKD=1 and was able to reach an assertionError:
Can't invest more time then this for today. Hope this help! |
are you sure you're following the right instructions? it sounds like you're following the "Buck for Windows building Android" instructions rather than the "Buck for Windows building Java" instructions. The top of the page should look like this: maybe try zeroing out the ANDROID_HOME/ANDROID_NDK env variables and trying again? |
(also i built a fresh Buck from head yesterday without problems...it sounds like your issues are more Buck-related and so maybe posting an issue in their repo would get you better advice than I can give...) |
Argg, it made a difference for sure but now I'm missing a zip cmd in my path, I might try to install the new Bash Sheel for windows 10 to see if I can mix up the zip command. `C:_repository\plovr>buck build plovr C:_repository\plovr\buck-out\gen\closure\closure-compiler\externs_zip__srcs>cd externs && zip -r C:_repository\plovr\buck-out\gen\closure\closure-compiler\externs_zip\externs.zip * 'zip' is not recognized as an internal or external command, BUILT 59/71 JOBS 0.2s //closure/closure-compiler:support_srcs#class-abi Error scrubbing non-deterministic metadata from C:_repository\plovr\buck-out\gen\closure\closure-templates\javacc\parser.src.zip BUILD FAILED: //closure/closure-compiler:externs_zip failed with exit code 1: [-] BUILDING...FINISHED 3.0s [100%]` The NO_BUCKD=1 environment variable seem to be mandatory in my case. Thanks for pointing the obvious out =). But still it feel like Buck is quite a weird beast, if I install Cordova to do Android app I will always have to remove-add my ANDROID_SDK environment variable when using Buck, doesn't sound right at all. |
yay! the let me poke around at the android sdk thing as well, it's kind of weird that it's loading the android sdk when it's not building android. |
Ok, I'm still progressing! choco install zip helped now I get the following when I build:
As you can see the JAVA_HOME does point to a JDK so I'm not sure how the closure-stylesheet build step try to get javac. Thanks |
And the java bin directory is in my Path, so java and javac do exec in cmd.exe On another attempt I get the same error elsewhere:
|
hmmm...do you have |
Finally got it to work! I had to change the following: remove a java.exe javaw.exe javaws.exe from my C:/WINDOWS/system32/ folder that was probably putted there by the JRE installation and was messing up the ToolProvider.getSystemJavaCompiler(); used by Buck. Thanks @nicks |
i added some notes to the README about |
After trying to build plovr under Windows (following the multiple steps to install Buck under windows) and realizing its not possible to build plovr due to Buck using Android SDK using python select.select()( ( select.select does not work under windows “preexec_fn is not supported on Windows”), I came to the conclusion it was quite a waste of time to begin with. Eventually I realized I could get plovr 6.0.0 from the npm repository by creating a blank project running "npm init" then "npm install plovr".
Could it be mentioned in the README.md that the release page is not up to date and to use the npm build instead. Also mentionning the "npm init" command would help people to save an extra 1 minute.
Thanks!
The text was updated successfully, but these errors were encountered: