Latest Contributions by ChristianNuckols

‎09-19-2018

Hi Lucas, Our company is providing several apps for municipal and other state agencies. Users record location data and take surveys of structures to ascertain compliance to federal regulations. Only one of these apps requires use of 32-bit libraries. Users operate the application on mobile equipment and use a button-based UI to record data about obstructions and obstacles. The 32-bit dlls are crucial because key collection sensors rely on 32-bit drivers for hardware that cannot be easily reimplemented to 64-bit. This hardware includes accelerometers and gyroscopes used to log data about slope, speed, and changes in the terrain. These drivers are maintained by one of our partner companies. As far as migrating the deployment of the 32-bit app – because this particular software is a joint-effort with another company, the timeframe would be contingent on our partners’ ability to upgrade their systems. We have heard that there is now a 64 bit driver available that they are looking into see if it works on the equipment, but it is going to take some time to test and implement and we need to get this app in production ASAP with the current hardware for a project starting next week. On our end, making a 64-bit build of this application would be inconsequential. Thanks

‎09-17-2018

Hi, my company has developed an app using the 100.2.1 runtime with the Qt SDK, and need to deploy a build for a 32-bit Windows device. I've read the release notes this version at Release notes for 100.2.1—ArcGIS Runtime SDK for Qt | ArcGIS for Developers and saw that: Version 100.2 is the last release to support: [...] Windows 32-bit support for Qt. Customers who require Windows 32-bit support for ArcGIS Runtime SDK 100.2 for Qt will need to request it by sending an email to QtRuntime32@esri.com. I've also read this thread on geonet by another developer who appears to have the same issue: https://community.esri.com/message/792149-re-missing-32-bit-libs-in-release-1002-for-windows?commentID=792149#comment-79… My question is, the above note is referring to deployment support, correct? I'm developing on 64 bit system, but I'm assuming I'll need these libraries to install our app since the esri runtime dlls I include in my deployment folders are x64-specific. I've already sent an email to the above address, I just wanted to clarify that I'm diagnosing my issue correctly.

‎07-30-2018

What you're saying makes sense; the qml import should not need to be named to correspond the version (or included) if it isn't used at all. I don't have a diagnosis for why adding the version number fixed my problem, all I know is that I'm sure I tried an identical deployment without the version number appended to the folder and the deployment didn't function. I have quite a few QML components that imported the parent qml class(component?) which many builds ago *did* have the import statement, so one guess is that maybe some part of the makefile wasn't getting updated correctly and was still looking for the import? Which still doesn't explain why the version number itself would be necessary. In any case, after I got the issue resolved I added the Extras import again to use the scaleFactor property. If I have time to figure out what the problem was I'll definitely come back to this thread and explain what was happening. But you're right, it shouldn't behave in that way.

‎07-27-2018

For anyone coming across this thread, when you copy this folder into your deployment: C:\Program Files (x86)\ArcGIS SDKs\Qt100.2.1\sdk\windows\x64\qml you need to look at C:\Program Files (x86)\ArcGIS SDKs\Qt100.2.1\sdk\windows\x64\qml\Esri\ArcGISExtras and either append a version number to ArcGIS Extras to the copied subfolder or copy the appropriate Extras import library from the corresponding sample sdk C:\Program Files (x86)\ArcGIS SDKs\Qt100.2.1\sdk\samples\ArcGISRuntimeSDKQt_CppSamples\bin\qml\Esri\ArcGISExtras.1.1 Even if your app doesn't use this import. My app doesn't and this was the difference between it functioning on the deploy device or not.

‎07-27-2018

James, I got the app to deploy by appending the version number. Thanks so much for your help!

‎07-27-2018

Thank you. I tried adding the just the QML folder you linked to and got the same result. C:\Program Files (x86)\ArcGIS SDKs\Qt100.2.1\sdk\windows\x64\qml The extras folder doesn't have version info, which was different from the qml folder in the esri samples: C:\Program Files (x86)\ArcGIS SDKs\Qt100.2.1\sdk\windows\x64\qml\Esri\ArcGISExtras C:\Program Files (x86)\ArcGIS SDKs\Qt100.2.1\sdk\samples\ArcGISRuntimeSDKQt_QMLSamples\bin\qml\Esri\ArcGISExtras.1.1 Also, should I be using the ArcGISRuntimeSDKQt_QMLSamples or ArcGISRuntimeSDKQt_CppSamples as a reference? (im using QML and cpp - have multiple .qml and multiple .cpp files) Also I tried moving all of the api-ms-win*.dll files to my app, in addition to copying any missing files. (from both the QML samples and the cpp samples). In both cases, I got this as a result:

‎07-27-2018

I should also note that I have this folder in my ArcGIS SDKs directory: C:\Program Files (x86)\ArcGIS SDKs\Qt100.2.1\sdk\windows\x64\qml\Esri\ArcGISExtras which has the same file structure, but doesn't use the version number.

‎07-27-2018

No I can't. Should I be seeing a qml folder even if I'm using the QtQuick compiler?

‎07-27-2018

I'm having trouble deploying software from my PC (on which I am developing our app) to our tablets (which are identical to our clients' systems). Both use windows and the msvc compilers are up to date on both of the systems. I know the tablets meet the system requirements for the runtime, because I've been able to build and deploy sample apps. For instance, on the tablets, I can build and deploy the basic 'Display Map' sample if I comment out import Esri.ArcGIS Extras 1.1 but if I don't, the app loads, but nothing is rendered: I understand that the extras require more .dll files. I'm able to deploy apps with the Extras component (to any location on disk) on the development PC even if I explicitly set the runtime environment variable: ArcGISRuntimeEnvironment::setInstallDirectory(QDir::currentPath()); I should note, that I am not actually using the extras component in my app. Deployment of the sample apps was part of my attempt to diagnose the issue, and I came across that problem. To deploy my app on the development PC, I take the following steps: 1. Compile my release in QtCreator. This stores the executable here: C:\Users\cnuckols\ArcGIS\AppStudio\Apps\build-ULIP-Desktop_Qt_5_10_0_MSVC2017_64bit-Release And the storage folder for my source code is: C:\Users\cnuckols\ArcGIS\AppStudio\Apps\ULIP\ 2. Move the executable to a folder on my desktop: C:\Users\cnuckols\Desktop\Deployment2\ULIP.exe 3. Use the qt deployment tool for windows: I should note that I've tried this with and without the angle option. 4. Copy the sdk runtime .dlls to the deployment folder: Here are the contents of my deployment folder: 5. I run the app, and it works correctly. However, when I move the deployment2 folder to the tablet it executes, but nothing is rendered: I get no error messages and no warnings. To further clarify, when I look at which dlls are being used by ULIP.exe in the tablet, msvcp140.dll and vcruntime140.dll. are both listed (the ones contained in System32): C:\WINDOWS\SYSTEM32\MSVCP140.dll and C:\WINDOWS\SYSTEM32\VCRUNTIME140.dll -I have read the page on deploying the app: Deploy your app—ArcGIS Runtime SDK for Qt | ArcGIS for Developers -I have read the system requirements page for the newer runtime: System requirements for 100.3.0—ArcGIS Runtime SDK for Qt | ArcGIS for Developers -I have read every geonet thread on deployment issues for the Qt SDK -I am using the QtQuick Compiler -I've been using the Qt windows deployment tool and have read the Qt page about using the tool: Qt for Windows - Deployment | Qt 5.11 Thanks!

Online Status	Offline
Date Last Visited	‎11-11-2020 02:24 AM

My Ideas

Latest Contributions by ChristianNuckols

Re: Runtime 100.2.1 32 bit deployment for sdk application

Runtime 100.2.1 32 bit deployment for sdk application

Re: Deployment problems with C++ sdk for 100.2 runtime windows using msvc2017_64

Re: Deployment problems with C++ sdk for 100.2 runtime windows using msvc2017_64

Re: Deployment problems with C++ sdk for 100.2 runtime windows using msvc2017_64

Re: Deployment problems with C++ sdk for 100.2 runtime windows using msvc2017_64

Re: Deployment problems with C++ sdk for 100.2 runtime windows using msvc2017_64

Re: Deployment problems with C++ sdk for 100.2 runtime windows using msvc2017_64

Deployment problems with C++ sdk for 100.2 runtime windows using msvc2017_64