Ticket Change Details

Artifact ID: 39940a5dc8ec9b5c88d9dab703492dd3a2c2cf31
Ticket: 7bf15618362cef2a1d624bf4e29443466c728c56
Adding Next Scripting Framework/Language (NSF/NX) build plugin
User & Date: anonymous on 2015-05-02 19:58:11

  1. comment changed to:
    Hi Roy!<br /><br />As briefly discussed on IRC, a couple of weeks ago, I kindly ask to add an "nsf" build plugin to your kitcreator build array.<br /><br />For some background on the Next Scripting Framework/Language (NSF/NX), which also comes with XOTcl 2, please see <a href="https://next-scripting.org/">https://next-scripting.org/</a>.<br /><br />Based on the build.sh examples available from the kitcreator fossil repo, I created an <a href="http://pastebin.com/JhYXqS1h">nsf/build.sh</a>. (I could not attach a proper fossil patch to this ticket, therefore the pastebin drop).<br /><br />I tested it using some examples from README:<br /><br />export KITCREATOR_PKGS="nsf"<br />./kitcreator<br /><br />export KITCREATOR_PKGS="nsf"<br />./kitcreator --enable-64bit<br /><br />export KITCREATOR_PKGS="nsf kitdll"<br />./kitcreator<br /><br />export KITCREATOR_PKGS="nsf kitdll"<br />./kitcreator --enable-64bit<br /><br />(I used kitcreator 0.9.2)<br /><br />I do not know whether this is sufficient from your point of view? Can I run further tests?<br /><br />Besides, I was wondering:<br /><br />- Why and, if yes, how you should I provide for static-linking support? NSF is a fully TEA-compliant, so adding this is not a big deal (based on your tryopts examples), but I do not see how this would be used then in a kitcreator build?!<br /><br />- Is it possble to have build plugins (nsf) assemble an SCM checkout (git, fossil) rather than a tarball?<br /><br />All the best,<br />Stefan
  2. foundin changed to: "0.9.2"
  3. login: "anonymous"
  4. private_contact changed to: "d4d1d8192a46acf2c7d58cddc1040ecdbc9c9d77"
  5. severity changed to: "Minor"
  6. status changed to: "Open"
  7. title changed to:
    Adding Next Scripting Framework/Language (NSF/NX) build plugin
  8. type changed to: "Feature Request"