hiltuniversity.blogg.se

Mapster32 duke3d sound reference
Mapster32 duke3d sound reference










mapster32 duke3d sound reference
  1. #Mapster32 duke3d sound reference how to
  2. #Mapster32 duke3d sound reference mac
mapster32 duke3d sound reference

X:~ user$ /Applications/eDuke32/eduke32 exit ĭyld: Library not loaded: from: /Applications/eDuke32/eduke32 Here is the error message from trying to run eduke:

mapster32 duke3d sound reference

Unfortunately, none of these attempts have succeeded, so I decided to post here.

#Mapster32 duke3d sound reference how to

That didn't work, and during my futile attempts to figure out how to make it work, I noticed the error mentioned so I made a Frameworks directory with both SDL_amework and SDL.framework in it, and put that in the directory above the eduke one due to the "./" I copied SDL_main.h to the root eduke32 directory, and just for good measure, also copied the entire SDL_amework and SDL.framework directories to the eduke32 directory. I did a search and was able to find SDL_main.h, but couldn't find any variation of that with the. It was mentioned earlier in this thread that Helix normally puts SDLMain.m and SDLMain.h in the root eduke32 directory. I have macports installed and do have both SDL.framework and SDL_amework in /Library/Frameworks. I am trying to get HelixHorned's latest build to work, but I keep receiving errors.

#Mapster32 duke3d sound reference mac

I'm really glad that there is finally a Mac client so that I can relive the glory days. When it finishes, copy (Command-C) and paste (Command-V) the output into either a 'spoiler' or 'code' tag here, or on some website made for that purpose like pastebin.Īnd please, be more verbose with your bug reporting.įirst, thanks for all the great work with eDuke.

  • Now, there should appear some output from the game on the console.
  • enter "cd ~/duke" and then "./eduke32" (without the quotes).
  • open a terminal program like 'Terminal' (on my Snow Leopard, it's under Applications->Utilities).
  • The directory ~/Library/Application Support/EDuke32 must contain DUKE3D.GRP.
  • extract the eduke32 binary to a directory of your choice, say, ~/duke ('~' denotes the home directory).
  • Here are step-by-step instructions to get my compilation running:

    mapster32 duke3d sound reference

    I know that my "raw binaries" are not the OSX way to do it, but for the sake of pinning down the problem, it might be worthwhile to start with a bare version: there's one less potential failing place. So, what executable are you using? I don't know what patches rhonie applied to the base code, so I can't give any support on his build. app versions and test those as at least one of them may work. app stuff you may also want to check out the builds there in general and get the. into your /Users/*User*/Library/Application Support/eDuke32/ folder.Īgain here's the link for rheonie's site who has the. But to just get eduke32 up and running it works fine.Īlso on the Mac it's best to put the grp files, the HRP files, etc. Rheonie just never made one that directly launches mapster rather than eduke32 and last time I checked mapster is looking for some Mac UI files that aren't available. app file and choose "show package contents* then navigate through /contents/MacOS/ and replace the executable files there with the new ones. In order to do this you right click on the. app file is just a folder with a special directory structure and some miscellaneous support files to launch that executable file as a proper mac app. app file from rheonie's web site and replace the executables inside with the latest ones from here to have an updated version though btw. Done the proper way you don't have to run it from the terminal or have the terminal launch whenever you double click on the executable file. To be perfectly honest with you just having the executable files loose like that is not the proper way to do it on OS X. It has nothing to do with built in startup windows. The only way to not have a terminal window pop up every time you launch an executable directly that way would be to turn it into a proper mac. so if they set it up wrong it'll just open show an error (pretty much flashing all the stuff that shows up in the eduke32 log file) and close. When you launch an executable directly like that it pops up the terminal and in there it shows the text that happens when it launches.












    Mapster32 duke3d sound reference