From: "Christopher A. Watford" <christopher.watford@gmail.com>
To: caml-list@inria.fr
Cc: John Goerzen <jgoerzen@complete.org>,
"Brandon J. Van Every" <vanevery@indiegamedesign.com>
Subject: Re: [Caml-list] Cross-compiling OCaml
Date: Tue, 31 Aug 2004 20:05:41 -0400 [thread overview]
Message-ID: <8008871f04083117055b609c87@mail.gmail.com> (raw)
In-Reply-To: <200408310841.18106.jgoerzen@complete.org>
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.
>>>SNIP>>>
> I think that offering a simple tarball with the source is just fine.
Its more out of respect for the operating system to include the source
as a zip file for windows users. Just as you might include an rpm for
Red Hat or an ebuild for Gentoo. I would agree that a .tgz file
'should' be the lowest common denominator, but hey, you can't always
get what you want.
> Oh please, tell us what is so wrong with posting the source code easily
> accessible as a tarball. Is it that Windows people can't figure out
> how to use Winzip?
Nah its 'cause they don't need to have winzip installed anymore. XP/2k
have compressed folder support built in, sort of takes away the need
for WinZip. Though John is right, if you're releasing the source to an
OCaml Library, that implies your users should be damn well smart
enough to open a tarball.
> John Goerzen
> Author, Foundations of Python Network Programming
> http://www.complete.org/pynet
I think this thread has gone horribly offtopic with gripes more about
CROSS-API support rather than CROSS-ARCHITECTURE. Hell, because of the
raw differences in API between Linux and Win32, I think it would be
harder to target Win32 from Linux. But, since Win32 tends to have like
90%-ish support for POSIX/stdlibc/etc, I think it would be easier to
have the Win32 compiler target Linux images.
However, like any good programmer, you must take into account
programming in a cross platform/architecture manner (in C I tend to
use ifdef's, yeah ugly but whatever) in order to even have a glimpse
of a hope with getting it to work across the 3 major regions (win32,
*nix/un*x/bsd, osx; I'm leaving out OpenVMS etc...).
--
Christopher A. Watford
christopher.watford@gmail.com
http://dorm.tunkeymicket.com
-------------------
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 0:05 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 [this message]
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=8008871f04083117055b609c87@mail.gmail.com \
--to=christopher.watford@gmail.com \
--cc=caml-list@inria.fr \
--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).