On 02/17/2016 06:01 PM, Óscar Fuentes wrote:
Apparently you are wrapping the MinGW-64 toolset with your own
application. At this point I can't help you any further, except
suggesting to try the cross-compilation with a tool chain file that
points to the MinGW-w64 toolset. Here is a very old one o
On 02/17/2016 04:21 PM, Óscar Fuentes wrote:
> Showing the cmake invocation you used for configuring the build would
> help. If you use a Toolchain-*.cmake file for describing the
> cross-tools to cmake, please show that too.
>
I don't use a tool chain file. I run cmake like this:
CC=/home/rich/el
On 02/17/2016 03:42 PM, Óscar Fuentes wrote:
> Richard Pennington
> writes:
>
>> I recently switched over to using cmake to build my clang/LLVM based
>> ELLCC cross development project (http://ellcc.org). I also recently
>> updated to LLVM svn version 258915 from 2
Hi,
I asked this on the LLVM lists, but thought I'd ask here also. I use a
clang based tool chain with the mingw-w64 header files and libraries to
build itself for Windoes.
I recently switched over to using cmake to build my clang/LLVM based
ELLCC cross development project (http://ellcc.org)
A new binary release of the ELLCC cross compilation tool chain is available,
ELLCC is a pre-packaged set of tools based on clang/LLVM designed to
support cross compilation for a variety of target processors.
The ELLCC run-time libraries are all covered with BSD-like licenses:
* libc++The C
