Hi, One thing that you could try is to add a custom target that will call windeployqt on your target. Something a bit like the tests target when using Qt's unit tests module. Hope it helps

@TioRoy Na verdade, quando eu digo "arquivos avulsos" eu me refiro a arquivos de código. Exemplo, Add New...>>Files and Classes não é possível em subdirs somente em projects. Minha ideia é a da imagem em anexo aqui Ou seja, funcionario e tecnico são projetos do tipo static lib. Assim sendo cada classe da modelagem UML que representa um objeto na regra de negocio será uma biblioteca estática. Não sei se essa é a melhor abordagem.

As soon as paths or library names differ, you will have to use scoped declarations. Otherwise it really does not matter. Win32 also links correctly using -lSomeCoolLib, therefor you could just use one LIBS directive.

Almost yes. Now I use $$PWD/../3rdparty/assimp-3.1.1/include(2x '$') for all platforms, including Android, but I still can't build my .pro for it. For using $PWD I should set it to the right value in Projects->Build Environment, for each kit separately, right?

Well, I tried compiling the source from scratch with a fresh source, and it works like a charm for some reason. Problem Solved.

I have found a reason, why LD_LIBRARY_PATH, CPLUS_INCLUDE_PATH and LIBRARY_PATH variables were ignored by QtCreator: I use KDE and it does not load the .bashrc in the session, but the bash does. So in KDE when you open Konsole - your environment is populated from .bashrc, but other apps, not launched from console - have different environment. So for me the solution was to create $HOME/.kde/env/user.sh file like this: #!/bin/bash if [ -f ~/.username.bashrc ]; then . ~/.username.bashrc fi ~/.username.bashrc contains my environment variables.