Changes between Initial Version and Version 1 of Ticket #58574, comment 15


Ignore:
Timestamp:
Jun 29, 2019, 5:45:09 PM (5 years ago)
Author:
ryandesign (Ryan Carsten Schmidt)
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #58574, comment 15

    initial v1  
    1212If no version of the library has been installed yet, you would think that g-ir-scanner would error saying the library was not found, but that doesn't happen because it sets `DYLD_FALLBACK_LIBRARY_PATH` to the path to the just-built library.
    1313
    14 It seems to me that the fix would be for g-ir-scanner to set `DYLD_LIBRARY_PATH` instead of `DYLD_FALLBACK_LIBRARY_PATH`, since we do want it to use the just-built library in all cases, even if one is already installed, not just as a fallback. In fact that's what g-ir-scanner used to do. It was switched to `DYLD_FALLBACK_LIBRARY_PATH` on [https://gitlab.gnome.org/GNOME/gobject-introspection/issues/205 your suggestion] because of [ticket:56301 a different problem].
     14It seems to me that the fix would be for g-ir-scanner to set `DYLD_LIBRARY_PATH` instead of `DYLD_FALLBACK_LIBRARY_PATH`, since we do want it to use the just-built library in all cases, even if one is already installed, not just as a fallback. In fact that's what g-ir-scanner used to do. It was switched to `DYLD_FALLBACK_LIBRARY_PATH` on ~~your suggestion~~ [https://gitlab.gnome.org/GNOME/gobject-introspection/issues/205 Marcus's suggestion] because of [ticket:56301 a different problem].
    1515
    1616That different problem should only occur if /opt/local/lib were also in `DYLD_LIBRARY_PATH`. So maybe the bug is that g-ir-scanner adds all `-L` paths to `DYLD_LIBRARY_PATH`. It should only add those paths to `DYLD_LIBRARY_PATH` that contain the just-built library(ies).