My path to the SDK etc is C:\Program Files\Unity\Hub\Editor\2019.3.15f1\Editor\Data\PlaybackEngines I am using an Asus TUF Gaming FX505DT laptop with Windows 10 Home installed. I installed Unity versions 2019.2.10f.3.15f1, and deployed applications to my Oculus Quest. I'm not use if it would have done this anyway if I had included other modules, but I'm sure through the two weeks of trying different things I ttried to install the 2020 version with other modules and it didn't work. With the right paths to the SDK, NDK and JDK. I also just found that when I installed version 2020.1.0f1 with just the Android Build support selected, including Andriod SDK and NDK Tools and OpenJDK (no other modulues selected including Visual Studio) it installed correctly I found that if I copied the SDK, NDK and OpenJDK folder to my desktop from the first installation, then copied them backafter I reinstalled the module it worked. When I did this a lot of the files in the SDK, NDK folder and the JDK folder were deleted, so I lost the paths to them in external tools. Module wasn't installed, so when I went to switch platforms to Android I had to install the module again. I finally got it to work when I realised that the SDK, NDK and JDK were installed when I installed Unity through hubs with the Android Build Support selected, but the full Android I tried a lot of the online solutions that didn't work for me. The SDK, NDK and JDK wouldn't install and I couldn't get it to work with paths in Android studio. bashrc file, But it gives me the following output when I opened the terminal bash: =/usr/lib/lightdm/lightdm:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games./home/ssrp/workspace/android-sdk-linux/platform-tools: No such file or directoryīash: PATH=/usr/lib/lightdm/lightdm:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games./home/ssrp/workspace/android-sdk-linux/tools: No such file or directoryīash: JAVA_HOME=./usr/lib/jvm/java-6-openjdk: No such file or directoryīash: NDK=.I put this solution on another post as well, as I spent two weeks trying to install the Android build support with different versions of Unity so that I could develop Oculus Quest applications. The NDK and SDK folders are located as they are in the path in the. # a case would tend to support setf rather than setaf.) (Lack of such support is extremely rare, and such # We have color support assume it's compliant with Ecma-48 # should be on the output of commands, not on the prompt # off by default to not distract the user: the focus in a terminal window # uncomment for a colored prompt, if the terminal has the capability turned # set a fancy prompt (non-color, unless we know we "want" color) # set variable identifying the chroot you work in (used in the prompt below) # make less more friendly for non-text input files, see lesspipe(1) # match all files and zero or more directories and subdirectories. # If set, the pattern "**" used in a pathname expansion context will # update the values of LINES and COLUMNS. # check the window size after each command and, if necessary, # for setting history length see HISTSIZE and HISTFILESIZE in bash(1) # append to the history file, don't overwrite it # don't put duplicate lines or lines starting with space in the history. # If not running interactively, don't do anything $export NDK=./home/ssrp/workspace/android-ndk-r9 $export JAVA_HOME=./usr/lib/jvm/java-6-openjdk $export PATH=$PATH./home/ssrp/workspace/android-sdk-linux/tools $export=$PATH./home/ssrp/workspace/android-sdk-linux/platform-tools # see /usr/share/doc/bash/examples/startup-files (in the package bash-doc) bashrc file # ~/.bashrc: executed by bash(1) for non-login shells.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |