Add warning to extractors when extracting with debug extractors

This is not the case for me. Is this just a Windows thing?

[quote=Xenithar]This is not the case for me. Is this just a Windows thing?[/quote]

Must be.

I'm sure of the reason behind why this should take that much longer in debug.

In the Build process there is a definition _DEBUG which indicates that it's a debug build

The issue with trying to do something with movemaps extractor itself is that it is called multiple times by the build scripts
- so it cannot keep track of its overall status beyond the current run

Olion has mentioned about setting and using the errorcode to flag the error during the run
- This combined with a -DEBUGOVERRIDE flag, might do the trick


As I see it, the logic flow would be this..

Are we in Debug Mode ?
No... Carry on as normal
Yes....
Do we have -DEBUGOVERRIDE set ?
Yes... Carry on as normal
No....
Do we have an Errorcode >0
No... Generate the Debug warning message and then set Errorcode to be greater then 0 and and Exit
Yes.... Exit

Thoughts ?

Why would this not affect the Linux build though? Seems odd. I am finishing my install now. Hopefully I will be up by Friday. No time anymore. Company is growing and I am being monopolized.