# Cross compilation help
**URL:** https://discourse.cmake.org/t/cross-compilation-help/1486
**Category:** Usage
**Tags:** comp:clang, gen:vs, os:windows
**Created:** [July 3, 2020, 8:33pm UTC](https://discourse.cmake.org/t/cross-compilation-help/1486 "2020-07-03T20:33:27Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@Arcnor](https://discourse.cmake.org/u/Arcnor)
#### Post date: [July 3, 2020, 8:33pm UTC](https://discourse.cmake.org/t/cross-compilation-help/1486/1 "2020-07-03T20:33:27Z")
Hi,
I’m trying to use CMake to generate a project for cross compiling for another system (gaming console). The SDK uses MSVC with a property sheet for settings and `clang` as its compiler. I’ve hacked around to make CMake accept the property sheet when identifying the compiler (it will be nice if properties could be set somehow before this happens, but setting `VC_GLOBAL_property` and similar doesn’t seem to affect this stage, so I’m using `CMAKE_GENERATOR_TOOLSET` with a custom `VCTargetsPath`). My problem is that the compiler doesn’t use `main` but something else for its entry point, and the compiler identification fails at this stage.
Is there anything I can do to tell CMake to use something different as `main` or something to that effect? I’d like to keep the rest of the process if possible, and if it’s not, I guess I can tell CMake what the compiler is, but there are a lot of properties to set and things like that which I’d like CMake to discover like it’s doing now.
Thanks in advance.
---
### Author:  [@ben.boeckel](https://discourse.cmake.org/u/ben.boeckel)
#### Post date: [November 11, 2020, 3:02pm UTC](https://discourse.cmake.org/t/cross-compilation-help/1486/2 "2020-11-11T15:02:30Z")
This sounds like a feature request to me. Could you please file [an issue](https://gitlab.kitware.com/cmake/cmake/-/issues) with this information so that it can be tracked? Thanks.
Cc: @brad.king