For some really warped idea of "barrier to entry"...
-
-
Replying to @RichFelker @Michcioperz
So what barrier to entry is there to downloading https://dl.google.com/android/repository/sdk-tools-linux-3859397.zip … from https://developer.android.com/studio/index.html … and using sdkmanager to update / install whatever you need?
3 replies 0 retweets 0 likes -
Replying to @CopperheadOS @Michcioperz
That's a start and probably ok for lots of users (but buried and hard to find and not documented). They don't even have a link to the source anywhere I can find though.
1 reply 0 retweets 0 likes -
Looks like big distros (e.g. Debian) might have it packaged tho, in which case you get most of the benefits of source (trusted reproducible build, compat with whatever arch you're running not just x86_64, ...).
1 reply 0 retweets 0 likes -
Replying to @RichFelker @Michcioperz
Debian has packages but it's a bad idea to use those. It's important to use the up-to-date tools and it really doesn't need to be installed system-wide. Can also decide to install the IDE later and it knows how to use an existing minimal SDK directory for the tools.
1 reply 0 retweets 0 likes -
Replying to @CopperheadOS @Michcioperz
Well where do you get the sources to build the SDK? This is all so awful and undocumented.
1 reply 0 retweets 1 like -
Replying to @RichFelker @Michcioperz
Not sure why you're talking about building it now. A hello world tutorial doesn't really start with building glibc, binutils and GCC.
2 replies 0 retweets 0 likes -
If you really want to use Debian packages, you can use them, but then you're deciding to do things in a weird way where you're using frozen Debian versions of the packages installed system-wide. If you were writing Python code, would you use their versions of libraries?
1 reply 0 retweets 0 likes -
Replying to @CopperheadOS @Michcioperz
I'd get the versions of the libraries I wanted but install all the *tools* from packages.
1 reply 0 retweets 1 like -
If Android can't get that distinction right it's more brokenness...
2 replies 0 retweets 0 likes
It's the difference between host utils (need to be built for your host OS, arch, library ecosystem, ...) and target libs (independent of your development host, can just be binaries distributed by vendor).
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.