Re: [Lazarus] Compile project release with LCL custom optimization

[Mattias Gaertner]

> patspiper  hat am 16. April 2013 um 15:34 geschrieben:
>[...]
> > I think an override would be more flexible. It should also a contain a
> > scope option. To handle some packages differently.
> An override would be super and very flexible! It would handle all packages.
>
> However, maybe a distinction (separate settings) should be done for the
> user project/packages, Lazarus core packages (LCL, SynEdit, ...), and
> FPC packages (FCL). The reason is that a user may need to debug his code
> only, his code + Lazarus' code, or his code + Lazarus' code + FPC code.
> Stepping over FCL code is almost always the case for regular users and
> probably Lazarus devs.

That's what I mean with scope.

Mattias

--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] Compile project release with LCL custom optimization

[patspiper]

On 16/04/13 14:52, Michael Van Canneyt wrote:



On Tue, 16 Apr 2013, Zaher Dirkey wrote:



On Tue, Apr 16, 2013 at 11:18 AM, Mattias Gaertner 
 wrote:

Yes.
Although it might be a good idea to add a macro for the name of
the active build mode and I guess BuildMode is a good name for that.


​Good and not :P​

​Here, it is not good to pass it to the packages include LCL and 
maybe (FCL even the FPC pascal one) when compile the project, because 
it it is variant name.


My need the build take Debug dirs (*.o units) if we define Debug or 
Release dirs when define Release, let name it BuildState (i am not 
good in naming)


We need this also even compile FPC projects, so ​(non LCL), i think 
FPC developer can take a look to this thread.


You can create various config files. Depending on what 'mode' you 
want, you can simply specify a different config file when compiling.

or use IFDEF's and macros in fpc.cfg

Stephano

--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] Compile project release with LCL custom optimization

[patspiper]

On 16/04/13 10:38, Mattias Gaertner wrote:

On Tue, 16 Apr 2013 09:50:48 +0300
patspiper  wrote:


On 15/04/13 23:18, Mattias Gaertner wrote:

On Mon, 15 Apr 2013 21:31:32 +0300
Zaher Dirkey  wrote:


On Mon, Apr 15, 2013 at 9:21 PM, Mattias Gaertner 
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?
1st, to clarify, $(BuildModeFolder) is a macro derived from the actual 
build mode name (or some user defined value in each build mode).


In this case, 3rd party packages would have to be handled either by the 
package maintainer or by the user.


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.

An override would be super and very flexible! It would handle all packages.

However, maybe a distinction (separate settings) should be done for the 
user project/packages, Lazarus core packages (LCL, SynEdit, ...), and 
FPC packages (FCL). The reason is that a user may need to debug his code 
only, his code + Lazarus' code, or his code + Lazarus' code + FPC code. 
Stepping over FCL code is almost always the case for regular users and 
probably Lazarus devs.


IIRC, Delphi has Debug and Release dcu's for the VCL.

Stephano

--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] Compile project release with LCL custom optimization

[Zaher Dirkey]

On Tue, Apr 16, 2013 at 2:52 PM, Michael Van Canneyt  wrote:

> You can create various config files. Depending on what 'mode' you want,
> you can simply specify a different config file when compiling


​In Packages in LCL and Lazarus Components and My Packages?​

Best Regards
Zaher Dirkey
--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] Compile project release with LCL custom optimization

[Michael Van Canneyt]

On Tue, 16 Apr 2013, Zaher Dirkey wrote:



On Tue, Apr 16, 2013 at 11:18 AM, Mattias Gaertner  
wrote:
  Yes.
  Although it might be a good idea to add a macro for the name of
  the active build mode and I guess BuildMode is a good name for that.


​Good and not :P​

​Here, it is not good to pass it to the packages include LCL and maybe (FCL 
even the FPC pascal one) when compile the project, because it it is variant 
name.

My need the build take Debug dirs (*.o units) if we define Debug or Release 
dirs when define Release, let name it BuildState (i am not good in naming)

We need this also even compile FPC projects, so ​(non LCL), i think FPC 
developer can take a look to this thread.


You can create various config files. 
Depending on what 'mode' you want, you can simply specify a different config file when compiling.


Michael.--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] Compile project release with LCL custom optimization

