Freewrap Package Require Problem

Running Freewrap 6.0 (or Freewrapplus) on XP, package provide doesn't
seem to work, wherein it worked fine with older versions (at least up
to 5.2).
Basically, nothing I can do seems to allow package require/provide to
work.

Test example:

Using efftcl's venerable balloon package I create file "wrap.txt"
containing:

/balloon/aprint_balloon_help.tcl
/balloon/balloon.tcl
/balloon/getopt.tcl
/balloon/pkgindex.tcl
/balloon/tclIndex

I then create this script:

lappend auto_path /balloon
package require balloon
puts "Hello"

I wrap it with:

freewrapplus.exe c:/test.tcl -f C:/wrap.txt

Launching the resultant exe file on any system without a "real"
c:/balloon directory gives me:

"Error sourcing /test.tcl: can't find package balloon"


Is there now no way to use packages in Freewrap 6.0 without first
dumping it to a directory prior to using package require?

Any insight into this would be great.  I need my Freewrap!

-Daniel

as far as I know you need to put the full path in your system of the
library you want to add. so if ballon is in c: do "lappend auto_path
c:/balloon" it looks strange also for me but it works.

Nope, not on my system at least.  Using c:/balloon in the AutoPath
gives the exact same error.  Tried that, and every combination (with
and without driver letters)  in terms of specifying the packages in the
wrap.txt file.

So, you are saying with version 6.0 of Freewrap, you're able to
"package require" "wrapped" packages?  It always worked in the older
versions for me, but not now.  Actually, if I can just get absolute
confimation that it's working for others on Windows, then at least I
can assume it's something specific with my system, and not a bug...

BTW, I have noticed a definite bug with 6.0 regarding mkdir--if you do
it as an absolute path (ie file mkdir c:\test )  it won't work--have to
be in the parent folder, then do it as a relative directory (cd \ ;
file mkdir test).

-Daniel

I am not sure about freewrap version 6. I worked with many freewrap
versions and it all worked with full path in the extension.txt file
and lappend to auto_path for the package library in the script. for
binary extenstions things work a bit different but this is not your
case.