Shahar Yakir 2 years ago
parent
commit
71f56fdb44
  1. 1
      README.md
  2. 4
      build/_build.ts

1
README.md

@ -78,7 +78,6 @@ Alternatively, you can ignore the above requirements and develop right inside a
* In the root repo dir, run in terminal `npm run build` * In the root repo dir, run in terminal `npm run build`
* Compilation errors will appear on screen * Compilation errors will appear on screen
* Resulting build artifacts include: * Resulting build artifacts include:
* `mycontract.merged.fc` - merged and flattened FunC source code with all imports
* `mycontract.fif` - Fift file result of compilation (not very useful by itself) * `mycontract.fif` - Fift file result of compilation (not very useful by itself)
* `mycontract.compiled.json` - the binary code cell of the compiled contract (for deployment). Saved in a hex format within a json file to support webapp imports * `mycontract.compiled.json` - the binary code cell of the compiled contract (for deployment). Saved in a hex format within a json file to support webapp imports

4
build/_build.ts

@ -140,10 +140,8 @@ async function main() {
// make sure cell build artifact was created // make sure cell build artifact was created
if (!fs.existsSync(cellArtifact)) { if (!fs.existsSync(cellArtifact)) {
console.log(` - For some reason '${cellArtifact}' was not created!`); console.log(` - For some reason, intermediary file '${cellArtifact}' was not created!`);
process.exit(1); process.exit(1);
} else {
console.log(` - Build artifact created '${cellArtifact}'`);
} }
fs.writeFileSync( fs.writeFileSync(

Loading…
Cancel
Save