We use MetaEditor on Windows, file/product version 5.0.0.6253.
Our existing command has this sanitised shape (illustrative paths only):
metaeditor64.exe /compile:"C:\Example\fixture.mq5" /log:"C:\Example\fixture.log" /include:"C:\Example\CompilerResources"
A retained fixture compilation produced neither a final Result summary nor an EX5 before our 90-second limit. Our wrapper then forcibly stopped the compiler. Other source files have compiled successfully with the same compiler, but these are not controlled comparisons.
We have not established the cause, the effective optimisation mode, or whether optimisation contributed.
Please clarify:
1. Does build 6253 support noninteractive MQ5-to-EX5 compilation with optimisation explicitly disabled, without project UI interaction or changes to global/working-terminal settings?
2. If supported, what exact documented invocation or isolated configuration is required? Please explain property precedence and any settings written outside the isolated workspace.
3. What supported output or metadata confirms which optimisation mode the compiler actually used?
4. If no such noninteractive route exists, please confirm explicitly. Is there a documented build-6253 issue relevant to this behaviour, and what evidence would distinguish it?
This is a procedure/feature enquiry only. No proprietary source or logs are attached.
- MetaEditor CLI fails silently on large modular projects
- Compilation of MQPROJ project file is weird from command line
- "#property indicator_buffers" update fails in Projects
Kasimu Ijelu:
that version is beta. use the latest release version and see if you have same issue.
You are missing trading opportunities:
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
Registration
Log in
You agree to website policy and terms of use
If you do not have an account, please register