Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. General and Desktop
  4. Qmake TEMPLATE variable manipulation via command line interface
Forum Updated to NodeBB v4.3 + New Features

Qmake TEMPLATE variable manipulation via command line interface

Scheduled Pinned Locked Moved Solved General and Desktop
2 Posts 2 Posters 366 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • Patrick FrombergP Offline
    Patrick FrombergP Offline
    Patrick Fromberg
    wrote on last edited by Patrick Fromberg
    #1

    According to the documentation this variable can have value lib or app or subdirs or etc...
    Why is TEMPLATE += or TEMPLATE-= not a syntax error then? Those are operators on list variables.

    The documentation of the cli option -t explains that it overwrites the TEMPLATE variable after processing the pro file. What effect can any variable change have after processing is complete? "After proessing" sounds to me a little bit like "when it is to late"

    The documentation of the cli option -tp explains that this will add a prefix to the TEMPLATE variable. The documentation of the TEMPLATE variable does not say anything about a prefix. What would prefix.lib as TEMPLATE value mean? Just like the other option, will this be "after processing"?

    Ah and one additional question. Will qmake command line options applied to a subdirs project also recurse to the child projects?

    sierdzioS 1 Reply Last reply
    0
    • Patrick FrombergP Patrick Fromberg

      According to the documentation this variable can have value lib or app or subdirs or etc...
      Why is TEMPLATE += or TEMPLATE-= not a syntax error then? Those are operators on list variables.

      The documentation of the cli option -t explains that it overwrites the TEMPLATE variable after processing the pro file. What effect can any variable change have after processing is complete? "After proessing" sounds to me a little bit like "when it is to late"

      The documentation of the cli option -tp explains that this will add a prefix to the TEMPLATE variable. The documentation of the TEMPLATE variable does not say anything about a prefix. What would prefix.lib as TEMPLATE value mean? Just like the other option, will this be "after processing"?

      Ah and one additional question. Will qmake command line options applied to a subdirs project also recurse to the child projects?

      sierdzioS Offline
      sierdzioS Offline
      sierdzio
      Moderators
      wrote on last edited by
      #2

      @Patrick-Fromberg said in Qmake TEMPLATE variable manipulation via command line interface:

      Why is TEMPLATE += or TEMPLATE-= not a syntax error then? Those are operators on list variables.

      Most probably because nobody bothered to make it into an error.

      What effect can any variable change have after processing is complete?

      After parsing sounds better? I guess that is what they have meant.

      The documentation of the cli option -tp explains that this will add a prefix to the TEMPLATE variable. The documentation of the TEMPLATE variable does not say anything about a prefix. What would prefix.lib as TEMPLATE value mean? Just like the other option, will this be "after processing"?

      This is used on Windows to generate Visual Studio stuff, I think. More info https://stackoverflow.com/questions/1043294/qt-qmake-tp-vc-to-create-visual-studio-project-files

      Will qmake command line options applied to a subdirs project also recurse to the child projects?

      Yes, as far as I remember. Just try it out ;-)

      (Z(:^

      1 Reply Last reply
      2

      • Login

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • Users
      • Groups
      • Search
      • Get Qt Extensions
      • Unsolved