Use the release profile for configure in opam

The build instructions in the opam files correctly use `-p` for the
builds themselves, but the configure script uses the default profile.
The configure script now recognises -release in its first argument as
meaning that `--profile=release` should be added to the `dune exec`
invocation, and the opam files are updated to include this flag.

Author: dra27

configure

@@ -11,4 +11,11 @@ then
     exit 1
 fi
 
-dune exec --root . -- $configure "$@"
+if [ "x$1" = 'x-release' ]; then
+  shift 1
+  dune_release='--profile=release'
+else
+  dune_release=''
+fi
+
+dune exec $dune_release --root . -- $configure "$@"

coq.opam

@@ -20,6 +20,7 @@ dev-repo: "git+https://github.com/coq/coq.git"
 build: [
   ["dune" "subst"] {dev}
   [ "./configure"
+    "-release" # -release must be the first command line argument
     "-prefix" prefix
     "-mandir" man
     "-libdir" "%{lib}%/coq"

coq.opam.template

@@ -1,6 +1,7 @@
 build: [
   ["dune" "subst"] {dev}
   [ "./configure"
+    "-release" # -release must be the first command line argument
     "-prefix" prefix
     "-mandir" man
     "-libdir" "%{lib}%/coq"

rocq-runtime.opam

@@ -39,6 +39,7 @@ dev-repo: "git+https://github.com/coq/coq.git"
 build: [
   ["dune" "subst"] {dev}
   [ "./configure"
+    "-release" # -release must be the first command line argument
     "-prefix" prefix
     "-mandir" man
     "-libdir" "%{lib}%/coq"

rocq-runtime.opam.template

@@ -1,6 +1,7 @@
 build: [
   ["dune" "subst"] {dev}
   [ "./configure"
+    "-release" # -release must be the first command line argument
     "-prefix" prefix
     "-mandir" man
     "-libdir" "%{lib}%/coq"