User forums > Nightly builds

The 16 September 2014 build (9916) is out.

<< < (5/8) > >>

scarphin:
I've been experiencing the weird error in the attachment. 'mingw-builds' is my default compiler which is also in the system path. I also have a tdm-4.8.1 installation which has its own entry in CB compiler settings. Steps to reproduce:

1- Load the 'CodeBlocks.cbp'
2- Change compiler to the tdm-4.8.1 for the whole project
3- Save project

It keeps popping up until I close CB and everything goes back to normal if I revert 'CodeBlocks.cbp' to its default. I do have the 'libiconv-2.dll' in tdm binary folder if that should help anything. I can't come up with any reason why the 'cc1plus.exe' is launched after saving the project?

Win7 SP1 x64
I'm using the official 9916 nightly

ollydbg:

--- Quote from: scarphin on October 06, 2014, 01:35:19 am ---I've been experiencing the weird error in the attachment. 'mingw-builds' is my default compiler which is also in the system path. I also have a tdm-4.8.1 installation which has its own entry in CB compiler settings. Steps to reproduce:

1- Load the 'CodeBlocks.cbp'
2- Change compiler to the tdm-4.8.1 for the whole project
3- Save project

It keeps popping up until I close CB and everything goes back to normal if I revert 'CodeBlocks.cbp' to its default. I do have the 'libiconv-2.dll' in tdm binary folder if that should help anything. I can't come up with any reason why the 'cc1plus.exe' is launched after saving the project?

Win7 SP1 x64
I'm using the official 9916 nightly


--- End quote ---

when you save project，codecompletion will fire a reparse which call compiler to fetch proprocessor directs.

scarphin:

--- Quote from: ollydbg on October 06, 2014, 03:07:39 am ---when you save project，codecompletion will fire a reparse which call compiler to fetch proprocessor directs.

--- End quote ---
Now it makes sense. CC launches the designated compiler for the project but it cannot find the needed files to run as it is not in the system path (I just confirmed that the needed dll is not in my default compilers bin folder). Is there a way to overcome this like launching the designated compiler with its own path when CC calls it?

danselmi:
This is a bug in CC plugin.

The compiler plugin is able to call the compiler correctly.

scarphin:
Good to hear that as embedded compilers not in system path might result in the same error.

Navigation

[0] Message Index

[#] Next page

[*] Previous page