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

Cannot compile it #7

Closed
G0ne opened this issue Aug 21, 2023 · 6 comments
Closed

Cannot compile it #7

G0ne opened this issue Aug 21, 2023 · 6 comments

Comments

@G0ne
Copy link

G0ne commented Aug 21, 2023

Software used: VS2022 community edition
OS: windows 10

Error:
image

@cgfandia
Copy link
Owner

I can't reproduce it on clean setup.
Try to disable clang-tidy in project properties:
Configuration Properties - Code Analysis - General - Enable Clang-Tidy - No

@G0ne
Copy link
Author

G0ne commented Aug 22, 2023

It works!! thanks!(:
Btw, i have 2 more questions:

  1. Why does it happen?
    [-] Cannot open 'c:\path\to\some.exe' image - it is not an issue about permissions because i can run it

  2. Can you please explain what does the option '-d'?

@cgfandia
Copy link
Owner

It works!! thanks!(: Btw, i have 2 more questions:

  1. Why does it happen?
    [-] Cannot open 'c:\path\to\some.exe' image - it is not an issue about permissions because i can run it
  2. Can you please explain what does the option '-d'?
  1. Maybe architecture of the image and windep.exe is different, x86 vs x64. It should be the same.
  2. This flag enables resolving of delayed imports.

A delay-load DLL is a DLL that is implicitly linked but not actually loaded until your code attempts to reference a symbol contained within the DLL.

@G0ne
Copy link
Author

G0ne commented Aug 22, 2023

yeah, i figured it out, i just wanted to be sure in case there was an unexpected error(:
last thing and i hope i won't annoy you anymore ahah

i gave in input an .exe which i knew could not find a specific .dll:

this is the .dll that the app does not find: MSVRC120.dll

image

but when i run windep.exe, i get the following result:

image

this is the only one that results "unresolved: true"
why are there 2 different results?
Also, why does not me show the full path where .dll is expected?

@cgfandia
Copy link
Owner

I'm not sure, but probably rdpcoresccm.dll depends on missed msvrc120.dll, and because of this windep cannot load it properly. I will check this case.
There is no expected path of the dependent DLL. OS is responsible for the search by DLL name.

@G0ne
Copy link
Author

G0ne commented Aug 22, 2023

thank you!
this tool looks nice, i was looking for something like that! simple, small, and from command line
to me, the only missing thing is an option to print just the missing .dll(s) rather then all

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

No branches or pull requests

2 participants