Add the GNOME porting guide to CVS.
This commit is contained in:
parent
fd1dd088fd
commit
f715183249
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/www/; revision=11632
2 changed files with 67 additions and 0 deletions
|
@ -8,5 +8,6 @@
|
|||
.endif
|
||||
|
||||
DOCS= faq.sgml
|
||||
DOCS+= porting.sgml
|
||||
|
||||
.include "${WEB_PREFIX}/share/mk/web.site.mk"
|
||||
|
|
66
en/gnome/docs/porting.sgml
Normal file
66
en/gnome/docs/porting.sgml
Normal file
|
@ -0,0 +1,66 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" [
|
||||
<!ENTITY base CDATA "../..">
|
||||
<!ENTITY date "$FreeBSD$">
|
||||
<!ENTITY title "FreeBSD GNOME Project: How To Make a Port">
|
||||
<!ENTITY email 'freebsd-gnome'>
|
||||
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
|
||||
]>
|
||||
<html>
|
||||
&header;
|
||||
|
||||
<table border="0">
|
||||
<tr>
|
||||
<td>
|
||||
<P>General instructions can be found in the <A HREF="http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/index.html">FreeBSD Porter's Handbook</A>.
|
||||
<P>For ports that <I>require</I> GNOME, you should define the following in your
|
||||
port's Makefile:</P>
|
||||
|
||||
<PRE>
|
||||
USE_GNOME= yes
|
||||
USE_X_PREFIX= yes
|
||||
</PRE>
|
||||
|
||||
<P>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:</P>
|
||||
|
||||
<PRE>
|
||||
WANT_GNOME= yes
|
||||
</PRE>
|
||||
|
||||
<P>If the user has defined <tt>WITH_GNOME</tt> in their <tt>/etc/make.conf</tt>
|
||||
then GNOME components will be built. Other useful GNOME-related macros
|
||||
that can be define in your port's Makefile include:</P>
|
||||
|
||||
<UL>
|
||||
<LI><p><tt>USE_GLIB (WANT_GLIB)</tt> : The application requires (can use) Glib.
|
||||
Defining <tt>USE_GNOME</tt> or <tt>USE_GTK</tt> takes care of this option
|
||||
automatically.</p></LI>
|
||||
<LI><p><tt>USE_GTK (WANT_GTK)</tt> : The application may not be GNOME-compliant, but
|
||||
requires GTK+ widgets. This will take care of those dependencies. Note, this
|
||||
option should <B>not</B> be defined if <tt>USE_GNOME</tt> is defined.</p></LI>
|
||||
<LI><p><tt>USE_ESOUND (WANT_ESOUND)</tt> : The application requires (can use)
|
||||
Esound. Normally, Esound support is added by specifying <tt>USE_GNOME</tt>.
|
||||
</p></LI>
|
||||
<LI><p><tt>USE_IMLIB (WANT_IMLIB)</tt> : The application requires (can use) the
|
||||
Imlib image library. This is not needed if <tt>USE_GNOME</tt> is defined.
|
||||
</p></LI>
|
||||
<LI><p><tt>USE_GNOMELIBS (WANT_GNOMELIBS)</tt> : The application requires (can use)
|
||||
GNOME libraries. This does not import as many dependencies as
|
||||
<tt>USE_GNOME</tt> 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.</p></LI>
|
||||
<LI><p><tt>USE_GNOMECTRL (WANT_GNOMECTRL)</tt> : 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.
|
||||
</p></LI>
|
||||
</UL>
|
||||
|
||||
<P>The more ported applications we have, the better.
|
||||
</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
&footer;
|
||||
</BODY>
|
||||
</HTML>
|
Loading…
Add table
Add a link
Reference in a new issue