ccportab.h
- Giovanni
- Site Admin
- Posts: 14444
- Joined: Wed May 27, 2009 8:48 am
- Location: Salerno, Italy
- Has thanked: 1074 times
- Been thanked: 921 times
- Contact:
Re: ccportab.h
The problem is that I have not yet decided to which layer it should belongs to: port, HAL or startup? there are pro and cons for each place, main problem is that HAL and RT/NIL/ports can work independently from each other.
So, undecided.
Giovanni
So, undecided.
Giovanni
Re: ccportab.h
Does it have to belong to a layer?
It really belongs with the compiler in use, to be included at the top of every file that is compiled.
For gcc, -include file (or maybe -imacros file) on the command line would do it; no doubt other compilers have similar options.
That command line value could be appended to the definition for CC and CPPC in arm-non-eabi.mk (I realise that file is in the 'startup' directory, but its actually only compiler-specific, I think)
This could be extended to allow inclusion of other arbitrary files in the same way.
It really belongs with the compiler in use, to be included at the top of every file that is compiled.
For gcc, -include file (or maybe -imacros file) on the command line would do it; no doubt other compilers have similar options.
That command line value could be appended to the definition for CC and CPPC in arm-non-eabi.mk (I realise that file is in the 'startup' directory, but its actually only compiler-specific, I think)
This could be extended to allow inclusion of other arbitrary files in the same way.
Who is online
Users browsing this forum: No registered users and 31 guests