Hi Romain,
Yes, your mail helped a lot. Sounds like opam is the best option for now,
but I'll try to have a look at the static option when I get a little more
time.
Thanks for your answer!
On Tue, May 24, 2016 at 5:03 PM, Romain Beauxis <[email protected]>
wrote:
> Hi Fernando,
>
> Yes, the stand alone distribution should be what you need. We have been
> using it to build the windows version of liquidsoap which can be downloaded
> and used right away.
>
> You should be able to do the same in linux but I think in this case you
> might have some real issues with the dynamic libraries required for
> liquidsoap. In windows, you can just copy them at the root of the directory
> where the binary is but in linux I believe that will be much more tricky.
>
> Your other alternative is to build a static binary for liquidsoap.
> However, OCaml doesn't make it very easy in this case. You might want to
> play with the 4.02.3+musl+static switch of opam. I know that I've managed
> to build static binaries for a smaller project in the past.
>
> Finally, you could also consider giving installation direction using opam.
> If the base system is Debian or Ubuntu, this could be made quite straight
> forward, install opam, install opam depext, install dependencies, install
> liquidsoap. We even have a liquidsoap-daemon now that will setup a
> daemonized liquidsoap from opam.
>
> Hope this helps,
> Romain
>
> 2016-05-24 9:47 GMT-05:00 Fernando Carmona <[email protected]>:
>
>> Hi all,
>>
>> I'm currently developing a webradio software using Django and Liquidsoap
>> as my final degree project. For development, I've been using the opam
>> version (1.2.0), but at the moment the binary location is hardcoded, and I
>> don't think that's a valid option.
>>
>> I want it to be deployable with the least effort possible (think of a
>> person with little knowledge trying to install it), so I've been looking
>> for other options. That's when I came across the custom path build section
>> of the docs, and I think it's pretty much what I need.
>>
>> My question is: is it possible to build a custom binary that can be
>> distributed with my software to work as is? Is there any extra steps to
>> achieve this, or are the build steps (with custom path settings) enough? I
>> wouldn't mind to control a couple of dependencies if required, provided
>> there's a simple way to install them.
>>
>> Another option would be making an installation guide with step-to-step
>> instructions, using the opam version, but since that proved tricky when I
>> installed it, I feel like it's not the best one.
>>
>> Any idea is welcome. Thanks in advance!
>>
>>
>> ------------------------------------------------------------------------------
>> Mobile security can be enabling, not merely restricting. Employees who
>> bring their own devices (BYOD) to work are irked by the imposition of MDM
>> restrictions. Mobile Device Manager Plus allows you to control only the
>> apps on BYO-devices by containerizing them, leaving personal data
>> untouched!
>> https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
>> _______________________________________________
>> Savonet-users mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/savonet-users
>>
>>
>
>
> ------------------------------------------------------------------------------
> Mobile security can be enabling, not merely restricting. Employees who
> bring their own devices (BYOD) to work are irked by the imposition of MDM
> restrictions. Mobile Device Manager Plus allows you to control only the
> apps on BYO-devices by containerizing them, leaving personal data
> untouched!
> https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
> _______________________________________________
> Savonet-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/savonet-users
>
>
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
Savonet-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/savonet-users
