Page 1 of 1

Script Compile Probs

PostPosted: Mon Aug 04, 2003 12:29 am
by Grae
Hiya,

As normal I followed Drockets instructions to the letter. And have once again no problems what so ever.
But I do get the following whenever I do try to compile, and cannot find the Version of DBGHELP.DLL anywhere as the compiler seems to ask for.

The following is what I get:-

D:\POL\scripts\misc>ecompile logon.scr
Warning: DBGHELP.DLL too old, version 5.1+ required.
EScript Compiler v1.03
Copyright (C) 1994-2003 Eric N. Swanson

Compilation Summary:


If anyone knows where I can get the correct file it would be appreciated. I downloaded the latest POL095 Core, and I also got the POL095 Complete. I even tryed to use the DBGHELP.DLL from the POL095 Complete, but for some reason POL095 Core set does not see it.

Neither package will allow me to compile scripts.

Any advice appreciated.

Peace Out.

PostPosted: Mon Aug 04, 2003 12:49 am
by SDonald
If it's the one from:
http://www.polserver.com/modules.php?na ... load&cid=2

Just make sure you put it in your pol\ directory.
You also might like to check your scripts\ecompile.cfg to make sure it knows the paths. 095 started using ecompile.cfg file rather than relying on environment variables.


Regards,
Stephen Donald.

PostPosted: Mon Aug 04, 2003 1:34 am
by Grae
Thank you so much Stephen, that did fix the above mentioned problem with the dbghelp.dll version. I had to put it in the scripts folder with the compiler for it to see.

The problem I have now is it runs, but does not create the .ecl file from the script.

Like you said above this is most likely due to the ecompile.cfg file not setup correctly.

Thanks again for putting me on the correct path.

Appreciated.

Peace Out.

PostPosted: Mon Aug 04, 2003 3:49 am
by Grae
Just a quick note to let you know I got the cfg file working properly (no errors). And the best thing I found is you don't have to tell the compiler what script to compile (ie. D:POL/Scripts/Misc> ecompile logon.scr), all I did was type "ecompile" at the prompt and accidently hit enter key before I entered the script name, to my surprise the compiler quickly ran through every script and file and up-dated only those that required the changes.

So now all I do whenever I add/edit new scripts/packages I just do that and it takes care of the rest (ie. D:POL/Scripts> ecompile).

Other than setting up the cfg file this new compiler is totally newbie friendly. Could'nt get any easier (mind you thats easy to say once you get it to work once).

Thanks again Stephen

Peace Out.

PostPosted: Wed Aug 06, 2003 1:16 am
by Lyl
I also thought compile.cfg was a great change. Makes it so easy. =]

PostPosted: Wed Aug 06, 2003 7:28 am
by SDonald
We are a much lazier generation..... :lol:

I got so used to typing "ecompile -a -u -r ."
to just compile the changes...
In fact I still do out of habit.

How much better is it just typing "ecompile" ?

Stephen Donald.

PostPosted: Wed Aug 06, 2003 9:38 pm
by Lyl
you still use a console window?
*is too lazy to type*

PostPosted: Thu Aug 07, 2003 11:07 am
by SDonald
I'm so set in my ancient ways, I still have a C prompt ready at all times.

I don't change things that work.
Right click compiling is just tooooo easy. :silly:

Yours in contempt,
Stephen Donald.