SDK not getting fully packaged about buildxl

[ScatteredRay]

This seems true of both the nuget build from https://pkgs.dev.azure.com/ms/BuildXL/_packaging/BuildXL/nuget/v3/index.json and from a locally deployed build at C:\Users\indy\Telltale\BuildXL\Out\Bin\debug\win-x64

[narasamdya]

It seems that we need to re-work some of our examples.

Indeed, to use functionalities in the SDK, one needs to include them in the resolver (specified in config.dsc). In this way DScript can find where they are located.

We typically include everything from the %BUILDXL_BIN_DIRECTORY%, in either of these two ways:

resolvers: [
        {
            kind: "DScript",
            modules: [
                ...globR(d`${Environment.getPathValue("BUILDXL_BIN_DIRECTORY")}/Sdk`, "package.config.dsc"),
                ...globR(d`${Environment.getPathValue("BUILDXL_BIN_DIRECTORY")}/Sdk`, "module.config.dsc"),
                ...globR(d`${Environment.getPathValue("BUILDXL_BIN_DIRECTORY")}/Sdk`, "module.config.bm"),
            ]
        },
    ],

or

resolvers: [
        {
            kind: "DScript",
            root: d`${Environment.getPathValue("BUILDXL_BIN_DIRECTORY")}/Sdk`,
        },
    ]

You can also take a look into how we set up/structure our integration tests here. In the tests we build a number of modules.

[ScatteredRay]

But it still seems that many SDK functionalities aren't included in the build, such as jsonSDK.dsc?

[smera]

Only the very basic SDKs are bundled together with BuildXL binaries. Those are the SDKs you see under <bxl-install-dir>/Sdk.

All SDKs (bundled with bxl binaries or not) that are needed have to be explicitly referenced from the main config.dsc file under 'resolvers', as the example Iman was showing above. A module.config.dsc (or package.config.dsc, the old name for module files) is what declares a particular module. If a module file exposes a module 'Foo' then referencing this module file in the main config will enable expressions like ' import * as Foo from "Foo" ' in a particular spec. The 'No resolver was found that owns...' error means that you are trying to import a module that is unknown to any resolver.

I believe at the moment we are not publicly publishing a NuGet with the additional SDKs. This is something we can consider doing. But if you clone BuildXL repo, you'll find all public SDKs here, you can just point your main config file resolvers to the module files you are interested about