Federico suggestion of using an executable compressor is very good. Charles, you can try using upx (or another similar tool) once-and-for-all on the iconx.exe and/or wiconx.exe, and then building all your executables, or you can try running it out the resulting output .exe files; one or the other method may work well for you.
Last I checked, if you specify that an output icode file should end with the extension .cmd (and possibly also .bat), Unicon will write out icode without iconx prepended to it. You can then invoke iconx explicitly, passing it the icode file as its first argument, as in the good old days. David Feustel did the work to produce an iconx.dll so that executables need not include the entire iconx in them. This work was for Visual C++ and I have tried to preserve it in that configuration, although I switched Windows Unicon binary distributions over to GCC awhile back because its console executables were able to support graphics and standard I/O more properly. Since the Visual C++ configuration was recently updated, it might be pretty easy to produce a set of Unicon binaries based on an iconx.dll. Clint ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Unicon-group mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/unicon-group
