Installation and Deployment

@MHermann Stuck with exact same problem. Can you be more specific on how you solved it? i don't understand the solution you put down here. can you be detailed?

I noticed that the .dmg file has been recreated after I posted. The new version works normally, just like it always did. Thanks. SGaist: Fusion drive (the Mac's from 2012.) ambershark: thanks for the -nomount trick. I'll keep it in mind next time I hit an issue like this.

Hi @Zueuk, please don't delete your post after the issue is resolved. Keep it there so that other people with the same problem can understand the solution.

No worries ! Don't forget to update this thread when you get an answer so other people can benefit from it :)

I was compiling qt5.9.3 with vs2017 and always get error. Can you tell me your step to compile source code ?

Thanks for your tip.I fixed it by selecting opengl option.

Hi, Glad you found out and thanks for sharing ! Did you also installed the MySQL client dev package ? If not, it might explain the missing symlink you had.

Have you installed Qt as root user? I'd rather recommend using standard user, and install it locally.

@BINALECTRUM said in Android build and deploy. 64bit, Clang, new app store developer console rules [2018 & 2019]: Is Qt going more in embedded/car side and just slowly drops Android/mobile platform? In Roadmap 2018 there is nothing new about mobile platform. i heavily doubt that. I guess the reason is more because Qt runs more or less stable on Android. There are no bigger features which need to be implemented, mostly bug fixing. What is your move Qt team on new app store rules in developer console: minimal platform-26 in August 2018 and 64-bit apk in 2019? Some new changes in build and deploy area? i asked this at the beginning of the year, but unfortunately haven't received an answer.

Hi jiancaiyang, Thanks for your answer. Do you mean qt examples? I studied all of them. But this issue is not covered. The core problem is: We need to register some logic before requesting the first respository. There is indeed some examples explaining how to register pages. But they all register pages within a package. Unfortunately, this is not what we need.

There is no easy way to do customize those windows. You would have to write your own installer. Installers in general are boring and people tend to just fast click through it to get the software installed. If it were me I wouldn't put much time into your installer. As long as it works nobody cares how fascinating it is. They'll only ever see it once and briefly at that. :)

@JosephTLyons If you used the installed for Qt 4.2 then it probably exists in a single directory. So just like anything else on OSX you can just delete that directory and should be all uninstalled. If there is a dir outside the /Applications directory you may need to clean that up too. Sorry not 100% sure here since all my OSX Qt installs were built from source so I don't know how the installer works on OSX. On Linux it's a single directory. Anyway, once /Applications/Qt* is deleted you should be ready to do the install from Qt 5.11. Qt4 and 5 rarely play nice together in my opinion so a nice clean install would be a good idea. You can make them work on the same system but in my experience on these forums people mix their dylibs all the time and get weird behavior, crashes, failures to load, etc. So if you want them both for some reason just make sure they stay separate.

I can't imagine that would make any difference. I redefine the folder to libs, so lib should be irrelevant. Also I am 100% sure I tried that anyway.

@Or-Hirshfeld This thread is a year old, lol. If you read my answers to his questions you'll get the answer for yours as well. TLDR: you are mixing 2 versions of Qt.

Update of Qt version ? Update of OpenSSL ?

You need a compiler, no doubt about it. However the screenshot shows you have VS2015 installed, while the kit name from the first post suggest you're using a Qt version built for VS2013. This is not a possible and valid combination with MS's compiler, the versions should match. So you need to reconfigure the kit (possibly download a matching Qt version) so the compilers match. Refer to the QtCreator documentation for more information on the matter.