As for embedded Linux it’s not only the build and deployment itself (I usually have a separate VM for each customer and board), but much more the nature of the device itself. On the target all „real“ interfaces and features are enabled. On the desktop I disable them to speed things up and/or to compensate missing hardware - which is also really useful for automated tests.
Beste Grüße / Best regards, Alexander Nassian > Am 29.11.2016 um 08:42 schrieb Jake Petroules <jake.petrou...@qt.io>: > > I don't know what sort of cross build and deployment environment you've set > up, but I've worked with Qt Creator developing on actual embedded Linux > hardware and the code-deploy-test cycle is lightning fast; no slower than > desktop at all. > > iOS may be slower in particular due to our suboptimal build process > implementation on that platform (and thus recommending that you use the iOS > Simulator instead might not be a viable alternative), but I at least have > never noticed any problems with slowness here so I'm not sure what you're > referring to. > > Android, I'm not sure. Again, possibly due to the suboptimal build process > implementation, but at least the emulators are blazing fast these days > compared to the original SDK back in 2010 or so. > >> On Nov 28, 2016, at 11:37 PM, Alexander Nassian >> <nass...@bitshift-dynamics.de> wrote: >> >> I don’t get the use case for having *only* iOS installed on my system. As >> well as for example only a cross Qt for an embedded device (iOS is >> practically the same thing). The normal development cycle should be (at >> least in my opinion) mainly develop on the desktop and check on the target >> in a regular manner. The cross build and deployment is enormously slower >> than on the desktop (which is ok with a cycle as I described), so why would >> I ever *only* use the cross build and deployment? Same thing for Android. >> Same thing for any embedded Linux target, but in contrast to Android and iOS >> we don’t deliver prebuilt binaries for them. >> >> Beste Grüße / Best regards, >> Alexander Nassian >> >>> Am 29.11.2016 um 08:24 schrieb Jani Heikkinen <jani.heikki...@qt.io>: >>> >>>> -----Original Message----- >>>> From: Development [mailto:development- >>>> bounces+jani.heikkinen=qt...@qt-project.org] On Behalf Of Jake Petroules >>>> Sent: maanantaina 28. marraskuuta 2016 20.23 >>>> To: Alexander Blasche <alexander.blas...@qt.io> >>>> Cc: development@qt-project.org; releas...@qt-project.org >>>> Subject: Re: [Development] Qt 5.9 >>>> >>>> >>>>> On Nov 28, 2016, at 7:40 AM, Alexander Blasche >>>> <alexander.blas...@qt.io> wrote: >>>>> >>>>> Ok, let's summarize and restate the package list for Qt 5.9 based on the >>>> comments provided on this mail thread. The list describes the delta to Qt >>>> 5.8 >>>> packages: >>>>> >>>>> * For macOS we drop 10.9 and support 10.10, 10.11 & 10.12 >>>>> * For iOS we drop 7.x and support 8.x, 9.x, 10.x >>>> >>>> * For tvOS we drop 9.x and support 10.x >>>> * For watchOS we drop 2.x and support 3.x >>>> >>>>> * MinGW remains 5.3 using 32 bit >>>>> * Add MSVC 2017 64bit desktop >>>>> * Add MSVC 2017 UWP (x64, x86, armv7) >>>>> * Drop MSVC 2013 x86 >>>>> * Drop MSVC 2013 for WinRT/WinPhone & MSVC 2013 for WinRT 8.1 and >>>> WinPhone 8.1 >>>>> * Drop standalone macOS Android installer; One having iOS & Android >>>> >>>> As I said, let's not, and instead drop the massive macOS+iOS+Android >>>> installer in favor of an iOS-only installer. >>> >>> Is it really so that users of iOS installer needs only iOS binaries and >>> nothing for desktop side? >>> >>> In this case I agree this might be the optimal solution but this doesn't >>> decrease amount of our installers and that's why I prefer just dropping >>> that one & keep those two old ones: >>> - one just for macOS + another one for macOS, iOS & Android >>> >>> br, >>> Jani >>> >>>> >>>>> * For Windows Android start doing Android Windows build with MinGW53 >>>>> * Start supporting QNX 7.0 >>>>> >>>>> -- >>>>> Alex >>>>> >>>>> _______________________________________________ >>>>> Development mailing list >>>>> Development@qt-project.org >>>>> http://lists.qt-project.org/mailman/listinfo/development >>>> >>>> -- >>>> Jake Petroules - jake.petrou...@qt.io >>>> The Qt Company - Silicon Valley >>>> Qbs build tool evangelist - qbs.io >>>> >>>> _______________________________________________ >>>> Development mailing list >>>> Development@qt-project.org >>>> http://lists.qt-project.org/mailman/listinfo/development >>> _______________________________________________ >>> Development mailing list >>> Development@qt-project.org >>> http://lists.qt-project.org/mailman/listinfo/development >> > > -- > Jake Petroules - jake.petrou...@qt.io > The Qt Company - Silicon Valley > Qbs build tool evangelist - qbs.io >
_______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
