Re: Is LibraryMake still current?
Sorry for the necroposting, but I found out a new way to build a native code library to be used by a Raku module. Using Distribution::Builder::MakeFromJSON one can configure the native library building by adding some sections to the META6.json file, without using LibraryMake and its Build.pm file. 'zef build' works flawlessly and so does Mi6, which OTOH can't deal with LibraryMake. HTH On Sat, Dec 21, 2019 at 7:41 PM Fernando Santagata < nando.santag...@gmail.com> wrote: > Hello, > > What can I use to help building native code for a Raku module? > Is LibraryMake still the preferred method or there's something else to use > nowadays? > > Thanks! > > -- > Fernando Santagata > -- Fernando Santagata
Re: Is LibraryMake still current?
…and the App::Mi6 author just released an updated version that deals well with the new naming scheme! Thank you! On Mon, Dec 23, 2019 at 4:51 PM Fernando Santagata < nando.santag...@gmail.com> wrote: > I hope that zef tests a distribution using both .t and .rakutest > extensions, because there is no --verbose option to let one see what's > happening. > > BTW I raised one issue on App::Mi6, because its dist.ini file doesn't > allow a module to end with .rakumod, and one on App:prove6, because the > prove6 program doesn't test files ending with .rakutest. > > On Mon, Dec 23, 2019 at 3:47 PM Elizabeth Mattijsen > wrote: > >> >> https://github.com/perl6/problem-solving/blob/master/solutions/language/Path-to-Raku.md#extensions >> >> > On 23 Dec 2019, at 15:28, Parrot Raiser <1parr...@gmail.com> wrote: >> > >> > With the name change to Raku, has anyone considered a naming suffix >> > policy for modules? I don't have a problem with .pm6, and I don't >> > want to cause an outbreak of bikeshedding, but some might consider it >> > inconsistent. >> > >> > As an aside, I deplore the practice of identifying the language of a >> > directly executable program in the top level. It means that any change >> > to the language used means lying to the world, (which destroys the >> > point) or hunting down and changing every script or other caller to >> > reflect the new situation. >> > > > -- > Fernando Santagata > -- Fernando Santagata
Re: Is LibraryMake still current?
I hope that zef tests a distribution using both .t and .rakutest extensions, because there is no --verbose option to let one see what's happening. BTW I raised one issue on App::Mi6, because its dist.ini file doesn't allow a module to end with .rakumod, and one on App:prove6, because the prove6 program doesn't test files ending with .rakutest. On Mon, Dec 23, 2019 at 3:47 PM Elizabeth Mattijsen wrote: > > https://github.com/perl6/problem-solving/blob/master/solutions/language/Path-to-Raku.md#extensions > > > On 23 Dec 2019, at 15:28, Parrot Raiser <1parr...@gmail.com> wrote: > > > > With the name change to Raku, has anyone considered a naming suffix > > policy for modules? I don't have a problem with .pm6, and I don't > > want to cause an outbreak of bikeshedding, but some might consider it > > inconsistent. > > > > As an aside, I deplore the practice of identifying the language of a > > directly executable program in the top level. It means that any change > > to the language used means lying to the world, (which destroys the > > point) or hunting down and changing every script or other caller to > > reflect the new situation. > -- Fernando Santagata
Re: Is LibraryMake still current?
https://github.com/perl6/problem-solving/blob/master/solutions/language/Path-to-Raku.md#extensions > On 23 Dec 2019, at 15:28, Parrot Raiser <1parr...@gmail.com> wrote: > > With the name change to Raku, has anyone considered a naming suffix > policy for modules? I don't have a problem with .pm6, and I don't > want to cause an outbreak of bikeshedding, but some might consider it > inconsistent. > > As an aside, I deplore the practice of identifying the language of a > directly executable program in the top level. It means that any change > to the language used means lying to the world, (which destroys the > point) or hunting down and changing every script or other caller to > reflect the new situation.
Re: Is LibraryMake still current?
With the name change to Raku, has anyone considered a naming suffix policy for modules? I don't have a problem with .pm6, and I don't want to cause an outbreak of bikeshedding, but some might consider it inconsistent. As an aside, I deplore the practice of identifying the language of a directly executable program in the top level. It means that any change to the language used means lying to the world, (which destroys the point) or hunting down and changing every script or other caller to reflect the new situation.
Re: Is LibraryMake still current?
Hi David, Thank you for replying! LibraryMake looked ancient to me for its use of a .pm file, instead of a .pm6, so I asked if there was anything newer. The quantity of Raku modules is not remotely comparable to Perl's, yet there's something new each week and I may have failed to notice something useful! Happy holidays! On Mon, Dec 23, 2019 at 3:28 AM David Warring wrote: > Hi Fernando, > I'm still in the habit of using LibraryMake. E.g. for > https://github.com/p6-xml/LibXML-raku released in this last few months. > Regards, > David > > On Sun, Dec 22, 2019 at 7:47 AM Fernando Santagata < > nando.santag...@gmail.com> wrote: > >> Hello, >> >> What can I use to help building native code for a Raku module? >> Is LibraryMake still the preferred method or there's something else to use >> nowadays? >> >> Thanks! >> >> -- >> Fernando Santagata >> > -- Fernando Santagata
Re: Is LibraryMake still current?
Hi Fernando, I'm still in the habit of using LibraryMake. E.g. for https://github.com/p6-xml/LibXML-raku released in this last few months. Regards, David On Sun, Dec 22, 2019 at 7:47 AM Fernando Santagata < nando.santag...@gmail.com> wrote: > Hello, > > What can I use to help building native code for a Raku module? > Is LibraryMake still the preferred method or there's something else to use > nowadays? > > Thanks! > > -- > Fernando Santagata >
Is LibraryMake still current?
Hello, What can I use to help building native code for a Raku module? Is LibraryMake still the preferred method or there's something else to use nowadays? Thanks! -- Fernando Santagata
