external languages don't bind acknex.dll to .exe

Posted By: LazyDog

external languages don't bind acknex.dll to .exe - 01/08/07 23:55

when using an external language NOT building dll plugins.........

During development it is a huge productivity killer to always have to publish against your .exe after each little change and compile of your program. It would be very nice if you would allow us to just copy an acknex.dll into our development directory and not have to publish against it.

If we want to release something then I don't have a problem with the publish requirement against the .exe
Posted By: jcl

Re: external languages don't bind acknex.dll to .e - 01/09/07 11:01

I allow it herewith.

It's undocumented, but you need to copy the following files from the Gamestudio installation: acknex.dll, ackutl.dll, ackold4.dll, med.exe, password.txt. With those files the acknex.dll can run outside of the Gamestudio folder. Of course you must not distribute this combination!

However, the 'official' way with publishing the EXE is not a productivity killer at all when you do it right. Just use the WED command line options in a batch file that is automatically called after every EXE compilation.
Posted By: TWO

Re: external languages don't bind acknex.dll to .e - 01/09/07 20:47

Please add this to the section in the manual it belongs to.

Thanks
Posted By: LazyDog

Re: external languages don't bind acknex.dll to .e - 01/09/07 23:11

Quote:


It's undocumented, but you need to copy the following files... Of course you must not distribute this combination!





Excellent! thanks!! my productivity is rising!!

Quote:


However, the 'official' way with publishing the EXE is not a productivity killer at all when you do it right. Just use the WED command line options in a batch file that is automatically called after every EXE compilation.





I do have a batch file setup for that; however, the publish creates a subdirectory and creates the files there but I like to just hit F9 in my IDE and to compile and run from there so if I need to start debugging something I just set a breakpoint. But the above solutions SOLVES all that for ME!!!!
© 2023 lite-C Forums