updates

Author: mobileink

.bazelrc

@@ -1,3 +1,8 @@
+# bug:
+# 18:19: error: 'get<std::function<bool ()>, std::string, std::function<bool ()>>' is unavailable: introduced in macOS 10.13
+
+build --host_cxxopt=-std=c++14 --cxxopt=-std=c++14
+
 try-import %workspace%/.config/registries.bazelrc
 common --registry=https://raw.githubusercontent.com/obazl/registry/main/
 common --registry=https://bcr.bazel.build

MODULE.bazel

@@ -12,11 +12,11 @@ bazel_dep(name = "rules_cc",     version = "0.1.1")
 bazel_dep(name = "stardoc",      version = "0.8.0")
 
 ## obazl deps:
-bazel_dep(name = "rules_ocaml",  version = "3.0.0.dev")
-bazel_dep(name = "rules_ppx",    version = "3.0.0.dev")
-bazel_dep(name = "rules_ctypes", version = "0.23.0.dev")
+bazel_dep(name = "rules_ocaml",  version = "3.0.0.beta.1")
+bazel_dep(name = "rules_ppx",    version = "3.0.0.beta.1")
+bazel_dep(name = "rules_ctypes", version = "0.23.0.beta.1")
 
-bazel_dep(name = "tools_opam",   version = "1.0.0.dev")
+bazel_dep(name = "tools_opam",   version = "1.0.0.beta.1")
 opam = use_extension("@tools_opam//extensions:opam.bzl", "opam")
 
 bazel_dep(name = "protobuf",     version = "29.0")

Makefile

@@ -1,10 +1,10 @@
 .PHONY: import lib module ns rt test
 
-default: ocaml tools_opam ppx
+default: rules_ocaml tools_opam ppx
 
 xdefault: rules_ocaml sidebars tools_ocaml providers
 
-ocaml: binary import lib module ns rt sig test
+rules_ocaml: binary import lib module ns rt sig test
 
 binary:
 	bazel build //stardoc:ocaml_binary --show_result=20 \
@@ -53,8 +53,6 @@ providers:
 
 
 
-rules_ocaml: binary import lib module ns rt sig test
-
 sidebars:
 	bazel build //stardoc:rules_ocaml_sidebar \
 	&& sudo cp -v .bazel/bin/stardoc/sidebar_rules_ocaml.yml docs/_data/sidebars/sidebar_rules_ocaml_refman.yml

docs/_data/sidebars/obazl_ug_sbdata.yml

@@ -46,9 +46,13 @@ entries:
       open: true
       url: "#_ocaml-platform-support"
       output: web
-    - title: Opam libraries
+    - title: Opam
       open: true
-      url: "#_opam-libraries"
+      url: "#_opam"
+      output: web
+    - title: Nix
+      open: true
+      url: "#_nix"
       output: web
     - title: Other tools
       open: true

docs/obazl/obazl_index.adoc

@@ -389,11 +389,34 @@ Related:
 ====
 
 
-== Opam libraries
+== Opam
 
 Opam libraries are modeled as Bazel repos. The name conversion is
 straightforward:
 
+== Nix
+
+* https://xeiaso.net/blog/how-i-start-nix-2020-03-08/[How I Start: Nix] excellent blog article for getting started. 2020/03/08
+
+* https://dimitrije.website/posts/2023-03-04-nix-ocaml.html[Nix-powered development with OCaml] Blog article, 2023-03-04
+
+Installing manpages: https://nixos.org/manual/nixpkgs/stable/#sec-getting-documentation[Getting documentation] (nixpkgs manual)
+
+Empty the store:
+
+    sudo nix-collect-garbage
+
+Emits messages like `deleting '/nix/store/pg7zsw894hv5v6q5h1cmqibs2jis2mkb-libmpack-1.0.5.drv'
+`
+
+but lots of stuff remains in /nix/store/
+
+
+=== MacOS
+
+* https://checkoway.net/musings/nix/[Using Nix on macOS] Blog article, 2022-07-23. Contains excellent detailed info about dealing with `zsh` (https://checkoway.net/musings/nix/#fixing-shell-integration[Fixing shell integration]).
+
+
 == Other tools
 
 Ordinary libraries are easy to use. You just list them as

docs/rules-ocaml/reference/ocaml_ns.adoc

@@ -72,7 +72,7 @@ Not to be confused with the https://bazel.build/concepts/visibility[visibility,w
 |  `None` | +++<a id="ocaml_ns-submodules"></a>+++submodules
 |  List of strings from which submodule names are to be derived for aliasing. Bazel labels may be used; the submodule name will be derived from the target part. For example, '//a/b:c' normalizes to C. But they are just strings, and will not be checked against any files.
 
-The normalized submodule names must match the names of the modules electing membership via the 'ns_config' attribute. | +++List of strings+++
+The normalized submodule names must match the names of the modules electing membership via the `ns` attribute. | +++List of strings+++
 | optional
 |  `None` | +++<a id="ocaml_ns-visibility"></a>+++visibility
 |  The visibility to be passed to this macro's exported targets. It always implicitly includes the location where this macro is instantiated, so this attribute only needs to be explicitly set if you want the macro's targets to be additionally visible somewhere else. | +++<a href="https://bazel.build/concepts/labels">List of labels</a>; <a href="https://bazel.build/reference/be/common-definitions#configurable-attributes">nonconfigurable</a>+++

docs/rules-ocaml/reference/ocaml_ns_config.adoc

@@ -77,7 +77,7 @@ Not to be confused with the https://bazel.build/concepts/visibility[visibility,w
 | [[_ocaml_ns_config_submodules]]submodules
 |  List of strings from which submodule names are to be derived for aliasing. Bazel labels may be used; the submodule name will be derived from the target part. For example, '//a/b:c' normalizes to C. But they are just strings, and will not be checked against any files.
 
-The normalized submodule names must match the names of the modules electing membership via the 'ns_config' attribute. | +++List of strings+++
+The normalized submodule names must match the names of the modules electing membership via the `ns` attribute. | +++List of strings+++
 | optional
 | []