#6427: Runtime loader doesn't look for relative add ons in $(PROGDIR)/add-ons/ ------------------------------------+------------------------------ Reporter: pulkomandy | Owner: pulkomandy Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/runtime_loader | Version: R1/Development Resolution: | Keywords: Blocked By: | Has a Patch: 1 Platform: All | Blocking: ------------------------------------+------------------------------ Comment (by phoudoin): I've rebuild a whole r39660 image with just this patch applied to runtime_loader, and use this image since one day long without detecting any regression. Oh, and it does fix this issue too ;-) Considering that both BeBook and at least one application - which loads with any issue his add-ons under BeOS - makes me think that the semantic for relative add-on pathname is indeed broken currently under Haiku, I've commit that change in r39661. One thing to check is if BeOS try to open CWD's relative addon pathname too (as we do even without this patch) or does it only search in ADDON_PATH. Currently, if both %A/subdir/some-addon and %A/add-ons/subdir/some-addon exists, and the current working directory is %A, load_add_on("subdir/some- addon") will load from the first one. According to BeBook, it should not, but I suspect it does it anyway. If it does not, we need to fix that too. Could someone with BeOS could check, after moving (not copying) for instance APlayer/add-ons/Clients/MainWindowSystem in a (temporary) APlayer/Clients folder? -- Ticket URL: <http://dev.haiku-os.org/ticket/6427#comment:11> Haiku <http://dev.haiku-os.org> Haiku - the operating system.