I started some weeks ago testing MVVMCross and I managed to compile in debug mode for simulator.
However, when I try to compile for Ad Hoc or debug mode for Device, I'm getting following errors:
Error MT3001: Could not AOT the assembly '/SomeDirectory/obj/iPhone/Ad-Hoc/mtouch-cache/Build/Cirrious.MvvmCross.Plugins.DownloadCache.dll' (MT3001)
Error MT3001: Could not AOT the assembly '/SomeDirectory/obj/iPhone/Ad-Hoc/mtouch-cache/Build/Cirrious.MvvmCross.dll' (MT3001)
Error MT3001: Could not AOT the assembly '/SomeDirectory/obj/iPhone/Ad-Hoc/mtouch-cache/Build/Cirrious.CrossCore.dll' (MT3001)
I'm linking more MVVMCross libraries, but it seems only these 3 are mentioned. I tried to play around with changing the Mac DLLs with the Windows DLLs but error stays (at a certain point I was getting 5 errors instead of 3 when changing them)
I'm using latest stable version of Xamarin.iOS + MVVMCross 3.0.12
Any Idea?
Regards, Matt
Related
I successfully built standalone llvm on windows with clang-cl (clang 8.0 downloadable binary) against back-end msvc build tool 2017 with windows 10 sdk using cmake/ninja
After that when I was building standalone clang, it reported "version.lib" in linking phase of clang-rename.exe is missing.
LINK Pass 1: command "....
" failed (exit code 1104) with the following output:
LINK : fatal error LNK1104: cannot open file 'version.lib'
The weird thing is that word version.lib was slabbed in place amoung various lib\clang?????.libs and the leading -LIBPATH:llvm\\.\lib
I tried looking for version.lib in both build folders of llvm and clang, and found none.
Am I supposed to have verson.lib in llvm\lib?
What am I missing here?
I'm uing ARM_EABI cross-compiler to compile a code that makes use of pthreads to run at an ARM Cortex A9 simulation.
While I'm able to compile it with no problems (just as I've did with others non-pthread applications, which ran fine in the simulation), I'm having an error message when trying to run my pthread application at the simulated ARM (which is running Linux as OS). It's the following:
./pttest.exe: /lib/libpthread.so.0: no version information available (required by ./pttest.exe)
I did my research and found out that's because it's a dynamic lib, and I'm compiling the application with a higher version than the one available on my simulator.
My question is: how to find force my cross-compiler to compile the application with the same pthread lib version of my simulator? Is there anywhere I can download different versions of pthreads? And how to set it?
Sorry, I'm quite a newbie in that area.
Try compiling your application statically, e.g.
gcc -static -o myapplication myapplication.c
Using Android NDK R10E, I am trying to build a shared library for all supported ABI's and I am getting the following error for some but not all ABI's:
[armeabi] SharedLibrary : libMyLib.so /home/user/android-ndk-r10e/toolchains/arm-linux-androideabi-4.8/prebuilt/linux-x86_64/bin/../lib/gcc/arm-linux-androideabi/4.8/../../../../arm-linux-androideabi/bin/ld:
fatal error: /home/user/source/MyLib/obj/local/armeabi/libMyLib.so: Input/output error
The project successfully builds for arm64-v8a, mips and mips64 but fails with the above error for armeabi, armeabi-v7a, x86 and x86_64.
I have a static library project and another shared library project and they both build successfully for all 7 ABI's.
If I compare the contents of obj/local/ for an ABI that builds and one that does not, they both contain all the same files except for libMyLib.so.
The difference between those two sets of ABIs is that the failing ones link using ld.gold and the working ones use ld.bfd.
Two things to try:
Use the 4.9 toolchain. It hopefully has the bug fix.
If that doesn't work, you can add -fuse-ld=bfd to your ldflags to use bfd even on the architectures that default to gold.
Same issue happened to me in r15c.
The fix was to copy
android-ndk-r15c/toolchains/arm-linux-androideabi-4.9/prebuilt/linux-x86_64/arm-linux-androideabi/bin/ld.bfd over ld.
I had to copy it because I could not easily find a way to specify this flag to CMake to use it while detecting the compiler features.
I wanted to run an OpenCV project on ARDrone (which is powered by arm7l).
So I cross compiled OpenCV for arm processor, moved the .so files to the drone and updated the LD_LIBRARY_PATH.
Now running the cross compiled OpenCV project throws the following error:
/lib/libc.so.6: version `GLIBC_2.15' not found (required by /data/video/opencvlib/libopencv_highgui.so.2.4)
Where do I get this libc.so
As #Notlikethat suggested I tried copying my cros-toolchain's shared libraries to ARM, it solved the above issue but caused other problems.
For a more permanent solution I followed #Chris 's suggestions and recompiled opencv with board's cross compiler.
I am stuck on LiveCode 5.5.2 because MergZXing triggers a deployment-time (IOS) error:
linking for armv7 failed with Undefined symbols for architecture armv7: "___libinfoptr_mergZXing", referenced from:
-u command line option ld: symbol(s) not found for architecture armv7
clang: error: linker command failed faith exit code 1 (use -v to ee invocation)
Do I have the latest version, is there a work-around?
I have updated to Xcode 5x and running on Mavericks. I also updated my mobile settings on LiveCode 6.5.
Any help will be highly appreciated.
The problem is you don't have the latest version of mergZXing which is built against iOS 7 SDK. It's available from the downloads page on mergExt.com.