-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cknieling/msi installer #197
base: develop
Are you sure you want to change the base?
Conversation
af6f19e
to
a41f235
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Solid work! We need to revisit the installation location, I don't think automated installation into a user $HOME/houdiniX.Y is the right way.
Please study https://www.sidefx.com/docs/houdini/ref/plugins.html how we can expand our package.json to install the files at a system wide location. The only unknown to me is currently where to put package.json so that Houdini finds it automatically without us having to fiddle with Houdini environment variables.
INSTALLER_HOUDINI_VERS.each { mv -> | ||
unstash(name: "houdini${mv.replaceAll('\\.', '_')}") | ||
def zipFile = cepl.findOneFile("*hdn${mv.replaceAll('\\.', '-')}*.zip") | ||
final String zipFileName = zipFile.name |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should check if the zipFile has been found or explict error with a message otherwise
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The call to findOneFile already throws an error if the file isn't found
Also avoid registry checking palladio versions, since we install for multiple patch/micro versions
Updated min cmake version
45943d4
to
c02026a
Compare
The Component Guid Generation Seed is a guid that must be used when a Component with the generate guid directive ("*") is not rooted in a standard Windows Installer directory (for example, ProgramFilesFolder or CommonFilesFolder). It is recommended that this attribute be avoided and that developers install their Components under standard directories with unique names instead (for example, "ProgramFilesFolder\Company Name Product Name Version"). It is important to note that once a directory is assigned a Component Guid Generation Seed the value must not change until (and must be changed when) the path to that directory, including itself and all parent directories, changes.