-
Notifications
You must be signed in to change notification settings - Fork 43
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
Android cross-compiling from Windows error "cargo:warning=The command line is too long" #75
Comments
@Jasper-Bekkers you were looking into this right? |
I am, patching up cc to get this to work.
…On Wed, 1 Jul 2020, 17:40 Johan Andersson, ***@***.***> wrote:
Assigned #75 <#75> to
@Jasper-Bekkers <https://github.com/Jasper-Bekkers>.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#75 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAMDOR3TBMRJ7GO573UFV3RZNKFZANCNFSM4ONRB6PQ>
.
|
Reduced to roughly |
@Jasper-Bekkers any further progress on this? |
rust-lang/cc-rs#547 solves this. |
Awesome! |
Alright, I've been looking into this issue quite a bit this week and am majorly confused. The error @repi shows above shouldn't actually error at all. The reason being, yes the command is 10k+ lines of code but Linking would actually fail on msvc -> Android as TLDR: no clue why we get this error :( |
@maxded ouch. you are able to reproduce the error locally on Windows right though? |
Yes |
Figured it out! Fix is on it's way rust-lang/cc-rs#572 :) |
Would it be possible to reduce the number of include directories when compiling |
You can try, but the way the physx code works means a lot of includes are needed. |
The latest version of |
Awesome! |
When building locally on Windows to Android I've been running into Cargo errors about the
cc
command-line being too long which fails the build.Windows has a max of 8192 characters, and got over 10k characters in some of the compile invocations, mostly due to long paths for all the include paths.
Example:
cc @Jasper-Bekkers @VZout
The text was updated successfully, but these errors were encountered: