[Lazarus] Compile project release with LCL custom optimization

[Mattias Gaertner]

On Tue, 16 Apr 2013 09:50:48 +0300
patspiper <patspiper at gmail.com> wrote:

> On 15/04/13 23:18, Mattias Gaertner wrote:
> > On Mon, 15 Apr 2013 21:31:32 +0300
> > Zaher Dirkey <parmaja at gmail.com> wrote:
> >
> >> On Mon, Apr 15, 2013 at 9:21 PM, Mattias Gaertner <nc-gaertnma at netcologne.de
> >>> wrote:
> >>> To get more variations in output directories you have to alter the
> >>> packages (lpk).
> >>> To add options to packages as well.
> >>>
> >>> Eventually such additions will be configurable in the IDE
> >>
> >> ​Directories to put precompiled units *.o​ of Packages, when compile the
> >> project it take the right .o Depend Release or Debug, so it is
> >> IDE/Envirement mechanism, Delphi do that for VCL, and Visual Stutio.
> > Some people want Debug/Release, some Debug/Profiling/Release, some
> > Experimental/Normal, some Debug/Release x WidgetSet and so forth.
> > IMO Lazarus should provide such flexibility.
> Can the Lazarus core packages have a macro in their unit output 
> directory in order to "inherit" the correct path upon rebuilding the 
> project or the IDE itself?
> ex for LCL:
> ../units/$(TargetCPU)-$(TargetOS)/$(LCLWidgetType)/$(BuildModeFolder)
> LCL has $(IDEBuildOptions) in its customs options. I am not sure if it 
> inherits macros as well.
> Is there an equivalent $(ProjectBuildOptions)?
> 
> The above would be the 1st step towards such a solution.

And who changes all the other third party packages?

And some developers may prefer this:
/Developer/$(BuildMode)/$(PkgName)

I think an override would be more flexible. It should also a contain a
scope option. To handle some packages differently.

Mattias