I sincerely want to thank you for your help! This project took six-months and your assistance was crucial in getting over the goal line in the final week. If I missed that hard deadline my six-month contract-to-hire would have been terminated. Partly because of your assistance I made it work and was hired full-time permanent! We shipped Version 1.0 and two weeks later I delivered a significant V1.1 follow up!.
I momentarily had it setup as a (static?)linked library but backtracked to direct #includes from the /common/ folder, mainly because I understood it better. I intend to switch again to the library method because of compile times as you suggested. I was also scared off by an article suggesting I would need to add C++ #EXTERN statements, etc. to create a public interface for the library. Is that true, or can the .pro/.pri files define that folder as a library with NO changes to the C++?
I still have to migrate *.qml files to the /common/ but I assume it's basically the same pattern as the C++. I haven't replied because I thought I had more questions but the project has been moving too rapidly.
Juste an update on this issue for anyone it could help.
The issue came from the INCPATH section of the makefile. Though similar beetween makefile.debug and makefile.release it seems that the compiler (or linker) could not interpret relative path ('../../../') when in release mode (whereas it works ok in debug). I could not find a solution to directly fix this issue so I now modify the makefile once created/updated in order to replace occurences of relative paths by absolute path. This is done using a batch file that I execute after the qmake.exe step (step added in the compilation steps of the project configuration)
Hi, I am developing a game engine edtior using QT for UI and GLFW for rendering.I am searching the experience who had soloved to get it quickly.So, could you tell me how did you solved this.Thank you in advance.
my friends,i had a similar case and found this happens when you mix different versions of Qt to compile the project
they simply change the ui_*.h files or sometimes they empty it and thus this happens. Occured at least with me ..
I'm not sure for the zip source package, but at least for the sources installed from the online installer the headers of QtMultimedia are placed next to qbase directory, not inside it.
Also, to make your life easier you should use a prefix in your configure step and after compilation call 'nmake install' i.e.
This would build Qt in the current directory and then copy over everything needed in their right places to the prefix directory. You can then safely delete the build directory and save a lot of space, since it contains all the intermediate build artifacts that you don't need. All the includes would be placed in a single <prefix dir>\include directory for you, such as they are in the precompiled packages.