Hi Jake,

   I too had built a vanilla GNOME 2.10 from sources using the Studio 10 
compiler.
The only difference being, that I did not depend on Blastwave packages. 
I built
almost all of the required libraries, utilites and a few extra apps 
(210+) so that
the binaries will need only few extra packages that already are part of 
Solaris or
are in the Companion CD.

Some comments below:

Jake Hamby wrote:

>Hi everyone,
>
>I just finished building GNOME 2.10 from CVS with JHBuild.  I still have some 
>serious bugs to resolve, but I wanted to share my build notes so far and 
>hopefully we can use this thread to put together a community version of GNOME 
>2.10 while we wait for the next version of JDS.  I'll volunteer to build the 
>binary packages once all the "showstopper" bugs are resolved.
>
   I have built a bunch of extra apps and utilities that are good to 
have in a desktop.
   I am not sure what stuff you have compiled so these may be already be 
present. Anyway
   here's a small list of stuff not already present in Blastwave:

   Mergeant: The new Database Frontend
   libgnomedb, libgda: GNU Data Access required for Mergeant
   GtweakUI: Extra Configuration Tweaks to GNOME without having to 
manually access GConf
   Gtk-Server: Accessing the power of GTK from various scripting 
languages including shells
               This requires libffi (gcc's foreign function interface).
   Dirac Codec and GStreamer plugin, Speex codec
   GtkAm and associated libexif, libexif-gtk, libgphoto: To parse Exif 
information from Digital Cams
         It is possible to access DigiCams from Solaris via USB
   SANE: It is also possible to access Scanners via USB on Solaris
   Ghex: Hex Editor
   gFTP (2.0.17)
   Gtk-thinice-engine: Nice lightweight theme
   CD Paranoia and associated libs
   Evolution

   Skippy: A full-screen task switcher similar to MacOS's Expose'
   Esetroot and Imlib2: Components from Enlightenment. I am using these 
to quickly set the
                        background pixmap rather than have a blank grey 
screen while logging
                        in
   Bluefish: A HTML editor
   Mjpegtools.

   Is it possible to add these to your build system ?

   I also have some customised themes and artwork I can contribute.
   

>1) Prerequisites.  JHBuild is a Python script that checks out (or updates) 
>each module from CVS and builds them in the correct order.  Here are the 
>environment variables I set before compiling:
>
>[...snipped]
>Problems building libIDL: change CPP_PROGRAM from "cc -E" to "gcc -E" or else 
>IDL parser won't work.
>
>ORBit: test/inhibit fails to compile.
>
>libbonobo:  use of nonportable __inline__.  First of many packages where I 
>needed to run "intltoolize --force" by hand to create intltool-*.in files 
>which aren't in CVS and weren't created by autogen.sh.
>
>GConf, gnome-mime-data: won't build with "gmake -j2"
>howl: libhowl needs "-lsocket -lnsl"
>startup-notification: change non-portable __FUNCTION__ to __func__
>
  Gnome-vfs also uses __FUNCTION__. It should be easier to just do 
-D__FUNCTION__=__func__ I guess.

>[...snipped]
>I see now that I have about a dozen more comments to type up so I'll write up 
>those notes in another message.  Besides the mozilla save file bug, the one 
>serious problem I have with the new GNOME 2.10 desktop is that my Applications 
>menu is empty except for "Run Application..."!  I've tried deleting my 
>~/.gnome*, ~/.gconf*, and ~/.nautilus directories, but I don't know enough 
>about how the gnome panel works to understand where it's supposed to get its 
>Applications menu items from.  Since everything is installed into /opt/gnome2, 
>it shouldn't be conflicting with anything from JDS.
>
   I put everything under /opt/gnome2_10 and used a startup script to 
set a variety of ENV
   variables. Gnome panel, metacity and others use these to properly 
locate the Menu entries:
   XDG_DATA_DIRS, XDG_CONFIG_DIRS and GTK_DATA_PREFIX.
   This script also extracts the user's current desktop wallpaper and 
puts it as the root
   pixmap via Esetroot to avoid the boring grey screen while logging in.

   In addition If you switch between JDS and Gnome 2.10 desktops your 
settings and Desktop
   configuration can get screwed up. So I prepared a few scripts to 
create backups of the
   appropriate dotfiles and directories in the user's home directory. 
The proper backup will
   be restored when logging in to either desktop.

   Finally one of the things I wanted is to have a shortcut that will 
ask for the root password
   and launch a root terminal with Xauthority properly setup, so that I 
do not have to use
   xhost/xauth manually. I had trouble with GkSU and ended up writing a 
small utility and a
   script to perform this task.

   I can send you the scripts if you want to take a look.

Regards,
Moinak.

>--
>Jake Hamby
>This message posted from opensolaris.org
>_______________________________________________
>Desktop-discuss mailing list
>Desktop-discuss at opensolaris.org
>  
>



Reply via email to