Re: [hatari-devel] AHHC Project files (was: Bug report: AHCC not working anymore with GEMDOS emulation)

[Eero Tamminen <oak@xxxxxxxxxxxxxx>]

Hi,

On sunnuntai 22 tammikuu 2012, Matthias Arndt wrote:
> Am Sonntag, den 22.01.2012, 02:49 +0200 schrieb Eero Tamminen:
> > When I drop c:\math\primes.prj on c:\ahcc_p.ttp, according to
> > GEMDOS trace, AHCC first opens primes.prj, and then it tries to
> > open following files, in this order:
> > - primes.prjprimes.ttp
> > - primes.prjprimes.o
> > - primes.prjprimes.c
> > 
> > which all obviously fail, so finally it complains about not
> > finding the last one.
> > 
> > The primes.prj content is this, and it works fine when I load
> > it from the GUI:
> > -------------
> > primes.ttp
> > =
> > ahcstart.o
> > primes.c
> > ahccstdi.lib
> > -------------
> > 
> > I think AHCC is buggy.
> 
> It is not, you just have to add some more information in the project
> file like this to find the paths:

If you look above, the problem is that AHCC TTP version prefixes all
file names with the project file name.

After trying this with EmuTOS console, it seems that AHCC TTP avoids
this bug if full path to the project file is given to it.

I.e. if one does:
  c:\ahcc_p.ttp c:\math\primes.prj

instead of:
  cd c:\math
  c:\ahcc_p.ttp primes.prj

It works.  However, real TOS seems to be using the latter method
when you do the drag & drop (= open ahcc dir window, then open
primes.prj dir window, then drag primes.prj on top of ahcc_p.ttp).


Additionally, AHCC doesn't seem to be searching for its own includes
and libs from paths that are either fixed, or relative to AHCC directory,
but relative to the current work directory i.e. where your sources are.

This makes the TTP pretty much useless.  I'm not going to hardcode
and update in dozens of project files the absolute paths to wherever
AHCC include and libraries happen to be[1], for the version of AHCC
I happen to be testing:

I'll mail Henk about that.


> > Hm.  In the GUI I always need to first select in the settings
> > "-Iinclude" before things work, but with the TTP version it
> > doesn't seem to proceed even that far.
>
> I never know which include paths are correct, it changes at times.
> Ask Henk Robbers for more information.

According to last time I asked about  it, sinclude/ is for AHCC internal
usage, it explicitly uses shorts instead of ints (AHCC ints are by default
short).  include/ is meant for normal programs.  It lacks quite a few things
that are in sinclude/ headers though.

AHCC headers are a bit of a mess.  Henk doesn't really want to touch
them, but he's applied any reasonable patches I've sent.


> He normally replies within days if not hours.

I know, I typically find and report few bugs for each of the AHCC
releases I try.  He fixes them very quickly. :-)


	- Eero

[1] for example:
-----------
..C [-ic:\ahcc\include]
primes.ttp
=
c:\lib\ahcc\ahcstart.o
primes.c
c:\lib\ahcc\ahccstdi.lib
-----------