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.

three problems

See original GitHub issue

Name is too long for a console application. Dependencies -> depend(depnd or other). you can make a symbolic link to the original or duplicate.
Options have too long names:

   Options :
   -h -help : display this help
   -json : activate json output.
   -apisets : dump the system's ApiSet schema (api set dll -> host dll)
   -apisetsdll : dump the ApiSet schema from apisetschema.dll (api set dll -> host dll)
   -knowndll : dump all the system's known dlls (x86 and x64)
   -manifest : dump FILE embedded manifest, if it exists.
   -sxsentries : dump all of FILE's sxs dependencies.
   -imports : dump FILE imports
   -exports : dump  FILE exports
   -modules : dump FILE resolved modules
   -chain : dump FILE whole dependency chain

Abbreviated versions can be made:

   Options :
   -h       --help           : display this help
   -j       --json           : activate json output.
   -as      --apisets        : dump the system's ApiSet schema (api set dll -> host dll)
   -asdll   --apisetsdll     : dump the ApiSet schema from apisetschema.dll (api set dll -> host dll)
   -kndll   --knowndll       : dump all the system's known dlls (x86 and x64)
   -mf      --manifest       : dump FILE embedded manifest, if it exists.
   -se      --sxsentries     : dump all of FILE's sxs dependencies.
   -im      --imports        : dump FILE imports
   -ex      --exports        : dump  FILE exports
   -md      --modules        : dump FILE resolved modules
   -ch      --chain          : dump FILE whole dependency chain

Or other short names.

there is no option for outputting direct dependencies, only dumps. eg:

$depend -d name.exe (or name.dll)
 
lib1.dll             C:\path\to\lib1.dll
lib2.dll             C:\path\to\lib2.dll
--> libz.dll           C:\path\to\libz.dll
lib3.dll             D:\path\to\lib3.dll

Or something like this.

Issue Analytics

State:
Created 2 years ago
Comments:5 (1 by maintainers)

Top GitHub Comments

2reactions

lucasgcommented, Aug 15, 2021

I’m not a big fan of abbreviated names, characters are free and we should use it. I agree it should have a autocompletion system to speed up usage but I don’t know if the optarg library I use can do it.

1reaction

fratfoxidcommented, Jul 17, 2021

I have not used the old version. Dependency Walker users may think differently, but I find the new names better and closer to the standards. Dependency Walker functionality is excellent. Don’t take away, for heaven’s sake, long names, they are great, informative names! I believe that double names are needed - short and long. Short names are handy for scripts and build systems, etc. Long names are good for human memory. thanks

Top Results From Across the Web

The Three-Body Problem (novel)

The series portrays a fictional past, present and future where, in the first book, Earth encounters an alien civilization in a nearby star...

The Three-Body Problem - Liu, Cixin, Liu, Ken: Books

The Three-Body Problem is the first chance for English-speaking readers to experience the Hugo Award-winning phenomenon from China's most beloved science ...

Classical Problems, Algebra, Geometry - Mathematics

The three classical problems. Although Euclid solves more than 100 construction problems in the Elements, many more were posed whose solutions required more ......

Three down? Current problems and issues - Downdetector

Real-time Three problems and issues. Network down or no internet? We'll tell you what is going on.

Three problems in the genetics of speciation by selection

The third problem concerns the source of genetic variation underlying reproductive isolation, and especially the role of standing genetic ...