You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Each of those folders contain some ocaml code compiled by dune. backend, frontend, and infra contain production code which should compile, be tested, have documentation, be formatted, etc. experimental on the other hand is a folder for quick POC, code snippets, ugly scripts, ... It is known that not all the code there will compile. Some of the code could compile but requires to have very specific dependencies installed. The problem is I would like to still be able to run dune command from the root of the project without involving experimental by default. Without ignoring experimental completely. One should still be able to use dune in experimental if they wish to do so.
One thing I tried is to overwrite the common aliases default/all/check/doc/doc-new/runtest. So I have a dune file at the root of the project which looks like this
For default, runtest, check, and doc-new things work as expected. It's not completely seemless, one has to run dune build @@check instead of dune build @check, but it's not too bad. But for all and doc it doesn't seem to work.
Lets simplify the dune file a bit to showcase the problem
Faced this problem while trying to get a workaround for #9692 and #9690.
I have a project which looks like this, with a dune-project at the root
Each of those folders contain some ocaml code compiled by dune.
backend
,frontend
, andinfra
contain production code which should compile, be tested, have documentation, be formatted, etc.experimental
on the other hand is a folder for quick POC, code snippets, ugly scripts, ... It is known that not all the code there will compile. Some of the code could compile but requires to have very specific dependencies installed. The problem is I would like to still be able to run dune command from the root of the project without involvingexperimental
by default. Without ignoringexperimental
completely. One should still be able to use dune in experimental if they wish to do so.One thing I tried is to overwrite the common aliases
default
/all
/check
/doc
/doc-new
/runtest
. So I have adune
file at the root of the project which looks like thisFor
default
,runtest
,check
, anddoc-new
things work as expected. It's not completely seemless, one has to rundune build @@check
instead ofdune build @check
, but it's not too bad. But forall
anddoc
it doesn't seem to work.Lets simplify the dune file a bit to showcase the problem
Then run the aliases for which things work as expected. I get a mostly empty
_build/log
with basically only 4 calls tobash
. And the expected output.While if I build the other 2 aliases, dune will actually compile and generate code in addition of running my bash commands.
The text was updated successfully, but these errors were encountered: