[
http://dev.sourcefabric.org/browse/LS-499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15517#action_15517
]
Romain Beauxis commented on LS-499:
-----------------------------------
BTW, the .camlp4.ml is a little trick in the Makefile.
%.ml is already declared for regular .ml files.
%.camlp4.ml is used a an intermediary target to automatically convert .cmlp4
files when camlp4 is installed:
+ You specify a .camlp4 file in the sources to be compiled,
+ If camlp4 is detected, then we create a set $(camlp4_ml) of .camlp4.ml from
those files, which is otherwise
+ Each .camlp4 also translates into a .ml file that is always added to the
program's sources.
+ The generated .ml file is also present if the sources to be able to compile
without camlp4
+ Files declared in $(camlp4_ml) are dependencies for ocamldepends, which
triggers the generation of ml from camlp4
+ The conversion of camlp4 code produces both .ml and .camlp4.ml files
End of the story...
If you have a better idea I'm all for it :)
> output.harbor isn't an active source
> ------------------------------------
>
> Key: LS-499
> URL: http://dev.sourcefabric.org/browse/LS-499
> Project: Liquidsoap
> Issue Type: Bug
> Components: Liquidsoap
> Reporter: David Baelde
> Priority: Major
> Fix For: 1.0
>
>
> There is something really weird going on in output.harbor: it isn't an active
> source, just try to use it as the only output and liquidsoap will say "No
> output defined, nothing to do.". I tried to insert an assert false in the
> base output class, it wasn't executed... it looks like output.harbor doesn't
> effectively inherit from it, or something.
> I'm wondering if this could be due to a bad translation of the camlp4 file.
> The ML output is unreadable because the way let-in are printed, they get
> nested. This could be enhanced. By the way, what's the <file>.camlp4.ml?
> For the record, here's the actual feature request I was after: make a
> two-stage output.start/stop. In the first stage the HTTP handler is set, but
> the encoder isn't started, and possibly (depending on an option) the source
> isn't pulled (note that it should be and remain available, since
> #output_start is only called in that case). In the second stage the encoder
> is created. This may require to not use the stock Output.encoded but this
> "on-demand stream computation" feature could be very useful.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://dev.sourcefabric.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Create and publish websites with WebMatrix
Use the most popular FREE web apps or write code yourself;
WebMatrix provides all the features you need to develop and
publish your website. http://p.sf.net/sfu/ms-webmatrix-sf
_______________________________________________
Savonet-devl mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/savonet-devl
