unikernel/duniverse/dune_/test/blackbox-tests/test-cases/exe-name-mangle/multi-exe-same-dir.t/dune

@@ -0,0 +1,7 @@
+(executable
+ (name foo)
+ (modules foo))
+
+(executable
+ (name bar)
+ (modules bar))

unikernel/duniverse/dune_/test/blackbox-tests/test-cases/exe-name-mangle/multi-exe-same-dir.t/dune-project

@@ -0,0 +1,2 @@
+(lang dune 1.11)
+(wrapped_executables true)

unikernel/duniverse/dune_/test/blackbox-tests/test-cases/exe-name-mangle/multi-exe-same-dir.t/run.t

@@ -0,0 +1,6 @@
+These tests show that (wrapped_executables true) addresses the problem of compilation
+units of exes colliding with libraries.
+
+Multiple executables defined in the same directory
+
+  $ dune build

unikernel/duniverse/dune_/test/blackbox-tests/test-cases/exe-name-mangle/multi-module.t/baz.ml

@@ -0,0 +1,2 @@
+let () =
+  Foo.run ()

unikernel/duniverse/dune_/test/blackbox-tests/test-cases/exe-name-mangle/multi-module.t/dune

@@ -0,0 +1,7 @@
+(executable
+ (libraries foo)
+ (name baz))
+
+(alias
+ (name default)
+ (action (run ./baz.exe)))

unikernel/duniverse/dune_/test/blackbox-tests/test-cases/exe-name-mangle/multi-module.t/dune-project

@@ -0,0 +1,3 @@
+(lang dune 1.11)
+
+(wrapped_executables true)

unikernel/duniverse/dune_/test/blackbox-tests/test-cases/exe-name-mangle/multi-module.t/foo.ml

@@ -0,0 +1,2 @@
+(* finally calling into library *)
+let run () = Bar.run ()

unikernel/duniverse/dune_/test/blackbox-tests/test-cases/exe-name-mangle/multi-module.t/foo/bar.ml

@@ -0,0 +1,2 @@
+(* directly usable but will cause linking error *)
+let run = Foo.run

unikernel/duniverse/dune_/test/blackbox-tests/test-cases/exe-name-mangle/multi-module.t/foo/dune

@@ -0,0 +1,3 @@
+(library
+ (name foo)
+ (wrapped false))

unikernel/duniverse/dune_/test/blackbox-tests/test-cases/exe-name-mangle/multi-module.t/foo/foo.ml

@@ -0,0 +1 @@
+let run () = print_endline "not directly usable"

unikernel/duniverse/dune_/test/blackbox-tests/test-cases/exe-name-mangle/multi-module.t/run.t

@@ -0,0 +1,7 @@
+These tests show that (wrapped_executables true) addresses the problem of compilation
+units of exes colliding with libraries.
+
+The multi module case always requires an alias.
+
+  $ dune build
+  not directly usable

unikernel/duniverse/dune_/test/blackbox-tests/test-cases/exe-name-mangle/single-module.t/collision-lib/collisionlib.ml

@@ -0,0 +1,2 @@
+(* make sure everything is linked *)
+let run = Exe.run

unikernel/duniverse/dune_/test/blackbox-tests/test-cases/exe-name-mangle/single-module.t/collision-lib/dune

@@ -0,0 +1,3 @@
+(library
+ (name exe)
+ (wrapped false))

unikernel/duniverse/dune_/test/blackbox-tests/test-cases/exe-name-mangle/single-module.t/collision-lib/exe.ml

@@ -0,0 +1 @@
+let run () = print_endline "this module is unlinkable"

unikernel/duniverse/dune_/test/blackbox-tests/test-cases/exe-name-mangle/single-module.t/dune

@@ -0,0 +1,7 @@
+(executable
+ (libraries foo)
+ (name exe))
+
+(alias
+ (name default)
+ (action (run ./exe.exe)))

unikernel/duniverse/dune_/test/blackbox-tests/test-cases/exe-name-mangle/single-module.t/dune-project

@@ -0,0 +1,5 @@
+(lang dune 1.11)
+
+(wrapped_executables true)
+
+(implicit_transitive_deps false)

unikernel/duniverse/dune_/test/blackbox-tests/test-cases/exe-name-mangle/single-module.t/exe.ml

@@ -0,0 +1,2 @@
+let () =
+  Foo.run ()

unikernel/duniverse/dune_/test/blackbox-tests/test-cases/exe-name-mangle/single-module.t/foo/dune

@@ -0,0 +1,3 @@
+(library
+ (libraries exe)
+ (name foo))

unikernel/duniverse/dune_/test/blackbox-tests/test-cases/exe-name-mangle/single-module.t/foo/foo.ml

@@ -0,0 +1,3 @@
+let run () =
+  Exe.run ();
+  Collisionlib.run ()

unikernel/duniverse/dune_/test/blackbox-tests/test-cases/exe-name-mangle/single-module.t/run.t

@@ -0,0 +1,9 @@
+These tests show that (wrapped_executables true) addresses the problem of compilation
+units of exes colliding with libraries.
+
+Single module case. Here we technically don't need an alias module
+
+  $ dune build
+  this module is unlinkable
+  this module is unlinkable
+