Author Topic: New compiler, old compiler information left in code::blocks build log.  (Read 2351 times)

Offline nore

  • Multiple posting newcomer
  • *
  • Posts: 20
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.

Code
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

Offline stahta01

  • Lives here!
  • ****
  • Posts: 7607
    • My Best Post
Re: New compiler, old compiler information left in code::blocks build log.
« Reply #1 on: December 23, 2023, 04:51:39 pm »
Check the global compiler settings.

Settings -> Compiler ->

Edit: Check the project compiler settings

Project -> build options ->

Tim S.
« Last Edit: December 23, 2023, 04:54:25 pm by stahta01 »
C Programmer working to learn more about C++ and Git.
On Windows 7 64 bit and Windows 10 64 bit.
--
When in doubt, read the CB WiKi FAQ. http://wiki.codeblocks.org

Offline nore

  • Multiple posting newcomer
  • *
  • Posts: 20
Re: New compiler, old compiler information left in code::blocks build log.
« Reply #2 on: December 27, 2023, 12:04:03 am »
I didn't see any left over compiler information is the project/build options.

Offline stahta01

  • Lives here!
  • ****
  • Posts: 7607
    • My Best Post
Re: New compiler, old compiler information left in code::blocks build log.
« Reply #3 on: December 27, 2023, 03:18:36 am »
If you post a full re-build log, someone might see something.

Or, you can just delete the Code::Blocks config files when C::B is shutdown and that would likely fix the stuff you did and forgot where you did it.
Edit: Add FAQ link https://wiki.codeblocks.org/index.php/FAQ-Settings#Q:_Where_does_C::B.27s_configuration_file_store.3F_How_do_I_make_Code::Blocks_portable.3F
Edit2: Remember to do all the toolchain settings needed.

Tim S.
« Last Edit: December 27, 2023, 05:57:59 am by stahta01 »
C Programmer working to learn more about C++ and Git.
On Windows 7 64 bit and Windows 10 64 bit.
--
When in doubt, read the CB WiKi FAQ. http://wiki.codeblocks.org

Offline nore

  • Multiple posting newcomer
  • *
  • Posts: 20
Re: New compiler, old compiler information left in code::blocks build log.
« Reply #4 on: December 27, 2023, 07:15:50 pm »
I don't see anything in the config file regarding the error either:
Code
			<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.

Offline stahta01

  • Lives here!
  • ****
  • Posts: 7607
    • My Best Post
Re: New compiler, old compiler information left in code::blocks build log.
« Reply #5 on: December 28, 2023, 12:04:00 am »
Create a new project and see if the include still exists.
If it does not you know the problem is located in the project file.

Tim S.
C Programmer working to learn more about C++ and Git.
On Windows 7 64 bit and Windows 10 64 bit.
--
When in doubt, read the CB WiKi FAQ. http://wiki.codeblocks.org

Offline nore

  • Multiple posting newcomer
  • *
  • Posts: 20
Re: New compiler, old compiler information left in code::blocks build log.
« Reply #6 on: December 28, 2023, 12:49:03 am »
This pinpoints the issue.
Code

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.

Offline nore

  • Multiple posting newcomer
  • *
  • Posts: 20
Re: New compiler, old compiler information left in code::blocks build log.
« Reply #7 on: December 28, 2023, 01:03:25 am »
The issue has been solved. After selecting the "Properties..." option for the project and then "Project Build Options" I received a message stating that the old compiler could not be found. Selecting the new compiler displayed the standard project-wide compiler options where I could navigate to the search directory and clear out any old information.