> 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 18/06/15 16:53, Jonas Maebe wrote:
> On 18/06/15 17:37, Peter wrote:
>
>> The problem occurs with BOTH switches -Cr & -CO
>> Any one of these, and the compiler is silent,
> -CO is a switch that is barely used and that is tested even less,
> unfortunately (no extensive tests were added along with
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,
On 18/06/15 17:37, Peter wrote:
> The problem occurs with BOTH switches -Cr & -CO
> Any one of these, and the compiler is silent,
-CO is a switch that is barely used and that is tested even less,
unfortunately (no extensive tests were added along with it). I would not
recommend to use it in its c
Hi Everybody,
I tried compiling with all warnings for a final polish/check on a
project, and seem to be getting a raft of false positives.
The following example stub gives two warnings;
Program test;
Const TAB = Char(Chr(9));
Var A : DWord;
Begin
A := 0;
End.
Also I get the same warning on e
