On 29/03/07, Frank Cusack <[EMAIL PROTECTED]> wrote:
In wintypes.h, I see types like:
typedef unsigned long DWORD;
Should long's and short's be sized types, eg:
typedef uint32_t DWORD;
Or is DWORD actually 64 bits long (for LP64) in the Windows world.
That is a very good que
On 29/03/07, Frank Cusack <[EMAIL PROTECTED]> wrote:
I'm not clear on when an ATR becomes available to my pcsc app.
>From what I can tell, if SCardGetStatusChange() returns SCARD_STATE_PRESENT,
it means that a card has been inserted and the reader has obtained the ATR.
I think this because pcsc_
On 28/03/07, Michael Bender <[EMAIL PROTECTED]> wrote:
I also don't understand the argument about compatibility with Windows
and how where Windows puts header files has any bearing on what we put
into an #include directive.
A Windows program just do:
#include
pcsc-lite is trying to mimic the
On 28/03/07, Frank Cusack <[EMAIL PROTECTED]> wrote:
Oh, I don't #include , I #include , since
that's what I saw the sample app do (and it seemed easier than finding
the location of the PCSC dir). Sorry for the confusion.
The sample app is not correct.
You should do something like
#ifdef __AP
In wintypes.h, I see types like:
typedef unsigned long DWORD;
Should long's and short's be sized types, eg:
typedef uint32_t DWORD;
Or is DWORD actually 64 bits long (for LP64) in the Windows world.
-frank
___
Muscle mailing list
Muscl
I'm not clear on when an ATR becomes available to my pcsc app.
From what I can tell, if SCardGetStatusChange() returns SCARD_STATE_PRESENT,
it means that a card has been inserted and the reader has obtained the ATR.
I think this because pcsc_scan never does an SCardConnect() yet it reports
the
On March 28, 2007 9:38:37 AM -0700 Michael Bender <[EMAIL PROTECTED]>
wrote:
> Isn't it broken to have install the PCSC include files in the PCSC
subdir and then to have them #include other PCSC include files but
> omit the PCSC part of the path?
I think the whole PCSC/ include subdir issue
On March 28, 2007 1:17:47 PM +0200 Ludovic Rousseau
<[EMAIL PROTECTED]> wrote:
On 28/03/07, Martin Preuss <[EMAIL PROTECTED]> wrote:
On Wednesday 28 March 2007 11:58, Ludovic Rousseau wrote:
> On 28/03/07, Frank Cusack <[EMAIL PROTECTED]> wrote:
[...]
> > Isn't it broken to have install the PCSC
On 28/03/07, Ludovic Rousseau <[EMAIL PROTECTED]> wrote:
I hope it will not break too many applications :-) I will make a
subversion snapshot available for testing.
A subversion snapshot if pcsc-lite and ccid driver are available at [1].
Please report any regression or problem.
Bye
[1] http:/
> Isn't it broken to have install the PCSC include files in the PCSC
subdir and then to have them #include other PCSC include files but
> omit the PCSC part of the path?
I think the whole PCSC/ include subdir issue came about when DaveC was
getting PC/SC-lite to work on MacOS-X. I think that ha
Thanks Dr Ludovic. Im gonna test as soon as possible.
Yes, I got them.
And I applied your patch in revision 2496 [1].
I hope it will not break too many applications :-) I will make a
subversion snapshot available for testing.
Bye
[1]
http://lists.alioth.debian.org/pipermail/pcsclite-cvs-comm
Can I achieve that they execute several applications on a same card, utilizing
PCSC?
<>___
Muscle mailing list
Muscle@lists.musclecard.com
http://lists.drizzle.com/mailman/listinfo/muscle
On 28/03/07, Frank Cusack <[EMAIL PROTECTED]> wrote:
On March 28, 2007 11:58:42 AM +0200 Ludovic Rousseau
> You should use pkg-config to know where to find the PCSC header files.
pkg-config isn't present on every platform, and it's broken for multilib
platforms.
How is it broken?
What do you c
On 28/03/07, Martin Preuss <[EMAIL PROTECTED]> wrote:
On Wednesday 28 March 2007 11:58, Ludovic Rousseau wrote:
> On 28/03/07, Frank Cusack <[EMAIL PROTECTED]> wrote:
[...]
> > Isn't it broken to have install the PCSC include files in the PCSC subdir
> > and then to have them #include other PCSC
On Wed, 2007-03-28 at 03:39 -0700, Frank Cusack wrote:
> > Your application should not include other PCSC files.
> > (or reader.h if you need it)
>
> I don't. It's winscard.h that is including other PCSC files.
>
I ran into something similar when building JPCSC from the muscle site.
The source
On Wed, 2007-03-28 at 07:56 +0100, Ludovic Rousseau wrote:
> On 28/03/07, Jason Grant <[EMAIL PROTECTED]> wrote:
> > [os = RHEL3 linux, pcsc-lite = 1.4.0, driver = Omnikey RFID 2.2-0
> > (ifdokrfid_lnx-2.2.0), reader = Omnikey 5121, card Mifare DESFire 4k]
...
>
> I would suspect a bug in the read
On March 28, 2007 11:58:42 AM +0200 Ludovic Rousseau
<[EMAIL PROTECTED]> wrote:
On 28/03/07, Frank Cusack <[EMAIL PROTECTED]> wrote:
Hi again,
Hello,
Isn't it broken to have install the PCSC include files in the PCSC subdir
and then to have them #include other PCSC include files but omit the
Hi,
On Wednesday 28 March 2007 11:58, Ludovic Rousseau wrote:
> On 28/03/07, Frank Cusack <[EMAIL PROTECTED]> wrote:
[...]
> > Isn't it broken to have install the PCSC include files in the PCSC subdir
> > and then to have them #include other PCSC include files but omit the PCSC
> > part of the pat
On 28/03/07, Frank Cusack <[EMAIL PROTECTED]> wrote:
Hi again,
Hello,
Isn't it broken to have install the PCSC include files in the PCSC subdir
and then to have them #include other PCSC include files but omit the PCSC
part of the path?
It is to be compatible with Windows with
#include
You
On 27/03/07, matheus ribeiro <[EMAIL PROTECTED]> wrote:
Dr Ludovic
Hello,
I have sent you a mail with the event changes I made to PCSC. Please,
let me know if you got them or not.
Yes, I got them.
And I applied your patch in revision 2496 [1].
I hope it will not break too many applications
Elvis Vazquez Aragon escribe:
> The development kit that we are using is Javacard 2.2.2, we
> installed it as the development kit user's guide said but we tried
> to execute the kit's example and it didn't work.
I'd go for 2.1.2, 2.2.2 is too new and too, let's say, unstandard
still for a new deve
Hi again,
Isn't it broken to have install the PCSC include files in the PCSC subdir
and then to have them #include other PCSC include files but omit the PCSC
part of the path?
For example, winscard.h includes pcsclite.h instead of PCSC/pcsclite.h.
Every other package I've ever seen includes the
22 matches
Mail list logo
