> I didn't continue yet because I'am not sure if subarch-abi are sufficient
or if another directory
> level with e.g. fpu type, custom options (debugging info, optimization
> level etc.) might be useful.
> Or if it would be only over engineering ...
fpcmkcfg already generates $fpcsubarch-$fpcme
> You can rename the compiler binaries to anything you want.
Then how would fpc be able to call the renamed binaries? I rely on fpc -P
for calling the cross compiler.
> A bigger problem is that all units will also be stored in the same
> directories.
If there's anyway to retrieve either the arme
Am 18.06.2015 um 17:55 schrieb Jonas Maebe:
> On 17/06/15 20:18, leledumbo wrote:
>> I currently have my [cross-]compilers under the same tree, to ease management
>> and the ability to use single fpc.cfg. AFAIU FPC ARMEL and ARMHF are two
>> distinct targets, thus two distinct compiler binary. Howe
On 17/06/15 20:18, leledumbo wrote:
> I currently have my [cross-]compilers under the same tree, to ease management
> and the ability to use single fpc.cfg. AFAIU FPC ARMEL and ARMHF are two
> distinct targets, thus two distinct compiler binary. However, the compiler
> binary has the same name. So,
