Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make spawn run build when trying to run a directory path #88

Closed
Tracked by #63
Parzival-3141 opened this issue Jan 24, 2024 · 0 comments · Fixed by #102
Closed
Tracked by #63

Make spawn run build when trying to run a directory path #88

Parzival-3141 opened this issue Jan 24, 2024 · 0 comments · Fixed by #102
Assignees
Milestone

Comments

@Parzival-3141
Copy link
Collaborator

Parzival-3141 commented Jan 24, 2024

When attempting to execute a program, if it's a source directory containing Go files, run it through the Build tool and cache the resulting binary in /sys/bin. This should happen at the kernel level instead of the shell.

Related #66 #69

@progrium progrium added this to the 0.1 milestone Jan 24, 2024
Parzival-3141 added a commit that referenced this issue Feb 8, 2024
…ctories

Closes #88
Closes #89

I though it was a bit silly casting `s.fsys` everywhere,
so I modifed `fs.go` to store the `watchfs` seperately.

There was also an issue in `wasm.js:writeSync()` where it would be passed
a null value for `buf` after the build tool finished in `proc.go:Spawn()`.
I added a catch-all fix, but perhaps its a bug that the null is passed in the
first place.

There's still some kinks to work out before you can edit the shell seamlessly,
namely using better heuristics for when files should be updated/rebuilt. We can use
mtime/ctime for those.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants