Need help compiling my first MUI app

[Nightfox]

Hi all

Due to the wishes of the Amiga community, I have started the process of rewriting my AmigaGPT app from ReAction to MUI but I can't get it to successfully compile when adding some basic MUI code. It gives me a linker error saying the MUI library has an undefined reference to MUIMasterBase.

I define this in the file that I am using the MUI library in.

/opt/m68k-amigaos/lib/gcc/m68k-amigaos/6.5.0b/../../../../m68k-amigaos/bin/ld: /opt/m68k-amigaos/m68k-amigaos/lib//libmui.a(libmui.o): in function `MUI_NewObject':

libmui.c:60: undefined reference to `MUIMasterBase'

/opt/m68k-amigaos/lib/gcc/m68k-amigaos/6.5.0b/../../../../m68k-amigaos/bin/ld: /opt/m68k-amigaos/m68k-amigaos/lib//libmui.a(libmui.o): in function `MUI_MakeObject':

libmui.c:62: undefined reference to `MUIMasterBase'

/opt/m68k-amigaos/lib/gcc/m68k-amigaos/6.5.0b/../../../../m68k-amigaos/bin/ld: /opt/m68k-amigaos/m68k-amigaos/lib//libmui.a(libmui.o): in function `MUI_Request':

libmui.c:64: undefined reference to `MUIMasterBase'

/opt/m68k-amigaos/lib/gcc/m68k-amigaos/6.5.0b/../../../../m68k-amigaos/bin/ld: /opt/m68k-amigaos/m68k-amigaos/lib//libmui.a(libmui.o): in function `MUI_AllocAslRequestTags':

libmui.c:66: undefined reference to `MUIMasterBase'

/opt/m68k-amigaos/lib/gcc/m68k-amigaos/6.5.0b/../../../../m68k-amigaos/bin/ld: /opt/m68k-amigaos/m68k-amigaos/lib//libmui.a(libmui.o): in function `MUI_AslRequestTags':

libmui.c:68: undefined reference to `MUIMasterBase'

collect2: fatal error: ld returned 1 exit status

compilation terminated.

I am compiling this with my Dockerised Amiga dev environment based on Bebbo's amiga-gcc toolchain. So all I have to do to compile it is just run the "build_os3.sh" script.

All this work is living in a branch called ""mui" on my repo here https://github.com/sacredbanana/AmigaGPT/tree/mui

The relevant files with mui changes are Makefile and src/gui.c

If you want to build the project with my exact dev environment just install Docker and then run the "build_os3.sh" script

I've been trying all sorts of things to get that linking error fixed but after several hours I'm starting to get disheartened. I'm guessing there must be something wrong in the Makefile.

Thank you so much <3

[a/b]

Declare a global variable MUIMasterBase (of type Library*)? And eventually initialize it via OpenLibrary()...

[Nightfox]

I already do that in gui.c

https://github.com/sacredbanana/Amig.../mui/src/gui.c

[a/b]

Hmmm, ok. Thinking...
1. Did you dump the symbols in libmui.a (on UX I use nm, ar might be helpful too but less user friendly output iirc, not sure what you have available on amiga) and mui.o and check that they match (this is pure c, no c++ obfuscation, but maybe naming/calling convention or something. no underscores but, just in case...).
2. Once upon a time, back in the '90, I was working on a project that was ported to 30+ platforms, and some of the c compilers were stupid, very sensitive to lib/obj order. Maybe have that declaration in a separate .c/.o file and when linking put it before all the libs (-l's).

[phx]

Where did you get that libmui.a from? Was it part of the gcc installation or is it from a different source (Aminet)?

MUIMasterBase

without leading underscore seems strange. Looks like ELF-ABI, but last time I checked Bebbo's linker libraries used hunk-format objects, although confusingly they have an .a suffix (for ar) instead of .lib. So I'm not sure if ar or nm would help.

You can also check if you can get rid of libmui completely and use inlines to call the library functions (including

<proto/muimaster.h>

might already do that).

[Nightfox]

I got the latest from 2021 here https://github.com/amiga-mui/muidev/...I-5.0-20210831

[Nightfox]

Originally Posted by a/b

Hmmm, ok. Thinking...
1. Did you dump the symbols in libmui.a (on UX I use nm, ar might be helpful too but less user friendly output iirc, not sure what you have available on amiga) and mui.o and check that they match (this is pure c, no c++ obfuscation, but maybe naming/calling convention or something. no underscores but, just in case...).
2. Once upon a time, back in the '90, I was working on a project that was ported to 30+ platforms, and some of the c compilers were stupid, very sensitive to lib/obj order. Maybe have that declaration in a separate .c/.o file and when linking put it before all the libs (-l's).

Ill try dumping the symbols and report back

[phx]

Originally Posted by Nightfox

I got the latest from 2021 here https://github.com/amiga-mui/muidev/...I-5.0-20210831

The SDK contains a libmui.a in a.out format (with a single object file!). And MUIMasterBase has a leading underscore. So now you have to check and compare what your compiler generates, when you define

MUIMasterBase

.

[Minuous]

I don't understand why you don't just use the official Amiga GUI and avoid all this?

[jPV]

Originally Posted by Minuous

I don't understand why you don't just use the official Amiga GUI and avoid all this?

Maybe because ReAction hasn't been the official GUI toolkit that long and feels quite alien for many, and MUI has been the de facto toolkit for ages. And older solutions are more limited...

[Minuous]

A quarter of a century is not long enough!?

[jPV]

Well, maybe I put it in a bit wrong way, but if we look at versions and amount of use instead of time. It was introduced in H&P's OS 3.5/9, which were released at the very late days when Amiga was still somehow popular, and they were a bit controversial updates and weren't adapted by all users, because they felt more like 3rd party collections than real official OS updates. In practise most programs were still made to run on OS 3.1 with other toolkits, and actual use of ReAction has been very minimal, not even all programs in 3.5/9 were converted to use it. So it's been difficult to take it seriously as the official path until very recently. Hyperion's recent OS releases make it feel more like an official solution, and might make it somehow more popular, but still many programmers want to use toolkits that have been more widely used for longer time and don't require these exact OS versions (or ripping components of them).