You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem:
I'm checking the docs for the current release (v5.0) on http://samsungxr.com/getting_started/ and it seems like it's not working because how the v5.0 demo repo and the starter template is built have drastically changed.
Example: 4.x have sdk uploaded in a maven repo, meanwhile 5.0 have instruction to download the release5.0.zip archive which is the compiled sdk-libs.
Following the instruction as is doesn't work for me (maybe I'm dumb) and A.Studio keep bugging about missing aar until I read the branch README and I found out I missed the 2nd step that is download and put the compiled aar in it's place.
Solution:
If you come from the sxrsdk-demos and have read the README it's possible you can have it up and running, but tbh, a project should have its dependencies managed like the previous 4.x version.
If this change is unintentional then we should get the sdk uploaded and revert to the old way, otherwise I want to understand why we're going with this direction.
The text was updated successfully, but these errors were encountered:
The binaries will be uploaded to maven and the dependencies will be managed the same way. We need to do some set up first though before we can upload. We are working on it.
Problem:
I'm checking the docs for the current release (
v5.0
) on http://samsungxr.com/getting_started/ and it seems like it's not working because how thev5.0
demo repo and the starter template is built have drastically changed.Example:
4.x
have sdk uploaded in a maven repo, meanwhile5.0
have instruction to download therelease5.0.zip
archive which is the compiledsdk-libs
.Following the instruction as is doesn't work for me (maybe I'm dumb) and A.Studio keep bugging about missing
aar
until I read the branch README and I found out I missed the 2nd step that is download and put the compiledaar
in it's place.Solution:
If you come from the
sxrsdk-demos
and have read the README it's possible you can have it up and running, but tbh, a project should have its dependencies managed like the previous4.x
version.If this change is unintentional then we should get the sdk uploaded and revert to the old way, otherwise I want to understand why we're going with this direction.
The text was updated successfully, but these errors were encountered: