diff --git a/en/gnome/docs/porting.sgml b/en/gnome/docs/porting.sgml index 7ba633e5b7..a918e61ac0 100644 --- a/en/gnome/docs/porting.sgml +++ b/en/gnome/docs/porting.sgml @@ -6,61 +6,73 @@ %includes; ]> -&header; + &header; - - - + +
-

General instructions can be found in the FreeBSD Porter's Handbook. -

For ports that require GNOME, you should define the following in your -port's Makefile:

+ + + - -
+

General instructions can be found in the + FreeBSD Porter's Handbook. +

+

For ports that require GNOME, you should define the following + in your port's Makefile:

-
+        
 USE_GNOME=	yes
 USE_X_PREFIX=	yes
-
+
-

These will take care of the install prefix and requiring all the core GNOME -dependencies. If your port can use GNOME, but it isn't required, you can -define the following in your Makefile:

+

These will take care of the install prefix and requiring all the + core GNOME dependencies. If your port can use GNOME, but it isn't + required, you can define the following in your Makefile:

-
+        
 WANT_GNOME=	yes
-
+
-

If the user has defined WITH_GNOME in their /etc/make.conf -then GNOME components will be built. Other useful GNOME-related macros -that can be define in your port's Makefile include:

+

If the user has defined WITH_GNOME in their + /etc/make.conf then GNOME components will be built. + Other useful GNOME-related macros that can be define in your port's + Makefile include:

-
    -
  • USE_GLIB (WANT_GLIB) : The application requires (can use) Glib. -Defining USE_GNOME or USE_GTK takes care of this option -automatically.

  • -
  • USE_GTK (WANT_GTK) : The application may not be GNOME-compliant, but -requires GTK+ widgets. This will take care of those dependencies. Note, this -option should not be defined if USE_GNOME is defined.

  • -
  • USE_ESOUND (WANT_ESOUND) : The application requires (can use) -Esound. Normally, Esound support is added by specifying USE_GNOME. -

  • -
  • USE_IMLIB (WANT_IMLIB) : The application requires (can use) the -Imlib image library. This is not needed if USE_GNOME is defined. -

  • -
  • USE_GNOMELIBS (WANT_GNOMELIBS) : The application requires (can use) -GNOME libraries. This does not import as many dependencies as -USE_GNOME and should be used for applications that use GNOME, but -do not need the GNOME Control Center, the GNOME capplet library, or -anything from the GNOME Core.

  • -
  • USE_GNOMECTRL (WANT_GNOMECTRL) : The application requires -(can use) all the GNOME libraries and the GNOME Control Center, but does not -use anything from GNOME Core. This option is usually used for backend APIs. -

  • -
+ +
    +
  • USE_GLIB (WANT_GLIB) : The application requires + (can use) Glib. Defining USE_GNOME or USE_GTK + takes care of this option automatically.

  • -

    The more ported applications we have, the better. -

+
  • USE_GTK (WANT_GTK) : The application may not be + GNOME-compliant, but requires GTK+ widgets. This will take care of + those dependencies. Note, this option should not be defined + if USE_GNOME is defined.

  • -&footer; +
  • USE_ESOUND (WANT_ESOUND) : The application requires + (can use) Esound. Normally, Esound support is added by specifying + USE_GNOME.

  • + +
  • USE_IMLIB (WANT_IMLIB) : The application requires + (can use) the Imlib image library. This is not needed if + USE_GNOME is defined.

  • + +
  • USE_GNOMELIBS (WANT_GNOMELIBS) : The application + requires (can use) GNOME libraries. This does not import as many + dependencies as USE_GNOME and should be used for + applications that use GNOME, but do not need the GNOME Control + Center, the GNOME capplet library, or anything from the GNOME + Core.

  • + +
  • USE_GNOMECTRL (WANT_GNOMECTRL) : The application + requires (can use) all the GNOME libraries and the GNOME Control + Center, but does not use anything from GNOME Core. This option is + usually used for backend APIs.

  • + + + +

    The more ported applications we have, the better. +

    + + &footer;