Status Update
Comments
di...@google.com <di...@google.com>
di...@google.com <di...@google.com> #2
I've made some progress in setting up some testing for this. I'm creating a new module in Studio that will contain tests meant to be used for integration testing with SNAPSHOTS. The problem that I had so far, is that androidx-studio-integration uses a version of external/protobuf that makes bazel fail. For my tests, I've manually changed the manifest to use the version from studio-master-dev but I assume that the version there was required by the androidx side of things.
Aurimas, since you setup the manifest, is that something we could update so we can use bazel to build Studio in that branch?
au...@google.com <au...@google.com> #3
We have a project that uses external/protobuf and builds it from source. As far as I know manifest files do not allow two branches of the same project. I assume if we switch over to the studio version, we'll likely fail the builds for androidx.
What version of protobuf does studio have?
di...@google.com <di...@google.com> #4
Studio uses an older 3.7.0. Androidx uses 3.9.0.
The main problem that I can see so far is that when bazel tries to build it, it does not find a bunch of dependencies like @zlib//:zlib
. That seems to be the recommended way of doing it but, in the Studio version we have //external:zlib
and that seems to trip the build.
au...@google.com <au...@google.com> #5
Given that we don't use bazel build files for it, could we make a modification so that studio also works with androidx copy? or can we maybe upgrade studio?
Description
We currently do not test tip of tree androidx-master-dev compose with latest of studio, which means we get breakages (e.g. b/160271417 ) where studio is not even able to open compose classes correctly. To prevent this, we should set up integration testing.