What is a recommended practice when compiling a scanner in GitLab?

Compiling a scanner in GitLab with all necessary libraries ensures that the resulting application is fully functional and can operate without dependency issues. This approach guarantees that the scanner has access to all the resources it needs to perform effectively, including any libraries for specific functionalities essential to the scanner's operation.

Utilizing all required libraries helps prevent runtime errors that can occur if a library is missing, which could compromise the scanner's performance and reliability. It also aligns with best practices concerning application development, where dependencies must be properly managed and included during the compile process to ensure a smooth deployment and wider compatibility across different systems.

Although a multi-platform approach could enhance portability and usability across different environments, it doesn’t directly ensure the application's functionality compared to ensuring all necessary libraries are included. Compiling with a sole focus on speed might lead to neglecting important libraries or components, and including as many optional components as possible could unnecessarily bloat the application and complicate maintenance without delivering meaningful advantages. Hence, compiling with all necessary libraries stands out as the optimal choice.