From: Jacob Sparre Andersen <sparre@nbi.dk>
Subject: Linking in an externally compiled .o file with gnatmake?
Date: Mon, 11 Jun 2012 12:06:17 +0200
Date: 2012-06-11T12:06:17+02:00 [thread overview]
Message-ID: <87oboq6u3q.fsf@adaheads.sparre-andersen.dk> (raw)
I'm working on a binding to the Linux sound API ALSA
(http://repositories.jacob-sparre.dk/alsa-binding). As a part of the
binding, I need to access a C macro. I do that by turning the macro
into a C function:
% cat alsa_macros.c
#include <alsa/asoundlib.h>
void allocate_alsa_hardware_parameters (snd_pcm_hw_params_t **hwparams_ptr) {
snd_pcm_hw_params_alloca (hwparams_ptr);
};
%
Compiling "alsa_macros.c" to "alsa_macros.o" is not a problem, but how
can I get gnatmake to link "alsa_macros.o" into the final program? Or
maybe into "sound-alsa.o" as it is package Sound.ALSA which imports the
function.
Greetings,
Jacob
--
"Facts are stubborn, but statistics are more pliable." -- Mark Twain
next reply other threads:[~2012-06-14 17:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-11 10:06 Jacob Sparre Andersen [this message]
2012-06-11 10:14 ` Linking in an externally compiled .o file with gnatmake? Jacob Sparre Andersen
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox