Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Attempt to solve #3366, regarding spurious shared library search paths. #3651

Merged
merged 3 commits into from
Feb 8, 2017

Commits on Feb 5, 2017

  1. Attempt to solve rust-lang#3366, regarding spurious shared library se…

    …arch paths.
    
    This drops `native_dirs` entries that are not within the target directory when
    modifying the (DY)LD_LIBRARY_PATH environment variable before running
    programs.
    pkgw committed Feb 5, 2017
    Configuration menu
    Copy the full SHA
    ff68a27 View commit details
    Browse the repository at this point in the history

Commits on Feb 7, 2017

  1. Update the 'run_with_library_paths' test to reflect the new filtering.

    For the library paths to be passed through, they must reside within the build
    output directory.
    pkgw committed Feb 7, 2017
    Configuration menu
    Copy the full SHA
    8913382 View commit details
    Browse the repository at this point in the history
  2. Attempt to fix the run_with_library_paths test for Windows.

    I was just pasting the build directories into Rust string literals, so Windows
    paths with backslashes were being interpreted as having unknown string
    escapes. Raw string guards should fix this for all but the most pathological
    of build directories.
    pkgw committed Feb 7, 2017
    Configuration menu
    Copy the full SHA
    d545a9f View commit details
    Browse the repository at this point in the history