Tour Preview

Find the Best Demos and Examples

Check out this quick tour to find the best demos and examples for you, and to see how the Felgo SDK can help you to develop your next app or game!

Forums

OverviewFelgo Installation › Installation error: qmake

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #21662

    Gabor

    Hi,

    I had to reinstall Qt. During the installation I got the following warning from Webroot:

    Filename: qmake.exe
    Malware type: Trojan.Monero.Coinminer

    I proceeded two ways:

    1. I used Webroot’s recommendation and removed qmake.exe
    2. I did not remove qmake.exe.

    Either way I got the following error messages when I tried to build or run (either C++ or QML):

    system.cpp:-1: error: undefined reference to `_imp____acrt_iob_func’
    system.cpp:-1: error: undefined reference to `_imp____acrt_iob_func’
    system.cpp:-1: error: undefined reference to `_imp____acrt_iob_func’
    b2Settings.cpp:-1: error: undefined reference to `_imp____acrt_iob_func’

    What can I do now?

    Thank you for your help.

    #21664

    Alex
    Felgo Team

    Hi,

    regarding the coinminer warning, this is obviously a false positive. Thanks for reporting though, we can forward this to the Qt team.

    Regarding the undefined reference, there are 2 potential solutions that you can try:

    1. Delete the shadow build folder of your project. You can find the location of the shadow build folder of your active project in the “Projects” tab of Qt creator. After that, performs a clean and qmake, before building your project.
    2. If 1. does not solve the issue, close Qt Creator and delete the Qt Creator kit profile. You can find it in your AppData (e.g. C:\Users\YourUserName\AppData\Roaming\QtProject\qtcreator\profiles.xml). Note that AppData is a hidden folder that you might need to display first. Then you can re-open Qt Creator. To be sure, you can again delete the shadow build folder as explained in 1. and perform a clean build.

    The reference errors can come from the build caching or Qt Creator kit caching, which should be solved with the steps above.

    Let me know if that helps.

    Cheers,
    Alex

    #21671

    Gabor

    Thank you Alex. The second solution solved the problem.

Viewing 3 posts - 1 through 3 (of 3 total)

RSS feed for this thread

You must be logged in to reply to this topic.