[Zaher Dirkey]

On Tue, Apr 16, 2013 at 2:30 PM, Mattias Gaertner  wrote:

> I got the feeling, you are still at only two modes.


I have a lot of build modes​, but i missed founded in Delphi 4 and above
When i compile project to debug it, i can (In Delphi) debug inside the
sources of VCL or more deep than VCL, Delphi will choose DCUs that in Debug
dir

C:\Program Files\CodeGear\RAD Studio\5.0\lib\Debug

But when we not debugging it, it will choose DCUs in Release dirs or in
fact in the parent it

C:\Program Files\CodeGear\RAD Studio\5.0\lib

​We need that at least in Lazarus, and it will be good in FPC too.

​My problem: i debug my project inside my packages(My Packages) and some
LCL or Components, so i need to rebuild all packages with Debug info no
optimize.
When i need to make realase my project i must rebuild all of them again
with no debug info and some optimize, i build the project, it is so hard
switching.

Best Regards
Zaher Dirkey
--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] Compile project release with LCL custom optimization

[Mattias Gaertner]

On Tue, 16 Apr 2013 14:21:08 +0300
Zaher Dirkey  wrote:

> On Tue, Apr 16, 2013 at 11:18 AM, Mattias Gaertner <
> nc-gaert...@netcologne.de> wrote:
> 
> > Yes.
> > Although it might be a good idea to add a macro for the name of
> > the active build mode and I guess BuildMode is a good name for that.

I added that.

 
> ​Good and not :P​
> 
> ​Here, it is not good to pass it to the packages include LCL and maybe (FCL
> even the FPC pascal one) when compile the project, because it it is variant
> name.

Can you explain this?

 
> My need the build take Debug dirs (*.o units) if we define Debug or Release
> dirs when define Release, let name it BuildState (i am not good in naming)

I got the feeling, you are still at only two modes.

 
> We need this also even compile FPC projects, so ​(non LCL), i think FPC
> developer can take a look to this thread.

The compiler has nothing to do with build modes.

Mattias

--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] Compile project release with LCL custom optimization

[Zaher Dirkey]

On Tue, Apr 16, 2013 at 11:18 AM, Mattias Gaertner <
nc-gaert...@netcologne.de> wrote:

> Yes.
> Although it might be a good idea to add a macro for the name of
> the active build mode and I guess BuildMode is a good name for that.
>

​Good and not :P​

​Here, it is not good to pass it to the packages include LCL and maybe (FCL
even the FPC pascal one) when compile the project, because it it is variant
name.

My need the build take Debug dirs (*.o units) if we define Debug or Release
dirs when define Release, let name it BuildState (i am not good in naming)

We need this also even compile FPC projects, so ​(non LCL), i think FPC
developer can take a look to this thread.


-- 
I am using last revision of Lazarus, FPC 2.6 on Windows XP SP3

Best Regards
Zaher Dirkey
--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] Compile project release with LCL custom optimization

[Mattias Gaertner]

On Tue, 16 Apr 2013 10:51:19 +0300
Zaher Dirkey  wrote:

> On Tue, Apr 16, 2013 at 10:38 AM, Mattias Gaertner <
> nc-gaert...@netcologne.de> wrote:
> 
> > /Developer/$(BuildMode)/$(PkgName)
> >
> 
> /Developer/$(BuildMode)/$(PkgName)
> ​​$(BuildMode) BuildMode here is user defined.

Yes.
Although it might be a good idea to add a macro for the name of
the active build mode and I guess BuildMode is a good name for that.


>[...]

Mattias

--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] Compile project release with LCL custom optimization

[Zaher Dirkey]

On Tue, Apr 16, 2013 at 10:38 AM, Mattias Gaertner <
nc-gaert...@netcologne.de> wrote:

> /Developer/$(BuildMode)/$(PkgName)
>

/Developer/$(BuildMode)/$(PkgName)
​​$(BuildMode) BuildMode here is user defined. many names come for each
project, need new name variable DEBUG_OR_RELEASE (example name)
/Developer//$(PkgName)/$(DEBUG_OR_RELEASE)
DEBUG_OR_RELEASE can take DEBUG value or RELEASE. (i know DEBUG_OR_RELEASE
is bad name)

