[Windows] Provide tutorial for installation from source

[kunaltyagi]

Is your feature request related to a problem? Please describe.

Several issues are asking relatively the same thing:

• How to start developing on PCL and install PCL from source in a reproducible manner?
• How to use PCL in a VS project?

Current Behavior

Tutorials are either old, or on third party websites (and thus out of touch)

Describe alternatives you've considered

Not supporting VS, but that's not possible 🤣

[UnaNancyOwen]

I think it is necessary to rewrite the tutorials for beginner.

[Neumann-A]

How to start developing on PCL and install PCL from source in a reproducible manner?

Use VCPKG ;)

How to use PCL in a VS project?

Use CMake with VCPKG

Not supporting VS, but that's not possible

Only Support VS via CMake

would be my answers to those question

[larshg]

If you are to only use PCL, I would suggest to use the All-In-One installer supplied with a good tutorial (to be made).

All-In-One-installer
Pros:

• Everything is precompiled (might limit what VS version can be used).
• Has, last I checked, a single folder with all dlls (debugs version with prefix).
• Takes less space don't know the exact.
  Cons:
• Missing a good tutorial showing how to setup a project using CMake. (ie. setting environment variables)

If you wan't to contribute to PCL I would suggest VCPKG, however the All-In-One-Installer can probably also be used, if the correct enviroment varables is set.

VCPKG:
Pros:

• Has every source file and building everything from scratch with the supplied compiler.
• Itergrates great with cmake supplying the toolchain file.
  Cons:
• Doesn't currently support VTK, ie no visualization.
• VCPKG takes approx 55 GB if you doesn't clean anything. (boost, vtk, flann, qhull, qt, + their dependcies)
• VCPKG doesn't build debug with a debug "prefix" so you can't have a single folder with all dlls, making it difficult to use. At least it doesn't copy all the required dlls after a integrate install here.