Early work for getting the framework build-file generator into the rules_csharp project. However, from the looks of it the generator is no longer mapping directly to this. This may be due to manual modifications or there may a branch with some unmerged diffs. I'm not particularly concerned with that, as I wanted to rough out the bazel run //tools/framework:generator workflow.
I have made some small modifications to the Label and other syntax generators to attempt to fit the expected data. These changes would not persist in the actual implement.
This PR is only for prototyping out ideas for generating the netN.BUILD files using rules_csharp, and under no circumstances should be merged. The actual work for getting this in rules_csharp will take the following:
Merging in relevant AST + files from our monorepo into rules_csharp with history
Matching the rules to the expected net.BUILD files
Configuring a build workflow (see stardoc with build run //tools/frameworks:generaotr && cp ..)
Either format with buildifier after generate (as temporary measure) or generate bazel by buildifier rules
Early work for getting the framework build-file generator into the rules_csharp project. However, from the looks of it the generator is no longer mapping directly to this. This may be due to manual modifications or there may a branch with some unmerged diffs. I'm not particularly concerned with that, as I wanted to rough out the
bazel run //tools/framework:generatorworkflow.I have made some small modifications to the
Labeland other syntax generators to attempt to fit the expected data. These changes would not persist in the actual implement.This PR is only for prototyping out ideas for generating the
netN.BUILDfiles using rules_csharp, and under no circumstances should be merged. The actual work for getting this in rules_csharp will take the following:net.BUILDfilesbuild run //tools/frameworks:generaotr && cp ..)Relates to #20