-
Pierre Rossi authored
This should allow us to have much better integration by generating the necessary gyp files directly from qmake. Mostly works for now, though we will most likely need to build the gyp generation as we go. * Out dir logic is still crap and needs to be (re)worked. * In the same vein, we probably don't want the generated gyp content ending up in the source tree in the long run, which could prove tricky with relative paths to sources and all.
3300873b
# This is a dummy .pro file used to extract some aspects of the used configuration and feed them to gyp# We want the gyp generation step to happen after all the other config steps. For that we need to prepend# our gypi_gen.prf feature to the CONFIG variable since it is processed backwardsCONFIG = gypi_gen $$CONFIGTEMPLATE = libTARGET = blinq# Defining keywords such as 'signal' clashes with the chromium code base.DEFINES += QT_NO_KEYWORDSQT += gui-privateSOURCES = \ blinqpage.cppHEADERS = \ blinqpage.h