[CHG] Deleted the Temporary fix (-DNOGUFIX)

This commit is contained in:
Crayon2000 2009-10-16 20:59:08 +00:00
parent 8c05d9ac06
commit fff851b34b
3 changed files with 2 additions and 56 deletions

View file

@ -34,34 +34,7 @@ THE SOFTWARE.
// Includes // Includes
//============================================================================== //==============================================================================
#include <gccore.h> #include <gccore.h>
//============================================================================== //==============================================================================
/*
*** Temporary fix ***
After the release of libogc v1.7.1a, Vector was renamed to guVector
"to avoid collisions" [svn 3650]
...also Quaternion was renamed to guQuaternion - but GRRLIB does not use these!
The main codebase of GRRLIB has been updated to reflect this change.
But until the new libogc is officially released,
if you are using a version of libogc later than v1.7.1a/svn3649,
you will need to add:
-DNOGUFIX
to the compiler flags in your makefile
When the libogc changes are officially released,
this *temporary fix* should be removed
The requirement for -DNOGUFIX will be deprecated,
but its lingering presence will not be a hinderance
Thanks to Nicksasa for reporting this problem :)
*/
//==============================================================================
#ifndef NOGUFIX
// If you are getting a compile error here, read the above comment!
typedef Vector guVector ;
typedef Quaternion guQuaternion ;
#endif
//============================================================================== //==============================================================================
// C++ header // C++ header

View file

@ -1,4 +1,4 @@
<html><body bgcolor="#FFFFFF" text="#000000"><center><table><tr><td> <html><head><title>GRRLIB</title></head><body bgcolor="#FFFFFF" text="#000000"><center><table><tr><td>
<!-- --------------------- This file is this wide -------------------------- --> <!-- --------------------- This file is this wide -------------------------- -->
<center><img src="grrlib_logo.png" /></center> <center><img src="grrlib_logo.png" /></center>
<pre><b> <pre><b>
@ -24,9 +24,6 @@ Using GRRLIB
Upgrading to v4.1.0 From Previous Versions of GRRLIB Upgrading to v4.1.0 From Previous Versions of GRRLIB
...I upgraded and now my programs won't compile properly!? ...I upgraded and now my programs won't compile properly!?
Error: guVector redefined
...How do I get rid of this error?
Using SVN Using SVN
...What is this SVN thing that the L337 devs keep talking about? ...What is this SVN thing that the L337 devs keep talking about?
@ -197,30 +194,6 @@ Because GRRLIB now does this for you automatically, these lines must be removed
from your code. from your code.
Error: guVector redefined
-------------------------
If you get this error, you are probably using a version of libogc more recent
than the released v1.7.1a.
In the libogc SVN revision 3650 Vector was renamed to guVector "to avoid
collisions" ...also Quaternion was renamed to guQuaternion - but GRRLIB does
not use these!
The main codebase of GRRLIB has been updated to reflect this change.
But until the new libogc is officially released, if you are using a version of
libogc later than v1.7.1a/svn3649, you will need to add:
-DNOGUFIX
to the compiler flags (CFLAGS) in your makefile
When the libogc changes are officially released, this *temporary fix* should be
removed [see grrlib.h, line 50ish]
The requirement for -DNOGUFIX will be deprecated, but its lingering presence
will not be a hinderance
Thanks to Nicksasa for reporting this problem
Using SVN Using SVN
--------- ---------

View file

@ -31,7 +31,7 @@ PROJECT_NAME = GRRLIB
# This could be handy for archiving the generated documentation or # This could be handy for archiving the generated documentation or
# if some version control system is used. # if some version control system is used.
PROJECT_NUMBER = 4.1.0 PROJECT_NUMBER = 4.1.1
# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute)
# base path where the generated documentation will be put. # base path where the generated documentation will be put.