Skip to content
  • Gerhard Sittig's avatar
    650f1946
    irmp: hook up IRMP to the build, create a separate shared object · 650f1946
    Gerhard Sittig authored
    Add the irmp/ subdirectory to the automake build instructions. Make the
    feature optional, provide an enable/disable switch (on by default).
    
    It's an essential implementation detail that the irmp.c file is required
    to build, but is not a compile unit of its own. It's yet to be seen how
    to most appropriately declare the dependencies of libirmp_la (can get
    refined in future commits).
    
    Create a separate shared object from the IRMP source, which shall result
    in a stable filename for the DLL/.so lookup. Decoder library code would
    not know the application's executable name, neither is anonymous symbol
    lookup "in the current process" portable across supported platforms.
    
    The configure.ac macros were modelled after the autobook DLL section.
    https://www.sourceware.org/autobook/autobook/autobook_137.html
    Symbol export is simple because the library gets implemented and built
    here, but is not used from C language code in this project. That's why
    we don't do the full dance of symbol import which would be needed on
    Windows.
    650f1946
    irmp: hook up IRMP to the build, create a separate shared object
    Gerhard Sittig authored
    Add the irmp/ subdirectory to the automake build instructions. Make the
    feature optional, provide an enable/disable switch (on by default).
    
    It's an essential implementation detail that the irmp.c file is required
    to build, but is not a compile unit of its own. It's yet to be seen how
    to most appropriately declare the dependencies of libirmp_la (can get
    refined in future commits).
    
    Create a separate shared object from the IRMP source, which shall result
    in a stable filename for the DLL/.so lookup. Decoder library code would
    not know the application's executable name, neither is anonymous symbol
    lookup "in the current process" portable across supported platforms.
    
    The configure.ac macros were modelled after the autobook DLL section.
    https://www.sourceware.org/autobook/autobook/autobook_137.html
    Symbol export is simple because the library gets implemented and built
    here, but is not used from C language code in this project. That's why
    we don't do the full dance of symbol import which would be needed on
    Windows.
Loading