Home > Archive > Tcl > September 2006 > Wrapping Tcl into Mac OS X executibles?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Wrapping Tcl into Mac OS X executibles?
|
|
|
| Hi guys.
Well, I have three apps coming up to a v1.0 release soon and I'd
like to release to the main platforms simultaneously. ActiveState's
TclApp does me fine for creating stand-alone executibles for Windows
and Linux. But Mac's the missing link.
As mine are commercial apps, the ability to 'compile' the Tcl code to
limit code snooping is essential for me. What are people currently
using to convert their Tcl apps into Mac executibles?
Cheers.
| |
| Kevin Walzer 2006-08-17, 8:01 am |
| Synic wrote:
> Hi guys.
>
> Well, I have three apps coming up to a v1.0 release soon and I'd
> like to release to the main platforms simultaneously. ActiveState's
> TclApp does me fine for creating stand-alone executibles for Windows
> and Linux. But Mac's the missing link.
>
> As mine are commercial apps, the ability to 'compile' the Tcl code to
> limit code snooping is essential for me. What are people currently
> using to convert their Tcl apps into Mac executibles?
>
> Cheers.
>
I wrap mine in a starpack and then put the whole thing in an application
bundle. Or you can just organize the scripts into the application bundle
itself. Mac OS X 10.4 comes with Tcl/Tk installed and includes tbcload,
so you can even obfuscate your code.
See http://tk-components.sourceforge.ne...rial/index.html
for details.
--
Kevin Walzer
Poetic Code
http://www.kevin-walzer.com
| |
| Cameron Laird 2006-08-18, 7:02 pm |
| In article <44E45991.1010107@kevin-walzer.com>,
Kevin Walzer <kw@kevin-walzer.com> wrote:
>Synic wrote:
>I wrap mine in a starpack and then put the whole thing in an application
>bundle. Or you can just organize the scripts into the application bundle
>itself. Mac OS X 10.4 comes with Tcl/Tk installed and includes tbcload,
>so you can even obfuscate your code.
>
>See http://tk-components.sourceforge.ne...rial/index.html
>for details.
| |
| Robert Hicks 2006-08-18, 7:02 pm |
|
Cameron Laird wrote:
> In article <44E45991.1010107@kevin-walzer.com>,
> Kevin Walzer <kw@kevin-walzer.com> wrote:
> .
> .
> .
> OR you can wait a very few w s for the Mac OS release of TclApp,
> which my sources tell me is due out any time. You might do well
> to contact ActiveState to learn the latest on its availability.
I have been sooo waiting for that!!!
:Robert
| |
| Kevin Walzer 2006-08-18, 7:02 pm |
| Cameron Laird wrote:
> In article <44E45991.1010107@kevin-walzer.com>,
> Kevin Walzer <kw@kevin-walzer.com> wrote:
| |
|
| Cameron Laird <claird@lairds.us> wrote:
> OR you can wait a very few ws for the Mac OS release of TclApp,
> which my sources tell me is due out any time. You might do well
> to contact ActiveState to learn the latest on its availability.
Huzzah! Excellent news indeed :-).
FWIW, the alternatives I ended up looking at were:
freeWrap: http://freewrap.sourceforge.net/
freeWrap for OS X: http://www.nscl.msu.edu/~bazin/freewrap/
Daniel Bazin's compiled freeWrap for PPC and Intel platorms.
(Of course, the freeWrap developers recommend against using precompiled
binaries for code obfuscation, as others may be able to load/view your
code with a common key, so you'd compile your own before releasing any
apps with it...)
| |
|
| Kevin Walzer <kw@kevin-walzer.com> wrote:
> Interesting news indeed. Can anyone speak to their experience using
> TclApp/Tcl Dev Kit on another platform, especially with Komodo integration?
I use TclApp/Tcl Dev Kit on MS Windows and Linux, though I don't really
use Komodo. On the whole, it works very well on both platforms.
| |
| Gerald W. Lester 2006-08-19, 7:01 pm |
| Synic wrote:
> Hi guys.
>
> Well, I have three apps coming up to a v1.0 release soon and I'd
> like to release to the main platforms simultaneously. ActiveState's
> TclApp does me fine for creating stand-alone executibles for Windows
> and Linux. But Mac's the missing link.
>
> As mine are commercial apps, the ability to 'compile' the Tcl code to
> limit code snooping is essential for me. What are people currently
> using to convert their Tcl apps into Mac executibles?
Compiling Tcl code and creating a single executable are two separate and
distinct things.
I'd recommend compiling the code using ActiveState's TclCompiler -- the .tbc
that is produced is platform independent.
Then for the Mac, create a StarPack -- this is basically what TclApp does.
Creating an executable (via StarPack, TclApp or FreeWrap) without the
compilation step does not really protect your code.
--
+--------------------------------+---------------------------------------+
| Gerald W. Lester |
|"The man who fights for his ideals is the man who is alive." - Cervantes|
+------------------------------------------------------------------------+
| |
|
| Cameron Laird <claird@lairds.us> wrote:
> OR you can wait a very few ws for the Mac OS release of TclApp,
> which my sources tell me is due out any time. You might do well
> to contact ActiveState to learn the latest on its availability.
After a couple of emails to ActiveState, the word I got back is:
1. TDK for Mac is not currently being actively worked upon.
2. TDK for Mac is "planned" and at a vague guess might be "5-6 months"
away (but then, it's the same sort of response I got when I last
emailed about TDK for Mac back in Aug 2005). So, 2007 at the very
earliest. Maybe. Perhaps.
It would have been extremely useful if things had turned out and it
was "generally available in time for the 13th Annual Tcl/Tk Conference
this fall, if not before" but it seems it's not to be. Good review on
TDK on Unixreview.com, Cameron :-). TDK is indeed a good product on the
platforms supported.
Cheers also to Jeff Hobbs (who I imagine gave the AS support dept
a gentle nudge to look around for any lost emails on the subject).
| |
| Robert Hicks 2006-09-06, 8:01 am |
|
Synic wrote:
> Cameron Laird <claird@lairds.us> wrote:
>
> After a couple of emails to ActiveState, the word I got back is:
>
> 1. TDK for Mac is not currently being actively worked upon.
>
> 2. TDK for Mac is "planned" and at a vague guess might be "5-6 months"
> away (but then, it's the same sort of response I got when I last
> emailed about TDK for Mac back in Aug 2005). So, 2007 at the very
> earliest. Maybe. Perhaps.
>
Ok, now I am bummed out.
Robert
|
|
|
|
|