Activity for Dennis R. LaBelle
-
Dennis R. LaBelle modified ticket #63
It seems ::freewrap::unpack no longer supported
-
zlib in version 7 not present
-
The TCLmtls package will be included in the next freeWrap release (version 7.02). The TCLmtls package provides the same commands as the TLS package.
-
The freewrap::unpack procedure was intentionally removed as of freeWrap version 7,0. I decided that the procedure's functionality should be the responsibility of the developer's application. Especially in terms of any necessary error trapping. Here is the source code from versions prior to 7 .0. proc unpack {path {destdir {}}} { ;# Unpack a file from ZVFS into a native location. ;# ;# path = ZVFS path of file to unpack ;# destdir = optional destination directory for unpacked file. ;# ;# Returns:...
-
Dana, With my testing, I find that the zlib behavior is identical between Linux and Windows. Please remove the [package require zlib] statement from your application. Zlib is not a loadable module. Instead, it is statically linked (and already loaded) into freeWish. There is no need to use a package require command. You application appears to work fine once the package require statement is removed.
-
The zlib command is still present in freeWrap 7. What makes you think zlib is not available? Please provide a script example that displays the problem.
-
freeWrap 6.76 released
-
freeWrap 6.76 released
-
Recently, using a newer version of mingW and the MSYS2 environment I have encountered the same #define CR error. I have found no other solution than the one noted by MMtsuchi. zip.h:278:16: error: expected identifier or '(' before numeric constant 278 | #define CR 13 / '\r' on ASCII machines; must be 13 due to EBCDIC / | ^~
-
Compiled on Linux, can't load BWidget on Windows
-
TcL_AppendResult is used by most TCL commands. It returns the results of the command. FreeWrap simply could not start and run if it were not present. Please elaborate on exactly when the Undefined symbol is produced. I have tested freeWrap with a sample shared library under both Linux and Windows with no problems I suspect your problem may be related on how you compiled your shared library. Did you properly link it to the tclStubs library?
-
Screen resolution and rendering
-
I was unable to duplicate this problem.
-
I received the same error some years ago after which I modified the build instructions to prevent this error. I do not recall exactly what part of the build instructions where changed. However, the current instructions should work as written. I have recently used the instructions myself. Since you were finally successful in building freeWrap, could you share with us what you needed to do for a successful compilation? Was it simply following the procedure or does the procedure need to be clarified...
-
I received the same error some years ago after which I modified the build instructions to prevent this error. I do not recall exactly what part of the build instructions where changed. However, the current instructions should work as written. I have recently used the instructions myself. Since you were finally successful in building freeWrap, could you share with us what you needed to do for a successful compilation? What is simply following the procedure or does the procedure need to be clarified...
-
Screen resolution (Freewrap for Windows)
-
Unable to wrap txt files
-
You are, most likely, simply having a problem locating the files within the virtual file system created by the freeWrapped application. Please read the section of the freeWrap documentation entitled "Naming and referring to wrapped files"for information on how to access your wrapped files.
-
The icon file you provided contains only 3 of the 10 icons that it should. Please, please read the freeWrap 6.73 documentation on this subject. You MUST replace all 10 of the freeWrap icons with 10 of your own. The freeWrap documentation specifically states: " If your ICO file doesn't contain at least these versions of your icon then only the matching icons will be replaced. This would leave a freeWrap icon that could be displayed by Windows at some time."
-
First, the /H option of the MKLINK command creates a hard link, not a symbolic link. Under my test environment (Windows 10 Home) the icon displays correctly for both symbolic and hard links i create with MKLINK. I suspect something is going wrong with the way you are creating your icon file or wrapping your application.
-
Application Icon
-
Improve the manual regarding file paths
-
Additional details were added to the version 6.73 documentation.
-
This problem has been corrected with version 6.73.
-
I have been unable to duplicate this behavior. What version of Windows are you using?
-
Problem adding icon to freewrap app
-
Reduce the size of the output
-
Given today's disk storage capacities and speeds and network speeds the size of the freeWrap executables is not a significant concern.
-
How to freewrap snack package
-
FreeWrap with XOTcl
-
freewrap 6.70 Command line : full path are handled incorrectly
-
Fixed in version 6.72
-
Freewrap 670 icon wrapping with 256x256 - 24 bit
-
Fixed in version 6.73
-
Typo in the PDF manual
-
Fixed in versin 6.73
-
At run time, your application should use the ::zvfs::list command to determine exactly where the files are in the virtual directory structure. For example: set vPath_u1 [::zvfs::list */utils/u1.tcl]
-
Yes. The project is still active. I issue an update about once a year.
-
Documentation inaccuracy - runMode variable
-
This deficiency has been corrected in the freeWrap 6.70 documentation.
-
Syntax issue - shell_fileType_open command
-
This problem has been fixed in freeWrap 6.70.
-
slow startup - tktableinit P:
-
exe file version information
-
I would like to test your distribution files before including them for download....
-
The freewrap::makeZIP command can be used. The command supports the -A option and...
-
The freewrap::makeZIP command can be used. The command supports the -A option and...
-
Yes, to be safe, the freewrap_init.txt file would need to be updated. This isn't...
-
exe file version information
-
This is not surprising. FreeWrap is compiled without any embedded version information...
-
You need to use freeWrap's -w option when wrapping for another operating system....
-
Sorry for the delay. SourceForge did not send me a message to indicate that a posting...
-
freewrap 6.63 win64 has only tcllib1.15
-
freeWrap 6.63 has been release with tcllib1.16 for the win64 version.
-
This bug has been corrected with version 6.64 of freeWrap.
-
file mtime will deliver wrong mtime in zfvs
-
Add Expect package to win32/64 versions of Freewrap
-
Freewrapped application cannot run after modified by Microsoft's code signing tool
-
I will not be making any changes to freeWrap to support the MS code signing tool...
-
Wrapped script with BWidget fails to run
-
Version 6.63: Cannot wrap from a network drive
-
This problem occurred on a Windows XP vmware image, run in VMWare Fusion on MacOSs...
-
need to rebuild on Linux64 with older GLIBC
-
Add compression level option to freewrap command line
-
I installed Centos 5.11 (DVD ISOs of 5.7 don't seem to be available) and compiled...
-
It doesn't look like this works. When I tried this, the object modules required the...
-
This has been a known problem with BWidget (and documented here under the freeWrap...
-
I have included a possible fix to this problem in the new release of freeWrap (version...
-
I have included a possible fix to this problem in the new release of freeWrap (version...
-
Wrapping from Linux32 to Linux64
-
This bug has been fixed with freeWrap 6.63. Please download the new version.
-
This bug has been fixed with the release of freeWrap 6.63. Please download the new...
-
FreewrapTCLSH 661 on Windows: -w option for wrapping linux binaries expects ".exe"
-
This feature has been added to freeWrap as of version 6.63. Please download the new...
-
freeWrap 6.62 released
1
