Re: [Plib-users] bug in PLIB/SSG
Brought to you by:
sjbaker
From: <Va...@t-...> - 2000-06-06 10:29:56
|
dongoodman wrote: > > I have downloaded PLIB 1.1.11; i do not know if this bug has been > addressed, so I will mention it anyway. > > with VC++ 6.0, when I attempt to compile SSG, VC++ returns four > errors in ssg.SimpleState.cxx: > C:\My Code\Plib\plib-1.1.11\src\ssg\ssgSimpleState.cxx(18) : error C2106: '=' : left operand must be l-value > C:\My Code\Plib\plib-1.1.11\src\ssg\ssgSimpleState.cxx(19) : error C2106: '=' : left operand must be l-value > C:\My Code\Plib\plib-1.1.11\src\ssg\ssgSimpleState.cxx(20) : error C2106: '=' : left operand must be l-value > C:\My Code\Plib\plib-1.1.11\src\ssg\ssgSimpleState.cxx(21) : error C2106: '=' : left operand must be l-value > > I have fixed these errors by commenting out lines 18,19,20,21 and > adding: > sgCopyVec4(specular_colour, src -> specular_colour); > sgCopyVec4(emission_colour, src -> emission_colour); > sgCopyVec4( ambient_colour, src -> ambient_colour); > sgCopyVec4( diffuse_colour, src -> diffuse_colour); > > in thier stead. I can generate a diff file if that would be preferred. This is a known bug and is already fixed in the newest versions in the CVS. > On that note: whenever I try to link against any PLIB static library (again, > in windows), I get a whole lot of undefined symbol linker errors: is there > something with the project files that prevents the libraries from compiling > properly, or is it more likely that I'm just not linking them in to my > project properly? The MSVC workspaces are quite old. So they miss out a few files. As these files aren't compiled their functions aren't availbe at linking. So you'd just need to add the missing files to the correct projects (IIRC only SSG is affected). CU, Christian |