How to change "Applications" subfolder for "productbuild"

jpfeuffer · November 17, 2022, 5:08pm

Hi!

Is it possible to change the subfolder where components get installed to
with the productbuild CPack generator?
It always installs everything in “Applications”. I would like to at least bundle everything under “Applications/MySoftwareBundle” and store all my .apps there.
In a next step I maybe want to install some Preferences in the Preferences folder.
How do I do that?

Thanks!
J

ben.boeckel · November 17, 2022, 6:35pm

I don’t know about ProductBuild, but the DragNDrop generator supported putting / in “application bundle names” to achieve this.

jpfeuffer · November 18, 2022, 9:49am

Thanks!
I found in the source code how to set an overall package prefix. The docs unfortunately do not mention any usage on macOS.

github.com

Kitware/CMake/blob/c5a945dce8e1a4fb1b1db91c2dae03795c74074b/Source/CPack/cmCPackProductBuildGenerator.cxx#L121


      
                   << (keychainPath.empty() ? ""
                                            : " --keychain \"" + keychainPath + "\"")
                   << " \"" << packageFileNames[0] << "\"";
          
          
  // Run ProductBuild
            return RunProductBuild(pkgCmd.str());
          }
          
          
int cmCPackProductBuildGenerator::InitializeInternal()
          {
            this->SetOptionIfNotSet("CPACK_PACKAGING_INSTALL_PREFIX", "/Applications");
          
          
  std::vector<std::string> no_paths;
            std::string program =
              cmSystemTools::FindProgram("pkgbuild", no_paths, false);
            if (program.empty()) {
              cmCPackLogger(cmCPackLog::LOG_ERROR,
                            "Cannot find pkgbuild executable" << std::endl);
              return 0;
            }
            this->SetOptionIfNotSet("CPACK_COMMAND_PKGBUILD", program);

But since the install-location for each component is hardcoded,
you probably won’t be able to install different locations easily

github.com

Kitware/CMake/blob/c5a945dce8e1a4fb1b1db91c2dae03795c74074b/Source/CPack/cmCPackProductBuildGenerator.cxx#L239


      
          }
          std::string keychainPath;
          if (cmValue p = this->GetOption("CPACK_PKGBUILD_KEYCHAIN_PATH")) {
            keychainPath = p;
          }
          
          
pkgCmd << pkgbuild << " --root \"" << packageDir << "\""
                 << " --identifier \"" << pkgId << "\""
                 << " --scripts \"" << scriptDir << "\""
                 << " --version \"" << version << "\""
                 << " --install-location \"/\""
                 << (identityName.empty() ? "" : " --sign \"" + identityName + "\"")
                 << (keychainPath.empty() ? ""
                                          : " --keychain \"" + keychainPath + "\"")
                 << " \"" << packageFile << "\"";
          
          
if (component && !component->Plist.empty()) {
            pkgCmd << " --component-plist \"" << component->Plist << "\"";
          }
          
          
// Run ProductBuild

I assume changing the prefix in-between install or cpack_component commands will not work.

craig.scott · November 18, 2022, 11:52pm

CPACK_PACKAGING_INSTALL_PREFIX is a general setting that is documented as applying to all CPack generators. I don’t know if the productbuild generator has any special handling or caveats around that though.