-
Notifications
You must be signed in to change notification settings - Fork 0
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
Monorepo structure #12
Conversation
On my side the Zig build is failing with the following: /home/ktorok/Projects/md4w/packages/core/build.zig:12:33: error: no field named 'path' in union 'Build.LazyPath'
.root_source_file = .{ .path = "src/md4w.zig" },
^~~~
/usr/lib/zig/std/Build.zig:2171:22: note: union declared here
pub const LazyPath = union(enum) {
^~~~~
referenced by:
build: /home/ktorok/Projects/md4w/packages/core/build.zig:4:14
runBuild__anon_8819: /usr/lib/zig/std/Build.zig:2116:27
remaining reference traces hidden; use '-freference-trace' to see all reference traces
/home/ktorok/Projects/md4w/packages/core/build.zig:12:33: error: no field named 'path' in union 'Build.LazyPath'
.root_source_file = .{ .path = "src/md4w.zig" },
^~~~
/usr/lib/zig/std/Build.zig:2171:22: note: union declared here
pub const LazyPath = union(enum) {
^~~~~ |
db1fc1b
to
93deb33
Compare
You may want to extend the README, @ije |
7370632
to
153e45e
Compare
please use zig 0.11, the wasm build output of zig 0.12+ is significantly increased. i still wonder what change happened, and i have a plan to rewrite it in pure zig. |
I see. If you have any other improvement ideas then let me know. By the way, I wished to name the webcomponent part like |
@ije are you still considering the merge of our works into a monorepo? If not then we can close this. |
sorry for the late reply and thanks for your contribution, i feel this PR beyonds the simple goal of being a wasm module wihtout deps. why not keep the |
Sure, no problem |
No description provided.