Skip to content
  • dt's avatar
    Use exact and aysnc .pro file evaluate · ab8fc52d
    dt authored
    This is a big change touching almost all of our .pro file parsing.
    With this patch we only evaluate once exact for all needs and once
    greedy for the filelist. That is the qt runconfigurations don't have own
    evaluaters but reuse the project wide exact evaluation.
    We reevaluate if the user changes the build directory, the qmake
    buildconfiguration or the qmake arguments. That is if you open
    (or of qt with a shadow build you still don't get all the
    files, but after correcting the build directory, we reevaluate the .pro
    files and find all files. So for a suitable definition of fixed, that
    bug is now fixed.
    We now get the exact defines of all .pro files instead of all defines for all
    buildconfigurations. We still don't distinguish in which
    .pro file a DEFINE is set. So the code model now knows about all the
    defines set for the given configuration but not for which files it is
    actually set. Also that includes all DEFINES set in .qmake.cache or the
    mkspecs. This means all defines from .pro files should now work.
    The intial loading is still synchronous. I haven't looked into it to
    deeply, but it seems possible to make it also async.There are probably a
    few issues which need to be solved fist.
    Also due to the asynchronous nature of the code, the executable is
    updated a few seconds after actually changing the build configuration