This is new for me since changing Linux distros from Debian Lenny to OpenSUSE 10.3.
On Debian I could just do the make and copy the glide64.so from the Glide64-wonder++ v.12 pack to the Mupen64 plugin folder and copy the Windows version glide64.ini from the Glide64-wonder++ Windows pack over there too, and it would initiate and run fine.
Got a dual-boot Vista/Linux now. I'm using the included older Glide64 in OpenSUSE just to have it available, but since glN64 works without the problems that older Glide64 had I just normally use that there.
It would be nice to figure out why the compiled version doesn't initialize the plugins when trying to start a game, and the panel for it doesn't open either. The included Mupen64-0.5 version runs as well as it has run, but the version 12 one is much better. Can't use it.
Actually, I've got a lot more available using these things on Vista. Project64 1.7 (I'm a subscriber), adding Glide64-Wonder++ (doesn't have the problems the same original version has on Linux so that Linux version 12 of it isn't needed), and then also installing the Windows Mupen64 0.5.1 and replacing its Glide64 with the Windows wonder++ gives me all sorts of options there. I run the emu's in administrator mode so they all can do what they're supposed to without permission and access problems.
Glide64-wonder++ doesn't end emulation on Mupen64 gracefully because of frame buffer being activated (or so I've read that's the reason), but at least the frame buffer thing works on Windows. On Linux it never activated that screen in MarioKart64, but on Vista it's there. And with Project64 1.7, it DOES end emulation fine, so it seems to be a Mupen64 thing. On Mupen64 I have to end the process in Task Manager.
Anyway, the central question is regarding using version 12 of Glide64-wonder++ on OpenSUSE. Does anyone know why Mupen64 can't initialize it? Is it not being built correctly and fully with the version of the build tools on OpenSUSE 10.3? I get various warnings while make is running but got some of that on Debian while building the thing and it worked fine regardless.
I saw that there were problems getting Glide64 running with the new ricevideolinux64 version of Mupen64 now in subversion, or so I've read in the forum here. Is this related to my problem? Possibly newer build tools playing havoc with building the plugin the way the make stuff is currently setup?
Heh, I haven't learned how to patch make files yet. Hopefully the coming this spring version of Glide64-Napalm will have something released for Linux as well that will compile using today's distro build tools. Or if someone has figured out the problem and solved it, they can show me how to patch the version 12 so it'll build in a way that'll initialize again. Or release something we could just replace in the build folder? I'm just guessing that it isn't building correctly, but I know it doesn't run anymore. The file is built. It just doesn't work.
On Debian I could just do the make and copy the glide64.so from the Glide64-wonder++ v.12 pack to the Mupen64 plugin folder and copy the Windows version glide64.ini from the Glide64-wonder++ Windows pack over there too, and it would initiate and run fine.
Got a dual-boot Vista/Linux now. I'm using the included older Glide64 in OpenSUSE just to have it available, but since glN64 works without the problems that older Glide64 had I just normally use that there.
It would be nice to figure out why the compiled version doesn't initialize the plugins when trying to start a game, and the panel for it doesn't open either. The included Mupen64-0.5 version runs as well as it has run, but the version 12 one is much better. Can't use it.
Actually, I've got a lot more available using these things on Vista. Project64 1.7 (I'm a subscriber), adding Glide64-Wonder++ (doesn't have the problems the same original version has on Linux so that Linux version 12 of it isn't needed), and then also installing the Windows Mupen64 0.5.1 and replacing its Glide64 with the Windows wonder++ gives me all sorts of options there. I run the emu's in administrator mode so they all can do what they're supposed to without permission and access problems.
Glide64-wonder++ doesn't end emulation on Mupen64 gracefully because of frame buffer being activated (or so I've read that's the reason), but at least the frame buffer thing works on Windows. On Linux it never activated that screen in MarioKart64, but on Vista it's there. And with Project64 1.7, it DOES end emulation fine, so it seems to be a Mupen64 thing. On Mupen64 I have to end the process in Task Manager.
Anyway, the central question is regarding using version 12 of Glide64-wonder++ on OpenSUSE. Does anyone know why Mupen64 can't initialize it? Is it not being built correctly and fully with the version of the build tools on OpenSUSE 10.3? I get various warnings while make is running but got some of that on Debian while building the thing and it worked fine regardless.
I saw that there were problems getting Glide64 running with the new ricevideolinux64 version of Mupen64 now in subversion, or so I've read in the forum here. Is this related to my problem? Possibly newer build tools playing havoc with building the plugin the way the make stuff is currently setup?
Heh, I haven't learned how to patch make files yet. Hopefully the coming this spring version of Glide64-Napalm will have something released for Linux as well that will compile using today's distro build tools. Or if someone has figured out the problem and solved it, they can show me how to patch the version 12 so it'll build in a way that'll initialize again. Or release something we could just replace in the build folder? I'm just guessing that it isn't building correctly, but I know it doesn't run anymore. The file is built. It just doesn't work.