Set up CI/CD pipeline based on the standalone template #308
Conversation
* Update readme with existing experiments * Add "CreateAnExperiment.md"
* Update README with feature/regexsrm * Update README.md
…ures (dotnet#238) * Add arcade common files * Add standalone library template for experiments that don't need runtime features * Add documentation to README.md * PR Feedback. Co-authored-by: Jan Kotas <[email protected]> * Quick fixups in README.md * PR Feedback * Simplify yml templates Co-authored-by: Jan Kotas <[email protected]>
…ortgenerator-hookup-build
jkoritzinsky
added
the
area-DllImportGenerator
jkoritzinsky
force-pushed
the
dllimportgenerator-hookup-build
branch
from
3831f15 to
ea7be41
Compare
jkoritzinsky
force-pushed
the
dllimportgenerator-hookup-build
branch
from
ea7be41 to
6696c0f
Compare
|
I may need some help with getting Linux and Mac onboard. Looks like there's something up with the clang support in DNNE that isn't hooked up quite right, but I might be wrong. |
| @@ -0,0 +1,16 @@ | |||
| { | |||
There was a problem hiding this comment.
Who updates this file?
There was a problem hiding this comment.
You can add an arcade subscription and then it would be auto update.
@jkoritzinsky DNNE assumes that |
| @@ -11,6 +11,6 @@ | |||
| } | |||
There was a problem hiding this comment.
Do you still need the runtimes section?
There was a problem hiding this comment.
Yes, we need the runtimes section to get some bug fixes in the hosting APIs for components. If we didn't need these bug fixes (or if they were in .NET 5), we wouldn't have the section.
I added |
…DllImportGenerator
Signed-off-by: Jeremy Koritzinsky <[email protected]>
jkoritzinsky
force-pushed
the
dllimportgenerator-hookup-build
branch
from
6696c0f to
106540b
Compare
|
|
…enerator-hookup-build Commit migrated from dotnet/runtimelab@c6ef6e1
This PR merges in the standalone template that @safern designed and adapts it to enable building DllImportGenerator.
Commits after 3e1b2ad have the changes to the template to integrate into our build; all commits before it are from the template.
There are now
build.cmdandbuild.shscripts that are the frontend of the Arcade build in the repo root.The following commands will be useful from the command line:
build.cmdto build the repobuild.cmd -testto build the repo and run unit testsbuild.cmd -integrationtestto build the repo and run integration testsbuild.cmd -test -integrationtestto build the repo and run all testsYou'll need to run
git clean -xdfafter pulling down a branch with this work since it changes the output directories to live underartifacts, so some files in the oldobjdirectories cause confilcts.Once you've run
build.cmdfrom the root of the repo once, you can develop, build, and test the project entirely from within VS or VSCode. The only time you need to run the root build script is when we update the runtime that we run tests on (useful for utilizing runtime bug fixes to improve our tests).I'm going to request that we do not Squash Merge or Rebase Merge this PR. I want to preserve the history of the standalone template (and I don't want git history to show that I own it).