unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Anthony Kozar <anthony.kozar@utoledo.edu>
Subject: Re: Compiling for Mac
Date: Fri, 24 Oct 2003 11:19:59 -0400	[thread overview]
Message-ID: <BBBE079F.8B8A%anthony.kozar@utoledo.edu> (raw)
In-Reply-To: <m3ismi1e62.fsf@laruns.ossau.uklinux.net>

Thanks Neil and Marius for the help.

If I understand both of you correctly, I should be able to transfer the *.x
files from another platform although it is possible for export code to be
included for functions which the configuration on Mac OS 9 will not support,
right?  This should be fairly easy to deal with I hope.  I imagine that I
can just delete the exports that I don't need.

Now if someone has any ideas on what should go in scmconfig.h, I might be
able to try compiling again.  Anyone?

Thanks :)

Anthony Kozar
anthony.kozar@utoledo.edu


On 10/21/03 5:20 PM, Neil Jerram<neil@ossau.uklinux.net> etched in stone:

> They contain the lines of C code necessary to export functions
> etc. defined in C to the Scheme world.
> 
> Anthony> * Would it be possible to use the *.x files from another
> Anthony> platform (Mac OS X for example) when compiling on Mac OS
> Anthony> 9?
> 
> Yes, because the generated output is platform-independent.


On 10/21/03 5:46 PM, Marius Vollmer<mvo@zagadka.de> etched in stone:

> Hmm, strictly speaking, it is not since it might depend on
> preprocessor conditionals like
> 
> #ifdef HAVE_FOO
> SCM_DEFINE ...
> #endif
> 
> but these things are hopefully rare.



_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user


  parent reply	other threads:[~2003-10-24 15:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-21  1:35 Compiling for Mac Anthony Kozar
2003-10-21 21:20 ` Neil Jerram
2003-10-21 21:46   ` Marius Vollmer
2003-10-24 15:19   ` Anthony Kozar [this message]
2003-10-24 15:55     ` Mike Gran
2003-10-27 16:30       ` Anthony Kozar

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

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=BBBE079F.8B8A%anthony.kozar@utoledo.edu \
    --to=anthony.kozar@utoledo.edu \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).