Fix hard coded kit name path and make building a lot easier v2 #3
Conversation
coding kit name paths for dependencies.
|
This replaces my old pull request at #1 |
|
Hey doug65536 ! :) Thanks you very much for this commit ! It does make sense to regroup both project together this way :) However, I just tested and this is what I have : No rule to make target 'C:/Users/James/Desktop/build-QtSnap-Desktop_Qt_5_4_0_MinGW_32bit-Debug/QtSnap-DemoApp/../QtSnap-Library/libQtSnap-Library.a', needed by 'debug\QtSnap-DemoApp.exe'. Stop. The issue is in the pro file, you forgot to add a check for the debug/release folder :) |
|
Are you cleaning the build directory and opening the top level QtSnap.pro? (The cleaning should only be necessary once) |
|
I chose not to have separate debug and release folders, it adds a wall of ugly mess to the qmake. If you want that, I can update the pull request to use separate directories. |
|
Yep the top level QtSnap.pro is open ;) How should seperate release/debug folder be disabled then ? It just does it automatically on my side |
Use qmake subdirs project to properly handle dependencies and avoid hard coding kit name paths for dependencies.