-
-
Cocoon
Posts: 45 from 2018/6/9
Not surprisingly, I think this is operator error. On multiple counts! The Flow UI is kind of confusing though in my defence.
1: There are multiple places, seemingly to enter the same information. You have Project Settings, Compiler and Linker tabs. These appear to me to be completely ignored in favour of the same tabs under the specific target when you edit the target. I'm thinking maybe they specify some defaults though because the targets do seem to come pre-populated if I've already populated though tabs, apart from "Linker Libraries" that I don't think it understands (see point 3).
2: I had specified gcc11 for the compiler and simply gcc (well, ppc-morphs-gcc) for the linker. That definitely caused at least one error / failure.
3: Final and probably bigger one is the way that you enter the libraries in the linker tab. When I go to enter a library I have a little folder widget which brings up an ambient file browser and seems to expect me to pick an actual static library file such as `libSDL3.a`. Then it populates the full paths. That's fine but for a novice like me, I don't know which path to pick (libnix? libb32? etc.) and it all fails horribly. BUT, I just realised that instead of clicking the widget I can just enter the name as I would in a Makefile - '-lSDL3', '-lGL' and so on for each entry. Add -L/gg/etc as a linker flag and indeed it does then all seem to work just fine. But it feels like I'm not doing what the application is expecting there.
I haven't got the hang of posting from MorphOS yet or I would include some screen shots to explain it better! I hope that makes some sense.
-
»18.05.25 - 17:51