# Disable compiler checks

**URL:** https://discourse.cmake.org/t/disable-compiler-checks/735
**Category:** Usage
**Created:** [February 28, 2020, 5:33pm UTC](https://discourse.cmake.org/t/disable-compiler-checks/735 "2020-02-28T17:33:08Z")
**Posts on this page:** 1
**Showing post:** 7

<div class="post-metadata">

### Author: ![ben.boeckel](https://discourse.cmake.org/letter_avatar_proxy/v4/letter/b/ea5d25/32.png) [@ben.boeckel](https://discourse.cmake.org/u/ben.boeckel)
#### Post date: [April 10, 2020, 11:39pm UTC](https://discourse.cmake.org/t/disable-compiler-checks/735/7 "2020-04-10T23:39:33Z")

</div>

> [@Grant\_Anderson](#):
>
> I want to generate a Unix Makefile for Eclipse, to run on another machine

This is not supported. Build trees have absolute paths baked into them and are not transferable between (non-identical) machines.

> [@Grant\_Anderson](#):
>
> Therefore, there must be a way to disable these “compiler tests” because that has nothing to do with the target compiler.

The way to fix this is to have CMake use your target compiler via a toolchain file. This toolchain must run on the host you configure CMake on. See [these docs](https://cmake.org/cmake/help/latest/manual/cmake-toolchains.7.html) for making a toolchain file for your compiler set.

> [@Grant\_Anderson](#):
>
> If it cannot do this, then the concept of supporting cross-compilers is flawed.

Cross compiling is supported in CMake and used all the time. It may not support the specific method of using them in the way you describe here, but they are supported.

---

_[View the full topic](https://discourse.cmake.org/t/disable-compiler-checks/735)._