Would you please make LCLWidgetType more easy to define it in Project options instead of define it in IDE macros

And more, also passing conditional values like "DEBUG" in a text box.

Best Regards
Zaher Dirkey
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20130406/a653edca/attachment.html>

Zaher Dirkey wrote

Would you please make LCLWidgetType more easy to define it in Project options instead of define it in IDE macros And more, also passing conditional values like "DEBUG" in a text box.

Please post feature requests in the bugtracker so they don't get forgotten...

On Sun, Apr 7, 2013 at 5:03 AM, Reinier Olislagers <

?Done?

http://bugs.freepascal.org/view.php?id=24244

Zaher Dirkey wrote

Would you please make LCLWidgetType more easy to define it in Project options instead of define it in IDE macros

I played with this a lit and did not find it "uneasy" at all (once you understand how it works). (Regarding you usually need do do this not very often during your workflow.)

-Michael
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20130408/ad513976/attachment.html>

Regarding you usually need do do this not very often during your workflow.

I suppose what you mean is to create build mode for each

Michael Schnell wrote

I played with this a lit and did not find it "uneasy" at all (once you understand how it works).

?When
?youneed to compile for Wince you need to define 4 parameters in compile options, OS, cpu, processor(we can leave it) ? then the widgetset, what you expected to see this field with its brothers fields not in "IDE macro Values"?

?I have bad memory, i always forget where is the last one, not easy believe me.
?

Best Regards
Zaher Dirkey
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20130408/1376ed53/attachment.html>

When you set OS wince then the default widgetset is wince. So you only need to set OS and CPU.

?I have bad memory, i always forget where is the last one, not easy believe me.

Mattias

?I retested it with new project i get this error

W:\programs\lazarus\components\lazutils\ttinterp.pas(736,23) Hint: Mixing signed expressions and longwords gives a 64bit result "Compiling package LazUtils 1.0" completed
"Compiling package LCLBase 1.0.1" completed
win32\win32wsdialogs.pp(38,12) Fatal: Can't find unit shlobj used by Win32WSDialogs
?
So it seem a bug?

Mattias Gaertner wrote

When you set OS wince then the default widgetset is wince. So you only need to set OS and CPU.

Either that or you have some misconfiguration.

What do you see in "Project / Project Options / Compiler Options / Inherited"?

What do you see in "View / IDE Internals / About FPC"? You don't need to post all paths.

Mattias

?All

W:\programs\lazarus\lcl\units\arm-wince\win32
W:\programs\lazarus\lcl\units\arm-wince
W:\programs\lazarus\components\lazutils\lib\arm-wince W:\programs\lazarus\packager\units\arm-wince
?
?LCL 1.0.1?

W:\programs\lazarus\lcl\units\arm-wince\win32

?But why i have it, it is very new project??

--------------------
Lazarus version: 1.1
Lazarus svn revision: 40683M
Lazarus build date: 2013/04/03
Lazarus was compiled for i386-win32
Lazarus was compiled with fpc 2.6.2

Global IDE options:
LazarusDirectory=w:\programs\lazarus\
Resolved LazarusDirectory=W:\programs\lazarus\
CompilerFilename=P:\programs\fpc\2.6\bin\i386-Win32\fpc.exe Resolved CompilerFilename=P:\programs\fpc\2.6\bin\i386-Win32\fpc.exe CompilerMessagesFilename=
Resolved CompilerMessagesFilename=

Project:
lpi=C:\temp\project1.lpi
Directory=C:\temp\
TargetOS=wince
TargetCPU=arm
CompilerFilename=$(CompPath)

Active target:
TargetOS=wince
TargetCPU=arm

FPC executable:
Compiler=P:\programs\fpc\2.6\bin\i386-Win32\fpc.exe Options=
CompilerDate=12/02/2013 18:55:52
RealCompiler=P:\programs\fpc\2.6\bin\i386-Win32\ppcrossarm.exe RealCompilerDate=12/02/2013 19:04:52
RealTargetOS=wince
RealTargetCPU=arm
RealCompilerInPath=P:\programs\fpc\2.6\bin\i386-Win32\ppcrossarm.exe Version=2.6.2
CfgFilename=P:\programs\fpc\2.6\bin\i386-Win32\fpc.cfg --------------------------

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

Best Regards
Zaher Dirkey
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20130408/37269e41/attachment-0001.html>

I can reproduce it (Linux -> WinCE cross-compilation) if I don't set explicitly the widgetset to WinCE:
gtk2/gtk2int.pas(56,3) Fatal: Can't find unit gdk2pixbuf used by Gtk2Int

What do you see in "Project / Project Options / Compiler Options / Inherited"?

