Fixed
Status Update
No update yet.
Comments
vi...@google.com
Thank you for your feedback. Team may reach out for more feedback in reproducing or triaging this issue.
ag...@google.com
Arif, can you help me triage this? Do you know who is taking care of renderscript and build tools?
ar...@google.com
Looks like this is an issue with MacOS 10.15 not allowing 32bit.
$HOME/Library/Android/sdk/build-tools/28.0.3/i686-linux-android-ld is a 32bit executable.
+Dan and +Xav to see if they have any workarounds.
$HOME/Library/Android/sdk/build-tools/28.0.3/i686-linux-android-ld is a 32bit executable.
+Dan and +Xav to see if they have any workarounds.
da...@google.com
If that's the problem then no, there are no workarounds. That needs to be updated.
en...@google.com
...or we could switch Studio over to using the NDK for this rather than bundling a second unmaintained copy of the linker?
ar...@google.com
That would require people to have NDK installed, but AFAIK not everyone who uses Renderscript needs to have NDK installed currently.
In fact the user reporting
In fact the user reporting
en...@google.com
i still don't understand why Studio can't just "do the right thing" in situations like that... those little links i keep having to click every time i use Studio, to make it actually do the thing i need to do to make any progress (rather than just tell me about it) are one of my least favorite parts of Studio.
xa...@google.com
OP: does build tools 29 works? If not we should ship new build tools (29.x) with a newer version of the linker.
retriaging this to Raju.
I think these are packaged from a prebuilt managed by the renderscript team.
I do agree with Dan that we should probably look at using the NDK instead but it's a bigger change.
Elliott, not sure what link you are talking about?
retriaging this to Raju.
I think these are packaged from a prebuilt managed by the renderscript team.
I do agree with Dan that we should probably look at using the NDK instead but it's a bigger change.
Elliott, not sure what link you are talking about?
en...@google.com
xa...@google.com
cc Raju since he handles build tools releases.
da...@google.com
> I do agree with Dan that we should probably look at using the NDK instead but it's a bigger change.
That was enh :) I don't think the NDK and build-tools are currently coupled, and that would yet another dimension to the test matrix. It's probably better to keep the RS tools on whatever linker they build/test against. We're going to be replacing the linker in the NDK somewhat soon.
That was enh :) I don't think the NDK and build-tools are currently coupled, and that would yet another dimension to the test matrix. It's probably better to keep the RS tools on whatever linker they build/test against. We're going to be replacing the linker in the NDK somewhat soon.
ar...@google.com
build-tools/29.0.2 also has 32 bit linkers.
As for requiring NDK, I think we want to be mindful of requiring a 800+ MB download for a linker when previously this was not required.
As for requiring NDK, I think we want to be mindful of requiring a 800+ MB download for a linker when previously this was not required.
en...@google.com
> Elliott, not sure what link you are talking about?
the little blue hyperlinks for "update Studio" or "update Gradle" or "regenerate something" or "install the NDK". seems like you could have one of those at least for "i need a linker from the NDK to build renderscript"?
> As for requiring NDK, I think we want to be mindful of requiring a 800+ MB download for a linker when previously this was not required.
do we have numbers on how many folks use renderscript with Studio? i'd guess that you're actually hurting regular users more by shipping three mostly-unused linkers. (but i don't _really_ want you to switch to the NDK --- i'm assuming that renderscript won't work with lld, so when the NDK removes the legacy linkers there won't be anyone to fix renderscript now they're all working on NNAPI instead.)
the little blue hyperlinks for "update Studio" or "update Gradle" or "regenerate something" or "install the NDK". seems like you could have one of those at least for "i need a linker from the NDK to build renderscript"?
> As for requiring NDK, I think we want to be mindful of requiring a 800+ MB download for a linker when previously this was not required.
do we have numbers on how many folks use renderscript with Studio? i'd guess that you're actually hurting regular users more by shipping three mostly-unused linkers. (but i don't _really_ want you to switch to the NDK --- i'm assuming that renderscript won't work with lld, so when the NDK removes the legacy linkers there won't be anyone to fix renderscript now they're all working on NNAPI instead.)
sr...@google.com
RenderScript would probably work with LLD. They are only creating a simple shared object file from a single object file. It still might require work to ensure that the command line flags are correct though.
ra...@google.com
I looked up the build-tools package and it has: x86_64-linux-android-ld. Is that the right linker to be used?
en...@google.com
the mips linker in there can be removed, but the other linkers in there all need to be updated (and renderscript tested for arm/arm64/x86/x86-64).
dg...@google.com
en...@google.com
no, this is the important bit:
> A problem occurred starting process 'command '/Users/tobias/Library/Android/sdk/build-tools/28.0.3/i686-linux-android-ld''
the other bit is just a warning that mips isn't supported at all.
> A problem occurred starting process 'command '/Users/tobias/Library/Android/sdk/build-tools/28.0.3/i686-linux-android-ld''
the other bit is just a warning that mips isn't supported at all.
ka...@gmail.com
Hi Team,
I have a case where we have pre bundled native libraries both (32 and 64 bit libraries ) so in last module we have abifilters for 32 and 64 bit architecgtures
and I set gradlew to build rederscript by using these flags in build.gradle. In latest mac update we are unable to build for 32 bit.
renderscriptTargetApi 21
renderscriptSupportModeEnabled true
question : When this is enabled in gradlew can android copy pre built native libs for 32 instead of building using ndk as java will be build for 64 anyway?
Thanks
Karthik K.
I have a case where we have pre bundled native libraries both (32 and 64 bit libraries ) so in last module we have abifilters for 32 and 64 bit architecgtures
and I set gradlew to build rederscript by using these flags in build.gradle. In latest mac update we are unable to build for 32 bit.
renderscriptTargetApi 21
renderscriptSupportModeEnabled true
question : When this is enabled in gradlew can android copy pre built native libs for 32 instead of building using ndk as java will be build for 64 anyway?
Thanks
Karthik K.
zy...@gmail.com
Hi everyone!
First, thank you for all your effort. Really been enjoying Android programming :)!
I was wondering if there was an estimate as to when this issue will be fixed? It is causing issues in 3 of our major projects and we have no work around for it for now.
Thank you!
First, thank you for all your effort. Really been enjoying Android programming :)!
I was wondering if there was an estimate as to when this issue will be fixed? It is causing issues in 3 of our major projects and we have no work around for it for now.
Thank you!
to...@gmail.com
Not the most fun workaround but I ended up downgrading to macOS Mojave that obviously works fine but would be great to get an estimate :)
ja...@specialized.com
Any updates regarding this issue?
We are seeing a similar issue for one of our projects. Downgrading OS is not really a workable solution for us.
Thanks!
We are seeing a similar issue for one of our projects. Downgrading OS is not really a workable solution for us.
Thanks!
je...@google.com
We'll try to make RenderScript work with LLD. We should know this week. As to when this fix could be released, we'll check with the NDK release schedule. Stay tuned.
da...@google.com
> As to when this fix could be released, we'll check with the NDK release schedule.
This is the build-tools renderscript stuff, so it's not tied to the NDK release.
This is the build-tools renderscript stuff, so it's not tied to the NDK release.
[Deleted User] <[Deleted User]>
Is there any workaround for this at current other than building on another machine?
da...@google.com
A Linux VM is probably your best bet. It'll perform better anyway.
On Wed, Nov 6, 2019, 04:43 <buganizer-system@google.com> wrote:
On Wed, Nov 6, 2019, 04:43 <buganizer-system@google.com> wrote:
dg...@google.com
Internal version of bug: http://b/144040336 Renderscript not compiling after updating to macOS Catalina
dg...@google.com
In Library/Android/sdk/build-tools/29.0.2 I see:
$ file *ld
aarch64-linux-android-ld: Mach-O 64-bit executable x86_64
arm-linux-androideabi-ld: Mach-O executable i386
i686-linux-android-ld: Mach-O executable i386
mipsel-linux-android-ld: Mach-O executable i386
x86_64-linux-android-ld: Mach-O 64-bit executable x86_64
Why is Studio picking i686-linux-android-ld rather than x86_64-linux-android-ld?
$ file *ld
aarch64-linux-android-ld: Mach-O 64-bit executable x86_64
arm-linux-androideabi-ld: Mach-O executable i386
i686-linux-android-ld: Mach-O executable i386
mipsel-linux-android-ld: Mach-O executable i386
x86_64-linux-android-ld: Mach-O 64-bit executable x86_64
Why is Studio picking i686-linux-android-ld rather than x86_64-linux-android-ld?
dg...@google.com
Oh, these are target names (i..e., targeting 32-bit x86 versus targeting 64-bit x86).
dg...@google.com
Per discussion with srhines@ we don't currently have GNU linkers for 64-bit host (e.g., Mach-O 64-bit) but 32-bit target (e.g., i686-linux-android); and Android is now using LLD. Hence the recommendation of
ja...@specialized.com
The work around will not work for our CI tool. CircleCI seems to complain about sometime similar issue.
Skipped RenderScript support mode compilation for mips : required components not found in Build-Tools 28.0.3
Please check and update your BuildTools.
warning: Linking two modules of different data layouts: '/home/circleci/code/sdk/build-tools/28.0.3/renderscript/lib/bc/armeabi-v7a/libclcore.bc' is 'e-m:e-p:32:32-i64:64-v128:64:128-a:0:32-n32-S64' whereas '/home/circleci/code/app/build/generated/res/rs/staging/debug/raw/bc32/yuv420888.bc' is 'e-p:32:32-i64:64-v128:64:128-n32-S64'
warning: Linking two modules of different target triples: /home/circleci/code/sdk/build-tools/28.0.3/renderscript/lib/bc/armeabi-v7a/libclcore.bc' is 'armv7--linux-android' whereas '/home/circleci/code/app/build/generated/res/rs/staging/debug/raw/bc32/yuv420888.bc' is 'armv7-none-linux-gnueabi'
:app:compileStagingDebugRenderscript FAILED
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':app:compileStagingDebugRenderscript'.
> A problem occurred starting process 'command '/home/circleci/code/sdk/build-tools/28.0.3/arm-linux-androideabi-ld''
Skipped RenderScript support mode compilation for mips : required components not found in Build-Tools 28.0.3
Please check and update your BuildTools.
warning: Linking two modules of different data layouts: '/home/circleci/code/sdk/build-tools/28.0.3/renderscript/lib/bc/armeabi-v7a/libclcore.bc' is 'e-m:e-p:32:32-i64:64-v128:64:128-a:0:32-n32-S64' whereas '/home/circleci/code/app/build/generated/res/rs/staging/debug/raw/bc32/yuv420888.bc' is 'e-p:32:32-i64:64-v128:64:128-n32-S64'
warning: Linking two modules of different target triples: /home/circleci/code/sdk/build-tools/28.0.3/renderscript/lib/bc/armeabi-v7a/libclcore.bc' is 'armv7--linux-android' whereas '/home/circleci/code/app/build/generated/res/rs/staging/debug/raw/bc32/yuv420888.bc' is 'armv7-none-linux-gnueabi'
:app:compileStagingDebugRenderscript FAILED
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':app:compileStagingDebugRenderscript'.
> A problem occurred starting process 'command '/home/circleci/code/sdk/build-tools/28.0.3/arm-linux-androideabi-ld''
ra...@google.com
I am going to be out of office between 9th Dec and 1st Jan 2020. Cc'ing chapin@ who can help with Build tools package release if required in that window.
um...@gmail.com
Hello I am also facing this issue. Any update on this issue please ?
dg...@google.com
je...@google.com
We are currently testing a solution for this. There will be a fix released to both build tools and AGP soon.
dp...@gmail.com
wait and see...
kh...@gmail.com
Any updates?
js...@gmail.com
3 months later and Google has not resolve the problem. If they don't care about android dev on macOS, they should remove support for it and stop pretending it is even possible. What a waste of time.
en...@google.com
> If they don't care about android dev on macOS
are you seeing issues with anything other than just Renderscript? if so, please report them so we can look at them more urgently.
are you seeing issues with anything other than just Renderscript? if so, please report them so we can look at them more urgently.
co...@zuricate.net
We are more than happy to help you test any possible solution as this is stalling our development since we depend on Renderscript. Would rather not run Android Studio in a Linux virtual machine.
je...@google.com
Hi all, thank you for your patience and help.
We already have a solution ready and as are just trying to sync the release between AGP and build tools to get it out to you.
um...@gmail.com
Dear google please don't ruin our projects and release something asap its frustrating now
js...@gmail.com
That is why we all develop on iOS first and if and only if we have some left over spare time, we make a botched Android version.
um...@gmail.com
Any update @DearGoogle ?
an...@gmail.com
Yet again we find ourselves dancing this dance Google... I complain for a couple of comments, you ignore me for a couple of years... then I'm forced to accept my pity developer fate and find an alternative or just tell my clients "it simply can't be done" because that's the trend on Android... and they all use iOS anyways...
js...@gmail.com
We are abandoning Android platform, 5 months without being able to test our code, the developper left our project for other projects. Like you said we also have no customers using Android anyway, they only use iOS and Windows. We just killed the Android version today. Maybe we will do a HarmonyOS (Huawei OS) this summer.
[Deleted User] <[Deleted User]>
It would sure be nice to have a fix for these Catalina related problems. I spent days just narrowing down a build problem to Catalina rather than some inept thing I was doing. Then I spend more days trying to work around it. I'm not sure it's related to the renderscript things here, but I had lots of "architecture not supported" and not finding datatypes like __int32_t . I am using android-ndk-r17c. I realize it's not the latest, but it is what the client requires. Anyhow, thanks for all the hard things you work on and I hope you find something effective with these Catalina issues.
je...@google.com
The fixes have been published.
You must update your gradle plugin version to 3.6.0-rc02 or 4.0.0-beta1, and your build tools version to 29.0.3.
I'm closing this bug, but feel free to re-open it or submit a new one if you have additional problems.
mu...@gmail.com
MYPRESTIGEOUSFAMILYAPPLE FATHER MUNIYANMANMILITARY MOTHER SUNDHARMMAALU ELDERBROTHER SIVAKUMARR ALIAS GURUMUDHALVAN MSC MATHEMATICENAR
mu...@gmail.com
MYPRESTIGEOUSFAMILYAPPLE FATHER MUNIYANMANMILITARY MOTHER SUNDHARMMAALU ELDERBROTHER SIVAKUMARR ALIAS GURUMUDHALVAN MSC MATHEMATICENAR
wa...@gmail.com
an...@google.com
The following changes were cherrypicked through Coastguard (https://android-build.googleplex.com/coastguard/ )
Release Track: (https://android-build.googleplex.com/coastguard/dashboard/5665532955918336/#/history/all )
Created: 2020-03-05 06:40:41.389592+00:00
Changes: ag/10486776, ag/10486797, ag/10448494, ag/10447464
Release Track: (
Created: 2020-03-05 06:40:41.389592+00:00
Changes: ag/10486776, ag/10486797, ag/10448494, ag/10447464
an...@google.com
to...@gmail.com
This fixes build on Catalina, but with the newes buildTools (29.0.3) I am getting this crash when trying to initialize renderscript on my Samsung Galaxy S5 Neo (Android 6):
03-25 07:29:20.025 18646-18760/? E/AndroidRuntime: FATAL EXCEPTION: DefaultDispatcher-worker-1
Process: com.airapp.android, PID: 18646
androidx.renderscript.RSRuntimeException: Loading of ScriptC script failed.
at androidx.renderscript.ScriptC.<init>(ScriptC.java:83)
at com.airapp.ScriptC_rotator.<init>(ScriptC_rotator.java:34)
at com.airapp.utils.RenderScriptUtils$initialize$1.invokeSuspend(RenderScriptUtils.kt:27)
at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
It works on other devices
03-25 07:29:20.025 18646-18760/? E/AndroidRuntime: FATAL EXCEPTION: DefaultDispatcher-worker-1
Process: com.airapp.android, PID: 18646
androidx.renderscript.RSRuntimeException: Loading of ScriptC script failed.
at androidx.renderscript.ScriptC.<init>(ScriptC.java:83)
at com.airapp.ScriptC_rotator.<init>(ScriptC_rotator.java:34)
at com.airapp.utils.RenderScriptUtils$initialize$1.invokeSuspend(RenderScriptUtils.kt:27)
at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
It works on other devices
zy...@gmail.com
"This fixes build on Catalina, but with the newes buildTools (29.0.3) I am getting this crash when trying to initialize renderscript on my Samsung Galaxy S5 Neo (Android 6):"
I had the same issue. I think I managed to fix it (steps to follow), but then still get that error for the Xiomi Redmi Go (which is SUPER weird cause its Android 8.1).
This is what I had to do:
1. Update your gradle to have
renderscriptTargetApi 22. <<< Was needed to be this high to have 64bit support (i think?)
renderscriptSupportModeEnabled false. << Was needed to fix the Android 6 issue, but it scares me a bit :P
2. Where you use it, change the imports to NOT be AndroidX, example:
import android.renderscript.Allocation;
import android.renderscript.Element;
import android.renderscript.RenderScript;
import android.renderscript.ScriptIntrinsicBlur;
From:https://stackoverflow.com/questions/52781821/renderscript-broken-with-androidx (kinda)
Sorry, I hope its allowed to post some solutions on this ticket? Not sure what the rules are for IssueTracker :(
Also, Please if there is a solution to get it to work on Xiomi Redmi Go as well, I would really appreciate the help! (OR if the above solution actually doesnt work, and coincidently my Android6 users just havent used the app since I updates - also let me know, cause them we both have a lot to panic about).
I had the same issue. I think I managed to fix it (steps to follow), but then still get that error for the Xiomi Redmi Go (which is SUPER weird cause its Android 8.1).
This is what I had to do:
1. Update your gradle to have
renderscriptTargetApi 22. <<< Was needed to be this high to have 64bit support (i think?)
renderscriptSupportModeEnabled false. << Was needed to fix the Android 6 issue, but it scares me a bit :P
2. Where you use it, change the imports to NOT be AndroidX, example:
import android.renderscript.Allocation;
import android.renderscript.Element;
import android.renderscript.RenderScript;
import android.renderscript.ScriptIntrinsicBlur;
From:
Sorry, I hope its allowed to post some solutions on this ticket? Not sure what the rules are for IssueTracker :(
Also, Please if there is a solution to get it to work on Xiomi Redmi Go as well, I would really appreciate the help! (OR if the above solution actually doesnt work, and coincidently my Android6 users just havent used the app since I updates - also let me know, cause them we both have a lot to panic about).
mi...@google.com
re
Could you try with build-tools 3.0.0rc1?
Could you try with build-tools 3.0.0rc1?
zy...@gmail.com
Sorry for butting in (again), but I'm pretty desperate for this to work (cause Renderscript rocks the party - and cause it forms a pretty important part of my work project). I tested with the latest Build Tools version, and it still crashed on Android6 - tested using both AndroidX version of Renderscript and NOT. It did not work - I really hope I did it correctly, and I could only test on a Virtual Device. I'll try again today for in case I messed up the first time. Will try update ASAP.
zy...@gmail.com
Ok tested again with 30.0.0rc, could not get it to work on Android6
Crashed using AndroidX, crashed using android.support.v8.renderscript.RenderScript (so no android x in the whole project) and crashed using android.renderscript.RenderScript with the rest of the project on AndroidX.
E/RenderScript: Couldn't load libRSSupportIO.so
Crashed using AndroidX, crashed using android.support.v8.renderscript.RenderScript (so no android x in the whole project) and crashed using android.renderscript.RenderScript with the rest of the project on AndroidX.
E/RenderScript: Couldn't load libRSSupportIO.so
xa...@google.com
mi...@google.com
Re
mi...@google.com
Actually, I saw that you are on
an...@google.com
he...@gmail.com
I am using Android studio 4.0, and this issue got fixed for me by just updating the gradle version.
In build.gradle of app:
- ext.gradle_version = '3.5.3'
+ ext.gradle_version = '4.0.0'
And in gradle/wrapper/gradle-wrapper.properties:
-distributionUrl=https\://services.gradle.org/distributions/gradle-5.6.4-all.zip
+distributionUrl=https\://services.gradle.org/distributions/gradle-6.1.1-all.zip
In build.gradle of app:
- ext.gradle_version = '3.5.3'
+ ext.gradle_version = '4.0.0'
And in gradle/wrapper/gradle-wrapper.properties:
-distributionUrl=https\://
+distributionUrl=https\://
bu...@gmail.com
Hi
[Deleted User] <[Deleted User]>
I updates my macOS to Catalina and suddenly RenderScript is not compiling.
Its complaining that some required components can not be found in Build-Tools 28.0.3.
Here is the full error print out:
The error Im getting is:
A problem occurred starting process 'command '/Users/tobias/Library/Android/sdk/build-tools/28.0.3/i686-linux-android-ld''
Skipped RenderScript support mode compilation for mips : required components not found in Build-Tools 28.0.3 Please check and update your BuildTools. warning: Linking two modules of different data layouts: '/Users/tobias/Library/Android/sdk/build-tools/28.0.3/renderscript/lib/bc/armeabi-v7a/libclcore.bc' is 'e-m:e-p:32:32-i64:64-v128:64:128-a:0:32-n32-S64' whereas '/Users/tobias/Repositories/app-android/app/build/generated/res/rs/minSdk19Dev/debug/raw/bc32/brightnesscontrastfilter.bc' is 'e-p:32:32-i64:64-v128:64:128-n32-S64'
warning: Linking two modules of different target triples: /Users/tobias/Library/Android/sdk/build-tools/28.0.3/renderscript/lib/bc/armeabi-v7a/libclcore.bc' is 'armv7--linux-android' whereas '/Users/tobias/Repositories/app-android/app/build/generated/res/rs/minSdk19Dev/debug/raw/bc32/brightnesscontrastfilter.bc' is 'armv7-none-linux-gnueabi'
warning: Linking two modules of different data layouts: '/Users/tobias/Library/Android/sdk/build-tools/28.0.3/renderscript/lib/bc/x86/libclcore.bc' is 'e-m:e-p:32:32-i64:64-v128:64:128-a:0:32-n32-S64' whereas '/Users/tobias/Repositories/app-android/app/build/generated/res/rs/minSdk19Dev/debug/raw/bc32/brightnesscontrastfilter.bc' is 'e-p:32:32-i64:64-v128:64:128-n32-S64'
warning: Linking two modules of different target triples: /Users/tobias/Library/Android/sdk/build-tools/28.0.3/renderscript/lib/bc/x86/libclcore.bc' is 'armv7--linux-android' whereas '/Users/tobias/Repositories/app-android/app/build/generated/res/rs/minSdk19Dev/debug/raw/bc32/brightnesscontrastfilter.bc' is 'armv7-none-linux-gnueabi'
Task :translation:compileDebugJavaWithJavac Note: /Users/tobias/Repositories/app-android/translation/src/main/java/com/tattoodo/translation/TranslationResources.java uses or overrides a deprecated API. Note: Recompile with -Xlint:deprecation for details. Note: /Users/tobias/Repositories/app-android/translation/src/main/java/com/tattoodo/translation/TranslationInterceptor.java uses unchecked or unsafe operations. Note: Recompile with -Xlint:unchecked for details.
Task :data:generateDebugRFile
Task :commons-lang:compileJava Note: /Users/tobias/Repositories/app-android/commons-lang/src/main/java/tat/org/apache/commons/lang3/ArrayUtils.java uses unchecked or unsafe operations. Note: Recompile with -Xlint:unchecked for details.
FAILURE: Build failed with an exception.
- What went wrong: Execution failed for task ':app:compileMinSdk19DevDebugRenderscript'.
A problem occurred starting process 'command '/Users/tobias/Library/Android/sdk/build-tools/28.0.3/i686-linux-android-ld''
-
Try: Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
BUILD FAILED in 5s
sr...@google.com
required components not found in Build-Tools 28.0.3 Please check and update your BuildTools.
I think you should update your BuildTools first, since 28.0.3 may not have all of the necessary fixes to support Catalina.
dg...@google.com
ta...@gmail.com
required components not found in Build-Tools 28.0.3 Please check and update your BuildTools.
I think you should update your BuildTools first, since 28.0.3 may not have all of the necessary fixes to support Catalina.
ta...@gmail.com
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
BUILD FAILED in 5s
is...@gmail.com
Eo
ba...@gmail.com
All security restricted off
sh...@gmail.com Restricted
Restricted
Comment has been deleted.
ma...@gmail.com
Eu não entendo a razão,dessas mudanças de letras acontecerem já que sou tão criterioso.
[Deleted User] <[Deleted User]>
Comment has been deleted.
aa...@gmail.com
I get the new tools
sh...@gmail.com
sh...@gmail.com
fa...@hotmail.com
<intent-filter ... > <action android:name="android.intent.action.EDIT" /> <action android:name="android.intent.action.INSERT" /> <action android:name="android.intent.action.DELETE" /> ... </intent-filter>
an...@gmail.com
pa...@gmail.com
くえ
Description
Its complaining that some required components can not be found in Build-Tools 28.0.3.
Here is the full error print out:
The error Im getting is:
> A problem occurred starting process 'command '/Users/tobias/Library/Android/sdk/build-tools/28.0.3/i686-linux-android-ld''
Skipped RenderScript support mode compilation for mips : required components not found in Build-Tools 28.0.3
Please check and update your BuildTools.
warning: Linking two modules of different data layouts: '/Users/tobias/Library/Android/sdk/build-tools/28.0.3/renderscript/lib/bc/armeabi-v7a/libclcore.bc' is 'e-m:e-p:32:32-i64:64-v128:64:128-a:0:32-n32-S64' whereas '/Users/tobias/Repositories/app-android/app/build/generated/res/rs/minSdk19Dev/debug/raw/bc32/brightnesscontrastfilter.bc' is 'e-p:32:32-i64:64-v128:64:128-n32-S64'
warning: Linking two modules of different target triples: /Users/tobias/Library/Android/sdk/build-tools/28.0.3/renderscript/lib/bc/armeabi-v7a/libclcore.bc' is 'armv7--linux-android' whereas '/Users/tobias/Repositories/app-android/app/build/generated/res/rs/minSdk19Dev/debug/raw/bc32/brightnesscontrastfilter.bc' is 'armv7-none-linux-gnueabi'
warning: Linking two modules of different data layouts: '/Users/tobias/Library/Android/sdk/build-tools/28.0.3/renderscript/lib/bc/x86/libclcore.bc' is 'e-m:e-p:32:32-i64:64-v128:64:128-a:0:32-n32-S64' whereas '/Users/tobias/Repositories/app-android/app/build/generated/res/rs/minSdk19Dev/debug/raw/bc32/brightnesscontrastfilter.bc' is 'e-p:32:32-i64:64-v128:64:128-n32-S64'
warning: Linking two modules of different target triples: /Users/tobias/Library/Android/sdk/build-tools/28.0.3/renderscript/lib/bc/x86/libclcore.bc' is 'armv7--linux-android' whereas '/Users/tobias/Repositories/app-android/app/build/generated/res/rs/minSdk19Dev/debug/raw/bc32/brightnesscontrastfilter.bc' is 'armv7-none-linux-gnueabi'
> Task :translation:compileDebugJavaWithJavac
Note: /Users/tobias/Repositories/app-android/translation/src/main/java/com/tattoodo/translation/TranslationResources.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: /Users/tobias/Repositories/app-android/translation/src/main/java/com/tattoodo/translation/TranslationInterceptor.java uses unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
> Task :data:generateDebugRFile
> Task :commons-lang:compileJava
Note: /Users/tobias/Repositories/app-android/commons-lang/src/main/java/tat/org/apache/commons/lang3/ArrayUtils.java uses unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':app:compileMinSdk19DevDebugRenderscript'.
> A problem occurred starting process 'command '/Users/tobias/Library/Android/sdk/build-tools/28.0.3/i686-linux-android-ld''
* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
* Get more help at
BUILD FAILED in 5s