~/.local/share/applications/sktop):įind this line: Exec="/home/username/tools/android/android-studio/bin/studio.sh" %fĬhange it to: Exec=env LIB_ROOT=/libraries_home "/home/username/tools/android/android-studio/bin/studio.sh" %f This makes sense because bashrc is for Bash not X.Īssuming you are using GNOME or Unity, to launch Android Studio with those environment variables being specified, just modify the. The reason you did not have those variables is the X-window environment you were using did not read $HOME/.bashrc which contained those variables.
variables being specified instead of from X-window dash board. You can prove it by launching Android Studio from the shell in which those env. Therefore I guess that AS is somehow not be able to access the environment variables set with my ~/.bashrcĭoes somebody of you maybe know a way how I can make AS aware of my environment?Īndroid Studio does read the environment variables.
> Configuration with name 'default' not found. If I unset the environment variable, the build on console fails with the same msg: * What went wrong:Ī problem occurred configuring project ':app'. But AS stops working with the following error msg: Gradle 'app' project refresh failed:Ĭonfiguration with name 'default' not found. If I build with the graddle wrapper from the console, it still works. Project(':libA').projectDir = new File("$_ROOT", '/libraries/libA') The adle for the example above would look like this: include ':app'
This works just fine within the console as well as with Android Studio.īut if I try to use an environment variable it stops working with Android Studio. In my adle file I am able to set the absolute path to the library project utilizing the projectDir attribute. As illustration you can imagine something like this: /projects_home/projects/app_root I do have a multi-module project with a library project in a different root path.
0 kommentar(er)
