[llvm-bugs] [Bug 43824] New: Question: Using std::filesystem on macOS prior 10.15 with statically linked libc++

[via llvm-bugs]

https://bugs.llvm.org/show_bug.cgi?id=43824

            Bug ID: 43824
           Summary: Question: Using std::filesystem on macOS prior 10.15
                    with statically linked libc++
           Product: libc++
           Version: 9.0
          Hardware: PC
                OS: MacOS X
            Status: NEW
          Severity: enhancement
          Priority: P
         Component: All Bugs
          Assignee: unassignedclangbugs at nondot.org
          Reporter: ki.stfu at gmail.com
                CC: llvm-bugs at lists.llvm.org, mclow.lists at gmail.com

My program linked statically with libc++.a (among with libc++abi.a), and it's
intended to run on macOS Sierra or higher. When we used Clang 6,
mmacosx-version-min was set to 10.12 and we were able to use
std::experimental::filesystem. Now we decided to upgrade to Clang 9, and faced
that now mmacosx-version-min should be set to 10.15.

Questions:
1. Can std::filesystem be used on macOS(-es) prior 10.15 if linking against
libc++ statically?
2. How does mmacosx-version-min affect statically linked programs? I thought it
only need for those who rely on system's libc++.dylib and its capabilities.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20191027/5df78e4f/attachment.html>