Re: [cc65] CC65 v2.9.1 r3 win32 package

Date view Thread view Subject view

From: Rafal (rafalszyja_at_poczta.onet.pl)
Date: 2003-08-19 09:05:41


Hi,

I fixed all these things Greg King said about , many thanks for reporting :)
without you I would be still stuck!

I'll upload new version up to 1st September 2003 (probably sooner anyway)
(modem time-based-cost in Poland is horrible expensive)

>
> No, not yet [but, we are getting close -- very close :-) ].

hehe :)

If there is no more installation bugs this is really fixed

anyway believe me or not but installers r2 and r3
worked fine on every 9x based system I tried it on!


>
> 1. When the batch-file's path-name has spaces in it, utod.exe sees more
> than one argument (each one is only part of a name).  Therefore, it cannot
> find "run.bat".  Probably, the path-name should be surrounded by
> quotation-marks.


FIXED
hmm...
script was
ExecWait "$INSTDIR\bin\utod.exe $INSTDIR\run.bat"
and that was bad - changed to
ExecWait '"$INSTDIR\bin\utod.exe" $INSTDIR\run.bat'

>
> 2. The installer adds a space to the end of each line in run.bat.
> So, cmd.exe cannot find cc65's programs because it tries to look
> in "cc65\bin \".  (The NT version of command.com has the same problem;
but,
> the DOS version does not have that problem.)

thast's why it worked on 9x :)

FIXED - removed spaces

>
> 3. The characters "rm -f", in "cc65\samples\Makefile", need to be replaced
> by "$(RM)".  And, the characters "-rm", in
> "cc65\samples\geos\ca65-vlir\Makefile", need to be replaced by "-$(RM)".
> (The batch-file puts a DOS command into the RM environment-variable.)
> Without those changes, we cannot use the "clean" and "zap" rules to remove
> old debris.

FIXED

> ---------------------------------------
>
> I love that installer!  I like being able to look at a listing of the
> installation's history without being forced to hunt for an undocumented
> log-file.  The "right-click" feature that saves to the clipboard is nice,
> too.

yeah :) it's easy to catch changes!
this installer also produces smaller executables than Inno Setup Extensions
I used before.
can you believe that all installer and unistaller code + script parser +
bzip2 depacker takes about 40 kilobytes
opposed to about 250-300 in innosetup with additional tricky setup-engine
packing
by me ;) (w/o these tricks was about 450k!!!)

Raf




----------------------------------------------------------------------
To unsubscribe from the list send mail to majordomo_at_musoftware.de with
the string "unsubscribe cc65" in the body(!) of the mail.


Date view Thread view Subject view

This archive was generated by hypermail 2.1.3 : 2003-08-19 11:21:52 CEST