Compiling for Mac

Compiling for Mac

[Anthony Kozar]

Hello Guilers!

I am a guile newbie and I am attempting to compile guile for the "legacy"
Mac OS (OS 9 and earlier).  My goal is to embed guile into a new program
that I am writing in C++.

Has guile ever been successfully built for the legacy Mac platform? (The
only mention of this in the archives was an unfinished attempt back in
1997).  If it never has been done before, I will really need some help in
order to get all of the configuration and stuff correct.

Clearly, there are some major hurdles to overcome in doing so.  Guile's
reliance on POSIX libraries is a problem for the Mac but not unsolvable.  I
have been using a library called GUSI which gives the Mac a partial POSIX
API.  

A bigger problem is the complicated build process of guile which relies on
several unix command-line tools to dynamically configure the guile code.
This part of the build process cannot really be emulated on a Mac and I
think the easiest solution is to develop static configuration files for the
Mac that can be compiled without modification.

Figuring out what needs to go into those config files is where I need your
help and expertise.  Specifically:

* What should go in scmconfig.h?

* What is the purpose of all of the *.x files?  Why are they built
dynamically?

* Would it be possible to use the *.x files from another platform (Mac OS X
for example) when compiling on Mac OS 9?

* Can you think of any other caveats or suggestions?

Thanks very much!

Anthony Kozar
anthony.kozar@utoledo.edu




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

Re: Compiling for Mac

[Neil Jerram]

>>>>> "Anthony" == Anthony Kozar <anthony.kozar@utoledo.edu> writes:

    Anthony> Hello Guilers!  I am a guile newbie and I am attempting
    Anthony> to compile guile for the "legacy" Mac OS (OS 9 and
    Anthony> earlier). [...]

Hi Anthony,

I'm afraid I can't help with much of the detail here, but I can help
with the .x files ...

    Anthony> * What is the purpose of all of the *.x files?  Why are
    Anthony> they built dynamically?

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.

Regards,
        Neil



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

Re: Compiling for Mac

[Marius Vollmer]

Neil Jerram <neil@ossau.uklinux.net> writes:

> Yes, because the generated output is platform-independent.

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.

-- 
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3  331E FAF8 226A D5D4 E405


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

Re: Compiling for Mac

[Anthony Kozar]

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

Re: Compiling for Mac

[Mike Gran]

What compiler are you using?

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


__________________________________
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com


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

Re: Compiling for Mac

[Anthony Kozar]

CodeWarrior Pro 8 running under Mac OS 9.1.  I am trying to compile the
libguile directory as a shared library.

On 10/24/03 10:55 AM, Mike Gran<spk121@yahoo.com> etched in stone:

> What compiler are you using?



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