i tried to use VCS > Import into version control > Share project on GitHub. https://snipboard.io/aTBxe9.jpg
However i got an error https://snipboard.io/6Eashw.jpg . then i used https://stackoverflow.com/a/27701083/15334005 and followed all the steps yet none of my files appear on github.
https://snipboard.io/7sSbcq.jpg
i would share any further information required. if someone provide me an updated ist of instruction to be followed since both github and android studio have changed w.r.t previous answer i promise to update the steps for newer version and changes below this line as i learn to do it for use of future people.
Will update my answer as i learn and will keep this answer updated wrt newer version and changes for future users.
Related
Can anybody recommend a working Android Studio sample app that I can use for Oculus Quest 2, preferably with good documentation? I am looking for something I can build and run to start playing with their OpenXR Mobile SDK.
I am on an Intel Macbook Pro running macOS Big Sur, and I tried with the latest stable Android Studio release (Arctic Fox).
I have tried two different samples so far:
VrSamples/VrCubeworld_Framework - from the official Oculus docs:
Android Development Software Setup
Getting Started with Oculus Native Samples: Import Gradle Project
After following all the steps, I keep hitting this error:
NDK not configured. Download it with SDK manager. Preferred NDK version is '21.0.6113669'.
I'm convinced my NDK is installed:
I believe I've tried every workaround listed in the popular Stackoverflow question, and the linked Google issue.
hello_xr - a comment on the Oculus Forum links to this helpful blog post with more detailed instructions than the official Oculus docs. Unfortunately, after following those, I hit this build error:
C/C++: /Users/dj/Code/OpenXR-SDK-Source/src/CMakeLists.txt debug|armeabi-v7a : CMake Error at /Users/dj/Code/OpenXR-SDK-Source/src/version.cmake:25 (file):
file STRINGS file
"/Users/dj/Code/OpenXR-SDK-Source/src/include/openxr/openxr.h" cannot be read.
Call Stack (most recent call first):
CMakeLists.txt:318 (include)
There doesn't appear to be an include folder under src, and there is no openxr.h in the top level include/openxr folder.
UPDATE: At Jherico's suggestion, I downloaded Oculus OpenXR Mobile SDK v1.0.13 and OpenXR-SDK-Source release-1.0.13, and followed the instructions again to exactly match the versions used in the blog post, and ultimately I did get it working!
I created https://github.com/daj/OculusHelloXR to snapshot my working Android Studio project with all its dependencies, with individual commits for each step that I followed (I had to make a couple of changes to steps in the blog post to get it working).
I wrote everything up in this blog post: https://daj.medium.com/oculus-vr-for-android-developers-a38134c759b0
The blog post instructions are likely out of date, since they're from April and the most recent version of the OpenXR SDK has it's own new build.gradle file for hello_xr that was added in 1.0.20 in October.
If you want to go by the blog post, I'd suggest that after you check out the OpenXR-SDK-Source repository, you then run git checkout release-1.0.14 since that would be the version that the blog post was written against.
Alternatively, you can just ignore the blog post and try importing the build.gradle project directly into Android Studio (basically following the "Import Gradle Project" steps you linked to, but importing hello_xr from the current version of the OpenXR-SDK-Source project instead) and try seeing it that builds.
If you're still getting NDK errors you might try explicitly setting the ANDROID_NDK_ROOT environment variable, and make sure it's visible to your build process.
I run setup file from Releases, and tried to follow official guide, but it has instructions for older versions only (Visual C++ 2010/2012/2013). I didn't find menus mentioned there. So how do I install vld on VS 2019?
Just use fork of VLD by Azure instead. It supports last versions of Visual Studio without additional configuration and fixes some bugs:
Microsoft Fork
This fork was created to address some of the issues found in the original repo https://github.com/KindDragon/vld, which has not been updated since November 24, 2017. The changes in this repo can be merged back into the original repo if it is again accepting pull requests.
If you would like to contribute to this fork, please submit a pull request. It will be looked at on a "best effort" basis as our team is available.
Copied from README.md
Congratulations, now you can use VLD, just
#include <vld.h>
I have downloaded the Android Support 23.2.0 and imported support7Demos under directory /Android/sdk/extras/android/support/samples/Support7Demos without making any changes. After importing the necessary dependencies, it builds successfully and generate an apk. I installed the apk on Smartisan T1 with API 19. The day night mode works as expected. But it does not work on Nexus 5 with API 23.
Please be noticed that the code is from the Android official Support V7 sample, I did not make any changes at all.
The same apk installed on different devices work different.
This is the link to download the apk to check it out.
You could also check out the two videos that recorded to see the difference.
Is it a bug? And if it is a bug, is there any workaround?
To those who still wonders the answer, here it is :
It's issue with AppCompatActivity.java of support library which is fixed now.
It is the official answer quoted from the bug logged in here
I am attempting to convert the Microsoft.Health C# class library that is installed as part of the HealthVault SDK, using instructions provided here. After following these instructions, I get the following error when attempting to load the project into Visual Studio 2013.
"The project is targeting frameworks hat are either not installed or
are included as part of future updates to Visual Studio. See
http://go.microsoft.com/fwlink/?LinkId=287985"
Visiting the link takes me to .NET SDKs and Downloads. Once there, I have no clue on what needs to be done.
I do realize that one will have to leverage the Portable Class Library Contrib project to fill in some missing bits, especially code related to System.Security. This, I will deal with later.
Any one run into a similar problem?
Maybe so late but for those who have the same problem.
I had the same error in a project which was working perfect before updating VS2013 and finally after 3 hours looking for the source of the error I found that the error is about TargetFrameworkProfile.
In my case I sloved it like so:
Right click in the unloaded project in your solution and click Edit.
Find the TargetFrameworkProfile tag and set it as below:
<TargetFrameworkProfile>Profile78</TargetFrameworkProfile>
At a guess, this is because you need to specify the TargetFrameworkVersion and TargetFrameworkProfile properties in the project file. Compare the .csproj you are trying to create to a newly created PCL project file, and make sure that everything that's not specific to your project matches.
I ran into the same issue and got it resolved by installing the latest Visual Studio Update
For our latest release, we want our customers to only download an upgrade patch of our applications and instead of uninstall and re-install all the process will be done by upgrader patch but I know nothing about this even after I googled it! Where to start guys? Note that our new release includes database upgrade as well as production code!
We are using .NET 4.0, Visual Studio 2010, C# and VB.NET in our software.
I might be a bit late to the party but hopefully this post helps anybody else who is looking for this answer.
You can use the 'Patch Design' method to create patches. You can find it in Installation Designer tab under Media.
For this you will need the latest build (msi/exe) and one or more previous build(s). In 'Patch Design' add a new patch configuration. From there you can specify latest version and previous version(s) of your setup file. If you are using Express version then you will need uncompressed build for both latest and previous. If you have Professional version then it can decompress it for you.
After this, just hit Build Patch and it will create a update.exe with only differences between latest and previous builds. It is quite smart in a way where it will only add the binary differences.
Good luck.