Installation and Deployment

im using qt 5.9 on mac this piece of code worked like charm for me brew install mysql-connector-c

I've been a fool! Needed to tick the compiler when installing - I didn't expand the Tools tab!

@jimmychau I've now discovered (thanks to a suggestion from a colleague) how to avoid this problem ! It turns out that building in the MS cmd.exe window works, where building in MinGW's Git Bash shell has the problem above. I won't pretend to understand why, but give cmd.exe a try !

I don't think it's a dependency issue but the error is indeed surprising...

Hi I also like this site for deployment info http://www.tripleboot.org/?p=138

@throtmax Try to delete the *.pro.user file in your project directory before opening it in QtCreator.

@name_qt said in Build QtCreator from source code: When this error comes, could you try make instead of make -j8 ? I assumed you are using make -j8 from the reference link you have given. the command is mingw32-make without argument "-j8"

@Kanguru Can you post the compiler/linker output? It looks like your app is not linked against QtChart lib.

make confclean But as I already suggested, do out of source builds and nuke the build folder as needed.

@JNBarchan Setting absolute path worked, thank you for your help.

@mrjj said in Building Qt 5 on Linux, for Windows: @cerr Hi And you did something like export PATH=<mxe root>/usr/bin:$PATH as mentioned in the link ? No, that actually was my problem! Thanks for pointing this out, I must have read over that comment...

Hi and welcome to devnet, Did you install all build dependencies for QtWebengine ? Also, why are you using 5.4.2 ? This version is outdated, you should upgrade to the latest version which currently is 5.9.2.

@mrjj Yeah, it does. I will try for the last time to stop the antivirus and see what will happen then. Anyway, thank you for your help.

Hi and welcome to devnet, The most simple is: avoid spaces in paths. One workaround: use the 8.3 notation.

when MACOSX10.13 was coming, the only way to fix is creating symbolic MacOSX10.13.sdk to MacOSX.sdk which is able to fix problem.

@JNBarchan oh thanks, I read this page but I didn't see that, thanks ! So I guess it's OK if I just copy them from my C:\Windows\SysWOW64 folder...

@AndersDK Not sure how to handle this (I don't do much on Windows). The correct runtime package from Microsoft must be installed on users machine. I do not know whether Microsoft allows to distribute this runtime. If not your installer could maybe download it from Microsoft if it is not installed and install then.