All files included in a wrapped application must be referred to by their full path within the application. However, any relative or full path specification can be used on the freeWrap command line.
Windows users will notice that freeWrap strips all drive letter information from a file's path prior to storing it inside the wrapped application. When referenced inside the wrapped program, the path to the wrapped files must have no drive letter. To the wrapped application, all of its internal files will appear to be on the same "default" drive.
For example, if an application is wrapped to include the file C:\projects\myproject\libmodule1.tcl with the following command:
freewrap myapp.tcl libmodule1.tcl
You would need to use a source command within the application such as:
source /projects/myproject/libmodule1.tcl
DO NOT expect the relative path of wrapped files to change when you move the executable program.
FreeWrap takes a "snapshot" of the file path for all wrapped files. You must use the same, full path (minus any drive letter) that existed at the time of wrapping to refer to the wrapped file. It is also important that the file paths you use in your program exactly match the letter case that exists at the time of wrapping.
These rules also apply to the file or open commands. Also, make sure the path you add to auto_path corresponds to the wrapped tclIndex file you include in your application. For example, if your wrapping command is:
freewrap myapp.tcl c:\devel\myapp1\tclIndex c:\devel\myapp1\libmodule1.tcl
you should add /devel/myapp1 to auto_path.
In summary:
You should use the paths to the files as they exist at the time of wrapping. Wrapping takes a "snapshot" of the file path for all wrapped files. Do not use relative paths to refer to wrapped files within the application since relative paths will not be found.
Send comments to freewrapmgr@users.sourceforge.net