MQL5 compiler issue with /include flag

[Leolouiski Gan]

Hello,

On build 6180, when compiling through command line with /include flag, the following error is observed "Invalid resource path". This is probably the same issue as mentioned here (the thread mentioned it was fixed in 6140). https://www.mql5.com/en/forum/513579/page9#comment_60243060

This issue did not exist on previous build (not sure what build was before live update triggered) as I'm compiling same source code but the error only appears after the last update to build 6180.

I'm not able to bypass this issue by downgrading the build due to live update.

Side question: through the Metaeditor command line is there a flag to disable optimisation equivalent to the one shown on Metaeditor GUI? There was no mention of it here https://www.metatrader5.com/en/metaeditor/help/development/compile

Appreciate anyone who have information. 

Thank you.

[Alain Verleyen]

Not reproducible the bug you mentioned was fixed and stay fixed. I just checked with B6180.

You need to provide technical details to report an issue.

Documentation of the command line is here : https://www.metatrader5.com/en/metaeditor/help/beginning/integration_ide

Launch this command to get an help window : 

MetaEditor64.exe /?

[Leolouiski Gan]

Alain Verleyen #:

Not reproducible the bug you mentioned was fixed and stay fixed. I just checked with B6180.

You need to provide technical details to report an issue.

Documentation of the command line is here : https://www.metatrader5.com/en/metaeditor/help/beginning/integration_ide

Launch this command to get an help window : 

MetaEditor64.exe /?

Thanks Alain. I was not aware of the /? help window.

As for the /include issue you are right its not the same one as i linked that one was indeed fixed. I found its because i was providing a path in the /include flag that was on different virtual Z: drive.

I also tried previous builds and it seems for my specific setup above, it worked on build 5833 but not 6090 or 6180. Probably something changed in regards to how the /include flag handles #resource processing that affected my setup.

Anyways, after identifying the real issue of the different drive, i changed my build setup to make it work.

Appreciate the help!