Walter Franzini wrote:
> On Tue, Sep 22, 1998 at 05:46:49PM +0200, gregor wrote:
> > a ct-api should named like this:
> >
> > ctapi-n.xyy.so
> >
> > where n is a "well know identifier"
> > x the major-no of the release
> > y the minor-no of the release
> I suggest to use a different naming co
Have someone already writed a program to test a ctapi library?
I mean a `complete' test.
With :
1) CTAPI implementation
2) CTBCS check
3) ISO7816-4 commands
--
Ciao Walter.
C makes it easy for you to shoot yourself in the foot. C++ makes that
harder, but when you do, it blows away your whole
On Sun, Sep 27, 1998 at 09:22:03AM +0200, gregor wrote:
>
> OK, you're right.
>
> but then i would prefer
>
> libctapi-.x.yy.so
>
> because, there is no need for symoblic links
Yes, but when you replace a library whit a newer version you must
recompile all programs that depend on it.
Usin
Walter Franzini wrote:
> Have someone already writed a program to test a ctapi library?
>
> I mean a `complete' test.
> With :
> 1) CTAPI implementation
> 2) CTBCS check
> 3) ISO7816-4 commands
i'm on it
bye
gregor
***
Linux Smart C
Walter Franzini wrote:
> On Sun, Sep 27, 1998 at 09:22:03AM +0200, gregor wrote:
> >
> > OK, you're right.
> >
> > but then i would prefer
> >
> > libctapi-.x.yy.so
> >
> > because, there is no need for symoblic links
> Yes, but when you replace a library whit a newer version you must
> rec
No, not yet. Are you up for it ? It would be really nice to have
something that tells what is wrong with a person's CT-API library.
Thanks
Dave
On Sun, 27 Sep 1998, you wrote:
>Have someone already writed a program to test a ctapi library?
>
>I mean a `complete' test.
>With :
>1) CTAPI
rn Sun, Sep 27, 1998 at 01:09:53PM +0200, gregor wrote:
> ok
> so the lib should look like: libctapi-n.so.x.yy
> and the link: libctapi-n.so
>
> is that correct?
>
Yes. Remember also the link libctapi-n.so.x
--
Ciao Walter.
C makes it easy for you to shoot yourself in the foot.
On Sun, Sep 27, 1998 at 09:33:55AM -0500, David Corcoran wrote:
> No, not yet. Are you up for it ? It would be really nice to have
> something that tells what is wrong with a person's CT-API library.
Yes. I hope to finish CT-API for the Argus 210 CT in a couple of weeks,
but I want test my w
Hi everyone,
I have just joined this project and I wonder if someone has some
archives of the mailing list.
Also, as a pure exercise for understanding how the CT-API and the
MCT works, I have made some modifications to the mct driver of gregor.
Mainly, I have introduced some symbolic constans an
