Important: Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

QT Compiler errors using NMAKE + _CRT_SECUR E_NO_WARNINGS



  • Where do I input this define: _CRT_SECURE_NO_WARNINGS?

    I am getting errors while building qt. My config flags are:
    configure -release -nomake examples -nomake demos -no-exceptions -no-stl -no-rtti -no-qt3support -no-scripttools -no-openssl -no-opengl -no-webkit -no-phonon -no-style-motif -no-style-cde -no-style-cleanlooks -no-style-plastique -plugin-sql-mysql -I C:\mysql\include -L C:\mysql\lib -l libmysql -nomake tests

    Error is:

    .\tokenizer.cpp(480) : warning C4996: 'strcpy': This function or variable may be
    unsafe. Consider using strcpy_s instead. To disable deprecation, use _CRT_SECUR
    E_NO_WARNINGS. See online help for details.
    C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\INCLUDE\string.h(7
    4) : see declaration of 'strcpy'
    .\tokenizer.cpp(568) : warning C4996: 'strcpy': This function or variable may be
    unsafe. Consider using strcpy_s instead. To disable deprecation, use _CRT_SECUR
    E_NO_WARNINGS. See online help for details.
    C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\INCLUDE\string.h(7
    4) : see declaration of 'strcpy'
    .\tokenizer.cpp(569) : warning C4996: 'strcpy': This function or variable may be
    unsafe. Consider using strcpy_s instead. To disable deprecation, use _CRT_SECUR
    E_NO_WARNINGS. See online help for details.
    C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\INCLUDE\string.h(7
    4) : see declaration of 'strcpy'
    yyindent.cpp
    NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio 9.0
    VC\BIN\cl.EXE"' : return code '0x2'
    Stop.
    NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio 9.0
    VC\BIN\nmake.exe"' : return code '0x2'
    Stop.
    NMAKE : fatal error U1077: 'cd' : return code '0x2'
    Stop.
    NMAKE : fatal error U1077: 'cd' : return code '0x2'
    Stop.



  • I'll try building using O1 instead of O2 for release optimization. Hope this will work.



  • Ok now I get real errors about
    'isalpha'
    'isalnum' etc identifier not found???


Log in to reply