-
-
Notifications
You must be signed in to change notification settings - Fork 132
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to vendor Dream? #294
Comments
Sorry for the delay! Did you clone Dream with |
Hello @aantron, no worries. So I tried again and this time, it (almost) works Here's a simple project structure:
I initialized the project like such:
Now the only remaining difficulty is this example which doesn't compile with dune.
It's unclear to me where Also, it looks like this example is old and maybe not relevant anymore? http://dream.as does not respond + the |
Just an additional info: using the The number of files to compile is about 1/4 the original size so the compilation is faster too.
I'd be interested to hear your response about the z-playground before closing. |
The playground needs to be fixed (#222). I'm glad the build working. Let's leave this open, as a reminder to me to take a look at why |
Hello!
I'd like to vendor dream into my project.
Even though I ran
opam install --deps-only ./dream.opam --with-test
insider the vendored dream directory, I get these compile errors at my project root.I still get complaints about a missing
paf
module, even after issuingopam install paf
.So it seems I can't manage the vendored libraries of my vendored library.
I found a workaround, by changing Dream's dune file at the root of its vendor folder here. Instead of containing this:
It contains just this:
And that seems to satisfy my dune instance, not to go further. And my project compiles fine, I can modify Dream's code alright.
Could this dune file be simplified as I did? If not, could you please advise how to proceed?
Thanks
The text was updated successfully, but these errors were encountered: