search

waynedog74 / mupen64plus

Automatically exported from code.google.com/p/mupen64plus
0 stars 0 forks source link

mupen64plus-video-glide64 build error - SetRenderingCallback #483

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Describe your system:
 - Operating System (be specific): Gentoo Linux
 - Machine type (32-bit or 64-bit): amd64
 - Mupen64Plus version: HG
 - Plugins used: all(?)

Describe the problem:

The glide64 plugin no longer compiles.  Here is the relevant error message:

# make -C mupen64plus-video-glide64/projects/unix all PREFIX=/usr/games 
LIBDIR=/usr/games/lib64/mupen64plus SHAREDIR=/usr/share/games/mupen64plus 
DESTDIR=/tmp/portage/games-emulation/mupen64plus-9999/image/ 
COREDIR=/usr/games/lib64/mupen64plus/ 
PLUGINDIR=/usr/games/lib64/mupen64plus/plugins MANDIR=/usr/share/man            

make: Entering directory 
`/tmp/portage/games-emulation/mupen64plus-9999/work/mupen64plus-video-glide64/pr
ojects/unix'                                           
    CXX _obj/Main.o                                                             
../../src/Main.cpp: In function ‘void SetRenderingCallback(void (*)())’:    

../../src/Main.cpp:1475:57: error: declaration of C function ‘void 
SetRenderingCallback(void (*)())’ conflicts with                              

../../../mupen64plus-core/src/api/m64p_plugin.h:198:18: error: previous 
declaration ‘void SetRenderingCallback(void (*)(int))’ here                 

make: *** [_obj/Main.o] Error 1                                                 
make: Leaving directory 
`/tmp/portage/games-emulation/mupen64plus-9999/work/mupen64plus-video-glide64/pr
ojects/unix'

Please provide any additional information below.

This is using a fresh clone of both mupen64plus itself as well as wahrhaft's 
glide64 plugin, and using the same build options as shown above for all 
mupen64plus modules as well as each plugin.  The last time I built this was in 
October 2011, and it worked fine then.  mupen64plus-video-arachnoid, for 
comparison, still compiles fine.

I'm not exactly sure how development of plugins is handled vs. mupen64plus, but 
I figured I'd start here.  If this needs to be reported elsewhere, I'll be 
happy to do so.

Original issue reported on code.google.com by nitro322@gmail.com on 6 Mar 2012 at 6:03

GoogleCodeExporter commented 9 years ago 
Thanks for the report, you just happened to pick a bad day to update.  There 
was recently a change in the core of Mupen64Plus that requires the video 
plugins' source to be updated.  I just updated Arachnoid yesterday, and the fix 
for Glide64 and Z64 are in the works.

Original comment by wahrh...@gmail.com on 6 Mar 2012 at 11:20

GoogleCodeExporter commented 9 years ago 
Indeed.  I just tried building again and it works fine.  Oh well - not like 
this is the first time I've ever had a case of bad timing.  :-)

Thanks for the quick response.  I'd say you can close this.  If you don't mind 
me asking an unrelated question, though...

When I ran mupen64plus to test just now, I noticed it used the Rice video 
plugin, whereas I had previously configured it to use glide64.  After looking 
at the config file, I noticed that it completely blew away my all of lovingly 
hand-crafted settings.  With no warning.  That's not really good.

Fortunately I have a backup, but is there any way I can make it *not* destroy 
my settings the next time I run it?  or do I just have to take the new file 
that it auto-gens and then manually configure it all over again?

Original comment by nitro322@gmail.com on 7 Mar 2012 at 7:39

GoogleCodeExporter commented 9 years ago 
I'm not sure about that one, but if it's something you can reproduce you can 
create a new issue for it.  Or, just stop by the IRC channel, #mupen64plus on 
Freenode, and ask there (can be slow at times, stick around and someone will 
respond).

Original comment by wahrh...@gmail.com on 7 Mar 2012 at 2:08