> On Mar 7, 2017, at 10:02 AM, ekke <e...@ekkes-corner.org> wrote: > > Am 07.03.17 um 18:55 schrieb Jake Petroules: >> Duplicate of an existing issue; see the link for details. > thanks > > so I can ignore these issues ?
Yes, they'll disappear in the next Qt release. > >> Also please note that these issues are related to Qt, not Qt Creator. >> >> In future please make sure to select the correct project when reporting >> issues, thanks! > sorry for that > I really have no idea when issues from build process are Qt Bugs or > QtCreator bugs > from some other QtCreator bugs I thought those things should be reported > there > > are there any rules or tips HowTo know (as a 'normal' mobile app > developer without deep knowledge of Qt build processes) where to report ? With regard to build issues: generally, if you can reproduce the issue when building on the command line, then it certainly goes in QTBUG. If an issue only occurs in Qt Creator, then it goes to QTCREATORBUG. > > thx > > ekke >> >>> ..... >>>>> :-1: warning: argument unused during compilation: '-fembed-bitcode-marker' >>>> https://codereview.qt-project.org/#/c/185931/ > > _______________________________________________ > Qt-creator mailing list > Qt-creator@qt-project.org > http://lists.qt-project.org/mailman/listinfo/qt-creator -- Jake Petroules - jake.petrou...@qt.io The Qt Company - Silicon Valley Qbs build tool evangelist - qbs.io _______________________________________________ Qt-creator mailing list Qt-creator@qt-project.org http://lists.qt-project.org/mailman/listinfo/qt-creator
