![]() System : Linux absol.cf 5.4.0-198-generic #218-Ubuntu SMP Fri Sep 27 20:18:53 UTC 2024 x86_64 User : www-data ( 33) PHP Version : 7.4.33 Disable Function : pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wifcontinued,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_get_handler,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority,pcntl_async_signals,pcntl_unshare, Directory : /usr/share/GNUstep/Documentation/User/GNUstep/gnustep-filesystem/ |
Upload File : |
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <!-- Created by GNU Texinfo 6.5, http://www.gnu.org/software/texinfo/ --> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> <title>Accessing Domain Locations (GNUstep Filesystem Hierarchy Document)</title> <meta name="description" content="Accessing Domain Locations (GNUstep Filesystem Hierarchy Document)"> <meta name="keywords" content="Accessing Domain Locations (GNUstep Filesystem Hierarchy Document)"> <meta name="resource-type" content="document"> <meta name="distribution" content="global"> <meta name="Generator" content="makeinfo"> <link href="index.html#Top" rel="start" title="Top"> <link href="index.html#SEC_Contents" rel="contents" title="Table of Contents"> <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.indentedblock {margin-right: 0em} blockquote.smallindentedblock {margin-right: 0em; font-size: smaller} blockquote.smallquotation {font-size: smaller} div.display {margin-left: 3.2em} div.example {margin-left: 3.2em} div.lisp {margin-left: 3.2em} div.smalldisplay {margin-left: 3.2em} div.smallexample {margin-left: 3.2em} 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.nolinebreak {white-space: nowrap} span.roman {font-family: initial; font-weight: normal} span.sansserif {font-family: sans-serif; font-weight: normal} ul.no-bullet {list-style: none} --> </style> </head> <body lang="en"> <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> [<a href="index.html#SEC_Contents" title="Table of contents" rel="contents">Contents</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> [<a href="index.html#SEC_Contents" title="Table of contents" rel="contents">Contents</a>]</p> </div> </body> </html>