I'm trying to start the emulator with this command emulator -avd Pixel_4_API_30 but it gives me an error:
[8633370112]:ERROR:android/android-emu/android/qt/qt_setup.cpp:28:Qt library not found at ../emulator/lib64/qt/lib
Could not launch '/Users/primulax/../emulator/qemu/darwin-x86_64/qemu-system-aarch64': No such file or directory
Android Studio specs:
Build #AI-203.7717.56.2031.7935034, built on November 21, 2021
Runtime version: 11.0.10+0-b96-7249189 aarch64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
macOS 12.2
GC: G1 Young Generation, G1 Old Generation
Memory: 2048M
Cores: 8
Registry: external.system.auto.import.disabled=true
Non-Bundled Plugins: org.jetbrains.kotlin
✅ I was able to run with ~/Library/Android/sdk/emulator/emulator -avd Pixel_4_API_30 with this command
Use ~/Library/Android/sdk/emulator/emulator instead of ~/Library/Android/sdk/tools/emulator on MacOS, for Ubuntu use ~/Android/Sdk/emulator/emulator.
I just experienced the same issue on a freshly setup machine, emulator installed through SDK manager and all.
The error message says it all actually: If you go to /Users/primulax/../emulator/qemu/ on your machine, you'll notice that of course there is no darwin-x86_64 directory, but darwin_aarch64, since you are on an M1 machine. Whatever the reason is the emulator looks in the wrong directory, if you just duplicate the darwin_aarch64 folder and name your copy darwin-x86_64, it works as intended. Not ideal, but it's a workaround until this path-problem is fixed.
Edit: Please take a look at #Andrew Stromme's comment. Of course symlinking is a much more elegant solution to this problem!
If you have Android Studio installed, you can run the emulator from terminal without having started Android Studio first.
First of all, run
cd ~/Android/Sdk/tools && ./emulator -list-avds
to get a list of all the available Android virtual devices that you have installed.
Then, copy the name of the virtual device you want to use and run
cd ~/Android/Sdk/tools && ./emulator -avd YOUR_DEVICE_NAME
where you replace "YOUR_DEVICE_NAME" with the name of a virtual device that was listed in the installed virtual devices list.
This info and more that you may find useful can be found in the official documentation.
Now for the error you get it's most possibly due to a wrong file path. It seems that others have also faced this issue and a bug has been opened before here. The most common solution proposed is to launch emulator from the
/path/to/android-sdk/tools
directory in command line.
Also, before trying this or any other solution listed in this issue tracker, firstly make sure that you have installed from the SDK Manager the Android Emulator in SDK Tools.
I have eclipse installed on my windows machine, but I can't seem to use it with bash so I installed eclipse on the bash terminal by using "sudo apt-get install eclipse". It installed fine, but I can't figure out how to launch the eclipse GUI from the linux subsystem so I can use it like the windows version. I tried using Xming and exporting DISPLAY, but that didn't work. Any ideas?
from what i understood from the link below, you require to update .bashrc to direct the GUI display to a X Server process. I installed xMing to run X Server from Windows 10. i also had to install gtk components that allowed me to run sublime text GUI from within WSL.
https://medium.com/#pck/how-to-use-sublime-text-3-from-command-line-with-ubuntu-bash-terminal-in-windows-10-subsystems-for-aa2ad59d088c
hope this helps
IMHO you should not install eclipse by apt but simply get your desired eclipse product from from https://www.eclipse.org/downloads/packages , download and unzip it to your wanted location and just start eclipse.
Reasons:
I do not know any Linux distribution containing a newer eclipse bundled, so you are always having older versions being slower and having less features
You can update your eclipse installation directly inside eclipse Check for updates
You can have multiple installations at same time
If you want to get rid of a eclipse installation just remove the folder and you are done.
But of course you can also use bash directly in Windows with Eclipse.
Please look at
https://stackoverflow.com/a/62724163/2590615 or take a glimpse at You Tube Video about Bash Debugging with Bash Editor eclipse plugin on a Windows 10 machine
PS: I am the maintainer of the mentioned eclipse plugin
install4j's multiplatform installer has been working great for years. Now out of the blue we are getting an error popup dialog that The installation file is corrupted. If it is a download please try again. It has installed about 19MB of 164MB and the last file it didn't write was a small jar that has been in the build for some time now.
We get this error when running the full installer right after it is built as a test. We are also building several 'companion' applications with all the same files just different start up options and its installer run fine.
We are using install4j in batch mode:
install4j version: 5.0.8 (build 5311)
Thanks.
Are you running it on the latest Mac OS? If so then this is because of the latest Gatekeeper "feature" of Apple and you need to sign your code: http://support.apple.com/kb/HT5290
How do I get the command-line build tools installed with the current Xcode/Mac OS X v10.8 (Mountain Lion) or later?
Unlike Xcode there is no installer, it's just a bundle.
It looks like all the command line tools are in the bundle, under Contents/Developer, but none of the appropriate environment variables are set to use them.
Is there a script I can run that will set-up my environment to support building from the command line?
Xcode 5.1 and OSX 10.9. (also works with Xcode 5.1.1 + OSX 10.10)
xcode-select --install worked with version 2333, failed with version 2003. So, try xcode-select --install and if that does not work download as described below.
In early February 2014 xcode-select --install has been reporting that "Can't install the software because it is not currently available from the Software Update server". In late February 2014 the command started only displaying help. The solution is to download directly, see "Separate Download" below.
Xcode 5.0.1 and OSX 10.9
With Xcode 5.0.1 and Mavericks 10.9 the command line tool is no longer available through Xcode. Instead they must be downloaded from the Apple Developer Tools site: https://developer.apple.com/downloads/index.action. This requires signing in with a developer account.
Or via terminal (from the release docs): The Command Line Developer Tools package can be installed on demand using "xcode-select --install” and the installed tools will be automatically updated using Software Update. OS X 10.9 is required for this feature. For earlier versions, continue to use the in-app download in Xcode.
Running the command in terminal produces the following GUI:
Inside Xcode (5.0)
Xcode includes a new "Downloads" preference pane to install optional components such as command line tools, and previous iOS Simulators. To open this pane click the "Xcode" button in the top left of the screen near the Apple logo, then click "Preferences", then click "Downloads".
Xcode 5.0 screenshot:
Xcode 4.x screenshot:
Separate Download
If you do not have Xcode, they are available as a separate download from Apple:
Go to developer.apple.com/downloads/index.action, and sign in with your Apple ID (the download's free). In the pane on the left, search for "command line tools" and choose the package appropriate to your version of OS X. Requires Mac OS X 10.7.3 or later.
If you take a look into "Console" while trying to pull the Command Line Tools, you will find out that there is actually an "unofficial" link to the Mountain Lion Command Line Tools!
So just try:
http://adcdownload.apple.com/ios/ios_simulator__resigned/cltools_mountainliondp2_march12.dmg
Here is my Console log:
01/04/2012 15:41:54.258 Xcode: [MT] DVTDownloadable: Download failed. Downloadable: {
dependencies = (
);
fileSize = 141452226;
identifier = "Xcode.CLTools.10.8";
name = "Command Line Tools";
source = "http://adcdownload.apple.com/ios/ios_simulator__resigned/cltools_mountainliondp2_march12.dmg";
userInfo = {
ActivationPredicate = "$MAC_OS_X_VERSION >= '10.8.0' && $MAC_OS_X_VERSION < '10.9.0'";
InstallPrefix = "/";
InstalledIfAllSHA1SumsMatch = {
"/usr/bin/clang" = 600c35175775a6002452a88f17e00c570cd2e2d0;
};
Summary = "Before installing, note that from within Terminal you can use the XCRUN tool to launch compilers and other tools embedded within the Xcode application. Use the XCODE-SELECT tool to define which version of Xcode is active. Type \"man xcrun\" from within Terminal to find out more.\n\nDownloading this package will install copies of the core command line tools and system headers into system folders, including the LLVM compiler, linker, and build tools.";
"Xcode.SDKs" = (
);
};
version = "1.1.1";
}. Error: Error Domain=NSCocoaErrorDomain Code=3840 "The data couldn’t be read because it has been corrupted." (Encountered unknown ampersand-escape sequence at line 18) UserInfo=0x401bc8e60 {NSDebugDescription=Encountered unknown ampersand-escape sequence at line 18, kCFPropertyListOldStyleParsingError=The data couldn’t be read because it has been corrupted.}
Here are links for Command Line Tools, located at Apple Developer Server. You may need an apple developer (Paid/Premium) account to access them. You can download current (stable and beta) Xcode Tools. (It does not need device verification. Just ensure your macOS and XCode Tool/SDK version while choosing your command line tool)
Xcode 13 RC
Xcode 13 RC
- (Command Line Tool (Xcode 13 RC) - for macOS BigSur +)
Once you've latest command line tool installed in your system, set it from Xcode Menu.
(Xcode Menu Items) Xcode ▶ Preferences ▶ Location ▶ Command Line Tool ▶ Select appropriate command line tool
As of big sur..
sudo rm -rf /Library/Developer/CommandLineTools
sudo xcode-select --install
Thanks homebrew maintainers for putting this helpful messaging in brew doctor
The "unofficial" links are also available at
http://developer.apple.com/downloads/
and 403: Forbidden unless logged in with a qualifying developer account. Free accounts have access to everything except prerelease software and full OS installs. In particular, the command-line tools packages that coincide with the release of Xcode 4.4 (the "July 2012" packages) were posted on July 27, for both Lion and Mountain Lion.
Unlike log files, deep-linking Web pages, and the Xcode Preferences window, this page also links to lots of other useful downloads for free and paid developers alike, including everything else that has been unbundled from Xcode (audio tools, accessibility tools, etc.), OS X kernel debug builds, and release versions of Xcode back to 1.0.
Instead of installing the "official" build of the command line tools from Apple, you can also install Kenneth's build from here:
https://github.com/kennethreitz/osx-gcc-installer
It doesn't even require XCode if all you are after is the command line tools.
I recently had to install Xcode command line tools on Mountain Lion over SSH.
Notice: I imagine this process would work identically for any version of Xcode or OSX. Just make sure you get your paths correct.
Here's how I did it...
If you don't have a free Apple developer account, register for one
Login to https://developer.apple.com/downloads
Download the "Command Line Tools for Xcode" appropriate for your version of OSX
For me, that was "Command Line Tools (OS X Mountain Lion) for Xcode - April 2014"
Copy the dmg file to your remote
In the following command, I'm using scp to securely copy the file from my local computer to the remote named remote
$ scp ~/Downloads/command_line_tools_for_osx_mountain_lion_april_2014.dmg remote:Downloads/
ssh to your remote
$ ssh remote
mount the dmg file on the remote
Here, I'm using hdiutil to mount the image
$ hdiutil attach ~/Downloads/command_line_tools_for_osx_mountain_lion_april_2014.dmg
install the package contained in the dmg
Here, installer must be run with sudo because this package needs to be installed on the root file system
$ cd /Volumes/Command\ Line\ Tools\ \(Mountain\ Lion\)
$ sudo installer -pkg Command\ Line\ Tools\ \(Mountain\ Lion\).mpkg -target /
unmount the dmg file
$ hdiutil detach /Volumes/Command\ Line\ Tools\ \(Mountain\ Lion\)
delete the dmg file from the remote; optional
I see no purpose keeping it around, but you can if you want.
$ rm ~/Downloads/command_line_tools_for_osx_mountain_lion_april_2014.dmg
You can automate the installation of Command-Line Tools in bash. I needed to do this when I was automating the developer onboarding setup process.
xcode-select --install && sleep 1
osascript -e 'tell application "System Events"' -e 'tell process "Install Command Line Developer Tools"' -e 'keystroke return' -e 'click button "Agree" of window "License Agreement"' -e 'end tell' -e 'end tell'
Go to developer.apple.com/download/all/ (log in if you're not logged in)
Expand the "View Details" tool tip for "Command Line Tools" of the version you need
Download the .dmg file of those Command Line Tools
Once the .dmg file is downloaded, double click it and install it
If you want to use the version of tools provided in XCode itself you can use xcrun (e.g. xcrun git). From the help at the bottom of the download preference pane:
note that from within Terminal you can use the XCRUN tool to launch
compilers and other tools embedded within the Xcode application. Use
the XCODE-SELECT tool to define which version of Xcode is active.
Type "man xcrun" from within Terminal to find out more.
UPDATED: On Lion 10.7.4 the Command Line Tools are already available from withing XCode. You can get it freely from App Store.
The GCC for OSX won't compile some packages obtained from macports.
https://github.com/kennethreitz/osx-gcc-installer/downloads
By updating my Mac to the latest Mac OS (ie Big Sur), everything broke down to repetition request of installing Xcode-select.
It might seem weird, but I solved the problem by reinstalling & updating to the latest Xcode.
This is just my experience to solve the problem.
try going into Xcode > Preferences... > Downloads and clicking the button with a downward arrow in a circle next to command line tools.
xcode command line tools can be downloaded from here: https://developer.apple.com/downloads/index.action#
April 2014 version direct download link (for developers who just want to get started right away)
https://developer.apple.com/downloads/download.action?path=Developer_Tools/command_line_tools_os_x_mavericks_for_xcode__april_2014/command_line_tools_for_osx_mavericks_april_2014.dmg
How do I get the command line builds tools installed with Xcode 4.4 / Mac OS X v10.8 (Mountain Lion) or later?
For OS X 10.9, you simply install Xcode. The Command Line Tools are bundled with Xcode. From Technical Note TN2339, Building from the Command Line with Xcode FAQ:
Downloading command-line tools is not available in Xcode for OS X 10.9. How can I install them on my machine?
In OS X 10.9, the Downloads pane of Xcode Preferences does not support
downloading command-line tools. Use any of the following methods to
install command-line tools on your system:
If Xcode is installed on your machine, then there is no need to install
them. Xcode comes bundled with all your command-line tools. OS
X 10.9 includes shims or wrapper executables. These shims, installed
in /usr/bin, can map any tool included in /usr/bin to the
corresponding one inside Xcode. xcrun is one of such shims, which
allows you to find or run any tool inside Xcode from the command line.
Use it to invoke any tool within Xcode from the command line.
...
Xcode Command Line Tools can be installed as a side effect of running git --version in Terminal without Git installed. You will be prompted to install the tools as a requirement for running Git. Apple ships a binary of git with the Command Line tools. This is confirmed on the Git for Mac Download page. This seems like a valid option considering that Homebrew requires the Command Line tools to install Git as well according to another SO post. Otherwise, the previous answers are the most direct methods of install the tools.
When I try to install the ADT 16.0.1 plugin on Eclipse Indigo java developer edition release 1 or Helios normal edition release 2, I get the following error:
Cannot complete the install because one or more required items could not be found.
Software currently installed: Shared profile 1.0.0.1316138460759(SharedProfile_epp.package.java 1.0.0.1316138460759)
Missing requirement: Shared profile 1.0.0.1316138460759 (SharedProfile_epp.package.java 1.0.0.1316138460759) requires 'org.maven.ide.eclipse [1.0.100.20110804-1717]' but it could not be found
I've tried to lookup the package it's refering to on apache, JDK reference and android developer reference but no luck!
This's not my first time installing ADT, I already have it installed on Ubuntu and it works. I also had the old release (ADT 15) installed on Eclipse galileo on windows, but I re-installed windows (i'm running windows 7 ultimate by the way) and I can run the old release but it's very good developing with ICS API-s.
So, if anyone could help, it would be highly appreciated.
Lots of people have this type of problem with many different required items missing.
The last time I had this problem it was fixed by going to Window->Preferences
Then selecting Install/Update->Available Software Sites
Make sure everything listed is checked
In my installation I have:
https://dl-ssl.google.com/android/eclipse/
http://download.eclipse.org/releases/indigo
http://download.eclipse.org/eclipse/updates/3.7
You may also need to run Eclipse as an administrator
I was able to install the ADT Plugin only after
I moved the eclipse folder to a location without spaces (e.g.: c:\development\android\eclipse
I ran the Eclipse Update procedure as administrator
Also I am using the 32bit version even though I use windows7 64bit.
you just need to run as administrator
run Eclipse with compatibility mode winXP pack 2 and Run as Administrator.
You can find it by Right clicking Eclipse.exe > Properties > Compatibility Tab