Databases
StackOverflow2013
Postsdbo
POQMake does not update subdir makefiles
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POQMake does not update subdir makefiles
    primarykey
    data
    text
    <hr> <h2><strong>Issue</strong></h2> <p>I am working on a multi-executable QT project using qmake in conjunction with QT Creator. Each executable has its' own .pro file, all of which are included in an over-arching .pro file (template=subdirs). Each individual .pro file also includes a common .pri file which sets DESTDIR so that all the executables end up in the same place. This DESTDIR is dependent on whether it is being compiled as debug or release. This has worked wonderfully until we added a collection of executables via another subdir .pro beneath the over-arching one. The overall setup looks something like this:</p> <ul> <li>All.pro</li> <li>| - Project1.pro</li> <li>| - Project2.pro</li> <li>| - Subdirs.pro</li> <li>| -- | - Project3.pro</li> <li>| -- | - Project4.pro</li> </ul> <p>If you have a freshly checked out copy, you can run qmake and all will work, until you switch from debug to release, or vice-versa. When you do, Project1.pro and Project2.pro update just fine and put their executables in the right directory, but Project3.pro and Project4.pro use the old directory.</p> <hr> <h2><strong>Attempts</strong></h2> <p>If I manually remove all the affected makefiles, qmake will generate new ones. I suppose I could write some sort of a pre-compile command to remove all makefiles every time, but that seems like the wrong way to do things, let alone the amount of time I would have to spend making sure it worked on all our platforms.</p> <p>I have tried this in QT 4.6.4 through 4.8.1</p> <p>When I use QT Creator, I switch between Debug and Release modes via differing build configurations which mimics what I do on the command lie (ie adding or removing CONFIG+=debug)</p> <hr> <h2><strong>Questions</strong></h2> <ul> <li>What is preventing qmake from updating the makefiles?</li> <li>If it is just a bug in qmake, what is the best workaround?</li> </ul> <hr> <p>Any and all help is greatly appreciated.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USTsubashi
    1. USTsubashi
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POQMake does not update subdir makefiles
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POQMake does not update subdir makefiles
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POQMake does not update subdir makefiles
      1. This table or related slice is empty.
      1. VTUpMod
    1. COCan you add more information about how you are switching between release and debug? Is it via QtCreator or command line? If command line, what commands in particular? Do you run any custom targets to switch?
      singulars
      1. POQMake does not update subdir makefiles
      1. USCaleb Huitt - cjhuitt
    2. COI have updated the question to include that.
      singulars
      1. POQMake does not update subdir makefiles
      1. USTsubashi
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload