Page 3 of 3

Re: libauto and application.library

Posted: Thu Jul 16, 2015 2:31 pm
by salass00
whose wrote: Maybe it´s time for a second .xml then, although they are identical in form and function? Sometimes it´s better to break SDK compatibility then to make coder´s live harder (I don´t think that there is so much vital OS4 code that makes use of the CIA resources).
New programs should use "timer.device" instead. Also CIA chips are only available on classic machines so I don't think it's worth fixing something that no-one will use anyway.

As I said before it makes no sense to generate a libauto from *all* the interface xml files (some are h/w dependent, some may use per task library bases, others may not be for general application use at all). Better would be to just have a list of common OS libraries that the libauto is generated from where new libraries can easily be added or removed as needed.

Re: libauto and application.library

Posted: Fri Jul 17, 2015 3:50 pm
by ssolie
salass00 wrote:Better would be to just have a list of common OS libraries that the libauto is generated from where new libraries can easily be added or removed as needed.
The current list lives in the Migration Guide at http://wiki.amigaos.net/wiki/Migration_ ... _Libraries