Usage on OSX 10.9?

[GusBricker]

Hi,

I'm having a lot of issues getting libgit2sharp to work on OSX 10.9. So far I've tried pulling from vNext and building myself, as well as downloading v0.14.1 from NuGet.

Both give me this exception:

System.DllNotFoundException: git2-96fb6a6
  at at (wrapper managed-to-native) LibGit2Sharp.Core.NativeMethods:git_threads_init ()
  at LibGit2Sharp.Core.NativeMethods+LibraryLifetimeObject..ctor () [0x00006] in /Users/Chris/Projects/MonoDevelop/libgit2sharp/LibGit2Sharp/Core/NativeMethods.cs:33
  at LibGit2Sharp.Core.NativeMethods..cctor () [0x00079] in /Users/Chris/Projects/MonoDevelop/libgit2sharp/LibGit2Sharp/Core/NativeMethods.cs:75

I have ran the build.libgit2sharp.sh build script to generate all the necessary Native Binaries. All I'm trying to do is a simple Repository.Clone() operation.

My mono version is 3.2.5 x86 and I'm using Xamarin Studio 4.2.2 if it helps.

What am I missing/doing wrong?

[nulltoken]

@ben already worked in this area with #560. He might be able to help you.

[GusBricker]

I've reviewed #560, which is what prompted me to move from 0.14.1 to vNext. I get the feeling the issue I'm having is probably something simple I'm overlooking. I can successfully run build.libgit2sharp.sh and have all tests complete successfully. Which implies that libgit2sharp is finding the native binaries successfully.

So maybe I just have my project setup incorrectly?
What i've done is copy the contents of the Build folder into my project and add an assembly reference for LibGit2Sharp.dll. Is there anything else I need to do? Do i need the .dylib files?

[anaisbetts]

@GusBricker No, we need to disable this hack on non-Windows. In the meantime, you can probably fix this via a DllMap Entry that points git-96fb6a6 to libgit2.dylib (or whatever the version is you're binding to)

[GusBricker]

Whats the proper fix for this? Why is the git-96fb6a6.dll needed on OSX/Linux anyway? Shouldn't OSX use the .dylib and Linux .so files?

[anaisbetts]

I think you're misunderstanding me - you don't need the .dll itself, you only need to configure the mapping, or change the -SHA1 to just git

[carlosmn]

The mapping would be useful if you wanted to use a system-installed libgit2, which is rarely going to be the case, as there is no API stability. So you want to use the version of libgit2 that the script built, which has that suffix in its name. While the name came primarily as a workaround for a Windows quirk, the name of the library that libgit2sharp is looking for is still the name of the library that's built at the same time and that you know works well with it.

As you wouldn't want your version of libgit2 to be installed in the system where it might conflict with libgit2 versions that other tools want to use, the way forward is the same as if it didn't have the suffix, export the environment variable DYLIB_LIBRARY_PATH so it points to where your native libraries are located, like the script does in order to run the tests. Or if you already have such an env variable, put libgit2-<sha>.so* there.

[GusBricker]

Ok guys, thanks for the help.
I've resolved it now without the usage of dllmaps. I renamed the library to libgit2-96fb6a6.dylib and placed into the folder alongside the executable and the rest of the libraries.

Apparently if don't specify a dllmap using a .config file the default name mapping procedure per OS is:
Windows, git2-96fb6a6.dll.
OSX, libgit2-96fb6a6.dylib
Linux, libgit2-96fb6a6.so
I think this is what @carlosmn was hinting at.

Once again, thanks for the help!