Best Regards
Zaher Dirkey
--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] Compile project release with LCL custom optimization

[Mattias Gaertner]

On Tue, 16 Apr 2013 09:50:48 +0300
patspiper  wrote:

> On 15/04/13 23:18, Mattias Gaertner wrote:
> > On Mon, 15 Apr 2013 21:31:32 +0300
> > Zaher Dirkey  wrote:
> >
> >> On Mon, Apr 15, 2013 at 9:21 PM, Mattias Gaertner 
> >>  >>> 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

--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] Compile project release with LCL custom optimization

[patspiper]

On 15/04/13 23:18, Mattias Gaertner wrote:

On Mon, 15 Apr 2013 21:31:32 +0300
Zaher Dirkey  wrote:


On Mon, Apr 15, 2013 at 9:21 PM, Mattias Gaertner 
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.

Stephano

--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] Compile project release with LCL custom optimization

[Mattias Gaertner]

On Mon, 15 Apr 2013 21:31:32 +0300
Zaher Dirkey  wrote:

> On Mon, Apr 15, 2013 at 9:21 PM, Mattias Gaertner  > 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.

Mattias

--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] Compile project release with LCL custom optimization

[Zaher Dirkey]

On Mon, Apr 15, 2013 at 9:21 PM, Mattias Gaertner  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.

Best Regards
Zaher Dirkey
--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] Compile project release with LCL custom optimization

[Mattias Gaertner]

On Mon, 15 Apr 2013 20:41:34 +0300
Zaher Dirkey  wrote:

> Our problem here
> I like to define a Many named Build profiles(Modes), for example, i want to
> build my project with special defines to make project for "Pascal" or "PHP"
> or "ALL"
> and for WINCE Wegetset etc. many of them.
> But we need debugging it when compile it in IDE, not the project only also
> many components have it in other packages.
> And we need to release it without debug info that mean need another
> Dimension for Build Modes/Profiles, at least DEBUG and RELEASE for all
> Build Modes/Profiles
> Also Lazarus and its Components must have 2 of dir one for Debug other for
> Release depend what we choose of current mode, that prevent from rebuild
> all of packages every time changing from DEBUG to Release and vise versa.

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.

Mattias

--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] Compile project release with LCL custom optimization

[Graeme Geldenhuys]

On 15/04/13 18:41, Zaher Dirkey wrote:
> Our problem here
> I like to define a Many named Build profiles(Modes), for example, i want to
> build my project with special defines to make project for "Pascal" or "PHP"
> or "ALL" snip


Yes, I fully understand what you want to do. And like you I simply
couldn't figure out how to accomplish that with Lazarus IDE. With
MSEgui, and even with Maximus, it was really simple to accomplish what I
(and apparently you) wanted.


Regards,
  - Graeme -


--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] Compile project release with LCL custom optimization

[Zaher Dirkey]

Our problem here
I like to define a Many named Build profiles(Modes), for example, i want to
build my project with special defines to make project for "Pascal" or "PHP"
or "ALL"
and for WINCE Wegetset etc. many of them.
But we need debugging it when compile it in IDE, not the project only also
many components have it in other packages.
And we need to release it without debug info that mean need another
Dimension for Build Modes/Profiles, at least DEBUG and RELEASE for all
Build Modes/Profiles
Also Lazarus and its Components must have 2 of dir one for Debug other for
Release depend what we choose of current mode, that prevent from rebuild
all of packages every time changing from DEBUG to Release and vise versa.

(Oh My English)


On Mon, Apr 15, 2013 at 2:40 PM, Graeme Geldenhuys
wrote:

> On 15/04/13 12:22, Mattias Gaertner wrote:
> >
> > Maybe you have some ideas how to put that into a grid that is easy to
> > understand?
>
> I'll take another look at the Build Mode settings is Lazarus and report
> ideas I come up with.
>
> The current Build Mode settings is Lazarus IDE is very confusing though
> - even though there was good intentions not to make it confusing. eg: I
> could type in the name of a non-existing marco (grid in Build Modes
> screen), and give it a value. But because that marco wasn't defined in
> another area of the Project Settings (Build macros screen), it didn't
> work. So why didn't Lazarus IDE report the problem, or why was I allowed
> to type in a non-existing macro name, or why didn't it automatically
> define that macro.
>
>
> Regards,
>   - Graeme -
>
>
> --
> ___
> Lazarus mailing list
> Lazarus@lists.lazarus.freepascal.org
> http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
>



