I'm in a situation where I'm building a binary that links against libfoo.so. That library does not exist on my build machine but it will exist at /some/dir/libfoo.so on the machine where the binary will be run.
Is there a way to tell clang, "Trust me, it'll be there"?
You can create a stub library that contains a dummy implementation of all the functions from libfoo.so that you want to use. E.g.,
int bar(void) {
return -1;
}
void *baz(int num) {
(void)num;
return NULL;
}
It doesn't matter what the implementation does since it will never be called. It's just there to satisfy the linker.
After compiling the stub implementation into libfoo.so, you'd compile with -Lpath/to/stub/lib -lfoo. The linker will be happy since it sees what it think is libfoo.so and that that library exports all the necessary symbols. However, when your binary is run, the real libfoo.so (assuming it's in an appropriate directory) will be picked up by the dynamic linker.