Hi, thanx Nico.
That's the solution I find the most elegant. It worked right away without
problem.
I couldn't make work the volatile function pointers. When it's declared as
volatile, the compiler says "assignment from incompatible pointer type". I
also tried to put volatile for the function declaration. It doesn't work.
Anyways, the .o solution works for me.
Thank you,
Yvan
From: "N. Coesel" <[email protected]>
Reply-To: [email protected]
To: [email protected]
Subject: RE: [Mspgcc-users] Problem linking interrupt functions in library
Date: Fri, 29 Jul 2005 21:55:26 +0200
At 18:52 29-07-05 +0000, you wrote:
>Well, our goal is to make some functions available to the programmer as
an
>API but also hide others that we don't want them to change. For
instance,
>the interrupt routines are vital in the core code. We don't want the
user
>to alter them in any way. Is there another method other than creating a
>library that can be used to hide functions then?
How about distributing an object (.o) file? All symbols within will be
linked and you don't need to supply the source.
Nico Coesel
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Mspgcc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mspgcc-users
