A '''Starpack''' is a special version of a [Starkit]. A Starpack combines a Starkit with a [Tclkit] runtime into a single file. Some people want only to know "[How to create my first Starpack]". Starpacks are standalone executables which run out of the box, making them even easier to distribute and use than Starkits. This convenience does introduce a number of trade-offs: * Starpacks only work on the platform for which they have been built * Starpacks cannot modify themselves * Starpacks must be updated as a whole, and are (much) larger than most Starkits Note that Starpacks use the same packaging mechanism as Starkits, their content can be listed and extracted with the [SDX] utility. The main difference is that the "header" is a large executable file, and that the files stored inside include all the standard Tcl/Tk runtime support files. Instructions on how to create a starpack are at [http://www.equi4.com/208] ---- [AEC], 7/22/2002: I have a tcl/tk edit application which opens a file which may be passed in on the command line (i.e. app.exe somefile.tcl). The file is opened by the app and not sourced. When I create a starpack with my app, it tries to source the file on the command line and fails. Is there a way to change this behavior of the starpack? [LV] writes: AEC, at the Starkit page there is a pointer to a mailing list where starkit developers discuss issues - you might want to report your problem there. [AEC]: Thanks. I'll look into that. ''This bug should be gone in Tclkit 8.4.x, i.e. Sept 2002 or later.'' ---- Also, from the [Tcl chatroom]: [stevel]: To wrap a script into a Starkit .... sdx qwrap myscript.tcl this gives you myscript.kit - which can be run with Tclkit. To unwrap ... sdx unwrap myscript.kit this gives you a "virtual filesystem" directory structure unpacked into myscript.vfs. To wrap back into a Starpack (i.e. application + Tclkit) then use sdx wrap myscript.kit -runtime /path/to/tclkit where /path/to/tclkit is the Tclkit for your target plaform ...One caveat, the Tclkit can't be the one you are running sdx with - just make a copy ... but you can generate for platforms other than the one you are running on. Well, except for MacOS - where the binary needs a resource fork for some reason, and that can't be generated except on a Mac... ---- [LV] from the [starkit] mailing list, [jcw] says: You're going to have to create starpacks on the Mac. Reason: mac files have a "data fork" and a "resource fork". The .bin files are an exchange format which ties them together (along with a bit of "finder info"). Catenating anything a the end probably will simply be ignored on unpack - which is what happens once you take it to the mac and unpack through StuffIt Expander or some such (Mac browsers tend to do that automatically, right after download). If you do it on the Mac, while the forks are distinct, sdx will concatenate after the data fork. Then you can run it through StuffIt to create the transferable .bin version. Running SDX on the Mac takes some trickery, since SDX is command-line driven, and the Mac has only tclkit: 1. Launch tclkit 2. In its console, type: set argv [list wrap myapp -prefix mytclkit] source sdx.kit 3. The sdx starkit will perform its work (and exit, I think) ---- Note that not all the useful info on [starkit]s, starpacks, etc. is here on this web site. For instance, an article titled ''Custom icons for win32 starpacks'' can be found here [http://www.equi4.com/267] . ---- [Custom Icons For Win32 Starpacks - The Real Story] The info given in the Equi4.com article mentioned above is DODGY! I can't correct that page itself, because it's not on the Wiki, and not editable. So click [Custom Icons For Win32 Starpacks - The Real Story] if you want to know a method of putting custom icons in a Starpack that actually works. ---- [[ [Category Application] | ]]