<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/source/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in Makefile</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>151bd3516b541823b16793460d73916e63d2b9c1 - flua: support our flua modules in the bootstrap flua</title>
        <link>http://kernelsources.org:8080/source/history/freebsd/libexec/flua/libfreebsd/kenv/Makefile#151bd3516b541823b16793460d73916e63d2b9c1</link>
        <description>flua: support our flua modules in the bootstrap fluaThis version builds every module into the flua binary itself, since allof the bootstrap tools are built -DNO_SHARED.  As a result, we alsocannot dlsym(), so we can&apos;t really discover the names of our newlybuiltin modules.  Instead, just build out a linker set with all of ourluaopen_*() functions to register everything up-front.Building in all of the modules isn&apos;t strictly necessary, but it meansthat we have an example of how to add a bootstrap module everywhere yougo and one doesn&apos;t need to consider whether bootstrap flua can use amodule when writing scripts.  On my build machine, the consequence onour binary size is an increase from around 1.6M -&gt; 1.9M, which isn&apos;treally that bad..lua modules can install into their usual path below $WORLDTMP/legacyand we&apos;ll pick them up automagically by way of the ctor that sets upLUA_PATH early on.This re-lands bootstrap module support with a more sensible subset, andafter having verified that it cross-builds fine on macOS and Linux -- wecannot do libfreebsd on !FreeBSD because it&apos;s more system headerdependant.  We also need to bootstrap libmd to bring in libhash, andlibucl + libyaml.Reviewed by:	bapt, emaste (both previous version)Differential Revision:	https://reviews.freebsd.org/D51890

            List of files:
            /freebsd/libexec/flua/libfreebsd/kenv/Makefile</description>
        <pubDate>Sat, 04 Oct 2025 04:16:51 +0200</pubDate>
        <dc:creator>Kyle Evans &lt;kevans@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>bbef1c72b4873b657fdb0466b48b15d1d4f0a731 - Revert &quot;flua: support our flua modules in the bootstrap flua&quot;</title>
        <link>http://kernelsources.org:8080/source/history/freebsd/libexec/flua/libfreebsd/kenv/Makefile#bbef1c72b4873b657fdb0466b48b15d1d4f0a731</link>
        <description>Revert &quot;flua: support our flua modules in the bootstrap flua&quot;This reverts commit 1953a12ee2cde1afacb3e3f7612d89695c96e04f, because itcannot work at all on macOS without more work, at a minimum.  We uselinker sets for module discovery, but we don&apos;t have a version of thisthat works for mach-o at the moment.

            List of files:
            /freebsd/libexec/flua/libfreebsd/kenv/Makefile</description>
        <pubDate>Sat, 04 Oct 2025 02:52:36 +0200</pubDate>
        <dc:creator>Kyle Evans &lt;kevans@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>1953a12ee2cde1afacb3e3f7612d89695c96e04f - flua: support our flua modules in the bootstrap flua</title>
        <link>http://kernelsources.org:8080/source/history/freebsd/libexec/flua/libfreebsd/kenv/Makefile#1953a12ee2cde1afacb3e3f7612d89695c96e04f</link>
        <description>flua: support our flua modules in the bootstrap fluaThis version builds every module into the flua binary itself, since allof the bootstrap tools are built -DNO_SHARED.  As a result, we alsocannot dlsym(), so we can&apos;t really discover the names of our newlybuiltin modules.  Instead, just build out a linker set with all of ourluaopen_*() functions to register everything up-front.Building in all of the modules isn&apos;t strictly necessary, but it meansthat we have an example of how to add a bootstrap module everywhere yougo and one doesn&apos;t need to consider whether bootstrap flua can use amodule when writing scripts.  On my build machine, the consequence onour binary size is an increase from around 1.6M -&gt; 1.9M, which isn&apos;treally that bad..lua modules can install into their usual path below $WORLDTMP/legacyand we&apos;ll pick them up automagically by way of the ctor that sets upLUA_PATH early on.Reviewed by:	bapt, emasteDifferential Revision:	https://reviews.freebsd.org/D51890

            List of files:
            /freebsd/libexec/flua/libfreebsd/kenv/Makefile</description>
        <pubDate>Fri, 03 Oct 2025 20:09:03 +0200</pubDate>
        <dc:creator>Kyle Evans &lt;kevans@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>696922fbfa3e1c400701a3a39dcadf7dee12b06c - flua: add freebsd.kenv, kenv(2) bindings</title>
        <link>http://kernelsources.org:8080/source/history/freebsd/libexec/flua/libfreebsd/kenv/Makefile#696922fbfa3e1c400701a3a39dcadf7dee12b06c</link>
        <description>flua: add freebsd.kenv, kenv(2) bindingsAdd bindings for kenv(2) right now only get() has been createdit allows do dump into a key/value table the kernel environement ifno argument is passed, or it returns the value associated to theprovided key.Reviewed by:	imp, kevans, markjAccepted by:	imp, kevansDifferential Revision:	https://reviews.freebsd.org/D46654

            List of files:
            /freebsd/libexec/flua/libfreebsd/kenv/Makefile</description>
        <pubDate>Thu, 12 Sep 2024 14:42:01 +0200</pubDate>
        <dc:creator>Baptiste Daroussin &lt;bapt@FreeBSD.org&gt;</dc:creator>
    </item>
</channel>
</rss>
