2016-09-07
| ||
14:16 | • Closed ticket [7bf1561836]: Adding Next Scripting Framework/Language (NSF/NX) build plugin plus 4 other changes artifact: 90b6860f41 user: rkeene | |
2015-08-20
| ||
14:00 | • Add attachment build.sh to ticket [7bf1561836] artifact: d8590b32f7 user: anonymous | |
13:59 | • Ticket [7bf1561836] Adding Next Scripting Framework/Language (NSF/NX) build plugin status still Open with 6 other changes artifact: f744088c16 user: anonymous | |
2015-05-02
| ||
19:58 | • New ticket [7bf1561836]. artifact: 39940a5dc8 user: anonymous | |
Ticket Hash: | 7bf15618362cef2a1d624bf4e29443466c728c56 | |||
Title: | Adding Next Scripting Framework/Language (NSF/NX) build plugin | |||
Status: | Closed | Type: | Feature Request | |
Severity: | Minor | Priority: | Immediate | |
Subsystem: | Tcl | Resolution: | Fixed | |
Last Modified: | 2016-09-07 14:16:12 | |||
Version Found In: | 0.9.2 | |||
Description: | ||||
Hi Roy! As briefly discussed on IRC, a couple of weeks ago, I kindly ask to add an "nsf" build plugin to your kitcreator build array. For some background on the Next Scripting Framework/Language (NSF/NX), which also comes with XOTcl 2, please see https://next-scripting.org/. Based on the build.sh examples available from the kitcreator fossil repo, I created an nsf/build.sh. (I could not attach a proper fossil patch to this ticket, therefore the pastebin drop). I tested it using some examples from README: export KITCREATOR_PKGS="nsf" ./kitcreator export KITCREATOR_PKGS="nsf" ./kitcreator --enable-64bit export KITCREATOR_PKGS="nsf kitdll" ./kitcreator export KITCREATOR_PKGS="nsf kitdll" ./kitcreator --enable-64bit (I used kitcreator 0.9.2) I do not know whether this is sufficient from your point of view? Can I run further tests? Besides, I was wondering: - 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?! - Is it possble to have build plugins (nsf) assemble an SCM checkout (git, fossil) rather than a tarball? All the best, Stefan | ||||
User Comments: | ||||
anonymous added on 2015-08-20 13:59:09:
I completed nsf/build.sh, including support for static builds and cross-compilation. Tested with all make-kit-* recipes (or variants thereof) in build/* subdir (each in static/dynamic settings), except for: make-kit-android-arm make-kit-hpux-hppa64 make-kit-solaris-* make-minkit (simply don't have access to suitable toolchains) The final build.sh is now attached to the ticket. Was also tested with trunk/tip kitcreator as of today. rkeene added on 2016-09-07 14:16:12: Applied |
Attachments:
- build.sh [download] added by anonymous on 2015-08-20 14:00:03. [details]