[cfe-dev] LibC++ v4.0 testing and exceptions

[Martin J. O'Riordan via cfe-dev]

Thanks Tim, can you send me more info about how to do this? off list if not generally useful?  I test under Linux (Centos 6 - our reference platform) and also on Windows (7, 8, 8.1 and 10) from both a native Windows CMD.EXE environment, and from a Cygwin environment which mostly mimics the Linux environment.

Our problem is that because the target is a heterogeneous multicore platform, the conventional steps of "compile -> link -> run" are nowhere near as simplistic; one of the joys of a deeply-embedded cross-compilation environment ;-)

Also, if I do find a way of integrating building LibC++ with the recommended approach, and testing, I will be certain to share my feedback to the community on how I resolved this with a fairly exotic cross-compilation system, and perhaps this could percolate into the generic framework so that other out-of-tree targets could be accommodated.

All the best,

	MartinO

-----Original Message-----
From: Tim Northover [mailto:t.p.northover at gmail.com] 
Sent: 09 February 2017 15:32
To: Martin J. O'Riordan <Martin.ORiordan at movidius.com>
Cc: Eric Fiselier <eric at efcs.ca>; cfe-dev <cfe-dev at lists.llvm.org>
Subject: Re: [cfe-dev] LibC++ v4.0 testing and exceptions

On 9 February 2017 at 01:25, Martin J. O'Riordan via cfe-dev <cfe-dev at lists.llvm.org> wrote:
> I eventually found the problem.  We are not able to test LibC++ using 
> the usual approach because the complexity of building runnable 
> programs for our platform is quite complicated and involves several steps after compilation.

If you're on Linux, I've had success with adding a binfmt_misc entry pointing the kernel at a wrapper for non-native binaries. It lets me just run "ninja check" on a cross-compiled AArch64 toolchain. Not tried it with libc++ specifically though.

Cheers.

Tim.