Hi Jim,
No it isn’t, at least at this moment. Pkgdep.sh brings a lot of stuff, like gcc, make, autotools, lspci, etc. in another words pkgdep.sh prepares the system to build and execute SPDK code. In this port, I ensure you have the right stuff to build SPDK, but not to run

The vcpkg is more like the OS package manager, but the main problem with package managers they are lagging behind latest stable releases and sometimes it built using other than your dev compiler (version/vendor) . So, what vcpkg does it just pulls the release from, let say, git hub, executes build (in your dev environment, using your dev tools), saves the artifacts and make it available to your project (CMake based project). So, what exactly the advantage of vcpkg? It saves you the “git clone – configure – make” sequence? Essentially, yes. But when you have to do it for dozen of third party projects it could be lengthy operation, and then new releases are out and you have to do it again. Vcpkg manages it for you, just tell it to upgrade and it will do an upgrade for all you outdated packages. In addition, it maintains all internal dependencies, for example project A depends on project B, and you ask to install project A, then B will be installed automatically, however it does not work with SPDK since you have forked original projects like ISA-L, DPDK, ip-sec etc.
Hope things are clearer now.

Sincerely,
Ernest

Sent from Mail for Windows 10

From: Harris, James R
Sent: Friday, April 26, 2019 02:11
To: Storage Performance Development Kit
Subject: Re: [SPDK] SPDK availability in vcpkg

Thanks Ernest.  Sorry for the delay in replying - between last week's SPDK summit and our upcoming 19.04 release I've gotten behind on e-mail replies.

vcpkg looks interesting but I'll admit I'm not really familiar with it.  Would this be an alternative to running the pkgdep.sh script in SPDK to prepare a system for building and running SPDK?

-Jim


On 4/16/19, 11:12 AM, "SPDK on behalf of Ernest Zed" <spdk-bounces(a)lists.01.org on behalf of kreuzerkrieg(a)gmail.com> wrote:

    Recently I've created ports for all SPDK dependencies (DPDK, isa-l, ipsec)
    for vcpkg package manager. In short, vcpkg is a curated (by Microsoft) tool
    and infrastructure to manage consumption of C/C++ libraries by developers
    all over the world, it is open source and cross platform (MS/Linux/MacOS).
    More on vcpkg here https://github.com/Microsoft/vcpkg
    A couple of weeks ago, I finally moved to creating SPDK port for vcpkg.
    Looks like it is doing well and it is close to be merged into `master`.
    I want to encourage you to visit the PR page on GitHub
    https://github.com/Microsoft/vcpkg/pull/5877 and give your opinion. What do
    you think? Is it a good thing for SPDK community? will it make developer's
    life easier? If you think it is worth the effort, do you think there is
    things to improve?
    Looking forward to hearing from you.
    _______________________________________________
    SPDK mailing list
    SPDK(a)lists.01.org
    https://lists.01.org/mailman/listinfo/spdk
    

_______________________________________________
SPDK mailing list
SPDK(a)lists.01.org
https://lists.01.org/mailman/listinfo/spdk