How to handle #include with MQLLock the exact way?

20 views
Skip to first unread message

Tom

unread,
May 4, 2012, 9:52:53 AM5/4/12
to mql...@googlegroups.com
Hello,

i read about, if we have #includes, we have to upload too- and in correct order.

So how to do it the correct way?

inside source code have:

....
#include <stdlib.mqh>
#include <stderror.mqh>
....


My take is that we should process the project as normal,
then next step would be to process the stdlib file and then the stderror file

So we then have 3 output files?

What if remote controle is active.. do we then need to "controle" all 3 files seperately?

This sounds weird to me and pretty sure i´m mistaken here!? but there is only one upload field so assuming multiple files are not going through.


Thank you!

Tom

unread,
May 4, 2012, 9:55:59 AM5/4/12
to mql...@googlegroups.com
Sorry, found the answer.
It´s already built in in a very smart way!

if uploader detects any #includes.. it will open more upload boxes!


Great!!

DougRH

unread,
May 17, 2012, 8:08:12 AM5/17/12
to MqlLock
> Re: Obfuscating INCLUDE files
>
> It´s already built in in a very smart way!
> if uploader detects any #includes.. it will open more upload boxes!
-
What about Library files ?

Fx1.Net

unread,
May 30, 2012, 8:30:25 AM5/30/12
to mql...@googlegroups.com
We dont support Library obfuscation yet. This will come on later stages, most likely after release.
Reply all
Reply to author
Forward
0 new messages