Re: [Cava Packager] desktop shortcut make it start in the bin folder after install with installer file, but i chose to put the exe file in the top level folder.

[Jeffrey Ray]

Change your settings in Cava Packager so that the executable is packaged in the root application directory instead of in the bin sub directory.

In cava packager under "Executables", select the executable you want to edit. In the right hand editor pane, find the "Executable Location" option. Check the box that says "Place executable in root of distribution (not bin folder)."

On Fri, Nov 9, 2012 at 6:29 PM, xy <gage....@gmail.com> wrote:

thouhg i can change to remove /bin, but hope it install automatically pointing to the correct place. in the desktop and menu setup for the installer configuration, i put ..\file.exe to be able to start the program when the desktop shortcut is clicked, but it didn't run correctly because it didn't find the sub folder under /bin because the program started in the /bin folder.

--
You received this message because you are subscribed to the Google Groups "Cava Packager" group.
To view this discussion on the web visit https://groups.google.com/d/msg/cava-packager/-/Hn-45HYTZ7YJ.
To post to this group, send email to cava-p...@googlegroups.com.
To unsubscribe from this group, send email to cava-package...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/cava-packager?hl=en.

[xy]

Hi, Jeffery,

Thanks for the information. That's exactly what I did, i.e. check the box saying place executable on top level (i.e. root but not in bin). it did produce the executable in the root. It's exactly because of this, when I produced an installer file and ran it in another computer. The MSI installer did install it, but the desktop shortcut points to the bin folder instead of the root where my executable is located.

 

When configuring the installer, I had to put ..\ before my executable file so that the short cut will find the executable file to open it.

 

The problem is: the shortcut considers itself running in the bin folder and any path I had in my executable is not working. Sounds a bit wierd becaus, but that's what is happening.

Gage