[Mono-list] C++/CLI Support

[Rodrigo Kumpera]

There are a bunch of thorny issues to consider.

Do we want to support C++ CLI binaries done using the MS toolchain outside
of windows?
Supporting those requires writing a whole PE dynamic linkers, which is a
huge amount of work.

If not, we can very much simply use mono's AOT engine and produce a pair of
.dll and .dll.so
files and be done with it. This approach is doable but the only issue is
that the AOT file format
inside an ELF file is not set in stone and changes frequently - we're at
version 84.

We can derive a stable forward, add mono support for it, and use it in
conjunction with LLVM
to output a linux/osx C++ CLI binary pair. This is doable, but keep in mind
that those binaries
are platform specific.

So, given than, all it's left is someone doing it.


On Mon, Sep 10, 2012 at 5:59 PM, kpedersen <kpedersen at live.co.uk> wrote:

> Indeed LLVM/clang certainly seems capable enough since I have seen some
> pretty good frontends and backends developed for it in the past.
>
> I think it depends if the work started using GCC
> (http://gcc.gnu.org/projects/cli.html) can be offset with the future
> development speed or maintainability using LLVM.
>
> However I am simply not skilled / knowledgeable enough in the matter or I
> would love to create it myself!
>
> As I understand we would need our compiler to generate a binary which also
> hosts the CLR and runs the embedded bytecode. (As well as tonnes of other
> stuff such as communicating native data with managed data and visa versa).
>
>
>
>
> --
> View this message in context:
> http://mono.1490590.n4.nabble.com/C-CLI-Support-tp4656534p4656552.html
> Sent from the Mono - General mailing list archive at Nabble.com.
> _______________________________________________
> Mono-list maillist  -  Mono-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-list
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ximian.com/pipermail/mono-list/attachments/20120910/a15934f4/attachment.html>