-- 
I am using last revision of Lazarus, FPC 2.6 on Windows XP SP3

Best Regards
Zaher Dirkey
--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] Compile project release with LCL custom optimization

[Mattias Gaertner]

> Graeme Geldenhuys  hat am 15. April 2013 um 16:33
> geschrieben:
>
>
> On 15/04/13 12:47, Mattias Gaertner wrote:
> >
> > You can define any macro you like. The name must follow the normal
> > pascal identifier rules.
>
> Yes I understand that, but you must first define the macro (somewhere
> else), before using them in the Build Modes screen. Lazarus IDE didn't
> prevent me from trying to use a macro in the Build Modes screen (with a
> legal pascal identifier rules name) that doesn't yet exist.

No, you can define any macro you like in the project options.
And then you can use the macro in the compiler options of project and packages.
For example in search paths and custom options.

Maybe you are confusing it with the macros from conditionals?
Conditionals have to define the macros they export.

Mattias

--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] Compile project release with LCL custom optimization

[Graeme Geldenhuys]

On 15/04/13 12:47, Mattias Gaertner wrote:
> 
> You can define any macro you like. The name must follow the normal
> pascal identifier rules.

Yes I understand that, but you must first define the macro (somewhere
else), before using them in the Build Modes screen. Lazarus IDE didn't
prevent me from trying to use a macro in the Build Modes screen (with a
legal pascal identifier rules name) that doesn't yet exist.

[hope I'm explaining this clearly]

Regards,
  - Graeme -


--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] Compile project release with LCL custom optimization

[Mattias Gaertner]

On Mon, 15 Apr 2013 12:40:23 +0100
Graeme Geldenhuys  wrote:

> On 15/04/13 12:22, Mattias Gaertner wrote:
> > 
> > Maybe you have some ideas how to put that into a grid that is easy to
> > understand?
> 
> I'll take another look at the Build Mode settings is Lazarus and report
> ideas I come up with.
> 
> The current Build Mode settings is Lazarus IDE is very confusing though
> - even though there was good intentions not to make it confusing. eg: I
> could type in the name of a non-existing marco (grid in Build Modes
> screen), and give it a value. But because that marco wasn't defined in
> another area of the Project Settings (Build macros screen), it didn't
> work. So why didn't Lazarus IDE report the problem, or why was I allowed
> to type in a non-existing macro name, or why didn't it automatically
> define that macro.

You can define any macro you like. The name must follow the normal
pascal identifier rules.

Mattias

--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] Compile project release with LCL custom optimization

[Graeme Geldenhuys]

On 15/04/13 12:22, Mattias Gaertner wrote:
> 
> Maybe you have some ideas how to put that into a grid that is easy to
> understand?

I'll take another look at the Build Mode settings is Lazarus and report
ideas I come up with.

The current Build Mode settings is Lazarus IDE is very confusing though
- even though there was good intentions not to make it confusing. eg: I
could type in the name of a non-existing marco (grid in Build Modes
screen), and give it a value. But because that marco wasn't defined in
another area of the Project Settings (Build macros screen), it didn't
work. So why didn't Lazarus IDE report the problem, or why was I allowed
to type in a non-existing macro name, or why didn't it automatically
define that macro.


Regards,
  - Graeme -


--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] Compile project release with LCL custom optimization

[Mattias Gaertner]

On Mon, 15 Apr 2013 11:42:45 +0100
Graeme Geldenhuys  wrote:

> On 14/04/13 07:42, Zaher Dirkey wrote:
> > 
> > ​What is B,M,1,2,..6, is it Build Modes also?​
>[...]
> All in one screen, and personally I think much simpler than what Lazarus
> IDE does.

I would be happy to have all information in one screen too. But IMO
it is not that easy. MSEIDE uses a small font and its own dense theme.
Lazarus should work with the users theme.

