New port for ARM Industrial Module AIM 711 - Checked by AntiVir DEM

[Jonathan Larmour]

Roland Caßebohm wrote:
> 
>>>>You include <string.h> but do not use anything from it as far as i can
>>>>see. You should not have this, it means you HAL is dependant on libc.
>>>
>>>I needed memcpy(). Should I make a small loop to copy instead?
>>
>>I missed that. The infra package implements memcpy, so it should
>>always be available. What i cannot find is a prototype in the infra
>>header files. I'm not sure what you are supposed to do!
> 
> 
> It seems like the isoinfra package which includes the string.h file
> is allways used. Also if the libc package is not used.
> I have searched how other hal packages make it, but most of them don't
> need memcpy(), some have there own and some have just a prototype. 
> I don't know what whould be the best?

For the avoidance of doubt, the best thing to do is indeed include 
<string.h> if you want memcpy(). isoinfra is, as far as I'm concerned, now 
compulstory. It is already in all templates. It should never have any build 
overhead (although there's an argument that memcpy/memset should move from 
infra to isoinfra, but there's no real need).

Jifl
-- 
eCosCentric    http://www.eCosCentric.com/    The eCos and RedBoot experts
--["No sense being pessimistic, it wouldn't work anyway"]-- Opinions==mine