Skip to content

Conversation

ethomson
Copy link
Member

Introduce GlobalSettings.NativeLibraryPath on Windows, that allows consumers to configure the location where native libraries will get loaded.

This is advantageous in some environments where you have control over the location of your native libraries, but do not have any control over the location of the executing assembly. An example of such a crazy setup would be an MSBuild task - custom tasks are built (and executed from) %LOCALAPPDATA%\Temp\<random>.

@nulltoken
Copy link
Member

Hmmm. AppVeyor doesn't like the change. Yet. 😉

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would there be a way to throw as well if any call to the native library has already been made?

@nulltoken
Copy link
Member

@ethomson Strange. AppVeyor is still failing...

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@ethomson
Copy link
Member Author

Yeah, I'm not sure why the natives aren't loading there yet. Should have been mostly a no-op, I would have thought, but maybe I did something dumb. Investigating.

@ethomson ethomson force-pushed the ethomson/custom_nativepath branch from 8bdc30c to d243f20 Compare March 12, 2015 20:55
Edward Thomson added 3 commits March 13, 2015 21:26
Allow consumers to set the native library path in case they are
running in a strange environment that they have little control
over where the actual executing assembly lives (but do have some
control over the references) and want to point the library to the
native location explicitly.
@nulltoken nulltoken force-pushed the ethomson/custom_nativepath branch from d243f20 to e56c097 Compare March 13, 2015 20:26
@nulltoken nulltoken merged commit e56c097 into vNext Mar 14, 2015
@nulltoken nulltoken deleted the ethomson/custom_nativepath branch March 14, 2015 09:28
@nulltoken nulltoken added this to the v0.22 milestone Mar 18, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants