Home/ Questions/Q 8331311
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-09T02:22:48+00:00

In our project, we added some source and header files if a MACRO is

  • 0

In our project, we added some source and header files if a MACRO is defined. We do this like that, in the .pro file:

contains(DEFINES, MY_DEF) {
message("Support MY_DEF")
INCLUDEPATH += \
    my_include_dir
SOURCES += \
    source1.cpp \
    source2.cpp
HEADERS +=  \
    my_include_dir/header1.h \
    my_include_dir/header2.h
FORMS +=  \
    myform.ui
}

This works fine during the build. The files are not compiled if MY_DEF is not defined. MY_DEF is defined like that:

DEFINES += MY_DEF

Curiously, Qt Creator always display the files in the project tree, whereas MY_DEF is defined or not. If not defined, they are not used for the build, but they still are displayed and editable, searches can scan them, etc… Is it a bug of Qt Creator?

This is not a big issue, just a little annoying, because we don’t know clearly if a file is part of the project or not.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    This seems to be an issue with QtCreator and how it reads the .pro files – it doesn’t seem to actually fully parse the files, opting instead to just pick out certain bits. I’ve got the same issue with files that are only included on one platform or another – in QtCreator, they always show up.

    I expect that the reason is either that they don’t want to re-implement half of qmake just to get the file lists, OR that there are situations where trying to parse it ‘correctly’ would get the wrong answer, and they’ve chosen to be predictably wrong instead of randomly wrong.

    • 0