And Lazarus needs settings for packages. For example it must be
possible to apply some settings only to the project and packages
A,B,C, or to all except packages X,Y. 
And such settings needs to be stored either globally, in the lpi or the
lps.

So Lazarus needs to handle more information on less space.
MSEIDE uses single character abbreviations to save space. That's a bit
confusing, but it is ok, because it is the only element.
Lazarus needs a grid, where build modes, storage and scope are
handled, so abbreviations would be quickly misunderstood.

Maybe you have some ideas how to put that into a grid that is easy to
understand?

Mattias

--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] Compile project release with LCL custom optimization

[Graeme Geldenhuys]

On 14/04/13 07:42, Zaher Dirkey wrote:
> 
> ​What is B,M,1,2,..6, is it Build Modes also?​

Yes. 6 build modes are available for use. Maximus allows more, but
starts with 6, and also has keyboard shortcuts for each build mode. So
building using a different build mode is simply a click away, or via a
keyboard shortcut. Defining each build mode, is simply a matter of
ticking a box saying which compiler setting applies to which build mode
column.

All in one screen, and personally I think much simpler than what Lazarus
IDE does.

Regards,
  - Graeme -


--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] Compile project release with LCL custom optimization

[Graeme Geldenhuys]

On 14/04/13 06:58, Martin Schreiber wrote:
>>
> Hehe. :-)
> http://article.gmane.org/gmane.comp.ide.mseide.user/18779
> ;-)

:-) [how do you guys find such old email of mine]

Anyway, that was probably before I knew about using configurable Macros
in paths - a MSEide help file would have gone a long way. Maximus IDE
(experimental project) does similar to MSEide, but not exactly the same.
For example, I split session information and project settings (separate
files), I also allow configurable (from within the IDE) Global and per
Project macros. These were small things that annoyed me of MSEide. But
overall, I think the Compiler Options flexibility you created in MSEide
is awesome! :)

Regards,
  - Graeme -


--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] Compile project release with LCL custom optimization

[Martin Schreiber]

On Sunday 14 April 2013 08:42:17 Zaher Dirkey wrote:
>
> ​What is B,M,1,2,..6, is it Build Modes also?​

The menu items 'Project'-'Make','Build','Make 1','Make 2','Make 3','Make 4'.
http://mseide-msegui.sourceforge.net/pics/projectmenu.png

Martin

--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] Compile project release with LCL custom optimization

[Zaher Dirkey]

On Sun, Apr 14, 2013 at 8:58 AM, Martin Schreiber wrote:

> On Saturday 13 April 2013 21:30:17 Graeme Geldenhuys wrote:
> > On 2013-04-13 20:05, Zaher Dirkey wrote:
> > > ​Not worked for me, i Added $(ProjectOpts) to custom options in SynEdit
> > > package (same with my packages but i will take SynEdit as example)​
> > > What i have I Have 2 build mode (Debug, Release)
> >
> > I use lots of build modes too... like I said, the Lazarus Package idea
> > was more problems than anything else. Now I just define all source paths
> > as needed.
> >
> Hehe. :-)
> http://article.gmane.org/gmane.comp.ide.mseide.user/18779
> ;-)


​What is B,M,1,2,..6, is it Build Modes also?​



-- 
I am using last revision of Lazarus, FPC 2.6 on Windows XP SP3

Best Regards
Zaher Dirkey
--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] Compile project release with LCL custom optimization

[Martin Schreiber]

On Saturday 13 April 2013 21:30:17 Graeme Geldenhuys wrote:
> On 2013-04-13 20:05, Zaher Dirkey wrote:
> > ​Not worked for me, i Added $(ProjectOpts) to custom options in SynEdit
> > package (same with my packages but i will take SynEdit as example)​
> > What i have I Have 2 build mode (Debug, Release)
>
> I use lots of build modes too... like I said, the Lazarus Package idea
> was more problems than anything else. Now I just define all source paths
> as needed.
>
Hehe. :-)
http://article.gmane.org/gmane.comp.ide.mseide.user/18779
;-)

> And in IDE's like Maximus or MSEide, it makes such configurations dead
> simple. See the last image of the page below.
>
>   http://fpgui.sourceforge.net/screenshots_apps.shtml
>
If one likes to see the original:
http://mseide-msegui.sourceforge.net/pics/optionsmake.png
http://mseide-msegui.sourceforge.net/pics/optionsdirectories.png
http://mseide-msegui.sourceforge.net/pics/optionsmacros.png

Martin

--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] Compile project release with LCL custom optimization

[Zaher Dirkey]

On Sat, Apr 13, 2013 at 10:44 PM, patspiper  wrote:

> I guess the original proverb is closer to 'tip of the string', meaning
> like the 1st lead or clue of a mystery or case.


​Yes true :) but i used "Yarn" instead of string, because string is
reserved word :P

Sorry for off topic.


Best Regards
Zaher Dirkey
--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] Compile project release with LCL custom optimization

[patspiper]

On 13/04/13 22:34, Martin wrote:

On 13/04/2013 20:27, Zaher Dirkey wrote:

Is is like
if defined(RELEASE) then
   CustomOptions := ' -O-1 ';
If yes it will be the "head of the yarn"(proverb)


Isnt the above identical to the below?

When I did it, I did have to define the MACRO myself. (in the project, 
in each buildmode.


I do not know if there are predefined macros



On Sat, Apr 13, 2013 at 10:17 PM, Martin > wrote:


if defined(MACRONAME) then
   CustomOptions := ' -O-1 ';





"head of the yarn"(proverb)

I couldn't find any reference to that. Neither www.phrases.org.uk nor 
urban dictionary have it. Even google doesn't find anything
I guess the original proverb is closer to 'tip of the string', meaning 
like the 1st lead or clue of a mystery or case.


Stephano
--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] Compile project release with LCL custom optimization

[Zaher Dirkey]

​fpGUI is in my list, but now i like to close my opened projects before
looking up to another sources, we have hard time here.​
Now there is Maximus i like the design :-)

On Sat, Apr 13, 2013 at 10:30 PM, Graeme Geldenhuys  wrote:

>   http://fpgui.sourceforge.net/screenshots_apps.shtml
>
> By default there are six build modes. For source paths I use macros like
> ${fpgui}, ${tiopf} etc... Macro values can be toggled by a single click
> to say which Macro Group you want to use (eg: one group for Windows, one
> for Linux, etc). Also in Maximus, all build modes have keyboard
> shortcuts. I normally use mode 'M - Make' for development with debug
> info, 'B - Build' for releases, and 1-4 for various other things.
>

I am using last revision of Lazarus, FPC 2.6 on Windows XP SP3

Best Regards
Zaher Dirkey
--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] Compile project release with LCL custom optimization

[Martin]

On 13/04/2013 20:27, Zaher Dirkey wrote:

Is is like
if defined(RELEASE) then
   CustomOptions := ' -O-1 ';
If yes it will be the "head of the yarn"(proverb)


Isnt the above identical to the below?

When I did it, I did have to define the MACRO myself. (in the project, 
in each buildmode.


I do not know if there are predefined macros



On Sat, Apr 13, 2013 at 10:17 PM, Martin > wrote:


if defined(MACRONAME) then
   CustomOptions := ' -O-1 ';





"head of the yarn"(proverb)

I couldn't find any reference to that. Neither www.phrases.org.uk nor 
urban dictionary have it. Even google doesn't find anything
--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] Compile project release with LCL custom optimization

[Graeme Geldenhuys]

On 2013-04-13 20:05, Zaher Dirkey wrote:
> ​Not worked for me, i Added $(ProjectOpts) to custom options in SynEdit
> package (same with my packages but i will take SynEdit as example)​
> What i have I Have 2 build mode (Debug, Release)


I use lots of build modes too... like I said, the Lazarus Package idea
was more problems than anything else. Now I just define all source paths
as needed.

And in IDE's like Maximus or MSEide, it makes such configurations dead
simple. See the last image of the page below.

  http://fpgui.sourceforge.net/screenshots_apps.shtml

By default there are six build modes. For source paths I use macros like
${fpgui}, ${tiopf} etc... Macro values can be toggled by a single click
to say which Macro Group you want to use (eg: one group for Windows, one
for Linux, etc). Also in Maximus, all build modes have keyboard
shortcuts. I normally use mode 'M - Make' for development with debug
info, 'B - Build' for releases, and 1-4 for various other things.

