From: Ken Rose <kenrose@tfb.com>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Cross-compiling OCaml
Date: Tue, 31 Aug 2004 08:56:12 -0700 [thread overview]
Message-ID: <41349F9C.5020200@tfb.com> (raw)
In-Reply-To: <200408310841.18106.jgoerzen@complete.org>
John Goerzen wrote:
> On Tuesday 31 August 2004 04:05 am, Brandon J. Van Every wrote:
>
>>james woodyatt wrote:
>>
>>>I'd rather that the Windows-centric guys on the list put their time
>>>into good Windows support for Ocaml,
>>
>>No problem. As I said, I realize Linux / mingw guys aren't into
>>this.
>>
>>I'm just objecting to the statement that Linux cross-compilation
>>support "would indeed be a great great additional functionality." As
>
>
> Well, let's look at that, because I believe you are missing the point.
>
> 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.
Just to clarify things, that is what I really would like to see. One of
the great things about GCC is that I can set it up to run on nearly any
adequate host, and generate code for any supported target. It would be
really handy to be able to do that with OCaml, too.
And yes, that means compiling windows programs on Linux, like for my
current DSL compiler project, or compiling Palm apps on Windows, or even
Windows games on Windows, should I ever want to wade back into that sewer.
- ken
-------------------
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-08-31 15:56 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 [this message]
2004-08-31 19:30 ` Brandon J. Van Every
2004-09-01 0:05 ` Christopher A. Watford
2004-09-01 7:53 ` Sven Luther
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=41349F9C.5020200@tfb.com \
--to=kenrose@tfb.com \
--cc=caml-list@inria.fr \
--cc=rose@acm.org \
/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).