The correct word for that is architecture. (for differences in processor-target)

+ From: Jeff Wormsley
+
+ On 1/31/2002 at 7:28 PM Michael A. Hess wrote:
+
+ >That is what LCL_PLATFORM indicates.
+ >
+ >OS_TARGET is used to indicate differences in OS.
+ >
+ >The problem I originally indicated is that portions of the default
+ >makefile assumes that win32 OS will only every use win32
+ >widget set. It needs to be flexible. As you indicated this will
+ >also be a problem if qt is desired for Linux.
+
+ Ok, so the core problem is the makefile.
+
+ The term LCL_PLATFORM isn't quite as descriptive as it could
+ be. The word platform to me brought to mind Windows vs Linux
+ vs FreeBSD, etc. which is, as you say, OS_TARGET, which does
+ make more sense. On second look at the word platform, if I
+ didn't know better, I would think it meant x86 vs. Sparc vs.
+ m68K, but that makes no sense with the LCL prefix. That it
+ meant widget set didn't occur to me.

Yeah..... At that time I needed a variable to make a difference in the makefiles. Didn't think that hard :-)

Marc

----- Original Message -----

Greetings,

Well it can be made to work but not straight out of the box.

There is a new Win32-GTK available. (labeled as not stable). However it does contain the various items that we are using in GTK in the Linux version. I downloaded these new libraries.

I modified the FPC GKT code to know about the new libraries and to remove some of the ifndef Win32 items indicated in the code. I then rebuilt the FPC GTK unit.

Next I had to monkey with the current make files. The current configuration doesn't allow for the command line selection of LCL_PLATFORM. In the interfaces makefiles it has

[target]
dirs_win32=win32

This needs to be changed to

dirs_win32=gtk

and the Makefile rebuild. Other wise it doesn't try to use the correct API set.

Peter,

Is there someway of make this so that you can just indicate 'make LCL_PLATFORM=gtk' and have it work correctly?

I also had to add gtk to some of the packages in the makefile.fpc so that it know to use those. We will probably have to modify package.fpc files.

Anyway after that it actually builds and runs.

Here is URL to download and installation of Lazarus using GTK.

http://ehost.bdhosting.com/~mhess/lazarus_ide_installer.exe

Please let me know if have you have problems with this installation.

Ok, so the core problem is the makefile.

The term LCL_PLATFORM isn't quite as descriptive as it could be. The word platform to me brought to mind Windows vs Linux vs FreeBSD, etc. which is, as you say, OS_TARGET, which does make more sense. On second look at the word platform, if I didn't know better, I would think it meant x86 vs. Sparc vs. m68K, but that makes no sense with the LCL prefix. That it meant widget set didn't occur to me.

Sorry for the confusion, I'll return to lurking now. :^)

Jeff.

I hesitate to do so. The GTK-Win32 developers call the release 'for developers only'. They don't consider it to be releaseable for general use. Second they have gone with a completely different naming structure which is closer to Unix. This means that the FPC GTK units would have to look for a totally different library breaking older code. Previous releases all maintained the same .dll name so you could update the unit without breaking older code that didn't use the new features. Next with the 1.0.6 release just around the corner I don't think it would be a good idea to mess with the apple cart at this time.

Besides at this time the only way to do a GTK build is to hand edit the Makefile.fpc from it's current cvs checkout state. I would rather see it be selectable at the commandline.

That is what LCL_PLATFORM indicates.

OS_TARGET is used to indicate differences in OS.

Might work on the linux side as well if anyone ever does a qt version.

If you indicated LCL_PLATFORM=qt that is the widget set it would try to use regardless of the OS.

The problem I originally indicated is that portions of the default makefile assumes that win32 OS will only every use win32 widget set. It needs to be flexible. As you indicated this will also be a problem if qt is desired for Linux.

PM Michael A. Hess wrote

Is there someway of make this so that you can just indicate 'make LCL_PLATFORM=gtk' and have it work correctly?

Wouldn't the LCL_PLATFORM still be win32. Sounds like it needs an LCL_WIDGETSET to differentiate between gtk and win32 native. Might work on the linux side as well if anyone ever does a qt version.

Just a thought, no dog in the hunt anymore, so maybe I am misreading the purpose of LCL_PLATFORM.

Jeff.