This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Problem with setup prerequisite dependency .prq file locations
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jun 07, 2007
05:55 AM
Problem with setup prerequisite dependency .prq file locations
I am encountering a problem with the locations of .prq files when setting dependencies. I use a version control system (perforce) and would like to check in the .prq’s in such a way that if the source is fetched from perforce it can be built on any build machine using our build process and the standalone system and/or using IS if that is available.
I have created some custom prerequisites and they have dependencies, if I edit the prerequisites using the prerequisite editor it incorrectly sets the path to the .prq to be ISProductFolder\SetupPrerequisites which causes builds to fail. If I manually edit the .prq to point to the correct location for the dependency this fixes the problem.
Although I have a workaround its likely that others will also encounter this problem so I felt it was worth posting about the problem and also raising the question of if there is likely to be a fix.
I have created some custom prerequisites and they have dependencies, if I edit the prerequisites using the prerequisite editor it incorrectly sets the path to the .prq to be ISProductFolder\SetupPrerequisites which causes builds to fail. If I manually edit the .prq to point to the correct location for the dependency this fixes the problem.
Although I have a workaround its likely that others will also encounter this problem so I felt it was worth posting about the problem and also raising the question of if there is likely to be a fix.
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jun 09, 2007
09:20 AM
I always go through and replace everything to be relative path'd so I can check it into the SCC system. Your right, ISProductFolder is bad since this creates a build time dependency thats not in your source system.