POST
|
I'm working on releasing an update to a project created with ArcGIS 10.2.6 in Qt 5.5, the project has since been verified to work on 5.6.2, and 5.7.1, 5.5 never worked for iOS so we switched to 5.6.2 and then 5.7.1. It has been months since we ran a build, and now when I attempt to, I get linker errors. Xcode is v8.2.1, OSX is 10.11.6 - I suspect an Xcode or OSX update is what destabilized this but I'm not sure how to fix it. The command being run is: Ld Debug-iphonesimulator/myProject.app/myProject normal x86_64 cd /Users/myUser/Documents/Qt/build-myProject-iphoneos_clang_Qt_5_6_2_for_iOS3-Release export IPHONEOS_DEPLOYMENT_TARGET=6.0 export PATH="/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin:/Applications/Xcode.app/Contents/Developer/usr/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin" /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang++ -arch x86_64 -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator10.2.sdk -L/Users/myUser/Documents/Qt/build-myProject-iphoneos_clang_Qt_5_6_2_for_iOS3-Release/Debug-iphonesimulator -L/Users/myUser/arcgis/qt10.2.6/sdk/iOS/armv7/lib -L/Users/myUser/Qt/5.6/ios/plugins/platforms -L/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator10.2.sdk/System/Library/Frameworks -L/Users/myUser/Qt/5.6/ios/lib -L/Users/myUser/Qt/5.6/ios/qml/QtQuick.2 -L/Users/myUser/Qt/5.6/ios/qml/ArcGIS/Runtime.10.26 -L/Users/myUser/Qt/5.6/ios/qml/QtQuick/Window.2 -L/Users/myUser/Qt/5.6/ios/qml/QtPositioning -L/Users/myUser/Qt/5.6/ios/qml/Qt/labs/settings -L/Users/myUser/Qt/5.6/ios/qml/ArcGIS/Extras.1.0 -L/Users/myUser/Qt/5.6/ios/qml/QtGraphicalEffects/private -L/Users/myUser/Qt/5.6/ios/plugins/iconengines -L/Users/myUser/Qt/5.6/ios/plugins/imageformats -L/Users/myUser/Qt/5.6/ios/plugins/qmltooling -L/Users/myUser/Qt/5.6/ios/plugins/bearer -L/Users/myUser/Qt/5.6/ios/plugins/position -L/Users/myUser/Qt/5.6/ios/plugins/sensors -F/Users/myUser/Documents/Qt/build-myProject-iphoneos_clang_Qt_5_6_2_for_iOS3-Release/Debug-iphonesimulator -filelist /Users/myUser/Documents/Qt/build-myProject-iphoneos_clang_Qt_5_6_2_for_iOS3-Release/myProject.build/Debug-iphonesimulator/myProject.build/Objects-normal/x86_64/myProject.LinkFileList -mios-simulator-version-min=6.0 -dead_strip -Xlinker -object_path_lto -Xlinker /Users/myUser/Documents/Qt/build-myProject-iphoneos_clang_Qt_5_6_2_for_iOS3-Release/myProject.build/Debug-iphonesimulator/myProject.build/Objects-normal/x86_64/myProject_lto.o -Xlinker -no_deduplicate -Xlinker -objc_abi_version -Xlinker 2 -headerpad_max_install_names -stdlib=libc++ -u _qt_registerPlatformPlugin -Wl,-e,_qt_main_wrapper -L/Users/myUser/arcgis/qt10.2.6/sdk/iOS/armv7/lib -L/Users/myUser/Qt/5.6/ios/plugins/platforms -framework UIKit -framework AssetsLibrary -L/Users/myUser/Qt/5.6/ios/lib -framework MobileCoreServices -framework OpenGLES -L/Users/myUser/Qt/5.6/ios/qml/QtQuick.2 -L/Users/myUser/Qt/5.6/ios/qml/ArcGIS/Runtime.10.26 -L/Users/myUser/Qt/5.6/ios/qml/QtQuick/Window.2 -L/Users/myUser/Qt/5.6/ios/qml/QtPositioning -L/Users/myUser/Qt/5.6/ios/qml/Qt/labs/settings -L/Users/myUser/Qt/5.6/ios/qml/ArcGIS/Extras.1.0 -L/Users/myUser/Qt/5.6/ios/qml/QtGraphicalEffects/private -L/Users/myUser/Qt/5.6/ios/plugins/iconengines -L/Users/myUser/Qt/5.6/ios/plugins/imageformats -L/Users/myUser/Qt/5.6/ios/plugins/qmltooling -L/Users/myUser/Qt/5.6/ios/plugins/bearer -L/Users/myUser/Qt/5.6/ios/plugins/position -L/Users/myUser/Qt/5.6/ios/plugins/sensors -framework CoreMotion -lz -lm -L/Users/myUser/Qt/5.6/ios/lib -framework MobileCoreServices -framework UIKit -lz -lm -Xlinker -sectcreate -Xlinker __TEXT -Xlinker __entitlements -Xlinker /Users/myUser/Documents/Qt/build-myProject-iphoneos_clang_Qt_5_6_2_for_iOS3-Release/myProject.build/Debug-iphonesimulator/myProject.build/myProject.app.xcent -lEsriRuntimeQt -lqios_iphonesimulator_debug -framework Foundation -framework QuartzCore -framework CoreFoundation -framework CoreText -framework CoreGraphics -lQt5PlatformSupport_iphonesimulator_debug -lqtfreetype_iphonesimulator_debug -lQt5OpenGL_iphonesimulator_debug -framework Security -framework SystemConfiguration -lQt5Xml_iphonesimulator_debug -lQt5Script_iphonesimulator_debug -lqtquick2plugin_iphonesimulator_debug -lArcGISRuntimePlugin -lwindowplugin_iphonesimulator_debug -ldeclarative_positioning_iphonesimulator_debug -lqmlsettingsplugin_iphonesimulator_debug -lArcGISExtrasPlugin -lqtgraphicaleffectsprivate_iphonesimulator_debug -lqsvgicon_iphonesimulator_debug -lqdds_iphonesimulator_debug -lqicns_iphonesimulator_debug -lqico_iphonesimulator_debug -lqsvg_iphonesimulator_debug -lQt5Svg_iphonesimulator_debug -lQt5Widgets_iphonesimulator_debug -lqtga_iphonesimulator_debug -lqtiff_iphonesimulator_debug -lqwbmp_iphonesimulator_debug -lqwebp_iphonesimulator_debug -lqmldbg_debugger_iphonesimulator_debug -lqmldbg_inspector_iphonesimulator_debug -lQt5Quick_iphonesimulator_debug -lQt5Gui_iphonesimulator_debug -lqtharfbuzzng_iphonesimulator_debug -lqmldbg_local_iphonesimulator_debug -lqmldbg_native_iphonesimulator_debug -lqmldbg_profiler_iphonesimulator_debug -lqmldbg_server_iphonesimulator_debug -lqmldbg_tcp_iphonesimulator_debug -lQt5Qml_iphonesimulator_debug -lqgenericbearer_iphonesimulator_debug -lQt5Network_iphonesimulator_debug -lqtposition_cl_iphonesimulator_debug -framework CoreLocation -lqtposition_geoclue_iphonesimulator_debug -lQt5DBus_iphonesimulator_debug -lqtposition_positionpoll_iphonesimulator_debug -lQt5Positioning_iphonesimulator_debug -lqtsensors_generic_iphonesimulator_debug -lqtsensors_ios_iphonesimulator_debug -lQt5Sensors_iphonesimulator_debug -lQt5Core_iphonesimulator_debug -lqtpcre_iphonesimulator_debug -Xlinker -dependency_info -Xlinker /Users/myUser/Documents/Qt/build-myProject-iphoneos_clang_Qt_5_6_2_for_iOS3-Release/myProject.build/Debug-iphonesimulator/myProject.build/Objects-normal/x86_64/myProject_dependency_info.dat -o /Users/myUser/Documents/Qt/build-myProject-iphoneos_clang_Qt_5_6_2_for_iOS3-Release/Debug-iphonesimulator/myProject.app/myProject and the errors are: ld: warning: ignoring file /Users/myUser/arcgis/qt10.2.6/sdk/iOS/armv7/lib/libEsriRuntimeQt.a, missing required architecture x86_64 in file /Users/myUser/arcgis/qt10.2.6/sdk/iOS/armv7/lib/libEsriRuntimeQt.a (2 slices) ld: warning: ignoring file /Users/myUser/Qt/5.6/ios/qml/ArcGIS/Runtime.10.26/libArcGISRuntimePlugin.a, missing required architecture x86_64 in file /Users/myUser/Qt/5.6/ios/qml/ArcGIS/Runtime.10.26/libArcGISRuntimePlugin.a (2 slices) ld: warning: ignoring file /Users/myUser/Qt/5.6/ios/qml/ArcGIS/Extras.1.0/libArcGISExtrasPlugin.a, missing required architecture x86_64 in file /Users/myUser/Qt/5.6/ios/qml/ArcGIS/Extras.1.0/libArcGISExtrasPlugin.a (2 slices) Undefined symbols for architecture x86_64: "qt_static_plugin_ArcGISRuntimePlugin()", referenced from: __GLOBAL__sub_I_myProject_qml_plugin_import.cpp in myProject_qml_plugin_import.o "qt_static_plugin_ArcGISExtrasPlugin()", referenced from: __GLOBAL__sub_I_myProject_qml_plugin_import.cpp in myProject_qml_plugin_import.o ld: symbol(s) not found for architecture x86_64 clang: error: linker command failed with exit code 1 (use -v to see invocation) I have previously run 10.2.6 builds on this machine with no problem. I modified the .prf as per this question: Can not build iOS for x86_64 processor architecture to no avail - I receive the same errors. Do any of you guys have any suggestions or do you see what mistake I've made? Thanks!
... View more
07-13-2017
09:02 AM
|
0
|
1
|
905
|
POST
|
I am going to share the dataset with you in a private message. I don't have time to create a stripped down demo right now, but I'll work on that. If you just want to try it yourself, the layer that has the most data there I think is the layer named "Storm Manholes", though on the JS api version we can smoothly use the map with all 7 feature sets added as individual feature layers.
... View more
06-01-2017
01:27 PM
|
0
|
0
|
992
|
POST
|
Lucas, Thanks for the quick response. Could you possibly point me towards the REST service for some demo feature sets that are publicly visible and have a large number of features? I probably shouldn't share my feature sets to make a demo for you as the data belongs to paying clients.
... View more
06-01-2017
10:47 AM
|
0
|
2
|
992
|
POST
|
Thank you Lucas, I was unable to ever find the response to my bug report submission, so thanks for sharing it. FeatureRequestModeManualCache seems to behave no differently for me than FeatureRequestModeOnInteractionCache. In both modes, every pan and zoom event on the map re-queries the current extent. Additionally, both modes seem to do some heavy processing and/or re-rendering on every query response because both modes trigger massive CPU spikes, introduce UI lag, and cause the layers to flicker if there are multiple layers visible and more than maybe 100 features on screen. The two separate modes performing identically strikes me as a bug, but maybe there's something I'm missing that is different between them. As a side note, and probably unrelated to the featureRequestMode property: In the JS API I'm able to query literally the entire feature set from every single feature service, render all of them on screen as separate feature layers, and begin smoothly interacting with the map faster than I can do this with just one of my somewhat large feature sets in the QML SDK. Even if I request all of the layers and features in the image below on every single pan with the JS API, it still performs more smoothly and utilizes less cpu than panning even a single layer on the QML. I am aware this is unrelated to the feature request mode, but this poor performance showcases why I am so concerned about "feature caching", because if the SDK has to re-request even a single layer with a few hundred features, performance in the app drops off a cliff. If this performance somehow gets fixed soon then feature caching wouldn't be quite as important to me anymore. Thank you, as always, for your effort in responding to me! I really appreciate the assistance.
... View more
05-30-2017
02:44 PM
|
0
|
4
|
992
|
POST
|
Right now, using Qt 5.7.1 and ArcGIS Runtime SDK v100, none of the caching modes seem to work on a service feature table. This means every interaction with the map is querying and then re-rendering hundreds or even thousands of features and it makes my application vastly inferior to ones made with any other technology. Is there any fix or workaround for this?
... View more
05-30-2017
08:02 AM
|
0
|
8
|
1577
|
POST
|
Thanks for getting back to me. The tablet is a Samsung and running Android 6.02. The app performs better in almost every respect on the tablet than on my desktop (although the flickering and redrawing of feature layers is still extremely bad). Perhaps I have a problem on my desktop, but other cpu/network intensive applications run without a hitch.
... View more
03-24-2017
05:59 AM
|
0
|
2
|
1006
|
POST
|
I'm using version 100.0, and basing my code off of Show legend—ArcGIS Runtime SDK for Qt | ArcGIS for Developers I get that the file for each legendInfo's image is being created by the LegendInfoListModel, but is there any way I can get that image data and turn it into an image myself without relying on this system? I can see the data in the responses from the server, but I don't know how to access it through your SDK. Currently, I have to generate a view/model/delegate for every layer, and keep them in existence while capturing the symbolUrl from the delegate itself and exposing that to the rest of my application. This means in order to render a simple icon I have to have all that overhead instead of just a simple Image {} object, which is probably not a good idea on mobile. One possibility I can already think of is to manually send a request to the legend endpoint, retrieve the imageData strings, and render a qt quick image from that. Is that what I'm going to have to do?
... View more
03-17-2017
08:17 AM
|
0
|
1
|
1198
|
POST
|
Do you have any information about the feature layer performance issue? I'm running the exact same map service side by side using the JS api and the QT SDK and the js api is buttery smooth while the QT SDK floors the CPU and takes full seconds (plural) to render the layers every time you pan/zoom. Surely you guys have rendered maps with multiple feature layers and thousands of features before, do you experience this problem? Are there workarounds or any plans to fix it soon? This has become a major issue, we switched to QT from JS to improve mobile performance and now we're experiencing the opposite effect.
... View more
03-07-2017
01:03 PM
|
0
|
4
|
1006
|
POST
|
Good catch, that was the problem. I'm sure you noticed that we switched to v100.0 for at least some of our apps, but we didn't want to bother rebuilding all the old ones just yet, so it's good to be able to get this working. Do you know if this particular issue has been fixed in the 10.x line since 10.2.6? We could always move our older apps to 10.2.8_1 to address this issue without having to manually modify the install if that's the case.
... View more
02-17-2017
11:52 AM
|
0
|
3
|
1769
|
POST
|
It doesn't matter what libs I try to add, anything I add to additional libraries gets automatically removed within seconds. If I remove libEsriRuntimeQt.so, it gets automatically added back in. Some script is clearly running when I make changes but I'm not familiar with what's happening behind the scenes when I make changes on the project settings screen.
... View more
02-17-2017
11:25 AM
|
0
|
5
|
1769
|
POST
|
There is a space in Program Files, but that space is there for the esri library as well. Just to be safe, I moved the libs to a space-less path, and the problem remains. The problem also remains in a brand new 10.2.6 Qt Quick project.
... View more
02-17-2017
10:54 AM
|
0
|
0
|
1769
|
POST
|
I'm on windows making builds for Android and I am trying to package libssl.so and libcrypto.so into my 10.2.6 application. Whenever I make any changes to "additional libraries" in the build android apk target, the changes are immediately un-done and a message about qmake.cache pops up in general messages: C:/....../build-eCOP-Android_for_armeabi_v7a_GCC_4_9_Qt_5_7_1-Debug/.qmake.cache: No such file or directory This happens even if i wipe out the entire build directory, and it happens even if I disable shadow build. Anyone know what I'm doing wrong to add these libraries? If I manually add them in the .pro file, they still don't make it into the makefile.
... View more
02-17-2017
10:02 AM
|
0
|
8
|
4108
|
Title | Kudos | Posted |
---|---|---|
2 | 02-08-2017 07:03 AM | |
1 | 11-22-2016 06:48 AM | |
1 | 11-22-2016 07:31 AM |
Online Status |
Offline
|
Date Last Visited |
11-11-2020
02:23 AM
|