Using fpmake, how does one append a compiler option like

-dSOMEDEFINE

Or

-xxSomeOptionNotIntegratedYet

I will put this info in the FPMAKE wiki page if it is possible to do.

Regards,
L505

3 ways:

var
  T : TTarget;
  P : TPackage;
T.Options:='-dSOMEDEFINE';
or
P.Options:='-dSOMEDEFINE';
or
Defaults.Options:='-dSOMEDEFINE';

Maybe in time, we'll add a 'Defines' property.

Michael.

Using fpmake, how does one append a compiler option like -dSOMEDEFINE

Solution:
Target.options:= '-dSOMEDEFINE';

Michael wrote

3 ways:

Thanks.. added compiler option info to the fpmake wiki page.

Now I'm wondering..when I use "fpmake clean" it doesn't clean any units that were compiled implicitly.. i.e. units that were not called in with AddUnit, but compiled because they were in uses clause of units. Is this by design that one cannot clean implicitly compiled units, and any ideas how I could clean those units too. Or should one always add all units explicitly with AddUnit that one wants to clean? I'm thinking it may be tedious to AddUnit every "uses" implicit unit and I might be missing some easy way to do that.

You have to add all units. Otherwise fpmake does not know that they need to be packed for distribution.

There is a special AddImplicitUnit() for implicit build units. See e.g. winunits-jedi/fpmake.pp for a nice trick how to use a buildjwa.pp having also correct dependencies so fpmake can check if a recompile of the build unit is required.

Peter