Freewrap question -- how to handle dll's
- From: Kevin Walzer <sw@xxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 05 Jan 2006 02:56:41 -0500
I'm adding Windows as a supported platform for an app I'm developing,
and can't use standard starkit/starpack as a deployment approach because
I'm using BLT on Windows, which doesn't support stubs. After
researching different alternatives, freewrap looks like the best
solution because of its support for BLT and also because its icons can
be easily customized.
Freewrap's recommended approach for handling binary extensions--copy a
bunch of dll's to a temp directory and then load them--seems a bit
messy, however. I'm wondering if this approach would work:
1. Use my installer to place my binary extensions in a fixed location
(say in the app's directory).
2. Add the app directory to the auto_path variable like so:
lappend auto_path \C:\myappdirectory
3. Then, simply do "package require foo" as normal.
It's #3 that I'm not clear on: will this work from inside a wrapped
file, i.e. will my freewrapped app see these packages? This approach is
preferable to me because it reduces the amount of Windows-specific code
I have to write, and is less complicated. The freewrap documents
aren't clear on how feasible this approach is.
Thanks for any advice.
--
Cheers,
Kevin Walzer, PhD
WordTech Software - "Tame the Terminal"
http://www.wordtech-software.com
sw at wordtech-software.com
.
- Follow-Ups:
- Re: Freewrap question -- how to handle dll's
- From: Roy Terry
- Re: Freewrap question -- how to handle dll's
- From: slebetman@xxxxxxxxx
- Re: Freewrap question -- how to handle dll's
- Prev by Date: Re: getting rid of '{}'
- Next by Date: Re: Problem with UNIX return code
- Previous by thread: tk widget
- Next by thread: Re: Freewrap question -- how to handle dll's
- Index(es):
Relevant Pages
|
