On Dec 18, 2005, at 4:12 AM, Peter O'Gorman wrote:
Can you not use the compiler that installs in /usr/local/ada ? I know
that
it is a different download, but it will not overwrite the system's gcc
(a
bad idea and a reason I never installed the macada package in the
past).
I assume you're
--- Martin Costabel [EMAIL PROTECTED] wrote:
We already have examples of packages that depend on
external stuff like specific commercial fortran
compilers or parts of the developer tools that are
not installed by default, and which manage their
dependencies on these external components
Is there a way to handle a package's dependence on a compiler besides
using a virtual package?
I have a program, written in Ada, that depends on the macada.org port
of GNAT to OSX. Is there a way I could express that dependence in a
package .info?
Thanks,
Ben Place
On Dec 13, 2005, at 6:35 AM, Benjamin Place wrote:
Is there a way to handle a package's dependence on a compiler
besides using a virtual package?
I have a program, written in Ada, that depends on the macada.org
port of GNAT to OSX. Is there a way I could express that dependence
in a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Trevor Harmon wrote:
| On Dec 13, 2005, at 6:47 PM, Benjamin Place wrote:
|
| I don't think there is a GNAT package in Fink, I looked on the
| Packages page and didn't find one. It seems to me that the GNAT Ada
| compiler is analogous to Apple's
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Peter O'Gorman wrote:
|
| Except that gnat needs an ada compiler to bootstrap (specifically it needs
| gnat). There is no gnat package in fink bacause making one is a pain and,
| until now, there has been no demand for one.
Replying to myself :)
Benjamin Place wrote:
On Dec 13, 2005, at 1:49 PM, Trevor Harmon wrote:
If I understand what you're asking, and GNAT is used *only* to build
the program, and there is a GNAT package in Fink, you can simply add
this line to the program's .info:
BuildDepends: gnat
Thanks for your response,
Benjamin Place wrote:
[]
You need a binary gnat to build gnat from source.
gnu.org doesn't have any binaries that'll run on OS X.
macada.org does, but can I make a package that's
binary-only? That would be fine, I guess. Maybe I
could make a source package that depends on the binary
package.
