I need to install python 3.9 on an embedded device so I used USB drive to not consume much storage space on the board. Yet, whenever I start installing usingmake install
I get this error :
This is the content of the installation Folder after starting the installation.
How can I change the permessions so I won't have that error again?
Related
I'm having trouble installing the Version 6 of the "CP210x Macintosh OS VCP Driver v6" on my mac OS Mojave.
The error is "unexpected reply from installKextFromBundle kOSKextReturnNotLoadable (-603946989) at -[AppDelegate takeInstallStep]_block_invoke_10:1290"
I have disabled the SIP on the mac, and trying to install this driver so that I can use the ESPxx family microcontrollers using the Arduino IDE.
I must have tried multiple times trying to install/ uninstall and have been unsuccessful so far.
The MacOS version is :
The installer is :
The USB interface is :
The only driver that is installed is :
$ ls -l /dev/cu*
crw-rw-rw- 1 root wheel 18, 1 Dec 8 18:54 /dev/cu.Bluetooth-Incoming-Port
Would appreciate if there is some one who can tell how to remove / clean up and install this driver clean.
Have run the ./uninstaller.sh multiple times, rebooted it and such.
Thanks
I received the same errors but I've successfully installed. I used Homebrew to brew install --cask silicon-labs-vcp-driver and the cask requires manually running the installer. I had Fast User Switching active and was logged-in with another admin user at the time. I found, after several failed install attempts on the first admin user's account, that the System Preferences authorisation pane was also displayed on the second admin user's account. I authorised and logged-out of the second user's account, then attempted to install from the .dmg I'd downloaded directly from https://www.silabs.com/developers/usb-to-uart-bridge-vcp-drivers. That finally succeeded.
My setup
macOS 10.15.7
The recent macOS can access iOS app documents on a physically connected device directly from Finder. But this process seems to need human intervention.
I wonder if I could retrieve my iOS app's file from Finder programmatically using AppleScript or JAX. So far I haven't found a way
Thanks!
Solved it myself.
The solution is not exactly as my title but it does the job: I can now access app documents from macOS programmatically without modifying my app code.
Short answer
I can use ifuse as part of libimobiledevice.
Details
Here are the steps taken.
Install macFUSE , which
allows you to extend macOS's native file handling capabilities via
third-party file systems.
mine is 4.0.5.
Install ifuse and ideviceinstaller from Homebrew.
brew install ifuse
mine is 1.1.4.
brew install ideviceinstaller
mine is 1.1.1.
Find your app's App ID using ideviceinstaller.
ideviceinstaller -l | grep "my_keyword"
This gives your app's ID and name. Assume tat the id was com.my.app
Mount the Documents folder, e.g., onto my desktop.
mkdir -p "~/Desktop/myappdoc"
ifuse --documents com.my.app "~/Desktop/myappdoc"
Now my app folder is mounted at the specified location.
To unmount so that next time around my script can still mount the drive at the same location,
umount "~/Desktop/myappfoc"
2 week old Ubuntu 18.04 install.
As a requirement of running a android device emulator for Android studio, I had to install KVM, so I installed it (the exact package name was kvm, it had some dependencies), and now my computer won't boot. It just sits there with a purple screen.
No keyboard or mouse input has any effect (including REISUB).
I have googled and nothing relevant comes up (it's all about booting VMs, understandably).
I have no idea what to do, especially since I cannot interact directly with my OS.
I still have my boot stick (that I used to install 18.04), and I can boot off that.
Turns out that installing linux-kvm actually doesn't install a VM program, it just installs another kernal that's obsolete, puts it at the top of the grub list, and that's how it breaks your computer.
I fixed it by using boot-repair (https://help.ubuntu.com/community/Boot-Repair).
Possible?
I think to do this I need to upgrade the AIR runtime on the Fire to 3, but the version in the app store won't install. I can't create an AIR apk that is both captive runtime and debug that I know of, so the debug version of the app has to run on the AIR runtime installed. Since the Fire comes with 2.7, 3.x apps won't run in debug mode.
Has anyone managed to get AIR 3 running on a Fire without using captive runtime?
To update AIR on your KF you have to get root privileges. Also keep in mind that android build on KF doesn't have any copy command (it cut off). So the best way I found is to flash your KF with modified (pre-rooted) stock version and then install new air.
Get pre-rooted stock version (I took it here). IMPORTANT: it installs via TWRP, google how to install TWRP on KF.
Put downloaded .zip and air_runtime.apk (latest AIR version) in the root of KF.
Reboot in Recovery mode (TWRP should load)
Flash this version.
On your PC open cmd and run "adb shell" (make sure you see your device in list when run "adb devices" otherwise check drivers).
Run "su" (if you downloaded secure version).
In shell go to sdcard ("ls" to get list of files/folders and "cd folder_name" to get into) and run "install air_runtime.apk /system/app/air_runtime.apk" (I think you can just run "install /sdcard/folder_with_air/air_runtime.apk /system/app/air_runtime.apk").
(7a. If it tells you that can't install because of file already exist, run the following two commands: "mount -o remount rw /system" (mount 'system' with read/write rights) and "mv /system/app/air_runtime.apk /system/app/air_runtime.bak" (rename air_runtime.apk into air_runtime.bak). Then repeat step 7.)
In KF just run (install) air_runtime.apk (use any file explorer, e.g. download ES File Explorer from Amazon).
Check AIR version in Applications.
That's all. Looks a bit complex, but in real it takes about 4-5 mins for me to update AIR (BUT I have TWRP already installed).
Hope it helps.
UPD. After your Kindle updates itself (version 6.3.1 currently the latest) you'll lose you SU privileges. AIR also will be rolled back to 2.7. You can prevent KF auto-updates (search on xda how to do it) or flash actual pre-rooted version (it gives you several months without problems).
I am trying to run up an app in release mode on my Nokia N8. When it builds the phones asks me if i want to install it. i press yes and install it to the mass memory. This happens with out a hitch. Then it asks me to install Qjson.sis i choose the same mass memory drive and then it starts to install. This is when i get a message that reads "Update Error"
this happens when i install it to both the mass memory and the system memory. Any suggestions? im running win7 with the latest qt creator. The N8 is running PR1.0 not the newer PR1.1
The most likely answer is that the QJSON executable (.dll) is already installed on the device, but under a different package and/or UID.
Best way to get around this is to re-build QJSON with a different UID, and ensure the new UID is appended to the executable name (e.g. qjson_0x20030000.dll). In this way you can avoid update errors.