When you hit the Configure button, you must:. Once the configuration process is done, tick Advanced and Grouped in cmake-gui. You will see entries for where header files and libraries are taken from. Some CGAL packages also have additional dependencies. For example, during the configuration process above, you may have observed the following message:. CGAL is a library of algorithms and data structures and as such does not depend on Qt. If you already have Qt installed, you can simply fill in the requested CMake variables and paths.
Otherwise, you can also install it using vcpkg :. Remember to specify --triplet or the related environment variable in case you target bit applications.
As Qt5 is modular and as the CGAL examples and demos use only some of these modules you can save download and compilation time by specifying an installation option :. In both cases, when you start cmake-gui again and hit the Configure button, the CMake variables and paths concerning Qt should now be filled.
Note that not all optional dependencies are available through the Vcpkg library manager. In this case, you must download and install them independently see page Essential and Optional Third Party Dependencies for information on support versions and download links as well as fill the missing information within the CMake interface until configuration is successful no more red lines indicating missing dependencies. The command tells the compiler to attempt a license check-out.
The error message gives much useful information. The license path is where the tools are looking for licenses. Note It is possible that there is more than one reason the tools are unable to connect to the server. The error message from the tools will only give the first error. So once you have resolved this issue, you should re-run the command to check for further errors! Note This test uses armcc to check-out a license. It may be that this check-out succeeds, but the check-out for other tools fail.
If this is the case for you, run the tool that is failing and see what error code it reports. The codes are common across Arm development tools. You should confirm, using Task Manager on Windows or the ps command on Linux. If the processes are listed, these may be stale processes left over from a crash. Usually you will have to manually kill these stale processes before attempting to re-start the server software.
BEWARE - it is possible to run multiple lmgrd servers but not armlmd on the same physical machine - refer to here. Once you have killed any stale processes try manually re-starting the lmgrd software. The command is as follows:. The -z flag causes the server to print all log and diagnostic information to the console. This is not usually desirable, but useful for troubleshooting. If the server appears to have started correctly, re-run "lmutil lmstat -a" to check that you are able to query it successfully.
If this also succeeds, then monitor the server as the problem may come during operation rather than start up. Otherwise, you will see an error message at some point after the notice. How far through the start up sequence it got before the error gives an indication of where the issue lies. Below are common messages to see in the output:. If all the seats are in use, further requests will not be satisfied. Normally, the server will queue a request until a seat becomes available - so that the client does not see a failure.
On the client you would see something like this:. There are cases where this queuing mechanism fails, and this is when you would see this error message on the client. It means that the something is interfering with the communication between the server and client.
However, the tools were unable to open a connection to a FLEX license server on the specified port. Possible causes include:. The FLEX server software lmgrd has not been started. If " lmutil lmstat -a " succeeded on the server then the server software is be running.
Check the port listed in the server's lmutil output, does it match the setting on the client? A firewall is blocking the connection.
It is possible that something is blocking communication, typically a firewall. However, the server does not host the feature that the client was trying to check-out. This can happen for a number of reasons. The Professional edition includes additional features. If you were to try using the Professional edition with a Standard license, you could see this error.
Another explanation could be that you have multiple license servers. For example, one server for Arm licenses and another third party licenses. In which case this could indicate that you are specifying the wrong server on the search path. Note Remember that you can specify multiple license sources on the search path! The server hosts the feature that was requested - but not the correct version. This usually indicates that you are trying to use an older license with a more recent tool.
For example, using the RVDS 4. Note You may see this message in license server logs, even when the check-out succeeded. This is due how the server operates internally when it hosts a mix of licenses, and can be ignored. This is done using an options file. For more information on option files, please see the following FAQ: ' Can I reserve floating licenses for specific users? Arm's tool licenses do not support the FLEX borrow feature.
Attempting to user borrow will result in this error. It shows that the OS failed to translate the hostname into an IP address. Check that the correct name is being specified, and that your network's name resolution is working correctly. If these are correct, try using the " ping " command to check that the client can see the server on the network.
Check on the server which port is being used by the daemon and that it is open on the server's firewall. By default, the armlmd port number is not specified. It is assigned by the host operating system at server start. If the server has a firewall it is advisable to set the port manually. In the license file change:. This usually indicates that armlmd has crashed.
Check the server's debug log, you should see a message indicating that lmgrd lost its connection to armlmd. Shut down lmgrd , and check that there are no stale lmgrd or armlmd processes. Then re-start lmgrd. Normally this will not happen, however there are cases where it can.
This could be because it has been edited, or accidentally commented out. Try re-downloading the license file from Arm's website. Alternatively, you may be passing a node-locked license file, which can not be hosted in this way.
It has tried to launch the Arm vendor daemon armlmd , but was unable to locate the executable. Check the location of armlmd armlmd. Alternatively you can specify the location in the license file. The file from Arm will have this line:. This is usually caused by having a lmgrd process already running, for example a stale process. Alternatively, if lmgrd has previously crashed the OS may not yet had released the port.
The hostid in the license file does not match the machine. You will need to rehost the license to use this machine. The license file has been edited. Only a few sections of the license file can be edited, editing any other section will result in this error. Re-download the license file from the Arm web licensing portal. If all the features in the license file have expired the server will fail to start.
You can run multiple FLEXnet license servers on the same machine - if they are for different vendors' licenses. However, only one instance of armlmd the Arm vendor daemon can be running on the machine. If armlmd is already running when the server software starts it fail with this error:. There are two common causes of this error. You be trying to run two instances of the license server on the same machine - both hosting Arm licenses.
This is not supported. You will need to merge the license files, and host them from a single instance of the server software. Merging license file is covered here. Alternatively, if lmgrd has previously exited uncleanly it is possible that armlmd did not close down.
You should check for stale instances of armlmd , and terminate them. On Linux this can be done with the " ps -ax grep armlmd " command. On Windows you can use Task Manager. It is usually caused when the server is passed a node-locked license. This configuration is not supported, and leads to this error message. The message is only seen at the point a client attempts to use the license, not when the license it initially parsed.
You confirm whether this is the cause by running "lmutil lmstat -a" on the either the server or a client. If a node-locked license is present on the server, the lmstat output will include one or more lines similar to this:.
The armlmd daemon requires libraries from Microsoft Visual Studio, if they are not present this error is seen. Passing the wrong file to lmgrd.
Check the command used to start the server, and verify the file path. Passing a node-locked license to lmgrd. This is not supported, only license files containing floating licenses should be passed to lmgrd. The aim of this guide is to make it easier for you to diagnose and solve node-locked licensing problems with the Arm tools.
We first need to identify what is going wrong. To do this open a command prompt window and execute the command armcc --vsn or armclang --vsn. Depending upon the version, the output of this command should look something like this:. The error message gives a lot of information, but initially we are interested in the Error and FlexNet Licensing error fields.
Between them these two fields give the type of failure. Another useful field is the License path , as this tells you where the tools are looking for a license file. This command may complete successfully, depending upon what is the cause of your problem. In this case you need to record the error message next time you see it. Flex error Cannot find license file Flex error No such feature exists Flex error Invalid inconsistent license key Flex error Invalid host.
The hostid of this system does not match the hostid specified in the license file. If the error code you are seeing does not match any of those listed above, or the you have not been able to resolve your issue, contact Arm License Support for further assistance. The e-mail address is license. Which tools you are trying to run, for example Arm Compiler 5. For users of RVDS 2. For users of other tool suites, please download the client diagnostic script from the Licensing Problem Diagnostic Scripts page.
Run it on your machine and include its output with your e-mail. Flex error Cannot find license file This means that the tools are unable to find a license file. This is normally because you have not yet installed a license file, or the license file has been moved since installation.
Flex error No such feature exists This error means that a license file was found, but did not contain a license valid or invalid for the feature you are trying to use. Typically this will be caused by:. Trying to use a feature which is an optional add-on for which you do not have a license For example multi-core debug support in RVD was an optional add-on in RVDS 2.
Trying to connect to more than one target simultaneously would lead this error message being reported. Corrupted license file It is possible that part of your license file has been deleted. Flex error Invalid inconsistent license key This error message indicates that you have a corrupted license file.
This could be accidental, or because you have tried to edit the license file. Only the comment sections of Arm tools licenses can be edited those lines starting with a character.
You can not not edit any other part of the file without it becoming invalid. To fix, download a fresh copy of the license file from your account on the Arm web licensing portal and then follow the instructions in: ' How do I install my node locked license? Flex error Invalid host. This error message occurs when the host ID the license has been locked does not match that of the system.
Arm tools licenses are locked to a specific machine using a hostid. For node-locked licenses the hostid can be the disk serial number of the C drive, or the MAC address of an Ethernet adapter. The hostid in the license file must be visible on on your system at all times, otherwise the tools will not work. To correct this, you will need to rehost the license to the correct hostid.
Flex error Feature has expired The license file the tools are trying to use is a temporary license, and it has expired. You can do this manually, or by using the License Wizard. For example, trying to run the RVCT 3. If you have recently upgraded to a newer version of the tools, it is possible that it is still trying to use the old license file.
The "License path" section of the error message shows the licenses file s the tools are trying to use. Navigate to this file, and check whether it is the correct file for the version of the tools you are using. If it is the incorrect file, run through the instructions in the following FAQ to install the newer license: ' How do I install my node locked license? Flex error This platform not authorized by license Some Arm licenses restrict usage of the tools to specific platforms e.
This error message is seen when a platform not authorized by the license is used. Flex error Terminal Server remote client not allowed Arm tools licenses do not support the use of terminal servers e.
Microsoft Windows Remote Desktop utility. This error message shows that a license file was found, but that the RVI-ME is either not plugged in or is not installed correctly. These errors occur when attempting to use the Evaluation Tools without having already launched one of the GUI tools, i. Once you have launched one of these applications using its GUI, your tools will become unlocked and the 45 day counter will begin.
This license file is installed by default into the ADS installation directory and is called license. Because the ADS license file is also called license. Please contact the Metrowerks licensing department Solution The problem can easily be corrected by locating the file license. There are a number of factors that need to be considered when deciding how many licenses license seats are needed to build an application as quickly as possible using the ArmCompiler toolchain:.
Will the clients be running the tools simultaneously or will some users have different shift patterns? All the above considerations, and more, will influence the number of seats required to fulfil your usage requirements. A make program can be invoked using the -j flag, for example:. The argument given to -j is the number of jobs the make program should attempt to run in parallel.
The above command would invoke a parallel build, running four jobs in parallel. Each job requests one seat, so in this case the client would attempt to check out four seats. If there are sufficient seats available, the client should observe optimal build times. If the license server only has one seat available, the additional requests will be queued and the client would not benefit from using the -j option.
If the operating system is capable of scheduling different jobs to different CPUs, then it is possible to run separate jobs on each core. So for a quad-core machine to operate at its optimum performance, when running a parallel build, it will require at least four seats, otherwise the build might be delayed.
For example, if the client machine is a quad-core machine and runs a parallel build using a single seat license, it will request four seats and will check out one seat. The remaining requests will be queued until the seat is returned to the license pool. Whilst the license seat is checked-out, the remaining requests are likely to result in the following message:. For example, a build farm might be used for an overnight build. Build farms typically support parallel jobs mentioned above , and also remote access to allow cross-platform development.
A number of clients send their builds to the "server farm" which then runs the builds, requesting seats from the license server. Server farms typically run more than one build in parallel using multiple cores, which can lead to a very high frequency of attempts to checkout a license.
Different versions of Arm tools Arm licenses are backward compatible, so the latest license will enable the use of all versions of the tools up to and including that version of the license. Conversely, the tools require a license of the same version number or higher to operate. When you have clients running different versions of the tools, you must ensure that you have sufficient seats of licenses to enable the use of the different tools, especially if your license file contains a mix of license versions.
Also, it is recommend to use an options file to prevent older versions of the Arm Compiler consuming licenses that enable newer versions of the Arm Compiler. It is important when planning your license requirements to take into account all of the above points.
It is also very important when upgrading your client machine specifications, that your server s are of a suitable specification to handle the clients' demands. Utilities are provided for running a license server on the platforms supported by the tools.
What software is needed to run a license server? License server software consists of two parts:. Which platforms are supported? A list of supported platforms can be found in the product documentation, and also in the following FAQs:. On what platforms will my Arm development tools work?
On what platforms are the Fast Models System Generator supported? Where can I get the license utilities? The latest Arm supported versions can also be downloaded from the Arm website:.
If you are using RVDS 3. If you invoke the RVDS v4. Daniel Earwicker k 35 35 gold badges silver badges bronze badges.
Misha Moroshko Misha Moroshko k gold badges silver badges bronze badges. Add a comment. Active Oldest Votes. Dean Harding Dean Harding Do you have an idea how to remove it?
I've updated my answer with details. The example in the answer works fine without quotation marks even when there is a space in the path. Still--very nice answer. Show 8 more comments. Arnaud Arnaud 2 2 silver badges 3 3 bronze badges.
In which world? Thanks to jeb's comment, I was not fooled by this answer. Why do people just make up stuff and go and start spreading their wild imagination to others.
I have this colleague who does this, but I blamed his young age. I wish my down-vote would count. This doesn't remove the filename from the path though e. We recommend installing the more stable Release build. The categories in the left-hand column, however, follow a slightly different logic that we find easier to navigate.
If you're using the Windows Home edition, switch to see settings in the Computer category only, since your system will ignore changes to per-user Group Policy Objects; you'll need to make those changes in the Windows Registry instead. Changing the settings works just like it does in the Group Policy Editor; more on that below. Note that if you're using Windows Home, you'll have to restart or log off and back on to activate changes.
Whether you're on Windows Vista, Windows 7, Windows 8. The proper installation with this tool requires a couple of tweaks and. NET Framework version 3. You will need a DevianArt account. You might have to manually navigate to that folder.
If your Windows username contains more than one word, you might have to adjust your installation. Right-click x If you can't find a gpedit. Open Notepad , enter the code below, and save the file as Enabler.
0コメント