All, > Federico suggestion of using an executable compressor is very good.
That worked very well, reducing my 553 KB executable to under 300 KB. (In case that didn't get out to the list, the link is www.upx.org.) > > 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. I tried the latter, but the former sounds interesting. > 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. Sure did. (My program is named "include.icn".) "icont -o include.cmd include" built an include.cmd of a mere 1728 bytes. "iconx include.cmd include.txt" (include.txt is my test input) ran it like a champ. Works for me! > 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 It looks like I have what I need, so don't schedule the work on my account. It might be good to update your basic documentation to point out the .cmd trick, though. I couldn't find that anywhere. Thanks very much. Charles Hethcoat ------------------------------------------------------- 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
