This seems to match what I've seen in my so-far light experimentation. What's
the fix? Use wix XML patches?
I'm betting my money on the WiX train as this is what we use elsewhere in my
organization. Also I can live without the start menu items in the very worst
case.
cheers
Paul
On 13.
As a side note, remember that CPACK_PACKAGE_EXECUTABLES is problematic
in another way too; it requires listed executables to be installed to
PACKAGING_INSTALL_DIR/bin/.
On Fri, Feb 13, 2015 at 1:56 AM, Nils Gladitz nilsglad...@gmail.com wrote:
On 02/13/2015 07:52 AM, Paul Anton Letnes wrote:
I
On 13.02.2015 22:11, Iosif Neitzke wrote:
As a side note, remember that CPACK_PACKAGE_EXECUTABLES is problematic
in another way too; it requires listed executables to be installed to
PACKAGING_INSTALL_DIR/bin/.
As far as I know that is just with the NSIS generator and can be
mitigated with
Hi!
I have been unable to come across any documentation on how the WiX CPack
generator can create start menu items. I'll need to create items both for a few
PDFs (documentation) and for an executable or two. Is this supported, or do I
need to write my own XML patch file and give that to WiX?
On 02/13/2015 07:52 AM, Paul Anton Letnes wrote:
I have been unable to come across any documentation on how the WiX CPack
generator can create start menu items. I'll need to create items both
for a few PDFs (documentation) and for an executable or two. Is this
supported, or do I need to write my
