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

Incomplete installation? #69

Closed
BengtGustafsson opened this issue Apr 7, 2021 · 4 comments
Closed

Incomplete installation? #69

BengtGustafsson opened this issue Apr 7, 2021 · 4 comments

Comments

@BengtGustafsson
Copy link

I just installed MicroProfiler in VS 2019.

When I enable profiling and start I get a linker error:

LINK : warning LNK4044: unrecognized option '/micro-profiler_x64.lib'; ignored

This turns out to be caused by the lack of a macro in VS as the linker input is set to be: $(MICROPROFILERDIR)/micro-profiler_$(PlatformName).lib

There is no variable MICROPROFILERDIR in VS macro list.

I assume the installation process should have created it and I have no idea how to create it manually.

I found the lib file in C:\Users\bengtg\AppData\Local\Microsoft\VisualStudio\16.0_7e09f2b5\Extensions\15mex1k0.gw5 so it is not very easy to guess where it is.

UI replaced the macro name with the path for testing, and now it misses the corresponding DLL instead.

Any ideas of what went wrong?

@tyoma
Copy link
Owner

tyoma commented Apr 7, 2021

Hello Bengt!
it sometimes requires restart of visual studio after the first run upon microprofiler installation. after you exit VS, please check if the env var mentioned is set in cmd.exe:

set

thank you!

@whitwhoa
Copy link

whitwhoa commented Aug 3, 2021

Had the same thing happen. Can confirm that after installation I needed to open vs, enable profiling, close vs, then open vs again, and everything was well!

tyoma added a commit that referenced this issue Jun 20, 2022
…isualStudio at startup are terminated if the environment setup needed to change the env variables
@tyoma
Copy link
Owner

tyoma commented Jun 20, 2022

Added a termination of child VS processes upon first VS run since MicroProfiler installation - this should fix the missing library issue.

@tyoma tyoma closed this as completed Jun 20, 2022
@Smurf-IV
Copy link

@tyoma
This needs to be reopened:
Installed V 2.0.651.0 via VS 2022 (17.3.7)
Performed "Right click" on project then build
Got the error described in the OP.

After some searching found this item.
Can confirm that after shutting down and restarting VS it then built as expected.
The fix instructions Need to be placed in the description and in the landing page of the project until fixed please.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants