macOS: The installation package is a file of the form SquishCocoSetup_ x.y.z_.Note that the CentOS version of the installer is also valid for RedHat Linux™. run and must be executed with bash, as in Linux™: The installer is a file SquishCocoSetup_ _.Microsoft ® Windows: The installer is a file SquishCocoSetup_ _Windows_x86.exe or SquishCocoSetup_ _Windows_圆4.exe and must be executed.In the noncommercial version, SquishCoco is replaced by SquishCocoNoncommercial. , where is the program version, describes the operating system and other details of the installation, and is an operating system specific suffix. The installers for the various platforms supported by Coco have a common naming scheme, but the way they must be executed differs. InstallationĪn installer for Coco can be downloaded via. The license server itself is not counted among the processes that need a license. froglogic will provide a license file which determines the maximal number of Coco processes that can be active at the same time. The server must be running on a machine that is reachable from the machine on which Coco runs. Builds with several compilations in parallel should however cause no real problem since a process that cannot get a license will wait until one is freed.įloating licenses are managed by a license server. each instance of the command line tools, cmmerge, cmcsexeimport and cmreportĮvery compiler call that is instrumented by Coco is counted separately because it requires one instance of the CoverageScanner to run.an instance of CoverageScanner or of the compiler wrappers.One needs as many floating licenses as there are Coco processes running at the same time.
Note that if you run Coco from a Continuous Integration Server, the server has a separate account, and therefore Coco needs an additional node-locked license.įloating licenses are bound to processes, not to computers.
On that account, you can run as many Coco processes as you like. There are two kinds of licenses, node-locked and floating licenses.Ī node-locked license is bound to a specific machine and a specific user account. This chapter describes the installation and setup of Coco on your machine and a later update of software and licenses.
0 kommentar(er)
