Skip to content
  • UI changes not reflecting when debugging

    Solved General and Desktop shadow build exceptions
    6
    0 Votes
    6 Posts
    2k Views
    osirisgothraO
    Occasionally I encounter similar problems. On occasion the project.pro.user file gets corrupted which can cause undesired behavior. In that case, removing the build directory is not enough. This is because clean essentially removes the build files. But if the project configuration is telling build to clean/compile things the wrong way, it makes sense removing it would not help. Removing the pro.user file should, though you will need to reconfigure a little (unless you want to check through it which is a pain). I found just deleting it and letting QtCreator regenerate it fixes most problems. I have yet to need to remove the .pro file, but that would be a last resort. I recommend to stick with qmake to make things simpler for your users until you absolutely need something beefier (unless your build team has a hard-set build environment). Making major changes to project settings is a great way to mess things up, you'd be surprised. Some settings have effects on certain project configurations that are not always spelled out in the documentation, if at all. Notice that "QtCreator The Application(tm)" does not have the greatest level of detail in its shipped documentation, and glosses over many of its features giving you just the bare minimum detail on some (but not all) items. I have noticed, however that it is slowly getting better. I think we just need more people contributing :3. Including the top page, the "Qt Creator Documentation" has a rather small number of (13) pages(!) which is hardly enough room to describe every single item within QtCreator. The number 13 is an unlucky number indeed. :3
  • 0 Votes
    2 Posts
    535 Views
    mrjjM
    Hi [image: XmvLBm.png]
  • Shadow build failure for iOS

    Solved Mobile and Embedded ios qt creator shadow build
    4
    0 Votes
    4 Posts
    2k Views
    SGaistS
    Hi, Because you didn't ask a question ;) Click on the "Topic Tools" button, there you'll see "Ask as question", then click again and you should get the usual mark as solved stuff.
  • 0 Votes
    3 Posts
    2k Views
    Q
    Whew! I think I got it... The mistake was to use the includes of shared \build_dev when building in release. There is only one little difference which made everything work: qconfig.h! It defines QT_STATIC in the static \build_app1 ... The debug config of the project created by the Qt Add-in has to be adjusted a little though: Include directory $(QTDIR$)\include =>...\build_dev\qtbase\include. Lib directory $(QTDIR$)\lib =>...\build_dev\qtbase\lib. The project still uses \build_app1\qtbase as Qt Version. That way, the Debug build looks for includes and libs in \build_dev while the Release build looks in \build_app1. And the .lib symlinks are not necessary anymore, I just kept the bin directory symlink. Just in case someone else wants to do something like this...
  • 0 Votes
    6 Posts
    3k Views
    SGaistS
    You're welcome ! Svn allows some interesting things like the use of properties that can simplify some handling for e.g. your files header.