Like much of Boost, Boost.Uuid is a header-only library, which means that only the functionality that you #include and use will become part of your project. So there's no problem with putting the entire Boost distribution somewhere in your include path and including Boost.Uuid headers.
(Boost.Uuid may itself depend on other Boost header files, so those may also become part of your project.)
With that said, there's no real reason not to do a standard installation of Boost, as in the question you linked; it's a good library, and only those parts that you actually use will become a part or become a dependency of your final project.
Edit: If you really want a subset of Boost, the BCP utility is designed to help you do this. I have no experience with it. To answer your question, Boost is designed to be cross platform, and I find it simplest to just install the whole thing and let it take care of its own dependencies.