Kolby Kunz04/24/2023, 6:49 PM
From what I understand the linker cannot find the definitions for the package for the target platform and is most likely looking in the standard include folders throughout the system but because it is a custom package they are not located there. Any advice on how to fix this would be greatly appreciated or if this is even something supported by cinterop.
Undefined symbols for architecture x86_64 '_askar_version', referenced from _askar_askar_version_wrapper76 in result.o ld symbol(s) not found for archutecture x86_64
vbsteven04/24/2023, 7:10 PM
in your .def file?
Kolby Kunz04/24/2023, 7:11 PM
vbsteven04/24/2023, 7:11 PM
linkerOpts.linux = \ -L/usr/local/lib \ -lgobject-2.0 \ -lglib-2.0
adds it to the search path (not 100% sure on the terminology),
tells the linker to link against the library with the given name
and link against
Kolby Kunz04/24/2023, 7:13 PM
vbsteven04/24/2023, 7:13 PM
Kolby Kunz04/24/2023, 7:14 PM
the .so is spelled incorrectly so it made sure to match the file name exactly. Not sure what to test next.
library not found for -llibaries_askar
vbsteven04/24/2023, 8:16 PM
Kolby Kunz04/24/2023, 8:17 PM
package = askar headers = ariesAskar.h headerFilter = ariesAskar.h staticLibraries = libaries_askar.so linkerOpts.macos_x64 = -Laskar/x86_64/ -llibaries_askar libraryPaths = askar/x86_64
vbsteven04/24/2023, 8:25 PM
file which is a shared library
Kolby Kunz04/24/2023, 8:28 PM
flag looks fora file with lib appended to the front of it. Knowing that the linking option should now be
causes the compilation to succed