Linker errors aren't treated as errors.

[marfi]

Hi Eran,
there is serious problem dealing with linker errors in the CL (and it exists here for a long time....). You surely know that linker errors aren't treated as compiler errors. It means that they aren't highlighted in the Output panel (which is a minor bug) and they don't increase total number of build errors (it is serious and confusing, because build summary tells the user that there are no errors which obviously isn't true). This confusing behaviour can lead to situation when user tries to run application which is seemingly built, but it isn't. Even more dangerous is this situation on Windows, where closing of application's terminal/launcher doesn't imply closing of the application itself. In this case the application remains loaded and active in the memory and next build will fail because of disabled write permissions on this runnig application. So, the solution of this bug should be as follows (in my opinion:)
1) Treat the linker errors in a proper way
2) Force closing of runing application if its launcher terminal window is closed manualy by a user also on Windows.

Best regards
Michal

[eranif]

I am aware of the link error is not detected as error.

See here:
http://codelite.org/RoadMap/Main - in the Compiler /Build Settings

For the second one, please open a bug/FR at SF

Eran

[marfi]

I am aware of the link error is not detected as error.

See here:
http://codelite.org/RoadMap/Main - in the Compiler /Build Settings

I'm really looking forward for all the stuff mentioned there...

For the second one, please open a bug/FR at SF

Done.

Regards
Michal

[jfouche]

Hi Marfi

Here is a screenshot showing that (some) link errors are detected by CodeLite (Just in my local repository actualy). Look this thread for more informations.