[CMake] [PackageMaker] Install location customization

[Domagoj Saric]

Hi,
Is there any way to:
 - disable the destination selection/customization altogether (both the 
"Change Install Location" option and the respective page and the "Choose 
Folder..." option one gets to if one clicks on "Change Install Location")
- disable the "Choose Folder..." option even though the "Change Install 
Location" still exists...i.e. to allow changing of the target drive but not 
the folder (hierarchy)
or
- (for non-monolithic/.mpkg packages) to allow full customization (both at 
CMake/CPack-time and at runtime/installation-time) of the target location(s) 
and folder hierarchy...i.e. to allow per component (independent) selection 
of the target folder (including disabling the customization for some 
components and allowing it for others)... This is what you get through the 
Choice/Destination, Choice/Allow alternate volume and 
Package/Configuration/Allow custom location options in the Apple's 
PackageMaker application...

To reiterate, I have an application which has two components, one of which 
must go strictly to a predesignated folder (the user must not be allowed to 
change it) and the other component's install location can (but does not 
necessarily need to be) changed... For this to work properly, CPack must, at 
the very minimum, allow disabling of the install location customization 
altogether or, better, allow 
proper/full/'uncluttered-with-typical-hardcoded-choices' customization...

I apologize if there is an obvious/documented way of doing this but I was 
unable to find it even after days of struggling with this issue...I even 
went searching for undocumented options/variables through the CPack 
binary...
set( CPACK_PACKAGE_RELOCATABLE ON ) did not help...

(using CMake 2.8.3)


ps. even though I set/use no installation type(s), the Installer 'sidebar' 
still shows "Installation type"...

pps. the 'application' in question is actually a VST plugin (similar to an 
AU component) for which CMake/CPack are additionally bugged by more/other 
hardcoded choices...for example a VST plugin is a bundle with a ."vst" 
extension making it impossible to use the install( TARGETS ... BUNDLE ) 
command because BUNDLE support is (AFAICT) hardcoded to use the ".app" 
extension...


-- 
"What Huxley teaches is that in the age of advanced technology, spiritual
devastation is more likely to come from an enemy with a smiling face than
from one whose countenance exudes suspicion and hate."
Neil Postman