-
-
Notifications
You must be signed in to change notification settings - Fork 130
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
file.write doesn't exist in 2.2.5 contrary to the documentation #4044
Comments
Hi! Most likely, you have a variable named This is an issue we're seeing more and more. I plan on looking at adding a warning when encountering such situation. |
We don't have any variable named
|
Hi @cdhowie,
|
Ah, I did not realize that these files didn't get bundled with the final executable, so that was a wrong assumption on my part. I will close the issue. If I was looking to remove all of the development dependencies after building, is there a single directory that I would be able to keep somewhere on the filesystem and toss everything else? I am attempting to optimize the size of the docker image (pltnk/docker-liquidsoap#20) as the dev dependencies leave GBs of cruft laying around. (If you do know the answer and would prefer to continue discussion on that pull request instead of here, that would be totally understandable.) Sorry for the noise! |
Ha that makes sense. We were discussing working out a more detailed build guide actually! @vitoyucepi wrote a detailed one here: #3609 We currently support 3 types of directory locations:
% LIQUIDSOAP_BUILD_TARGET=standalone dune build
...
* Configured paths
- mode : standalone
- standard library : ./libs
- scripted binaries : ./bin
- rundir : ./run
- logdir : ./log
- user cache : ./cache (override with $LIQ_CACHE_USER_DIR)
- system cache : ./cache (override with $LIQ_CACHE_SYSTEM_DIR)
- camomile files : ./camomile
... This is the build mode for windows so you can follow the build script for what to do next:
Of course you will also need the shared libraries unless you are able to build a static binary (which is the case on windows) Here's the posix mode:
I'm not sure if we still have scripted binaries.. We used to but I think nowadays its mostly all internal. |
Very useful info, thanks!
Right, the two-stage build I did installed the necessary runtime dependencies in the second stage, so that was sorted. I just didn't realize there was other stuff on the filesystem that liquidsoap needed to function. I'll give this another read tomorrow or next week when I'm ready to resume work on it and will see if I can't get the two-stage build working correctly then. |
Description
file.write
is mentioned in the documentation, but after upgrading from 2.0.0 to 2.2.5, our script that usesfile.write
gives an error indicating that this function no longer exists:Steps to reproduce
Use
file.write
in a script.Expected behavior
The function call should succeed, or the function should not be listed in the documentation.
Liquidsoap version
Liquidsoap build config
Installation method
From OPAM
Additional Info
No response
The text was updated successfully, but these errors were encountered: