question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Add x64 native tools to documentation (for usage)

See original GitHub issue

After dotnet new and dotnet restore (which appear to work fine, as does dotnet run), I get an error doing a native compile:

PS C:\users\Public\hello-world> dotnet compile --native
Compiling hello-world for DNXCore,Version=v5.0

Compilation succeeded.
    0 Warning(s)
    0 Error(s)

Time elapsed 00:00:01.8077755
Input Assembly: C:\users\Public\hello-world\bin\Debug\dnxcore50\hello-world.dll
LINK : fatal error LNK1104: cannot open file 'kernel32.lib'
Linking of intermediate files failed.

And with -c Release as suggested here https://github.com/dotnet/cli/issues/633

PS C:\users\Public\hello-world> dotnet compile --native -c Release
Compiling hello-world for DNXCore,Version=v5.0

Compilation succeeded.
    0 Warning(s)
    0 Error(s)

Time elapsed 00:00:01.8150396
Input Assembly: C:\users\Public\hello-world\bin\Release\dnxcore50\hello-world.dll
LINK : fatal error LNK1181: cannot open input file 'kernel32.lib'
Linking of intermediate files failed.

Installed just now from https://dotnetcli.blob.core.windows.net/dotnet/dev/Binaries/Latest/dotnet-win-x64.latest.zip

Environment:

PS C:\users\Public\hello-world> dotnet --version
.NET Command Line Tools (1.0.0)
Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.10586
 OS Platform: Windows
 Runtime Id:  win10-x64

Issue Analytics

  • State:closed
  • Created 8 years ago
  • Comments:5 (4 by maintainers)

github_iconTop GitHub Comments

1reaction
brthorcommented, Jan 11, 2016

Are you inside VS 2015 x64 Native Tools command prompt? This is currently a requirement for Native Compilation.

0reactions
blackdwarfcommented, Jan 11, 2016

We need to document the fact that you need to run the native compilation within a certain context (cmd prompt).

Read more comments on GitHub >

github_iconTop Results From Across the Web

Use the Microsoft C++ toolset from the command line
x64_x86 Cross Tools Command Prompt - Sets the environment to use 64-bit, x64-native tools to build 32-bit, x86-native code. The Start menu ...
Read more >
Enable a 64-Bit MSVC Toolset on the Command Line
Use Vcvarsall.bat to set a 64-bit hosted build architecture ... Any of the native or cross compiler tools build configurations can be used...
Read more >
How do I get the x64 Native Tools Developer Command ...
In my case it is named x64 Native Tools Command Prompt for VS 2019 and I can find it by the following sequence:...
Read more >
x64 Native Tools Command Prompt for VS 2019 Preview ...
Start 'x64 Native Tools Command Prompt for VS 2019 Preview' · run 'where cl' · cl points to non-preview version (in my case...
Read more >
How to build on windows
Recomended: Use Visual Studio x64 Native Tools Command Prompt . Just press the Win button and search for x64 (be careful to not...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found