Changeset 111

Show
Ignore:
Timestamp:
05/28/05 13:22:42 (3 years ago)
Author:
aldacron
Message:

* added a heading to the top of each HTML doc so that, when navigating through the links in the left frame, it is easy to see which page you are on
* corrected several spelling mistakes and improved readability in the general docs

Files:

Legend:

Unmodified
Added
Removed
Modified
Copied
Moved

  • trunk/docs/al.html

    r109 r111  
    22<head><title>DerelictAL</title></head> 
    33<body> 
     4<hr> 
     5<hr> 
     6<h2 align="center">DerelictAL</h2> 
     7<hr> 
     8<hr> 
    49<h3>Introduction</h3> 
    510DerelictAL is a D binding to the <a href="http://www.openal.org">OpenAL</a> 
    6 library. Note that some functions have been omitted from the binding. This was 
     11library. 
     12<p> 
     13<b>NOTE</b>: some functions have been omitted from the binding. This was 
    714done because the functions were, in the C headers, either marked as unused or 
    815flagged for removal in the future. Also, no bindings for the alut* functions are 
    …… 
    1219on other platforms, then DerelictAL will eventually expose them on those platforms 
    1320as well. 
    14  
     21</p> 
    1522<h3>Using</h3> 
    1623<ol> 
    …… 
    6976<li> ensure that Derek Parnell's Build utility is on your path OR that the path 
    7077to it is configured in buildconfig.bat in your toplevel Derelict directory 
    71 (henceforth known as &lt derelict_dir &gt). See the documentation about  
     78(henceforth known as [derelict_dir]). See the documentation about  
    7279<a href="build.html">Derek Parnell's Build Utility</a> for more information on 
    7380setting up Build and configuring Derelict's Build scripts.</li> 
    74 <li>from a command prompt, cd to &lt derelict_dir &gt\DerelictAL</li> 
     81<li>from a command prompt, cd to [derelict_dir]\DerelictAL</li> 
    7582<li>type <tt>buildme.bat</tt></li> 
    76 <li>when the build completes, your command prompt will be back in &lt derelict_dir &gt, 
    77 and the file derelictAL.lib will be located in &lt derelict_dir &gt\lib.</li> 
     83<li>when the build completes, your command prompt will be back in [derelict_dir], 
     84and the file derelictAL.lib will be located in [derelict_dir]\lib.</li> 
    7885</ol> 
    7986<p> 
    …… 
    8289<p><ol> 
    8390<li>ensure that both dmd and gcc are on your path</li> 
    84 <li>from a command prompt, cd to &lt derelict_dir &gt/DerelictAL</li> 
     91<li>from a command prompt, cd to [derelict_dir]/DerelictAL</li> 
    8592<li>type 'make' or 'make all' to build derelictAL.a</li> 
    8693<li>optionally type 'make clean' to delete all object files OR 

  • trunk/docs/build.html

    r109 r111  
    22<head><title>Derek Parnell's Build Utility</title></head> 
    33<body> 
     4<hr> 
     5<hr> 
     6<h2 align="center">Derek Parnell's Build Utility</h2> 
     7<hr> 
     8<hr> 
    49<h3>Introduction</h3> 
    510The Build utility, created and maintained by Derek Parnell, is an incredibly 
    …… 
    1318Build entirely eliminates the need for Makefiles. If you have ever maintained 
    1419project Makefiles for multiple platforms, you will appreciate what that means. 
    15 The big thing for me, as maintainer of Derelict, is that it means a huge savings 
     20The big thing for me, as a maintainer of Derelict, is that it means a huge savings 
    1621in time. As such, Makefiles are no longer maintained as part of the Derelict 
    1722project. Derelict now requires the use of the Build utility if you want to build 
    …… 
    2126</p> 
    2227<p> 
    23 <b>NOTE:</b> Derelict still uses Makefiles on Linux. This will change once 
    24 shell scripts have been created and tested. 
     28<b>NOTE:</b> Derelict still uses Makefiles on Linux. This will change once Linux 
     29build scripts have been created and tested. 
    2530</p> 
    2631 
    …… 
    4045so that the build scripts on each platform need not be changed every time a new 
    4146command line option is added to the project - each platform shares the same 
    42 Build Response File (excepting any platform-specific options). 
     47Build Response File (excepting any platform-specific options, and options that 
     48are common across release and debug builds). 
    4349<p> 
    4450Building Derelict with the Build utility is as simple as this: 
    …… 
    5157That's it. Every Derelict package you have in that directory will be built. Once 
    5258complete, the resulting library files will be found in the <tt>lib</tt> directory 
    53 (&lt derelict_dir &gt>/lib). You may then leave them there or copy them elsewhere 
     59([derelict_dir]/lib). You may then leave them there or copy them elsewhere 
    5460as you wish. If you would ever like to delete all of the libraries, execute the 
    5561<tt>cleanlib</tt> script in the top-level Derelict directory. 
    …… 
    5864<h3>Building Individual Derelict Packages</h3> 
    5965Each Derelict package has its own <tt>buildme</tt> script in the package 
    60 directory (i.e. &lt derelict_dir &gt\&lt package_name &gt\buildme.bat on Windows). 
     66directory (i.e. [derelict_dir]\[package_name]\buildme.bat on Windows). 
    6167If you have multiple packages, you can build an individual package like this: 
    6268<p><ol> 
    63 <li>CD to the package's directory (&lt derelict_dir &gt/&lt package_name &gt).</li> 
     69<li>CD to the package's directory ([derelict_dir]/[package_name]).</li> 
    6470<li>type <tt>buildme</tt> on windows, or <tt>./buildme</tt> on Linux.</li> 
    6571</ol> 
    6672</p><p> 
    6773Once complete, the resulting library file will be found in the <tt>lib</tt>  
    68 directory (&lt derelict_dir &gt>/lib). <b>IMPORTANT:</b> Also, when the build 
     74directory ([derelict_dir]/lib). <b>IMPORTANT:</b> Also, when the build 
    6975completes, the command prompt will be located in the top-level Derelict directory 
    7076rather than the package directory. Though that is something most people won't 
    …… 
    8389</p><p> 
    8490<ul> 
    85 <li><b>BUILD_CMD</b>: This is the command that runs Build utility executable. If 
     91<li><b>BUILD_CMD</b>: This is the command that runs the Build utility executable. If 
    8692the path to Build is on your system path and you have renamed (or created an alias  
    8793to) the downloaded executable as  <tt>build</tt>, you need not change this. If it 
    …… 
    105111options listed here <b>are required</b> for the build to complete successfully, 
    106112with the exception of the <tt>-cleanup</tt> argument (which you may safely remove 
    107 if you wish to keep the compiled object filed rather than deleting them).</li> 
     113if you wish to keep the compiled object files rather than deleting them).</li> 
    108114</ul> 
    109115</p><p> 

  • trunk/docs/credit.html

    r110 r111  
    11<html="en"> 
    2 <head><title>Credits</title></head> 
     2<head><title>Crontributors</title></head> 
    33<body> 
    44 
     5<hr> 
     6<hr> 
     7<h2 align="center">Contributors</h2> 
     8<hr> 
     9<hr> 
    510<h3>Credit Where Credit is Due</h3> 
    611When I first started Derelict, I did it because it was something I needed. I  
    712decided to make it available to the D community at large in case other D  
    8 programmers would need it. I never really expected that anyone would. Thus, it  
    9 was surprising to learn that not only were people using it, but they were willing 
    10 to contribute to it!  
     13programmers found a need for it also. I never really expected that anyone would.  
     14Thus, it was surprising to learn that not only were people using it, but they  
     15were willing to contribute to it!  
    1116<p> 
    1217Contributions have come in various forms: bug reports, bug fixes, new ports, 
    13 and advice. For the first year of Derelict's existance, I did not maintain a 
     18and advice. For the first year of Derelict's existence, I did not maintain a 
    1419list of contributors. But, most everyone is on record in the forums (or my email 
    1520box). Names in parentheses are the handles on either the Derelict forums or the  
    16 D newsgroups. If I missed anyone, forgive me! 
     21D newsgroups (D NGs). If I missed anyone, forgive me! 
    1722</p><p> 
    1823<b>Maintainers</b> - the people who can commit to SVN and maintain the codebase</br> 
    1924<ul> 
    20 <li>Michael Parker (Aldacron) - founder and primary Windows maintainer</li> 
     25<li>Michael Parker (Aldacron) - project founder and primary Windows maintainer</li> 
    2126<li>John Reimer (JJR) - primary Linux maintainer</li> 
    2227</ul> 
    …… 
    5358</ul> 
    5459</p><p> 
    55 <b>Misc.</b> - people who have in some way, or another, influenced the development 
    56 of Derelict in a profound way.<br> 
     60<b>Misc.</b> - people who have influenced the development of Derelict in a  
     61profound way.<br> 
    5762<li>Walter Bright - the father of D and the DMD compiler. Without him, Derelict 
    5863has no reason to live!</li> 

  • trunk/docs/gl.html

    r109 r111  
    22<head><title>DerelictGL</title></head> 
    33<body> 
     4<hr> 
     5<hr> 
     6<h2 align="center">DerelictGL</h2> 
     7<hr> 
     8<hr> 
    49<h3>Introduction</h3> 
    510DerelictGL is a D binding to the <a href="http://www.opengl.org">OpenGL</a> 
    …… 
    6065<li> ensure that Derek Parnell's Build utility is on your path OR that the path 
    6166to it is configured in buildconfig.bat in your toplevel Derelict directory 
    62 (henceforth known as &lt derelict_dir &gt). See the documentation about  
     67(henceforth known as [derelict_dir]). See the documentation about  
    6368<a href="build.html">Derek Parnell's Build Utility</a> for more information on 
    6469setting up Build and configuring Derelict's Build scripts.</li> 
    65 <li>from a command prompt, cd to &lt derelict_dir &gt\DerelictGL</li> 
     70<li>from a command prompt, cd to [derelict_dir]\DerelictGL</li> 
    6671<li>type <tt>buildme.bat</tt></li> 
    67 <li>when the build completes, your command prompt will be back in &lt derelict_dir &gt, 
    68 and the file derelictGL.lib will be located in &lt derelict_dir &gt\lib.</li> 
     72<li>when the build completes, your command prompt will be back in [derelict_dir], 
     73and the file derelictGL.lib will be located in [derelict_dir]\lib.</li> 
    6974</ol> 
    7075<p> 
    …… 
    7378<p><ol> 
    7479<li>ensure that both dmd and gcc are on your path</li> 
    75 <li>from a command prompt, cd to &lt derelict_dir &gt/DerelictGL</li> 
     80<li>from a command prompt, cd to [derelict_dir]/DerelictGL</li> 
    7681<li>type 'make' or 'make all' to build derelictGL.a</li> 
    7782<li>optionally type 'make clean' to delete all object files OR 

  • trunk/docs/glfw.html

    r109 r111  
    22<head><title>DerelictGLFW</title></head> 
    33<body> 
     4<hr> 
     5<hr> 
     6<h2 align="center">DerelictGLFW</h2> 
     7<hr> 
     8<hr> 
    49<h3>Introduction</h3> 
    510DerelictGLFW is a D binding to the <a href="http://glfw.sourceforge.net">GLFW</a> 
    …… 
    6772<li> ensure that Derek Parnell's Build utility is on your path OR that the path 
    6873to it is configured in buildconfig.bat in your toplevel Derelict directory 
    69 (henceforth known as &lt derelict_dir &gt). See the documentation about  
     74(henceforth known as [derelict_dir]). See the documentation about  
    7075<a href="build.html">Derek Parnell's Build Utility</a> for more information on 
    7176setting up Build and configuring Derelict's Build scripts.</li> 
    72 <li>from a command prompt, cd to &lt derelict_dir &gt\DerelictGLFW</li> 
     77<li>from a command prompt, cd to [derelict_dir]\DerelictGLFW</li> 
    7378<li>type <tt>buildme.bat</tt></li> 
    74 <li>when the build completes, your command prompt will be back in &lt derelict_dir &gt, 
    75 and the file derelictGLFW.lib will be located in &lt derelict_dir &gt\lib.</li> 
     79<li>when the build completes, your command prompt will be back in [derelict_dir], 
     80and the file derelictGLFW.lib will be located in [derelict_dir]\lib.</li> 
    7681</ol> 
    7782<p> 
    …… 
    8085<p><ol> 
    8186<li>ensure that both dmd and gcc are on your path</li> 
    82 <li>from a command prompt, cd to &lt derelict_dir &gt/DerelictGLFW</li> 
     87<li>from a command prompt, cd to [derelict_dir]/DerelictGLFW</li> 
    8388<li>type 'make' or 'make all' to build derelictGLFW.a</li> 
    8489<li>optionally type 'make clean' to delete all object files OR 

  • trunk/docs/glu.html

    r109 r111  
    22<head><title>DerelictGLU</title></head> 
    33<body> 
     4<hr> 
     5<hr> 
     6<h2 align="center">DerelictGLU</h2> 
     7<hr> 
     8<hr> 
    49<h3>Introduction</h3> 
    510DerelictGLU is a D binding to the  
    …… 
    7984<li> ensure that Derek Parnell's Build utility is on your path OR that the path 
    8085to it is configured in buildconfig.bat in your toplevel Derelict directory 
    81 (henceforth known as &lt derelict_dir &gt). See the documentation about  
     86(henceforth known as [derelict_dir]). See the documentation about  
    8287<a href="build.html">Derek Parnell's Build Utility</a> for more information on 
    8388setting up Build and configuring Derelict's Build scripts.</li> 
    84 <li>from a command prompt, cd to &lt derelict_dir &gt\DerelictGLU</li> 
     89<li>from a command prompt, cd to [derelict_dir]\DerelictGLU</li> 
    8590<li>type <tt>buildme.bat</tt></li> 
    86 <li>when the build completes, your command prompt will be back in &lt derelict_dir &gt, 
    87 and the file derelictGLU.lib will be located in &lt derelict_dir &gt\lib.</li> 
     91<li>when the build completes, your command prompt will be back in [derelict_dir], 
     92and the file derelictGLU.lib will be located in [derelict_dir]\lib.</li> 
    8893</ol> 
    8994<p> 
    …… 
    9297<p><ol> 
    9398<li>ensure that both dmd and gcc are on your path</li> 
    94 <li>from a command prompt, cd to &lt derelict_dir &gt/DerelictGLU</li> 
     99<li>from a command prompt, cd to [derelict_dir]/DerelictGLU</li> 
    95100<li>type 'make' or 'make all' to build derelictGLU.a</li> 
    96101<li>optionally type 'make clean' to delete all object files OR 

  • trunk/docs/index_a.html

    r109 r111  
    11<html lang="en"> 
    22<head><title>Derelict Documentation</title></head> 
    3  
    43<body> 
     4<hr> 
     5<hr> 
     6<h2 align="center">Front Page</h2> 
     7<hr> 
     8<hr> 
    59<h3>Introduction</h3> 
    610Derelict is a collection of D bindings to C shared (dynamic) libraries which are 
    …… 
    2428bindings normally require the application to link with a static import library. 
    2529The import library makes the symbols exported from the shared library available 
    26 to the application and causes the shared library to be loaded automatically 
    27 by the operating system during application startup. This is a standard practice 
    28 in the C/C++ world, however there are a couple of drawbacks with doing so. 
    29 </p><p> 
     30to the application. It also causes the shared library to be loaded automatically 
     31by the operating system during application startup. It is common in the C++ world 
     32to statically link with import libraries during compilation, however there are  
     33some drawbacks to doing so. 
     34</p> 
     35<h4>Static Import Issues</h4> 
    3036One issue with static import libraries is that of the object format used. If the 
    3137D linker on your platform does not support a particular object format for a library 
    …… 
    4046startup. If the shared library is missing or corrupt, then the application will 
    4147fail to load and the operating system will display an error message to the user. 
    42 This could also occur if an version of the shared library which is older than 
    43 the version of the static import library is available on the user's system. The  
    44 error message displayed may not be very user friendly and can cause the developer 
    45 of the application to appear unprofessional. 
    46 </p><p> 
     48This could also occur if the only version of a shared library available on the 
     49user's system is older than the version of the static import library. The  
     50error message displayed may not be very user friendly. Some users who do not 
     51understand the concepts behind the error message could become frustrated with 
     52you, the developer, and may even view you as unprofessional. 
     53</p> 
     54<h4>Derelict's Solution</h4> 
    4755Derelict solves both potential problems by eliminating the requirement of a 
    4856static import library. Instead, Derelict handles the loading of shared libraries 
    …… 
    5765With Derelict, shared libraries can be loaded and unloaded at will. When you 
    5866consider that each shared library, when loaded, consumes system resources, then 
    59 it you might find it beneficial to only load the library when it is needed and 
     67you might find it beneficial to only load the library when it is needed and 
    6068not before. Some applications could also benefit from a hot-swap system. For 
    6169example, a game might have a generic rendering interface with implementations 
    62 for Opengl and Direct3D on Windows, and allow the user to switch between the 
    63 two at runtime. Derelict helps to simplify this process (DirectX bindings will 
     70for both Opengl and Direct3D on Windows, and allow the user to switch between the 
     71two at runtime. Derelict helps to simplify this process (DirectX bindings might 
    6472be included in a future Derelict release). 
    65 </p><p> 
     73</p> 
     74<h4>Special Features</h4> 
    6675Derelict goes one step further and allows selective loading of shared library 
    67 symbols. This allows you to, for example, allow older versions of a shared 
     76symbols. This allows you to do things like allowing older versions of a shared 
    6877library to be loaded. For example, if a particular Derelict package is setup to 
    6978load version 2 of a shared library, but your application does not use any exported 
    …… 
    7685selective symbol exceptions</a>) are provided through the DerelictUtil package. 
    7786As a side effect, all Derelict packages have an implicit dependency upon DerelictUtil.  
    78 This means that when compiling any individual packages, DerelictUtil must be 
    79 available on the import path, and when linking, DerelictUtil must be linked into 
    80 the application. See the DerelictUtil documentation for more details. 
    81 </p><p> 
     87This means that when compiling any individual packages, DerelictUtil <b>must</b> 
     88be available on the import path, and when linking, DerelictUtil <b>must be</b>  
     89linked into the application. See the DerelictUtil documentation for more details. 
     90<h4>The Docs</h4> 
    8291The documents linked in the first section below give a general overview of  
    8392Derelict, explaining functionality common to all Derelict packages. The 
    84 documents linked in the second secion give specific details on building and using 
     93documents linked in the second section give specific details on building and using 
    8594specific packages. 
    8695</p> 

  • trunk/docs/loading.html

    r108 r111  
    22<head><title>Loading/Unloading Shared Libraries</title></head> 
    33<body> 
     4<hr> 
     5<hr> 
     6<h2 align="center">Loading/Unloading Shared Libraries</h2> 
     7<hr> 
     8<hr> 
    49<h3>Introduction</h3> 
    510All Derelict packages interface to C shared libraries. No package in Derelict 
    …… 
    5459package which has a currently loaded shared library will unload that library. The 
    5560*_Unload functions are provided as a convenience so that you may swap out libraries 
    56 at runtime. For example, may you have a renderer that uses OpenGL, and you want 
    57 to switch to using a Direct3D implementation. In this case, it is beneficial to 
    58 unload the OpenGL shared library to free up resources. 
     61at runtime. For example, you might have a renderer that uses OpenGL and want 
     62to switch to using a Direct3D implementation at runtime. In this case, it is  
     63beneficial to unload the OpenGL shared library to free up resources. 
    5964 
    6065<p><hr></p><p> 

  • trunk/docs/sdl.html

    r109 r111  
    22<head><title>DerelictSDL</title></head> 
    33<body> 
     4<hr> 
     5<hr> 
     6<h2 align="center">DerelictSDL</h2> 
     7<hr> 
     8<hr> 
    49<h3>Introduction</h3> 
    510DerelictSDL is a D binding to Sam Lantinga's <a href="http://www.libsdl.org">Simple 
    …… 
    7075<li> ensure that Derek Parnell's Build utility is on your path OR that the path 
    7176to it is configured in buildconfig.bat in your toplevel Derelict directory 
    72 (henceforth known as &lt derelict_dir &gt). See the documentation about  
     77(henceforth known as [derelict_dir]). See the documentation about  
    7378<a href="build.html">Derek Parnell's Build Utility</a> for more information on 
    7479setting up Build and configuring Derelict's Build scripts.</li> 
    75 <li>from a command prompt, cd to &lt derelict_dir &gt\DerelictSDL</li> 
     80<li>from a command prompt, cd to [derelict_dir]\DerelictSDL</li> 
    7681<li>type <tt>buildme.bat</tt></li> 
    77 <li>when the build completes, your command prompt will be back in &lt derelict_dir &gt, 
    78 and the file derelictSDL.lib will be located in &lt derelict_dir &gt\lib.</li> 
     82<li>when the build completes, your command prompt will be back in [derelict_dir], 
     83and the file derelictSDL.lib will be located in [derelict_dir]\lib.</li> 
    7984</ol> 
    8085<p> 
    …… 
    8388<p><ol> 
    8489<li>ensure that both dmd and gcc are on your path</li> 
    85 <li>from a command prompt, cd to &lt derelict_dir &gt/DerelictSDL</li> 
     90<li>from a command prompt, cd to [derelict_dir]/DerelictSDL</li> 
    8691<li>type 'make' or 'make all' to build derelictSDL.a</li> 
    8792<li>optionally type 'make clean' to delete all object files OR 

  • trunk/docs/sdlimg.html

    r109 r111  
    22<head><title>DerelictSDLImage</title></head> 
    33<body> 
     4<hr> 
     5<hr> 
     6<h2 align="center">DerelictSDLImage</h2> 
     7<hr> 
     8<hr> 
    49<h3>Introduction</h3> 
    510DerelictSDLImage is a D binding to Sam Lantinga's 
    …… 
    5863<li> ensure that Derek Parnell's Build utility is on your path OR that the path 
    5964to it is configured in buildconfig.bat in your toplevel Derelict directory 
    60 (henceforth known as &lt derelict_dir &gt). See the documentation about  
     65(henceforth known as [derelict_dir]). See the documentation about  
    6166<a href="build.html">Derek Parnell's Build Utility</a> for more information on 
    6267setting up Build and configuring Derelict's Build scripts.</li> 
    63 <li>from a command prompt, cd to &lt derelict_dir &gt\DerelictSDLImage</li> 
     68<li>from a command prompt, cd to [derelict_dir]\DerelictSDLImage</li> 
    6469<li>type <tt>buildme.bat</tt></li> 
    65 <li>when the build completes, your command prompt will be back in &lt derelict_dir &gt, 
    66 and the file derelictSDLImage.lib will be located in &lt derelict_dir &gt\lib.</li> 
     70<li>when the build completes, your command prompt will be back in [derelict_dir], 
     71and the file derelictSDLImage.lib will be located in [derelict_dir]\lib.</li> 
    6772</ol> 
    6873<p> 
    …… 
    7176<p><ol> 
    7277<li>ensure that both dmd and gcc are on your path</li> 
    73 <li>from a command prompt, cd to &lt derelict_dir &gt/DerelictSDLImage</li> 
     78<li>from a command prompt, cd to [derelict_dir]/DerelictSDLImage</li> 
    7479<li>type 'make' or 'make all' to build derelictSDLImage.a</li> 
    7580<li>optionally type 'make clean' to delete all object files OR 

  • trunk/docs/sdlmix.html

    r109 r111  
    22<head><title>DerelictSDLImage</title></head> 
    33<body> 
     4<hr> 
     5<hr> 
     6<h2 align="center">DerelictSDLMixer</h2> 
     7<hr> 
     8<hr> 
    49<h3>Introduction</h3> 
    510DerelictSDLMixer is a D binding to Sam Lantinga's 
    …… 
    6267<li> ensure that Derek Parnell's Build utility is on your path OR that the path 
    6368to it is configured in buildconfig.bat in your toplevel Derelict directory 
    64 (henceforth known as &lt derelict_dir &gt). See the documentation about  
     69(henceforth known as [derelict_dir]). See the documentation about  
    6570<a href="build.html">Derek Parnell's Build Utility</a> for more information on 
    6671setting up Build and configuring Derelict's Build scripts.</li> 
    67 <li>from a command prompt, cd to &lt derelict_dir &gt\DerelictSDLMixer</li> 
     72<li>from a command prompt, cd to [derelict_dir]\DerelictSDLMixer</li> 
    6873<li>type <tt>buildme.bat</tt></li> 
    69 <li>when the build completes, your command prompt will be back in &lt derelict_dir &gt, 
    70 and the file derelictSDLMixer.lib will be located in &lt derelict_dir &gt\lib.</li> 
     74<li>when the build completes, your command prompt will be back in [derelict_dir], 
     75and the file derelictSDLMixer.lib will be located in [derelict_dir]\lib.</li> 
    7176</ol> 
    7277<p> 
    …… 
    7580<p><ol> 
    7681<li>ensure that both dmd and gcc are on your path</li> 
    77 <li>from a command prompt, cd to &lt derelict_dir &gt/DerelictSDLMixer</li> 
     82<li>from a command prompt, cd to [derelict_dir]/DerelictSDLMixer</li> 
    7883<li>type 'make' or 'make all' to build derelictSDLMixer.a</li> 
    7984<li>optionally type 'make clean' to delete all object files OR 

  • trunk/docs/sdlnet.html

    r109 r111  
    22<head><title>DerelictSDLImage</title></head> 
    33<body> 
     4<hr> 
     5<hr> 
     6<h2 align="center">DerelictSDLNet</h2> 
     7<hr> 
     8<hr> 
    49<h3>Introduction</h3> 
    510DerelictSDLNet is a D binding to Sam Lantinga's 
    …… 
    5863<li> ensure that Derek Parnell's Build utility is on your path OR that the path 
    5964to it is configured in buildconfig.bat in your toplevel Derelict directory 
    60 (henceforth known as &lt derelict_dir &gt). See the documentation about  
     65(henceforth known as [derelict_dir]). See the documentation about  
    6166<a href="build.html">Derek Parnell's Build Utility</a> for more information on 
    6267setting up Build and configuring Derelict's Build scripts.</li> 
    63 <li>from a command prompt, cd to &lt derelict_dir &gt\DerelictSDLNet</li> 
     68<li>from a command prompt, cd to [derelict_dir]\DerelictSDLNet</li> 
    6469<li>type <tt>buildme.bat</tt></li> 
    65 <li>when the build completes, your command prompt will be back in &lt derelict_dir &gt, 
    66 and the file derelictSDLNet.lib will be located in &lt derelict_dir &gt\lib.</li> 
     70<li>when the build completes, your command prompt will be back in [derelict_dir], 
     71and the file derelictSDLNet.lib will be located in [derelict_dir]\lib.</li> 
    6772</ol> 
    6873<p> 
    …… 
    7176<p><ol> 
    7277<li>ensure that both dmd and gcc are on your path</li> 
    73 <li>from a command prompt, cd to &lt derelict_dir &gt/DerelictSDLNet</li> 
     78<li>from a command prompt, cd to [derelict_dir]/DerelictSDLNet</li> 
    7479<li>type 'make' or 'make all' to build derelictSDLNet.a</li> 
    7580<li>optionally type 'make clean' to delete all object files OR 

  • trunk/docs/sdlttf.html

    r109 r111  
    22<head><title>DerelictSDLImage</title></head> 
    33<body> 
     4<hr> 
     5<hr> 
     6<h2 align="center">DerelictSDLttf</h2> 
     7<hr> 
     8<hr> 
    49<h3>Introduction</h3> 
    510DerelictSDLttf is a D binding to Sam Lantinga's 
    …… 
    6166<li> ensure that Derek Parnell's Build utility is on your path OR that the path 
    6267to it is configured in buildconfig.bat in your toplevel Derelict directory 
    63 (henceforth known as &lt derelict_dir &gt). See the documentation about  
     68(henceforth known as [derelict_dir]). See the documentation about  
    6469<a href="build.html">Derek Parnell's Build Utility</a> for more information on 
    6570setting up Build and configuring Derelict's Build scripts.</li> 
    66 <li>from a command prompt, cd to &lt derelict_dir &gt\DerelictSDLttf</li> 
     71<li>from a command prompt, cd to [derelict_dir]\DerelictSDLttf</li> 
    6772<li>type <tt>buildme.bat</tt></li> 
    68 <li>when the build completes, your command prompt will be back in &lt derelict_dir &gt, 
    69 and the file derelictSDLttf.lib will be located in &lt derelict_dir &gt\lib.</li> 
     73<li>when the build completes, your command prompt will be back in [derelict_dir], 
     74and the file derelictSDLttf.lib will be located in [derelict_dir]\lib.</li> 
    7075</ol> 
    7176<p> 
    …… 
    7479<p><ol> 
    7580<li>ensure that both dmd and gcc are on your path</li> 
    76 <li>from a command prompt, cd to &lt derelict_dir &gt/DerelictSDLttf</li> 
     81<li>from a command prompt, cd to [derelict_dir]/DerelictSDLttf</li> 
    7782<li>type 'make' or 'make all' to build derelictSDLttf.a</li> 
    7883<li>optionally type 'make clean' to delete all object files OR 

  • trunk/docs/selective.html

    r108 r111  
    22<head><title>Selective Symbol Exceptions</title></head> 
    33<body> 
     4<hr> 
     5<hr> 
     6<h2 align="center">Selective Symbol Exceptions</h2> 
     7<hr> 
     8<hr> 
    49<h3>Introduction</h3> 
    510There may be times when you wish to provide backwards compatibility with an 
    …… 
    2833complete example of using this feature to load a version of GLFW that does not 
    2934have the function <tt>glfwSetTime</tt> compiled in (a known issue with a precompiled 
    30 GLFW shared library from the GLFW homepage). 
     35GLFW 2.4.2 shared library that was available on the GLFW homepage). 
    3136</p> 
    3237 
    3338<p><hr><pre> 
    34 import derelict.util.exception;        // MissingProcCallback interface declared here 
     39import derelict.util.exception;             // MissingProcCallback interface declared here 
    3540import derelict.glfw.glfw; 
    3641 
    …… 
    3944void myMissingProcCallback(char[] libName, char[] procName) 
    4045{ 
    41  // some glfw shared libs are missing glfwSetTime 
    42    if(procName.cmp("glfwSetTime") == 0) 
    43       return true;   // continue loading 
     46    
     47   if(procName.cmp("glfwSetTime") == 0)     // some glfw shared libs are missing glfwSetTime 
     48      return true;                          // continue loading 
    4449 
    45    return false; // throw an exception for any other missing functions 
     50   return false;                            // throw an exception for any other missing functions 
    4651} 
    4752 

  • trunk/docs/util.html

    r108 r111  
    22<head><title>DerelictUtil</title></head> 
    33<body> 
    4  
     4<hr> 
     5<hr> 
     6<h2 align="center">DerelictUtil</h2> 
     7<hr> 
     8<hr> 
    59<h3>Introduction</h3> 
    610DerelictUtil currently provides two modules: <tt>derelict.util.exception</tt> and