From: Sven Luther <sven.luther@wanadoo.fr>
To: "Christopher A. Watford" <christopher.watford@gmail.com>
Cc: caml-list@inria.fr, John Goerzen <jgoerzen@complete.org>,
"Brandon J. Van Every" <vanevery@indiegamedesign.com>
Subject: Re: [Caml-list] Cross-compiling OCaml
Date: Wed, 1 Sep 2004 09:53:22 +0200 [thread overview]
Message-ID: <20040901075322.GA20548@pegasos> (raw)
In-Reply-To: <8008871f04083117055b609c87@mail.gmail.com>
On Tue, Aug 31, 2004 at 08:05:41PM -0400, Christopher A. Watford wrote:
> Reply within,
>
> >>>SNIP>>>
> > Who ever said that cross-compilation support would only involve running
> > a compiler on x86 Linux to target x86 Windows? It could involve
> > running a compiler on x86 Linux to target arm Zaurus, or m68k Linux, or
> > x86 FreeBSD, or amd64 Linux. Or running a compiler on PowerPC NetBSD
> > to target Alpha NetBSD. Or whatever else.
>
> I think this point needs to be streesed. Like John is trying to say,
> people are asking for CROSS-ARCHITECHTURE compiling, not CROSS-API.
> You can't expect to just plop down code and expect the API to be
> supported by your machine/compiler, however, you should be able to
> retarget the compiler for any architecture that may support it.
No, cross compiling to window is nice, and it should work.
The main point is that the code generation part should be made to build for a
different arch/os than the one the compiler is built on, which is not possible
right now, well at least not easily possible without mangling the built system
a lot.
Xavier and the rest of the ocaml team, would you consider such a feature for
3.09 ?
Friendly,
Sven Luther
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2004-09-01 7:41 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-30 21:02 Ken Rose
2004-08-30 21:30 ` Erik de Castro Lopo
2004-08-31 6:09 ` Sven Luther
2004-08-31 6:50 ` Brandon J. Van Every
2004-08-31 7:14 ` james woodyatt
2004-08-31 9:05 ` Brandon J. Van Every
2004-08-31 13:41 ` John Goerzen
2004-08-31 15:56 ` Ken Rose
2004-08-31 19:30 ` Brandon J. Van Every
2004-09-01 0:05 ` Christopher A. Watford
2004-09-01 7:53 ` Sven Luther [this message]
2004-09-01 7:32 ` james woodyatt
2004-09-01 16:38 ` Brandon J. Van Every
2004-09-01 17:17 ` Brandon J. Van Every
2004-09-01 22:56 ` Sven Luther
2004-09-01 17:32 ` John Goerzen
2004-09-02 21:24 ` I R T
2004-08-31 7:16 ` Sven Luther
2004-08-31 9:05 ` Brandon J. Van Every
2004-08-31 9:18 ` Sven Luther
2004-08-31 9:41 ` Brandon J. Van Every
2004-08-31 15:17 ` skaller
2004-08-31 16:49 ` Sven Luther
2004-08-31 13:48 ` John Goerzen
2004-09-01 13:22 ` I R T
2004-08-31 13:56 ` Erik de Castro Lopo
2004-08-31 13:29 ` John Goerzen
2004-08-31 14:06 ` Erik de Castro Lopo
2004-08-31 15:48 ` skaller
2004-08-31 15:54 ` John Goerzen
2004-08-31 22:49 ` Jon Harrop
2004-08-31 23:36 ` Benjamin Geer
2004-09-01 8:08 ` Erik de Castro Lopo
2004-09-02 11:30 ` Richard Jones
2004-09-09 1:46 ` Jon Harrop
2004-09-01 4:05 ` skaller
2004-09-01 8:45 ` Erik de Castro Lopo
2004-09-01 7:40 ` Erik de Castro Lopo
2004-08-31 19:11 ` Brandon J. Van Every
2004-09-01 21:18 ` I R T
2004-08-31 22:36 ` [Caml-list] game development Brandon J. Van Every
2004-09-01 23:28 ` I R T
2004-09-01 0:37 ` Brandon J. Van Every
2004-08-31 18:34 ` [Caml-list] Cross-compiling OCaml brogoff
2004-08-31 21:07 ` [Caml-list] OCaml's critical mass Brandon J. Van Every
[not found] <Pine.LNX.4.44.0408312302560.3196-100000@localhost>
2004-08-31 20:04 ` [Caml-list] Cross-compiling OCaml Brandon J. Van Every
[not found] <AA48BAF0-FC3A-11D8-8C25-000A958FF2FE@wetware.com>
2004-09-01 18:37 ` Brandon J. Van Every
2004-09-01 19:45 ` John Goerzen
2004-09-01 21:16 ` Brandon J. Van Every
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040901075322.GA20548@pegasos \
--to=sven.luther@wanadoo.fr \
--cc=caml-list@inria.fr \
--cc=christopher.watford@gmail.com \
--cc=jgoerzen@complete.org \
--cc=vanevery@indiegamedesign.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).