Re: Ciderpress for OS/X?

[datajerk <datajerk@gmail.com>]

On Aug 12, 10:01 am, "John B. Matthews" <nos...@nospam.invalid> wrote:
> In article
> <75988cab-f024-4985-a92b-d6688d3dd...@c14g2000yqm.googlegroups.com>,
>
>
>
>  datajerk <dataj...@gmail.com> wrote:
> > On Aug 11, 6:23 pm, "John B. Matthews" <nos...@nospam.invalid> wrote:
> > > In article
> > > <1f0f92e3-f832-4b32-9c51-6739cf4df...@q40g2000prh.googlegroups.com>,
>
> > >  datajerk <dataj...@gmail.com> wrote:
>
> > > [...]
>
> > > > > Did anyone compare the code generated by Aztec with that from cc65?
> > > > > I'm more concerned about  the size than the speed.
>
> > > > I tried, but I could not get cc65 to compile my code.  It errors with
> > > > too many local variables.  So I gave up.  But I would like to compare
> > > > the speed of my pi.c program.  cc65 vs Aztec. mano-a-mano.
>
> > > <http://sense.net/~egan/apple2e_aztec_c/pi.c>
>
> > > $ cl65 -O2 --static-locals -t apple2enh pi.c
>
> > Apparently I didn't try hard enough.  Thanks for the tip.  I too get
> > a 12377 byte pi.
>
> > I am having a few challenges running it however.  I have been unable
> > to use Ciderpress or AppleCommander to put this on a disk image and
> > run it.  However a2tools does work--DOS3.3 images only.
>
> ProDOS keeps the start address and length as metadata, while cc65 (like
> DOS) prepends it. AppleCommander has an option to sort it out [1].
> Here's an excerpt from my Makefile:
>
> PI = pi
> ${PI}: ${PI}.c
>     cl65 --static-locals -O -t apple2enh ${PI}.c
>     ac -d p1.po ${PI}
>     ac -cc65 p1.po ${PI} bin < ${PI}
>
> > So now I have a DOS3.3 image with pi, when I BRUN PI I get screen
> > garbage when the following code is run:
>
> >         printf("Start time: %s\n",asctime(localtime(&starttime)));
>
> > This code works with any *NIX and Aztec C.  My emulator has the
> > Thunderclock card in slot 7.  If I use the no-slot clock it also gets
> > garbage.  So I am unable to time this without using a wall-clock.  
> > Any ideas?
>
> I get the same thing with %s, but %ju works. Of course, it only takes a
> few seconds with Sweet16! :-)

Excellent thanks for the ac help.  The %ju does clean up the screen
junk, however it is not reporting the system time.  time() returns
-1.  Does cc65 have support for getting the time from a //e?  Google
has been little help.

Thanks.