You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/error-messages/tool-errors/linker-tools-error-lnk1104.md
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -38,27 +38,27 @@ translation.priority.mt:
38
38
# Linker Tools Error LNK1104
39
39
cannot open file '*filename*'
40
40
41
-
The tool could not open the specified file.
41
+
The linker could not open the specified file.
42
42
43
-
To fix this error, check for the following possible causes:
43
+
To fix this error, check for the following possible causes:
44
44
45
-
-You don't have enough disk space.
45
+
-The file *filename* does not exist. If your project depends on another project to produce this file, make sure your project dependencies are set correctly.
46
46
47
-
-The file *filename* does not exist.
47
+
-When specifying libraries in a project's Property Pages dialog box, library names must be separated by spaces, not commas.
48
48
49
-
-When specifying libraries in a project's property pages dialog box, library names must be separated by spaces, not commas.
49
+
-The filename or path specified on the command line is incorrect, or the path has an invalid drive specification. Check your spelling and verify the file name and location. If you are building a project that was copied from another computer, check the paths on the [VC++ Directories Property Page](../../ide/vcpp-directories-property-page.md) and update them if necessary.
50
50
51
-
- The filename or path specified on the command line is incorrect.
51
+
- The libraries for the project configuration or platform toolset are not installed. Verify that the platform toolset and Windows SDK specified in the Property Pages for your project is installed, and includes the toolset and libraries needed by your configuration settings. There are separate settings for Debug and Retail configurations, so if one build works but the other causes an error, make sure the settings are correct and the required tools are installed for both configurations.
52
52
53
-
-The path has an invalid drive specification.
53
+
-You don't have enough disk space. It's not unusual for the linker to consume a lot of temporary disk space during a link.
54
54
55
55
- You have insufficient file permissions to access *filename*.
56
56
57
-
- The path for *filename* expands to more than 260 characters.
57
+
- The path for *filename* expands to more than 260 characters. Change the names or rearrange your directory structure if needed to shorten the paths to the required files.
58
58
59
59
- If the *filename* is named LNK*n*, which is a filename generated by the linker for a temporary file, the directory specified in the TMP environment variable may not exist, or more than one directory may be specified for the TMP environment variable. Only one directory path should be specified for the TMP environment variable.
60
60
61
-
- If the error message occurs for a library name, and you recently ported the .mak file from a previous Microsoft Visual C++ development system, the library may no longer be valid. Ensure that the library still exists in this circumstance.
61
+
- If the error message occurs for a library name, and you recently ported the .mak file from a previous Microsoft Visual C++ development system, the library may no longer be valid. Ensure that the library name is correct and still exists in the specified location, or update the LIB path to point to the new location.
62
62
63
63
- Another program may have the file open and the linker cannot write to it. Antivirus programs often temporarily block access to newly created files. Try excluding your project build directories from the antivirus scanner.
0 commit comments