I am hoping to port PortablE (my implementation of the E language) to AROS. But I have hit a big problem:

To allow OS calls to be used, I need to tell PortablE about them. I have written a crude tool which semi-automatically converts C headers into the form PortablE needs, and that has worked well for both OS3.9 & OS4. Unfortunately, it appears that AROS's procedure declarations use some funky macros, like this:

AROS_LP2(struct TagItem *, FindTagItem,
         AROS_LPA(Tag, tagValue, D0),
         AROS_LPA(const struct TagItem *, tagList, A0),
         LIBBASETYPEPTR, UtilityBase, 5, Utility
);

That's completely useless to me, as I need it to look something like this for my tool to work:

struct TagItem *FindTagItem( Tag tagVal, CONST struct TagItem *tagList );

While I suppose it ought to be possible to modify my tool to handle AROS's esoteric declarations, it would be so much easier if either (a) someone told me where to find AROS's headers without macros, or (b) told me how to preprocess the header files (under Windows) to remove the macros.

Quote:

AFAIK we don't have those.

Quote:

The macros are defined in aros/libcall.h. You could start from this file to adapt the macros to output what you want.

greets,
Staf.

Quote:
I was hoping that this could be done automatically, otherwise I might as well try parsing the AROS format directly

I would have thought that it ought to be possible, since originally the C preprocessor would have been a separate program, but I have no idea where to look, or whether it might be possible to even get GCC to do the job for me...

gcc -E will give you the raw output from the preprocessor that would normally be passed to the compiler. You could process this output to get what you need.

Quote:

Another possibility I am now thinking of is to parse the .conf files in the AROS source. Every library has a .conf file (e.g. exec library has rom/exec/exec.conf) where the functions are listed. I think the format in these files resembles more what you want.

greets,
Staf.

@rob
Great, that sounds like just want I want - I think!

@Fats
Thanks for that suggestion - AmiDevCpp does not seem to contain those *.conf files, so I will download the 50MB of AROS source to (presumably) find those files.

You may also try to make stub functions. Such solution would work well on all amiga-like platforms.