[Scummvm-devel] Problems building Plugins.cpp using GCC 2.95.3

Max Horn max at quendi.de
Sun Feb 18 15:35:33 CET 2007


Am 18.02.2007 um 15:21 schrieb Lars Persson:

> Hi!
>
> I  have problems building Plugins.cpp using GCC 2.95.3 in later  
> revisions.
Note that we are not really supporting GCC pre-3.x anymore. If  
possible w/o too much hassle, we try to fix issues with it, but other  
than that, it is *strongly* recommend to use 3.x or 4.x.

> I'm getting
>
> ..\..\..\..\BASE\Plugins.cpp: In method `class PluginList  
> StaticPluginProvider::getPlugins()':
> ..\..\..\..\BASE\Plugins.cpp:75: unknown escape sequence `\.'
> ..\..\..\..\BASE\Plugins.cpp:75: unknown escape sequence `\.'
> ..\..\..\..\BASE\Plugins.cpp:75: unknown escape sequence `\B'
> ..\..\..\..\BASE\Plugins.cpp:75: unknown escape sequence `\P'

Odd. There is no "\." and no "\B" nor "\P" in the source. Maybe the  
"." is substituted for something else... Could it be a line ending  
problem? Seems unlikely, though.

Have you tried to just run the preprocessor on the file, then review  
its output? That provide some more insight on the issue.

> .
>
> .
>
> ........BASEPlugins.cpp:86: unknown escape sequence `\.'
> ........BASEPlugins.cpp:86: unknown escape sequence `\.'
> ........BASEPlugins.cpp:86: unknown escape sequence `\.'
>
> and I have compared the new plugins.cpp with the older one, and it  
> seems to be pretty similar, but I think its the order of defines  
> etc, which is causing this old compiler to misbehave.
It's very unlikely that the order of the #defines has any effect on  
this.

Maybe the indention of the #define / #ifndef is causing problems,  
although that would surprise me, too.



Bye,
Max






More information about the Scummvm-devel mailing list