error: cast from '...' to 'long int' loses precision [-fpermissive] #6827
Description
System Information
- Compiller: MinGW64 8.1.0 (sjlj/posix)
- Operating System: Windows 7 x64
- IDE: CodeBlocks 17.12
Description of error
Doxygen sources has successfully configured with CMake (but with changes because of issue #6786).
Similar errors occur when compiling:
error: cast from '...' to 'long int' loses precision [-fpermissive]
Compilling log
||=== Сборка: all in doxygen (compiler: GNU GCC Compiler) ===|
C:\Work\SDK\Apps\Doxygen_source\qtools\qcstring.cpp||In member function 'QCString QCString::simplifyWhiteSpace() const':|
C:\Work\SDK\Apps\Doxygen_source\qtools\qcstring.cpp|346|error: cast from 'char*' to 'long int' loses precision [-fpermissive]|
C:\Work\SDK\Apps\Doxygen_source\qtools\qcstring.cpp|346|error: cast from 'const char*' to 'long int' loses precision [-fpermissive]|
C:\Work\SDK\Apps\Doxygen_source\qtools\qcstring.cpp||In function 'int qstricmp(const char*, const char*)':|
C:\Work\SDK\Apps\Doxygen_source\qtools\qcstring.cpp|574|error: cast from 'const uchar*' {aka 'const unsigned char*'} to 'long int' loses precision [-fpermissive]|
C:\Work\SDK\Apps\Doxygen_source\qtools\qcstring.cpp|574|error: cast from 'const uchar*' {aka 'const unsigned char*'} to 'long int' loses precision [-fpermissive]|
C:\Work\SDK\Apps\Doxygen_source\qtools\qcstring.cpp||In function 'int qstrnicmp(const char*, const char*, uint)':|
C:\Work\SDK\Apps\Doxygen_source\qtools\qcstring.cpp|588|error: cast from 'const uchar*' {aka 'const unsigned char*'} to 'long int' loses precision [-fpermissive]|
C:\Work\SDK\Apps\Doxygen_source\qtools\qcstring.cpp|588|error: cast from 'const uchar*' {aka 'const unsigned char*'} to 'long int' loses precision [-fpermissive]|
[qtools\CMakeFiles\qtools.dir\build.make|91|qtools/CMakeFiles/qtools.dir/qcstring.cpp.obj] Error 1|
[CMakeFiles\Makefile2|145|qtools/CMakeFiles/qtools.dir/all] Error 2|
[C:\Work\SDK\Apps\Doxygen_build\Makefile|162|all] Error 2|
||=== Build неудачно: 9 error(s), 0 warning(s) (0 minute(s), 0 second(s)) ===|
Conclussion
I probably know how to fix that, so I will provide a pull request