All (notice the gtk2):
/home/me/Programs/lazarus/lazarus-svn/lcl/units/arm-wince/gtk2 <- LCL 1.0.1 package
/home/me/Programs/lazarus/lazarus-svn/lcl/units/arm-wince <- LCLBase 1.0.1 package
/home/me/Programs/lazarus/lazarus-svn/components/lazutils/lib/arm-wince /home/me/Programs/lazarus/lazarus-svn/packager/units/arm-wince

What do you see in "View / IDE Internals / About FPC"? You don't need to post all paths.

Lazarus version: 1.1
Lazarus svn revision: 40749
Lazarus build date: 2013/04/08
Lazarus was compiled for i386-linux
Lazarus was compiled with fpc 2.6.3

Global IDE options:
LazarusDirectory=../lazarus-svn/
Resolved LazarusDirectory=/home/me/Programs/lazarus/lazarus-svn/ CompilerFilename=fpc
Resolved CompilerFilename=/home/me/Programs/fpc/2.6.3/bin/fpc CompilerMessagesFilename=
Resolved CompilerMessagesFilename=

Project:
lpi=
Directory=
TargetOS=wince
TargetCPU=arm
CompilerFilename=$(CompPath)

Active target:
TargetOS=wince
TargetCPU=arm

FPC executable:
Compiler=/home/me/Programs/fpc/2.6.3/bin/fpc
Options=
CompilerDate=08/04/13 8:47:32 PM
RealCompiler=/home/me/Programs/fpc/2.6.3/lib/fpc/2.6.3/ppcrossarm RealCompilerDate=08/04/13 8:49:51 PM
RealTargetOS=wince
RealTargetCPU=arm
RealCompilerInPath=/home/me/Programs/fpc/2.6.3/lib/fpc/2.6.3/ppcrossarm Version=2.6.3
CfgFilename=/home/me/.fpc.cfg

Stephano

[...] >> So it seem a bug?

Yes. Fixed.

Please test.

Mattias

The CVS Version supports definable project-specific or global "build mode" setting, that seem to do what you want. (Right now this feature is marked as "under construction".

-Michael

Michael Schnell wrote

The CVS Version supports definable project-specific or global "build mode" setting, that seem to do what you want. (Right now this feature is marked as "under construction".

Yes, this "under construction" is by me. I faced some technical problems and it takes more time than expected.
However, only the GUI is under construction. Build modes already work, just their user interface is not very intuitive.
Now the build mode tab is at the same level with other settings tabs. It should be visually "above" the others to indicate that it applies to all of them.

Yet, I will only change the user interface, not the functionality.

Juha

Thanks for this !

So I already can happily use it ? (I did not dare to try it, yet.)

-Michael

Michael Schnell wrote

So I already can happily use it ? (I did not dare to try it, yet.)

Yes. The feature is made by Mattias and has worked well already for some time.

Juha

It is OK now. Thanks on behalf of the OP (Zaher Dirkey)

:)

Stephano

I'm sure the release notes must have mentioned it as well... if not, they should ;)

Juha Manninen wrote

On 4/9/13, Michael Schnell wrote: > So I already can happily use it ? (I did not dare to try it, yet.) Yes. The feature is made by Mattias and has worked well already for some time.

Is the under construction interface functional? Here it only provides a dropdown list which does nothing.

Btw, build modes can be a little bit difficult to use. In a use case close to the OP's, compilation may be required for Win32/i386, Linux/i386, WinCE/arm, and Linux/arm (4 build modes). If debug and release modes are needed on top, the number of build modes goes up to 8. These can be defined once, and set as project defaults.

However, the difficulty is in switching build modes. Using the change build mode dropdown toolbar button (to the left of the run button) is acceptable for a few build modes, but becomes difficult to use with a large number of build modes. A solution could be to let the user define a list of 'generic' build modes list (names only) and have a matrix to define which combination (generic mode + debug/release) yields which actual build mode (see attached mockup). The build mode selection dropdown button would be extended to include 2 dropdowns, one for the generic mode and the other for debug/release. A debug/release macro would be useful for the output path.

Another nice feature to have is the ability to use LCL, FCL, and or other installed packages debug/release ppu's (to debug Lazarus and/or FPC code). We can have 2 folders (release and debug) for each Lazarus package, while a macro (like FPCVER) decides which one gets used. I am not sure where the GUI setting should be.

Stephano
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Buildmodes.jpg
Type: image/jpeg
Size: 19113 bytes
Desc: not available
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20130409/21cabb5f/attachment-0001.jpg>

Michael Schnell wrote

The CVS Version supports definable project-specific or global "build mode" setting, that seem to do what you want. (Right now this feature is marked as "under construction".

yep! i had this working on my setup at one time but then when it went "under construction" it doesn't look the same any more and i haven't figured out how it should work now as compared to the (slightly convoluted) way it worked previously :?

Tested and works for me too,

But still need to be easy to set it in same options window, the idea sometime i like to set GTK2 or QT in Windows, and maybe in Linux.

Thanks