Changes between Version 3 and Version 4 of GraphicsApiOld

Timestamp:

Apr 24, 2007, 10:31:01 AM (17 years ago)

Author:

KSMarksPsych

Comment:

Updated links to point to wiki pages. UpdateVersions and ExampleApps need to be created.

GraphicsApiOld

@@ -24 +24 @@
 On Unix, your graphics code must be put in a separate shared library (.so) file. This is because Unix hosts may not have the needed libraries (OpenGL, GLUT, X11). If an application is linked dynamically to these libraries, it will fail on startup if the libraries are not present. On the other hand, if an application is linked statically to these libraries, graphics will be done very inefficiently on most hosts.
 
-The shared library must have the same name as the executable followed by '.so'. It must be linked with `libboinc_graphics_impl.a`, with your rendering and input-handling functions, and (dynamically) with glut and opengl. You must bundle the main program and the shared library together as a [http://boinc.berkeley.edu/tool_update_versions.php multi-file application version]. Unix/Linux applications that use graphics should compile all files with `-D_REENTRANT`, since graphics uses multiple threads.
+The shared library must have the same name as the executable followed by '.so'. It must be linked with `libboinc_graphics_impl.a`, with your rendering and input-handling functions, and (dynamically) with glut and opengl. You must bundle the main program and the shared library together as a [UpdateVersions multi-file application version]. Unix/Linux applications that use graphics should compile all files with `-D_REENTRANT`, since graphics uses multiple threads.
 
-The [http://boinc.berkeley.edu/example.php BOINC example application] uses this technique, and shows the Makefile command that are needed to produce the shared library on Unix.
+The [ExampleApps BOINC example application] uses this technique, and shows the Makefile command that are needed to produce the shared library on Unix.
 
 == Rendering and input-handling functions ==