[Scons-users] Error when passing from python 3.5.4 to python 3.6

Mats Wichmann mats at wichmann.us
Fri Jul 24 17:14:11 EDT 2020

On 7/24/20 2:32 PM, Pierre-Luc Boily wrote:
> I'll take a step back.  I would like very much to use the default
> builder's behavior.  But, the default uic builder uses those tree actions : 
> Action 1 generates the header file:
> [['$QT_UIC', '$QT_UICDECLFLAGS', '-o', '${TARGETS[0]}', '$SOURCE'], 
> Action 2 generates a useless file in our case:
> ['$QT_UIC', '$QT_UICIMPLFLAGS', '-impl', '${TARGETS[0].file}', '-o',
> '${TARGETS[1]}', '$SOURCE'], 
> Action 3 generates the moc out of the header from the action 1.
> ['$QT_MOC', '$QT_MOCFROMHFLAGS', '-o', '${TARGETS[2]}', '${TARGETS[0]}']]  
> and action 2 is not working for us  because of the -impl argument that
> is obsolete for our version of qt (5.12)
> I did a quick research about -impl.  It looks like that this argument is
> for qt3 :  https://doc.qt.io/archives/3.3/uic.html  .  UIc man page for
> qt5 is not talking about this argument at all
> Moreover, qt4 and qt5 scons tool from dirk are not using -impl argument
> either. 
> So, in retrospect, I think that what I need is a clarification about the
> default Uic builder on why it uses -impl. This argument looks obsolete
> in qt4/qt5.  I searched in scons documentation if there is something
> where I could specify qt version.  No luck.  
> Maybe a mechanism is needed to have one builder for qt3 and another one
> for qt4/qt5 ?
> thx

it sounds like the setup in the tool module needs to be somewhat
version-aware.  This is not actually unusual: e.g. java also needs to do
some different things depending on Java version (some of that not
implemented yet).

More information about the Scons-users mailing list