You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am attempting to work on a zig library that will eventually be shared/public and published. But in the interim, I am using a test app to flesh it out. I have used a local app in the same library and things work there. I am now trying to ensure I understand how to import this library in to other apps outside this library project. So I have a sibling zig project set up. It has a build.zig and build.zig.zon. In build.zig.zon I have a dependency with a path in it (not url/hash), which is mapped to ../mylibrary which is the sibling directory (root) of my library, where build.zig and build.zig.zon are also found.
In the test app build.zig I set up the dependency and add it just as I did in my library which depends on a 3rd party module.
In my test app, when I build I continually get the "panic: unable to find module 'mylibrary'
So one thing I am not sure of.. with the whole build.zig.zon and package management, when referring to a path in build.zig.zon, which I assume is the root path where the module exists.. the build.zig in THAT path needs to have the SAME name as defined in the test app build.zig dependency declaration? Or does that matter in any way?
The text was updated successfully, but these errors were encountered:
Hey all.
I am attempting to work on a zig library that will eventually be shared/public and published. But in the interim, I am using a test app to flesh it out. I have used a local app in the same library and things work there. I am now trying to ensure I understand how to import this library in to other apps outside this library project. So I have a sibling zig project set up. It has a build.zig and build.zig.zon. In build.zig.zon I have a dependency with a path in it (not url/hash), which is mapped to ../mylibrary which is the sibling directory (root) of my library, where build.zig and build.zig.zon are also found.
In the test app build.zig I set up the dependency and add it just as I did in my library which depends on a 3rd party module.
In my test app, when I build I continually get the "panic: unable to find module 'mylibrary'
test app build.zig.zon:
test app build.zig:
So one thing I am not sure of.. with the whole build.zig.zon and package management, when referring to a path in build.zig.zon, which I assume is the root path where the module exists.. the build.zig in THAT path needs to have the SAME name as defined in the test app build.zig dependency declaration? Or does that matter in any way?
The text was updated successfully, but these errors were encountered: