Ok I understand. Thank you!

Adding to @JKSH, the qml option expects the path to the files in your project sources so it can parse them to pull all the required dependencies.

If you did something like CONFIG = debug You, in fact, nuked the content of the variable and replaced it with debug. If you want to modify the content of such a variable, use either += or *=. The first to add a value and the second to add the value only if not already in the variable.

Great ! Since you have it working now, please mark the thread as solved using the "Topic Tools" button so that other forum users may know a solution has been found :-) In case, there's an answer that provides the correct hint, you can also use the three button menu to mark it as the correct answer.

Oops! It worked in my last attempt, although it look a long time. So, my problem was Emscripten's version after all. Here is the version that worked: emscripten-1.37.1 Note: I've used emsdk to install Emscripten and I had to install a matching LLVM/CLang version: clang-e1.37.1-64bit

@ambershark oki, i appreciate your attention

Remove the -j 8. The error is somewhere else. These are just warnings.

@VRonin said in QCA no Makefile: also, if you are using MSVC you have to tell cmake to generate makefiles instead of project files. Pass the -G "NMake Makefiles" arguments to your cmake call You sir, have saved me. I can't believe they don't specify that in the guide (it also uses MSVC, so idk why there wasn't the same problem). I've run into some trouble while building, but that can/should be its own topic. @VRonin said in QCA no Makefile: Slightly related, is QCA supported and updated? The last thing you'd want is to use an out of date cryptographic library. I normally use Crypto++ but libcrypto of OpenSSL is also very good (if you don't mind messing with C) It is still active, looking at the the git (https://cgit.kde.org/qca.git/) the last commit was in 2017-09-30 (some months ago, but it isn't dead). I had also been looking at Crypto++, but ended up settleing for QCA for no pacticular reasons. And I wouldn't mess with C, I'm still even just a C++ newbie afterall ;) QCA can also use OpenSSL btw.

@no_ideaw Can you show your pro file? Also did you run qmake and rebuild your project after changing Kit to "Android for armeabi-v7a"?

@Pamplemousse-MK-2 When you are entering this on each machine where the creator is used, it will apply to all projects on that machine. Eventually you need to check whether it is updated for all projects already loaded in created. New projects are taking over those system environment settings.

@SGaist Thanks for your help.. it's successfuly got connected finally.. i changed localhost\sqlexpress to localhost and it got connected.. what ever sqlexpress is there for. Thanks again

@dridk2 Great news! Happy coding. :)

@tomy Did you realize that you are looking in the wrong directory? MinGW is in c:\Qt\Tools\mingw492_32\bin! You should be more proactive and look by yourself instead of asking for exact answers. You can search in Windows-Explorer for *make*.exe On my machine I get 4 hits one of them is mingw32-make.exe

I had the same problem, solved it by making a new compiler that uses the generated header file as input and runs moc on it to generate the missing source file. From my .pro: dbc2cpp_canbus_h.name = Generating canbus.h from DBC file. dbc2cpp_canbus_h.CONFIG += combine dbc2cpp_canbus_h.input = "DBC_A_C" dbc2cpp_canbus_h.output = canbus.h dbc2cpp_canbus_h.commands = bash -c 'dbc2cpp --target CANBUS_H CLUSTER <($${DBC_A_GIT}) <($${DBC_C_GIT})' dbc2cpp_canbus_h.variable_out = HEADERS QMAKE_EXTRA_COMPILERS += dbc2cpp_canbus_h CANBUS_H = canbus.h new_moc.commands = moc $(DEFINES) $(INCPATH) canbus.h -o ${QMAKE_FILE_OUT} new_moc.input = "CANBUS_H" new_moc.output = moc_canbus.cpp new_moc.variable_out = SOURCES QMAKE_EXTRA_COMPILERS += new_moc

I never got around to solve this issue, so due to time constraints i reverted to compile natively on the Raspberry Pi.

Hi, Did you configure Qt Creator to find your Android/Java stuff ?

Hi and welcome to devnet, While it might be doable, I'd recommend using a build manager either CMake like suggested by @debian, QBS or qmake. You'll have an easier way to handle your project and its submodules (not to mention that it will also make your life easier if changing OS to build your project). Note that you can use qmake for non-Qt project without a problem.

Later to that, I have figured out a problem in having: We need to have \" in the argument: -DBOO_PATH="/path/to/boost" Problem is that, the macro turned out to be #define BOO_PATH /path/to/boost which is actually useless. We need to have double quotes to cover them up. BOOST = $ $ ( BOOST_PATH ) BOOST_STR = ' \ \ " $ $ { BOOST } \ \ " ' DEFINES += BOOST_PATH=\ " $ $ { BOOST_STR } \" Again, eliminate the spaces :)