I am using meteor 1.6, meteor command works perfect and run app locally within few seconds, but when I try to build meteor app for android, it takes more than 30 minutes. I found this issue thread but didn't found any solution.
I am running on:
Device: Mac Book Pro
OS: Mac OS Sierra
Processor: Intel Core i5 2.5GHz
Memory: 8GB 1333 MHz DDR3
Any solutions?
Related
I am new in these waters. After installing aarch64 arch on several arm boards. Decided to try android x86 and then android arm.
However in documentations it says it supports nvidia through nouvaeu driver I have rtx 3060 and NV170 is not supported in nouvaeu I get it. However it should support RX 6500 XT with or without vulkan supports. That I dont get. When I boot with virtual VGA as primary and rx 6500 XT as secondary I see AMD GPU in listed in lspci output however cant make modprobe to load gpu drivers. What am I missing ? Both happens in blissOS'es and Android_X86's latest versions.
Did you make them work, should quadruple check everything ? (vga rom, binary drivers etc)
We have a Blazor application, which we compile with AOT. The output dotnet.wasm is approximately 300 MB. And when we run the app, it uses 3GB of RAM in the Browser. And as a result, the app works slow, significantly slower compared to the Interpreter mode.
Is there a way to reduce the size of dotnet.wasm and the memory consumption?
Are there any tools to analyze it?
.NET SDK (reflecting any global.json):
Version: 6.0.100-rc.1.21463.6
Commit: e627d556a1
Runtime Environment:
OS Name: Windows
OS Version: 10.0.19043
OS Platform: Windows
RID: win10-x64
Base Path: C:\Program Files\dotnet\sdk\6.0.100-rc.1.21463.6\
Host (useful for support):
Version: 6.0.0-rc.1.21451.13
Commit: d7619cd
There is an issue for .NET 6 Preview 3,4,7, RC1
Maybe we attached too many 3rd party libraries. Is there a way to understand which libraries cause the issue?
Now I installed the AMD APP SDK 3.0 and try to check if it is installed successfully.When I use cmd and clinfo command, it displays information but with an error terminated finally.It makes me confused. The picture as follows.
The clinfo.exe error
I don't know how to solve with it. Before I run the command clinfo, I can use CodeXL Teapot sample and debug and analysis it. After I run the clinfo command, CodeXL Teapot sample also crashed. When I unistall AMD APP SDK 3.0, the clinfo command has no error and CodeXL is also recovered.
My system is windows 10 X64, GPU is AMD FirePro W7100,AMD APP SDK is X64.
Who can give me some advice?
I have spent dozens of time looking for the solution. I gave up.
I use Qt 5.3 for development and I build cross platform solution.
My MacbBook Pro runs Mac OS X 10.9.3 Mavericks.
My project successfully runs in ios-simulator and desktop builds.
But I couldn't deploy it to neither AVD nor real Android Device.
Here is the logs:
Building the android package failed!
-- For more information, run this command with --verbose.
Generating Android Package
Input file: /Users/xxx/build-xxx-Android_for_armeabi_v7a-Debug/android-libxxx.so-deployment-settings.json
Output directory: /Users/xxx/build-xxx-Android_for_armeabi_v7a-Debug/android-build
Application binary: /Users/xxx/build-xxx-Android_for_armeabi_v7a-Debug/libxxx.so
Android build platform: android-19
Install to device: emulator-5554
19:43:56: The process "/Applications/Qt/5.2.1/android_armv7/bin/androiddeployqt" exited with code 14.
Error while building/deploying project xxx (kit: Android for armeabi-v7a (GCC 4.8, Qt 5.2.1))
When executing step 'Deploy to Android device'
19:43:56: Elapsed time: 02:13.
Do you have any ideas?
Solved.
The issue was:
I set incorrect path to ant executable.
Qt was not able to build android app and for sure deploy it.
Now I am able to run app on the device, but still can't run app with emulator.
Good luck.
I get the error CL_DEVICE_NOT_AVAILABLE when running this sample code. However, unlike in that question, my CPU, the Intel Core 2 Duo E8500 CPU, appears to be supported. I've made sure to link against the Intel version of the OpenCL libraries, since I also have the Nvidia libraries installed. Why is this error occurring?
The Intel OpenCL SDK 2013 required SSE 4.2. From what I can tell (here) the Intel Core 2 Duo E8500 CPU only has SSE 4.1
"CL_DEVICE_NOT_AVAILABLE" is the error you get when you try to create an OpenCL device on an unsupported CPU.
The good news for you is that the Intel OpenCL SDK 2012 works on SSE 4.1; you should uninstall the 2013 SDK and use the 2012 SDK instead (or get a newer CPU).
"CL_DEVICE_NOT_AVAILABLE" has nothing to do with the SDK. It's due to the OpenCL device driver which is part of the video card device driver.
It's common to confuse the SDK and the OpenCL device driver. You develop the host code with the SDK but the kernel is compiled and run through the device driver. I often develop with the Intel SDK but I run my kernels on the CPU using the Intel video driver or the AMD Radeon drivers and on the GPU using the Nvidia video drivers (GTX590). I have all three video drivers installed in Windows. You don't have to have an AMD video card to instal the Radeon drivers.
So in your case you can use the AMD drivers to run your kernel on the CPU. They are much less restrictive than Intel's.
On windows I get faster results running my Kernel on my Sandy Bridge CPU using the Intel OpenCL drivers than AMD. However, on Linux the AMD driver runs my kernel faster on my Intel CPU than the Intel driver does.
I encountered this error while creating a tutorial on how to install hashcat on Ubuntu 18.04; I've included the instructions below for Installing OpenCL™ Runtimes for Intel® Processors - Option A (Recommended)- feel free to review my full gist on GitHub. Hope that helps!
Installing OpenCL™ Runtimes for Intel® Processors
Installing OpenCL™ Runtimes for Intel® Processors - Option A (Recommended)
Check your CPU system processor architecture by running sudo lscpu to identify the class of CPU e.g. "Intel (R) Core (TM) i7-7700 CPU # 3.60Ghz"- alternatively, you can go to Settings > Details which will also reveal the CPU-family (e.g. Intel (R) HD Graphics 630 (Kaby Lake GT2)).
Go to the Intel Developer Zone and scroll down to the corresponding download link for your system; assuming you're running Ubuntu 18.04 and have a Intel Core-class CPU, scroll down to "Linux* OS Ubuntu* 16.04.x (deb)" and click on the Github link for 18.46.11837 Runtimes to access the runtime-packages to download.
There should be instructions within the aforementioned Github repo- or you can proceed with the following in the next steps.
cd ~/Desktop
mkdir neo
cd neo
sudo wget https://github.com/intel/compute-runtime/releases/download/18.46.11837/intel-gmmlib_18.4.0.348_amd64.deb
wget https://github.com/intel/compute-runtime/releases/download/18.46.11837/intel-igc-core_18.44.1060_amd64.deb
wget https://github.com/intel/compute-runtime/releases/download/18.46.11837/intel-igc-opencl_18.44.1060_amd64.deb
wget https://github.com/intel/compute-runtime/releases/download/18.46.11837/intel-opencl_18.46.11837_amd64.deb
Install the packages by running sudo dpkg -i *.deb.
Restart the system by running sudo reboot.
Installing OpenCL™ Runtimes for Intel® Processors - Option B
Go to Intel OpenCL Runtimes website and scroll down to the bottom of the page to Download Intel CPU Runtime for OpenCL Applications 18.1 for LINUX OS (64-bit only).
After downloading the OpenCL Runtimes for Intel Processors, cd ~/Downloads
Run sudo tar -xzf l_opencl_p_18.1.0.013.tgz to unpack the tgz file- please note, the OpenCL file version may update since the time as of this gist (ie as of this gist, the version is 18.1.0.013.)
cd l_opencl_p_18.1.0.013
Run sudo ./install.sh
A welcome screen is prompted- hold-down the "Enter" key until able to input select "2" for "I do NOT consent to the collection of my Information"
Hit "1"
Hit "1"
Hit "Enter" and then restart the computer.
If any additional Intel OpenCL errors are encountered after testing hashcat, go to section 'Installing OpenCL™ Runtimes for Intel® Processors - B'- if not, proceed with section "Testing Hashcat"