We are trying to integrate Xtify SDK in our iPhone and iPad apps for receiving PUSH notifications and when we use tried, we are getting linker errors. I believe the Xtify SDK is not compiled with the arm64 architecture and that is the reason we are getting this error. Can anyone confirm this?
Thanks!
Later iOS Xtify library versions are compiled with the standard architectures (armv7 and arm64 - but not armv7s, which is no longer standard as of Xcode 6 - see Xcode 6 Standard architectures exclude armv7s). You will need to use version 2.74 or higher to compile on Xcode 6.x.
Related
I want to build a iPad/Mac Catalyst app that features language translation using the Firebase machine learning framework.
I know by default that the frameworks are designed to support iOS. But if I want to built a new Catalyst app (where it's an iOS app that will port over to MacOS), how do I get these frameworks to work?
I just tried to compile for the Mac and I get this error:
ld: building for Mac Catalyst, but linking in object file built for iOS Simulator, file '/Documents/TestAppCatalyst/Pods/FirebaseMLNLTranslate/Frameworks/FirebaseMLNLTranslate.framework/FirebaseMLNLTranslate' for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
It's a bit cryptic but I am guessing it means I am trying to use a framework designed for the iOS but I can't. Has anyone come up with a workaround for this type of issue?
ML Kit does not currently support Mac Catalyst. It only supports iOS at the moment.
I'm trying to make a app with Gluon mobile but i'm not able to make the Android version work.
I try to download the SDK directly from android but the SDKManager will not open.
After some research I find that SDKManager is not support anymore.
I install Android studio, but the Support Repository is now obsolete.
Anybody know how I can make it work?
I change my JavaJDK to 1.8 instead of java 11 or 12 but still nothing.
Thanks
Jc
The Gluon Plug-in won't deploy to Android with gradle task androidInstall as the Android SDK is missing "Android Support Repository" which is no longer available with current versions of Android Studio, but the androidInstall gradle task console-log outputs a DOS command-line showing how to download it.
Something like:
C:/Users/.../Android/Sdk/tools/bin/sdkmanager "extras;android;m2repository"
(the above is described in the link mentioned earlier by José Pereda)
I'm trying to build a simple application with CUDA and I've been trying for hours on end and I just can't make it work on windows. nvcc absolutely refuses to compile without Visual Studio's compiler which doesn't support things I need. I tried building using nvcc with clang but It just asks me to use Visual Studio's compiler. I've also tried using clang directly since it now supports CUDA but I receive this error:
clang++.exe: error: Unsupported CUDA gpu architecture: compute_52
This makes no sense to me because I have the CUDA toolkit version 7.5 and my graphics card is a GTX 970 (two of them). I have googled this extensively and everywhere I come across the error the person always has is their CUDA toolkit is < 7.5. I'm on the brink of tears right now trying to get something as simple as VLA to work on this CUDA application and I just can't achieve it...
The CUDA windows toolchain requires the Visual Studio C++ compiler. You cannot use anything else on that platform. If the VS compiler doesn't support the language features you need within CUDA host code, you have no choice but to change platforms, or your expectations.
You can still potentially compile non-CUDA host code using another compiler and then link that code using NVCC and the VS toolchain.
Try to use clang-cl, --cubin=clang-cl.exe
It may be worth to work on a Linux VM or WSL2 within windows. As per the CUDA docs.
To compile new CUDA applications, a CUDA Toolkit for Linux x86 is
needed. CUDA Toolkit support for WSL is still in preview stage as
developer tools such as profilers are not available yet. However, CUDA
application development is fully supported in the WSL2 environment, as
a result, users should be able to compile new CUDA Linux applications
with the latest CUDA Toolkit for x86 Linux.
https://docs.nvidia.com/cuda/wsl-user-guide/index.html#:~:text=However%2C%20CUDA%20application%20development%20is,becomes%20available%20within%20WSL%202.
I have been working with Qt Desktop for a year now, and I needed to set up the environment for Android. I have followed carefully the steps in Qt documentations, downloaded Android SDK, NDK, Ant and JDK 7. I included all the paths and created a kit for Android. I installed the latest Android APIs and System Images from SDK and also created a AVD Nexus running Android 5.1.
I created a project (when i create a Widget project, in the supported platforms at the right, Android is not shown, as in tutorial I have seen) and build and run it on Desktop - eveything Ok. When I try to run it on Android, a pop up shows, wanting the path of the executable, saying it can not find it. I don't know what to include here, cause in all the tutorials I have seen the AVD should start automatically (it is on, in the moment I try to run from Qt).
I don't what other settings to check, been seven hours now, trying to figure out the problem. I think the problem is in the Kit or in the Debugger, or in the Qt Version that can not detect the Android Kits or AVDs. Or it is just a silly thing that just need a path for the executable when running. These are all my system setting, please let me know if you need other info:
Qt Creator 3.3.2 (opensource)
Based on Qt 5.4.1 (MSVC 2010, 32 bit)
Android Kit:
Name: Android
File System Name: empty
Device Type: Android Device
Device: Run on Android(default for Android)
Sysroot: empty
Compiler: MinGw 4.9.1 32bit
Environment: No Changes to apply
Debugger: Android Debugger (I also tried to leave this Auto Detect, it was the same)
Android GDB server: Auto-Detect (I also tried including: C:\Qt_for_Android\android-ndk-r10e\prebuilt\android-arm\gdbserver, it was the same)
Qt Version: Qt 5.4.1 MinGW 32bit
Qt mkspec: empty
Qt Versions:
Auto-Detected: QtQt %{Qt:Version} MinGW 32bit
no Manual
Compilers:
MinGW 4.9.1 32 bit
and several others for Android GCC (arm-4.8, mips, x86), but when I try to include them into the Android Kit, the Kit is not Available, I can choose only MinGW, which seems the most probable problem to me.
Debuggers:
Auto-Detect:
GNU gdb 7.8 for MinGW
CDB at ...
Manual"
Android with path : C:\Qt_for_Android\android-ndk-r10e\toolchains\arm-linux-androideabi-4.9\prebuilt\windows\bin\arm-linux-androideabi-gdb.exe
I really don't know what the problem is, and I need to start soon.
can you still build applications you made from SDK 4 to an updated iOS 5 device?
without having to update to the beta version of XCode (4.2)?
Or maybe, Will it be okay also if I will just have two versions of XCode?
Thanks
You need to update to Xcode 4.2 to get the latest version of the iOS SDK. I'm not sure if you can use the iOS 5 SDK with Xcode 4.1; maybe if you update your compiler to clang 3.0.
Of course, you can always run iOS 4 apps on iOS 5 devices.