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

no field or member function named 'standardReleaseOptions' in 'Build' #141

Open
dlazerka opened this issue May 8, 2024 · 3 comments
Open

Comments

@dlazerka
Copy link

dlazerka commented May 8, 2024

Hi, just did

git clone [email protected]:jedisct1/minisign.git
git checkout 0.11
zig build -Drelease

observe

$ zig build -Drelease
./minisign/build.zig:5:19: error: no field or member function named 'standardReleaseOptions' in 'Build'
    const mode = b.standardReleaseOptions();
                 ~^~~~~~~~~~~~~~~~~~~~~~~
./zig-linux-x86_64-0.11.0/lib/std/Build.zig:1:1: note: struct declared here
const std = @import("std.zig");
^~~~~
referenced by:
    runBuild__anon_7135: ./zig-linux-x86_64-0.11.0/lib/std/Build.zig:1639:37
    remaining reference traces hidden; use '-freference-trace' to see all reference traces

on zig 0.11.

On zig 0.12:

 $ zig build -Drelease
./minisign/build.zig:4:9: error: local variable is never mutated
    var target = b.standardTargetOptions(.{});
        ^~~~~~
./minisign/build.zig:4:9: note: consider using 'const'
@dlazerka
Copy link
Author

dlazerka commented May 8, 2024

Tried to change var to const, still no luck:

$ zig build 
./minisign/build.zig:3:21: error: root struct of file 'std' has no member named 'build'
pub fn build(b: *std.build.Builder) !void {
                 ~~~^~~~~~
./zig-linux-x86_64-0.12.0/lib/std/std.zig:1:1: note: struct declared here
pub const ArrayHashMap = array_hash_map.ArrayHashMap;
^~~

@jedisct1
Copy link
Owner

jedisct1 commented May 8, 2024

Remove git checkout 0.11 and use the current code.

Zig 0.12 was released after minisign 0.11 was tagged.

@jedisct1
Copy link
Owner

jedisct1 commented May 8, 2024

Maybe I should tag a new version. Not a lot of changes since 0.11 but why not.

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

No branches or pull requests

2 participants