Ununderstandable documents (wiki) about detours HOT 6 OPEN

Agree!!!

Every step in working with Detours seems to be a challenge. For example, it seems like only in the FAQs is the need to "nmake" the Detours library discussed ... and, even then, it doesn't specify which version of "nmake" should be used (e.g., my computer somehow has five versions of it in various directories), what pathing needs applied before running "nmake", how/where to find various required additional libraries (e.g., windows.h). All this stuff may seem obvious to the experienced ... but we newbies are left scratching our heads, guessing, and googling ... when this wiki should simply provide fully viable step-by-step instructions for downloading, building, and using Detours for the first time!

from detours.

Hey guys, you might find this helpful, let me know: https://github.com/0xeb/detours-cmake

from detours.

Hopefully PR #128 will make things slightly easier, I'll expand the documentation to talk about how to open a VS developer command prompt required to build.

from detours.

Also #48 as well should improve things and make the project just like any other C++ build.

from detours.

I fleshed out the FAQ a bit more with more details on setting up a build environment, the main thing being linking to the MSVC C++ command line tooling page, where they explain how to set up your developer command prompt. https://github.com/microsoft/Detours/wiki/FAQ#where-can-i-find-detourslib-and-detoursh

from detours.

I think that such poor documentation is due to the fact that Microsoft deliberately wanted it this way. This technology provides quite a lot of opportunities for developers, which also can not always be used for good purposes. Therefore, most likely, such a quest in order to increase the "entry threshold" for this technology. So that a person already understands at least roughly how it works, and also has skills and curiosity to work on this.

from detours.