Perl 6 - the future is here, just unevenly distributed

IRC log for #marpa, 2014-04-14

| Channels | #marpa index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
02:25 jeffreykegler1 joined #marpa
05:56 ronsavage joined #marpa
16:02 jeffreykegler joined #marpa
17:17 jeffreykegler jdurand: I notice MarpaX-Languages-XML-AST/BuildMarpa.pl on your github site: https://github.com/jddurand/MarpaX-Languages-XML-AST/blob/master/BuildMarpa.pl -- Does that do what I think it does?
17:18 jeffreykegler The question of how to grab the libmarpa C library comes up from time to time, and all I've had in the past was Peter Stuifzand's effort, which was some time ago and am no longer sure where to find.
19:36 jdurand joined #marpa
19:36 jdurand Re http://irclog.perlgeek.de/marpa/2014-04-14#i_8586048 - yes it does what you think
19:36 jdurand Now, to be frank:
19:37 jdurand if you want to have Marpa popularity, I suggest to be able to extract libmarpa and do a shared library out of it
19:38 jdurand then, almost wll distros will be happy to have a libmarpa packaging, that will include a .so of it, instead of the .a currently being built
19:38 jdurand In particular, all linux-based distros would be happy to do that. I worked in parallel in a "debianization" of Marpa, and it worked quite well, but the best would be to have a separate libmarpa tarball
19:40 jdurand BuildMarpa.pl will simply do a "Build" out of the CPAN disto, and locate where is the lib, then copy the result to where I want
19:49 jdurand wihtout trying to do a .so... still the default .a
20:09 jdurand Btw, I just tried to do ./configure stand-alone in libmarpa_dist. Failed. Ok, I do the usual autoreconf -f -i, then ./configure works. But impossible to build a .so, only a .a - and I do not find where .a is forced...
20:29 jeffreykegler1 joined #marpa
20:33 jeffreykegler1 jdurand: re http://irclog.perlgeek.de/marpa/2014-04-14#i_8586651 -- it should be quite possible to build .so from libmarpa, and to distribute it.
20:34 jeffreykegler1 I deliberately kept the autoconf setup "vanilla", although I did change defaults in a standard way.
20:36 jeffreykegler1 So it should be quite possible to create the shared library of your choice, package it with the Libmarpa docs, and create what you might call a Marpa "distro"
20:37 jeffreykegler1 I'm reluctant to take this on myself, especially for boxes I don't have access to, but anything that prevents this happening I will treat as a bug, and give it a priority.
20:38 jeffreykegler1 The autoconf configure defaults "as delivered" are (of course) tailored to building with Perl and XS.
20:40 jeffreykegler1 The last time I was dealing with library defaults, there was no demand for a separate-standing libmarpa, so I gave it a low priority.
20:41 jeffreykegler1 I'll look into the build after lunch.  In the meantime, if you'd point out the obstacles you encounter to creating libraries of the kinds you want, that will help guide where I look.
20:45 jeffreykegler1 autoconf can be hard to work with, but there should be no real obstacle to the creation of Libmarpa libraries in whatever form is wanted.
20:46 jeffreykegler1 AFK until after lunch.
20:46 jdurand Have a nice lunch -;
23:37 jeffreykegler joined #marpa

| Channels | #marpa index | Today | | Search | Google Search | Plain-Text | summary