Unfortunately the screenshot doesn't use compiler defines in that
configuration, but my projects use many. Simply click which build mode
they belong - as easy as that.


Regards,
  - Graeme -

-- 
fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal
http://fpgui.sourceforge.net/


--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] Compile project release with LCL custom optimization

[Zaher Dirkey]

​Is is like
if defined(RELEASE) then
   CustomOptions := ' -O-1 ';
If yes it will be the "head of the yarn"(proverb)

On Sat, Apr 13, 2013 at 10:17 PM, Martin  wrote:

> if defined(MACRONAME) then
>CustomOptions := ' -O-1 ';
>




-- 
I am using last revision of Lazarus, FPC 2.6 on Windows XP SP3

Best Regards
Zaher Dirkey
--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] Compile project release with LCL custom optimization

[Martin]

Hm, yes, sorry $(ProjectOpts)  may not work. Not sure where I picked it 
up, but I had it as a left over.


If you want to push changed project options, down into the used 
packages, then that is going to be tricky. (Dependencies normally do not 
go that way)


IIRC ( I do no longer have my example, but I did have it working once)
You can define "IDE Macro" or values, in the project (they should be 
able to depend on build mode)


In the package, under IDE macros, you add (in the lower field "conditionals"

if defined(MACRONAME) then
   CustomOptions := ' -O-1 ';



There is a wiki page about that too (sorry havent got the link). It is a 
big page, and a lot to read.



On 13/04/2013 20:05, Zaher Dirkey wrote:
Not worked for me, i Added $(ProjectOpts) to custom options in SynEdit 
package (same with my packages but i will take SynEdit as example)

What i have
I Have 2 build mode (Debug, Release) i want when use Debug all 
compiler option passed to SynEdit package and have debug info and so 
on, When use Release same.


I have tested all adding $(ProjectOpts) or $(IDEBuildOptions) but 
debug not added to the sources.



On Sat, Apr 13, 2013 at 6:06 PM, Martin > wrote:


1) If you want a single package only, open the package and edit
the options  like for a project.

2) Do add the same settings as for the IDE (from "configure build
IDE")
http://imagebin.org/253861
Add $(IDEBuildOptions) to the custom options

Or for the options from the project: $(ProjectOpts)

Check the compiler output ("test" button) for the order it applies.

If one setting has -O1 and the other -O2 then the order matters.
The order can not be changed.

Afaik (please verify, not sure) an -O1 does NOT undo a -O2.
But a -O-1 does undo a -O2

3) For (almost) all packages.
Check package-graph for dependencies on FCL (includes indirect
dependency)

http://imagebin.org/253862





--
I am using last revision of Lazarus, FPC 2.6 on Windows XP SP3

Best Regards
Zaher Dirkey


--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus


--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] Compile project release with LCL custom optimization

[Zaher Dirkey]

​Not worked for me, i Added $(ProjectOpts) to custom options in SynEdit
package (same with my packages but i will take SynEdit as example)​
What i have
I Have 2 build mode (Debug, Release) i want when use Debug all compiler
option passed to SynEdit package and have debug info and so on, When use
Release same.

I have tested all adding $(ProjectOpts) or $(IDEBuildOptions) but debug not
added to the sources.


On Sat, Apr 13, 2013 at 6:06 PM, Martin  wrote:

> 1) If you want a single package only, open the package and edit the
> options  like for a project.
>
> 2) Do add the same settings as for the IDE (from "configure build IDE")
> http://imagebin.org/253861
> Add $(IDEBuildOptions) to the custom options
>
> Or for the options from the project: $(ProjectOpts)
>
> Check the compiler output ("test" button) for the order it applies.
>
> If one setting has -O1 and the other -O2 then the order matters. The order
> can not be changed.
>
> Afaik (please verify, not sure) an -O1 does NOT undo a -O2.
> But a -O-1 does undo a -O2
>
> 3) For (almost) all packages.
> Check package-graph for dependencies on FCL (includes indirect dependency)
>
> http://imagebin.org/253862
>




-- 
I am using last revision of Lazarus, FPC 2.6 on Windows XP SP3

Best Regards
Zaher Dirkey
--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] Compile project release with LCL custom optimization

[Martin]

1) If you want a single package only, open the package and edit the 
options  like for a project.


2) Do add the same settings as for the IDE (from "configure build IDE")
http://imagebin.org/253861
Add $(IDEBuildOptions) to the custom options

Or for the options from the project: $(ProjectOpts)

Check the compiler output ("test" button) for the order it applies.

If one setting has -O1 and the other -O2 then the order matters. The 
order can not be changed.


Afaik (please verify, not sure) an -O1 does NOT undo a -O2.
But a -O-1 does undo a -O2

3) For (almost) all packages.
Check package-graph for dependencies on FCL (includes indirect dependency)

http://imagebin.org/253862


On 13/04/2013 15:51, Zaher Dirkey wrote:

Hi, again, i failed to do that, any example to do it, for SynEdit package?


On Tue, Mar 19, 2013 at 6:43 PM, Martin > wrote:


Yes, with macros you can force packages to be recompiled on
project changes.


You can also change all (almost all) packages very quickly.

Most packages depend on FCL. So in FCL you can add options to the
custom field in the "Usage" section. Anything that uses FCL will
look at that "Usage" section


Thanks

I am using last revision of Lazarus, FPC 2.6 on Windows XP SP3

Best Regards
Zaher Dirkey


--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus


--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] Compile project release with LCL custom optimization

[Zaher Dirkey]

​Hi, again, i failed to do that, any example to do it, for SynEdit package?


On Tue, Mar 19, 2013 at 6:43 PM, Martin  wrote:

> Yes, with macros you can force packages to be recompiled on project
> changes.
>
>
> You can also change all (almost all) packages very quickly.
>
> Most packages depend on FCL. So in FCL you can add options to the custom
> field in the "Usage" section. Anything that uses FCL will look at that
> "Usage" section
>

​Thanks

I am using last revision of Lazarus, FPC 2.6 on Windows XP SP3

Best Regards
Zaher Dirkey
--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] Compile project release with LCL custom optimization

[Martin]

On 19/03/2013 15:38, Graeme Geldenhuys wrote:

On 2013-03-19 11:21, Zaher Dirkey wrote:

I already have mode "Release" with that options, but not sure it take
over LCL sourcecode too.

No, that is the really annoying thing about Lazarus Packages. Settings
do not resonate up the hierarchy. So if you have settings in your
Project, it is only for your project files, and not for any dependant
packages.

Mattias once mentioned there is a possibility of having settings
resonate up the package hierarchy, but that meant Macros and other
trickery - thus modifying all packages that get pulled in by your project.



Yes, with macros you can force packages to be recompiled on project changes.


You can also change all (almost all) packages very quickly.

Most packages depend on FCL. So in FCL you can add options to the custom 
field in the "Usage" section. Anything that uses FCL will look at that 
"Usage" section


--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] Compile project release with LCL custom optimization

[Graeme Geldenhuys]

On 2013-03-19 11:21, Zaher Dirkey wrote:
> 
> I already have mode "Release" with that options, but not sure it take
> over LCL sourcecode too.

No, that is the really annoying thing about Lazarus Packages. Settings
do not resonate up the hierarchy. So if you have settings in your
Project, it is only for your project files, and not for any dependant
packages.

Mattias once mentioned there is a possibility of having settings
resonate up the package hierarchy, but that meant Macros and other
trickery - thus modifying all packages that get pulled in by your project.

Lately I find simply not using Lazarus Packages much easier. I setup a
project template with all the correct search paths for my most used
components (you can do that in fpc.cfg too). Project compiler settings
then apply to ALL source code. This is how I roll these days. YMMV


Regards,
  - Graeme -

-- 
fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal
http://fpgui.sourceforge.net/


--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus

[Lazarus] Compile project release with LCL custom optimization

[Zaher Dirkey]

Hi,

I like when release my project to compile all components and LCL with
special options like change the optimization for example to make the
best file execute.
Is it possible and how when i am using LazBuild in command line?

I already have mode "Release" with that options, but not sure it take
over LCL sourcecode too.

-- 
I am using last revision of Lazarus, FPC 2.6 on Windows XP SP3

Best Regards
Zaher Dirkey

--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus