I updated to Xcode 8.3 and Swift 3.1 and got this warning in my bridging header file, referencing to an Objective-C header file:
Non-portable path to file "File.h"; specified path differs in case from file name on disk
How can I resolve this?
Asked
Active
Viewed 3.5k times
28
Tamás Sengel
- 55,884
- 29
- 169
- 223
5 Answers
43
It turned out that I misspelled the file's name, the correct name was "FILE.h" instead of "File.h". The warning appeared because of the soon coming APFS to macOS.
Tamás Sengel
- 55,884
- 29
- 169
- 223
-
5But when you upgrade your file system to APFS, it *will* be case sensitive and this code will no longer compile. – Anya Shenanigans Mar 28 '17 at 10:25
-
Thanks, I will include this in my answer. – Tamás Sengel Mar 28 '17 at 10:26
-
1I'm getting a bunch of these warnings and they're all false. Why would it flag the problem when it doesn't exist? – Bungles May 08 '17 at 21:32
-
me too! damn capital letters – dowi May 14 '17 at 14:54
-
Thanks. Renamed the file according to the class name and the warning disappeared. – CGN Oct 09 '17 at 10:21
2
In my case, the !!project folder name!! isn't match the bridging header path.
I changed
"project/project-Bridging-Header.h"
to
"Project/project-Bridging-Header.h"
Tested on Xcode 9.3
Den
- 3,179
- 29
- 26
1
One additional cause, that I experienced, was that a library project was importing itself incorrectly. For example, given projects Main and Library, Main would import Library with:
#import "Library/Library.h"
If Library attempts to use the same import, the Non-portable path warning will appear. Removing the path portion is the easy fix:
#import "Library.h"
The better fix is to import the specific components that Library needs from itself:
#import "Widget.h"
#import "NSString+Library.h"
Joel Murphy
- 845
- 1
- 6
- 13
1
Encountered the problem in Qt (C++) on a MacOS computer from a code developed and working on Ubuntu.
My project had two files : server.cpp and Server.cpp.
The solution was to change the name of one file or the other.
secavfr
- 628
- 1
- 9
- 24
0
If you can't change the file names because it's a library code you could make the files that include your libraries case-sensitive! (If your PC is Windows 10 or up)
- Open Powershell(Admin)
- Use
Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linuxtoo enable case-sensitivity atribute - Restart the PC
- Use
fsutil.exe file SetCaseSensitiveInfo YourDestinationFolder enableto enable case-sentivity
This could make the file case sensitive and solve the build problem.
