FS-UAE (OSX-PPC) - No OSD menu?
 

Hello again,
this time I wish to point a difference between intel and PPC builds: on my G4 (OSX 10.5.8) there is no OSD menu when pressing CMD + F12.
The main screen tilt to left as it should but the area on the right remain empty (see attached image) I am missing something in compiling process?
Attachment 33099

Most likely the problem is just that the images are not found. Please attach FS-UAE.log to a new post, it contains relevant information (Documents/Logs/FS-UAE.log).

After some investigations I have managed to add the missing menus to the PPC build simply doing a bit of cut'n'paste :)
Here is in short the way I have followed:

- On the PPC G4 build the executable from inside the /macosx directory of FS-UAE source: the process will stop because of lacking of the libfs part but goes far enough to have the FS-UAE.app almost ready with the fs-uae CLI executable inside
- Put the OSX intel version somewhere on the PPC desktop, you will see its icon with the slashed circle on it meaning its build will not run on PPCs
- With CTRL-click on this icon choose from the pop-up menu to show the package contents and copy the directories Contents/Frameworks and Contents/Resources from the FS-UAE.app (intel) to the very same locations FS-UAE.app (ppc)
- Voilà, icons and menus are there on PPC too! :)

Ok, I know this is a very dirty job but in the meantime it works without too much headaches ;)

I really would like that someone expert in PPC developing will write a step-by-step guide for the newbies (as it has been done for the SDL Mame on Bannister's forum) so everyone still in G4/G5 business can safely build its executable on its own.

I assume it stops at this line in the Makefile:
You don't need this, so you can simply write # in front of it to skip it.

But the libcapsimage library is needed for IPF file support. Here's how to make a full bunde including libcapsimage:

The libcapsimage source code is downloadable from the FS-UAE download page. You can compile this simply by running make, and the you manually copy the created libfs-capsimage.dylib into the "out" directory in the fs-uae source dir.

And to compile FS-UAe, instead of cd-ing into macosx, you stay in the root source directory and run:
If you get stuck, I can probably help, but you need to provide any error messages, log files, terminal output or whatever information is relevant.

Btw, you don't need to create a bundle to run FS-UAE, you can run it directly from the source dir like this:
(it should find the image resources then too).

Hi All,

I followed the instructions from snakecoils but it still failed copying the libs-capsimage.dylib file during the recompile. I checked the Makefile under macosx folder and I noticed that the cp line had some extra ../
the at the top level of the folder didn't work either. I had to cd into the macosx sub folder and just run

with the following changes in the Makefile from the same directory.

so the cp for libfs-capsimage.dylib should start as:

Ahhhh I spoke too soon. The compilation completes with no error but the application crashes when I launch it :-(. It does work if I skip the libfs-capsimage.dylib hack.

OK I got a working FS-UAE.APP on my Powerbook G4. I didn't copy the Contents/Frameworks and Contents/Resources from the intel version. I just copied the libfs-capsimage.dylib in the out folder and modified the Makefile by removing the extra ../ in the cp ../../out/libfs-capsimage.dylib etc. etc. line and voila'

Now I need to figure out a way to create an executable for the launcher.

Hi, and welcome here :) I'll try to help you (and snakecoils) as best as I can.

The extra ../ is not an error, but rather a consequence of how my automated build system works (which executes make -f macosx.mk).

When you run "make -f macosx.mk", a new clean copy of the source dir is created in a subdir, and the compilation process occur in this subdir, so the extra ../ is to account for this. Alternatively, if "make -f macosx.mk" fails, you could post the error here, and we could fix that problem instead.

If you compile from the source tarballs, there's nothing wrong with modifying that line and running make from within the macosx dir (If you compile from the git repository, make -f macosx should be used instead, because this updates the version number thoughout the source code).

Copying resources from another FS-UAE.app is generally a bad idea, and copying files from Contents/Frameworks for another CPU architecture is an especially bad idea ;)

An app bundle for the launcher will be created when you run "make -f macosx.mk", or if you CD into macos and run "make launcher" there. For this to work, you need to have Python 2.7 installed along with the following Python extensions (for 2.7): setuptools, wxPython, pygame, and py2app.

Hope this helps :)

If you get stuck, just ask for help, but please post any error messages / relevant console output!

The real problem is that libfs-capsimage.dylib is not in the source files archive. I tried to look for it but it is not included. I just compiled 2.2.0 and it could not complete without that file. Once I copied it from the Intel archive, I was able to complete the compilation. This is on a PPC MAC

Hi, See my post further up (http://eab.abime.net/showpost.php?p=849308&postcount=4).

Hello,
just a thing remain to understand for me for a complete self-made build: is possible to make a PPC compile of libfs-capsimage library? Every tries result in the following message:

And here is the config.log output:

Any suggestions? Thanks in advance