/usr/share/GNUstep/Documentation/User/GNUstep/gnustep-filesystem/Accessing-Domain-Locations.html is in gnustep-make-doc 2.6.6-3.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 | <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<!-- Created by GNU Texinfo 5.2, http://www.gnu.org/software/texinfo/ -->
<head>
<title>GNUstep Filesystem Hierarchy Document: Accessing Domain Locations</title>
<meta name="description" content="GNUstep Filesystem Hierarchy Document: Accessing Domain Locations">
<meta name="keywords" content="GNUstep Filesystem Hierarchy Document: Accessing Domain Locations">
<meta name="resource-type" content="document">
<meta name="distribution" content="global">
<meta name="Generator" content="makeinfo">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<link href="index.html#Top" rel="start" title="Top">
<link href="Structure-of-a-Domain.html#Structure-of-a-Domain" rel="up" title="Structure of a Domain">
<link href="Applications.html#Applications" rel="next" title="Applications">
<link href="The-GNUstep-Filesystem-Layout.html#The-GNUstep-Filesystem-Layout" rel="prev" title="The GNUstep Filesystem Layout">
<style type="text/css">
<!--
a.summary-letter {text-decoration: none}
blockquote.smallquotation {font-size: smaller}
div.display {margin-left: 3.2em}
div.example {margin-left: 3.2em}
div.indentedblock {margin-left: 3.2em}
div.lisp {margin-left: 3.2em}
div.smalldisplay {margin-left: 3.2em}
div.smallexample {margin-left: 3.2em}
div.smallindentedblock {margin-left: 3.2em; font-size: smaller}
div.smalllisp {margin-left: 3.2em}
kbd {font-style:oblique}
pre.display {font-family: inherit}
pre.format {font-family: inherit}
pre.menu-comment {font-family: serif}
pre.menu-preformatted {font-family: serif}
pre.smalldisplay {font-family: inherit; font-size: smaller}
pre.smallexample {font-size: smaller}
pre.smallformat {font-family: inherit; font-size: smaller}
pre.smalllisp {font-size: smaller}
span.nocodebreak {white-space:nowrap}
span.nolinebreak {white-space:nowrap}
span.roman {font-family:serif; font-weight:normal}
span.sansserif {font-family:sans-serif; font-weight:normal}
ul.no-bullet {list-style: none}
-->
</style>
</head>
<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" vlink="#800080" alink="#FF0000">
<a name="Accessing-Domain-Locations"></a>
<div class="header">
<p>
Next: <a href="Applications.html#Applications" accesskey="n" rel="next">Applications</a>, Previous: <a href="The-GNUstep-Filesystem-Layout.html#The-GNUstep-Filesystem-Layout" accesskey="p" rel="prev">The GNUstep Filesystem Layout</a>, Up: <a href="Structure-of-a-Domain.html#Structure-of-a-Domain" accesskey="u" rel="up">Structure of a Domain</a> </p>
</div>
<hr>
<a name="Accessing-Domain-Locations-1"></a>
<h4 class="subsection">1.5.2 Accessing Domain Locations</h4>
<p>In order to install and run software that uses some resources, you
need to be able to install the resources in the appropriate location,
and your software needs to be able to locate these resources when it’s
running.
</p>
<p>Since domain locations can be mapped to arbitrary locations on disk,
you must use the appropriate gnustep-make and gnustep-base facilities
to install things in the right place and to find things at runtime.
</p>
<p>GNUstep-make creates makefile variables for all the domain locations.
If you need to perform some custom installation for your software, you
must use these variables to make sure your installation will work with
all filesystem layouts. For example, the <samp>Applications</samp> location
for the domain where the software will be installed is available as
the <code>GNUSTEP_APPS</code> variable. You can also access the locations
for specific domains by using the variables
<code>GNUSTEP_SYSTEM_APPS</code>, <code>GNUSTEP_NETWORK_APPS</code>,
<code>GNUSTEP_LOCAL_APPS</code> and <code>GNUSTEP_USER_APPS</code>.
</p>
<p>GNUstep-base provides you with the
<code>NSSearchPathForDirectoriesInDomains()</code> function that allows you
to retrieve the domain locations at runtime. You must lookup
resources only via this function. For example, the
<samp>Applications</samp> location can be found by using the
<code>NSApplicationDirectory</code> directory key, so you can use it in your
software to iterate over all the <samp>Applications</samp> directories in
the various domains searching for an application.
</p>
<p>In general, all interesting domain locations have a set of variables
defined in gnustep-make (such as <code>GNUSTEP_APPS</code>,
<code>GNUSTEP_SYSTEM_APPS</code>, <code>GNUSTEP_NETWORK_APPS</code>,
<code>GNUSTEP_LOCAL_APPS</code> and <code>GNUSTEP_USER_APPS</code>) and a
corresponding directory key in gnustep-base (such as
<code>NSApplicationDirectory</code>).
</p>
<p>When examining the various domain locations, we will explicitly
mention the gnustep-make variables and the gnustep-base directory keys
that can be used to access them.
</p>
<hr>
<div class="header">
<p>
Next: <a href="Applications.html#Applications" accesskey="n" rel="next">Applications</a>, Previous: <a href="The-GNUstep-Filesystem-Layout.html#The-GNUstep-Filesystem-Layout" accesskey="p" rel="prev">The GNUstep Filesystem Layout</a>, Up: <a href="Structure-of-a-Domain.html#Structure-of-a-Domain" accesskey="u" rel="up">Structure of a Domain</a> </p>
</div>
</body>
</html>
|