GitXplorerGitXplorer
r

FaithlifeBuildTasks

public
1 stars
1 forks
0 issues

Commits

List of commits on branch master.
Unverified
aed079d60abc201d4cbc950e33ca5b38cd4b4e59

fix(cmd): use powershell for cmd bootstrappers.

rrandymarsh77 committed 4 years ago
Verified
77876ab2be4d782b1707dd99b7d5f472d1f7075f

fix(license): add a license file.

rrandymarsh77 committed 4 years ago
Verified
60c6724af2d73533f792c55c395b92f4284c028f

Add LICENSE file

TTyMick committed 4 years ago
Unverified
95f57b18a2d10a4be31a8c52815d585200f53f8b

fix(groups): properly group tasks.

rrandymarsh77 committed 4 years ago
Unverified
2235cad8a26bdd87a062e828165b286b9c30eac0

fix(exec): run commands from the bootstrapper directory.

rrandymarsh77 committed 4 years ago
Unverified
d18f0639f8c39eb19ecb5e00a97b4c53a2a869ba

fix(defaults): use corret defaults and fix the fingerprinting check.

rrandymarsh77 committed 4 years ago

README

The README file for this repository.

Faithlife.Build Tasks

Contributes VSCode tasks for Faithlife.Build projects.

Requirements

You need the associated tool to run your bootstrapper script installed and accessible in your PATH.

  • .ps1 will use pwsh (macOS and Windows).
  • .sh will use sh (macOS).
  • .cmd will use powershell (Windows).

Settings

Build Flags

Any extra flags to pass with build and package tasks. The setting is a ; separated list of global or per-project flags. Prefix with All: to apply these flags for all projects. Prefix with the workspace folder name to apply these flags for only this workspace. Workspaces can be comma separated and partial matches. Each scope is case insensitive.

Example:

All: --no-test ; MyMultiPlatformProject,Other: -p macOS

NuGet Output

A path to a directory in which to place built NuGet packages. Consider using with hotreloadnuget.

Example (macOS):

~/nuget-output

Custom Build Files

Some projects might have legacy and/or custom configuration as relates to the bootstrapper script(s) and build files.

Bootstrapper

You can specify an override to the bootstrapper. If the project has two platform independent scripts, .sh and .cmd use a pipe separated list contained in brackets of the valid extensions. The "best" match will be chosen based on the platform and tools available. e.g.

build.[sh|cmd]
Tools

The tools directory must contain Build.csproj and Build.cs. However, if these files aren't in tools/, then provide a path override to their location. e.g.

tools/Build