Hi all,
I recently installed a new compiler from winlibs after much research into 32-bit executable formats (x86) and processor architectures. I experienced some trouble working with a certain .dll and thought it best to go the route of working with 32-bit compiling. I first tried going the route of using a distribution of MinGW with SJLJ exception handling which did not end well, and finally decided to work with a 32-bit compiler instead. All is working well--no troubles; but I notice that when compiling programs within codeblocks there is a string of text at the top of the build log that references an include path left over from my previous actions. Having re-installed the program and ensuring that all search directories do not include this path, I do not see the cause of this text appearing.
i686-w64-mingw32-g++.exe -Wall -Wall -m32 -g -Wall -m32 -g -IC:\mingw64_sjlj\x86_64-w64-mingw32\include
The second entry shows the extraneous text.
-nore
I don't see anything in the config file regarding the error either:
<gcc>
<NAME>
<str>
<![CDATA[GNU GCC Compiler]]>
</str>
</NAME>
<COMPILER_OPTIONS>
<str>
<![CDATA[-Wall;-m32;-g;]]>
</str>
</COMPILER_OPTIONS>
<LINKER_OPTIONS>
<str>
<![CDATA[-m32;]]>
</str>
</LINKER_OPTIONS>
<MASTER_PATH>
<str>
<![CDATA[C:\mingw32]]>
</str>
</MASTER_PATH>
<C_COMPILER>
<str>
<![CDATA[i686-w64-mingw32-gcc.exe]]>
</str>
</C_COMPILER>
<CPP_COMPILER>
<str>
<![CDATA[i686-w64-mingw32-g++.exe]]>
</str>
</CPP_COMPILER>
<LINKER>
<str>
<![CDATA[i686-w64-mingw32-g++.exe]]>
</str>
</LINKER>
</gcc>
The build log seems to include the old compiler directory as a path (-I) though it is not included in codeblocks' global directory or project-specific build options.
This pinpoints the issue.
i686-w64-mingw32-g++.exe -o bin\Debug\console.exe obj\Debug\main.o -m32 -m32
Output file is bin\Debug\console.exe with size 121.67 KB
I will look around in the project files.