Re: [platform-swt-dev] gtk port

["James Moody/OTT/OTI" <James_Moody@xxxxxxx>]

Havoc,

Well, we have some tools here at OTI which produce the ZIP files that you
see on the download pages automatically. I don't know in what state
they are, and I don't know if they're in the repository (i.e. if they're 
open
source). They're command-line driven, and I'm sure they could be
modified to output .RPMs (your favourite) or .DEBs (my favourite). :-)

[By the way, as you've noticed the GTK+ port isn't currently in the
open source repository. Stay tuned and someone more knowledgable
and powerful than I will inform you further].

Actually, if you look at the "windows" install and the "linux" (motif) 
install
files (ZIP and tarball, respectively), you'll notice that the only 
difference 
effectively is the eclipse executable. On X, this is independent of a 
widget
toolkit, it's just a top-level shell and a pixmap. In particular, I think 
that
all versions of swt (win32, motif, photon) are included in each drop, and
the selection of which one to use at runtime is determined by the -ws
and -os parameters. A proper GTK build would just add the directory 
org.eclipse.swt\ws\gtk to the build, which would contain the shared
library for the JNI + the jar file and source file for the SWT 
implementation.
You would pass "-ws gtk" on the command line and away you go.

The idea of building linux packages in a form other than .tar.gz is
interesting, because the current usage model is that the eclipse/ contents
is personal, i.e. I unzip eclipse in my home directory and away I go. That
doesn't mean is HAS to be, since obviously the workbench and plugins
can be in some root-accessible place as long as my workspace is
in my home directory. All I mean is that I'm not what the current story
is for the distribution of a system-wide eclipse for common use. In that
scenario, where do the plugins go that I want to use myself? Does 
root have to install them for me? But this is for someone else to worry
about...

But as you say, I wouldn't worry about the build issues for now. As far 
as I know it would be trivial for us to start producing builds including 
GTK+ when the code becomes available, and such builds are not 
necessary for normal coding and development.

Hope this helps,

james





Havoc Pennington <hp@xxxxxxxxxx>
Sent by: platform-swt-dev-admin@xxxxxxxxxxx
11/14/2001 05:23 PM
Please respond to platform-swt-dev

 
        To:     platform-swt-dev@xxxxxxxxxxx
        cc: 
        Subject:        Re: [platform-swt-dev] gtk port


"James Moody/OTT/OTI" <James_Moody@xxxxxxx> writes:
> I think he just wants to know how to self-host and run a workbench with 
> his changes in it.
> If that is the case, you don't need to build a new executable or new 
jars 
> or anything. 
> (Havoc, self-hosting is our term for developing Eclipse within Eclipse 
and 
> running 
> a second Eclipse workbench with your changes in it to try it out).
> 
> The steps we use on the VCM team are (SWT team members can correct if 
> their setup differs):
> 
> 1. Start Eclipse workbench.
> 2. Add the projects you want to hack on to the workspace using the 
> repositories view
>         and anonymous CVS.
> 3. Change code, implement new features, etc.
> 4. Select the project, Properties->Launcher. Select "Run-time 
Workbench". 
> You only have
> to do this step once.
> 5. Select the project and hit the running man icon in the Java 
> perspective.
> 
> A new workbench will appear, and should be running with your changes. 
SWT 
> folk can fill you
> in on anything I got wrong above.
> 

Perfect, I got this mostly working (my previous problem with the
Repository View was that I was using Project Versions instead of
Streams).

So I'm predicting there's no way to do this from the command line?
That makes the traditional SRPM packaging method on Linux tricky, but
it's not necessary for us to get started with development.

Havoc
_______________________________________________
platform-swt-dev mailing list
platform-swt-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-swt-dev