Finishing the renaming changes

This commit is contained in:
2026-05-01 21:47:46 +02:00
parent 4f62d5eb4c
commit b388b1e08e
2 changed files with 7 additions and 7 deletions

View File

@@ -28,7 +28,7 @@ pub fn build(b: *std.Build) void {
// to our consumers. We must give it a name because a Zig package can expose
// multiple modules and consumers will need to be able to specify which
// module they want to access.
// const mod = b.addModule("base_road_network", .{
// const mod = b.addModule("traffic-simulator", .{
// // The root source file is the "entry point" of this module. Users of
// // this module will only be able to access public declarations contained
// // in this file, which means that if you have declarations that you
@@ -68,7 +68,7 @@ pub fn build(b: *std.Build) void {
// If neither case applies to you, feel free to delete the declaration you
// don't need and to put everything under a single module.
const exe = b.addExecutable(.{
.name = "base_road_network",
.name = "traffic-simulator",
.use_llvm = true,
.root_module = b.createModule(.{
// b.createModule defines a new module just like b.addModule but,
@@ -84,12 +84,12 @@ pub fn build(b: *std.Build) void {
// List of modules available for import in source files part of the
// root module.
.imports = &.{
// Here "base_road_network" is the name you will use in your source code to
// import this module (e.g. `@import("base_road_network")`). The name is
// Here "traffic-simulator" is the name you will use in your source code to
// import this module (e.g. `@import("traffic-simulator")`). The name is
// repeated because you are allowed to rename your imports, which
// can be extremely useful in case of collisions (which can happen
// importing modules from different packages).
// .{ .name = "base_road_network", .module = mod },
// .{ .name = "traffic-simulator", .module = mod },
// Raylib import
.{ .name = "raylib", .module = raylib },