From: Evaldo Gardenali (evaldogardenali.biz)
Date: Tue Jul 26 2005 - 01:55:28 CDT

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Hi

Karsten Ohme wrote:
> Evaldo Gardenali wrote:
>> Hi,
>>
>> In pcsc-lite-1.2.9-beta7, I see in <PCSC/winscard.h> this:
>> #include <pcsclite.h>
>>
>> in <PCSC/pcsclite.h>:
>> #include <wintypes.h>
>>
>> in libmusclecard-1.2.9-beta7: in <PCSC/musclecard.h>:
>> #include <mscdefines.h>
>>
>> in <PCSC/mscdefines.h>:
>> #include <winscard.h>
>>
>> in muscleframework-1.1.5 MCardPlugin: in musclecardApplet.c:
>> #ifndef __APPLE__
>> #include <musclecard.h>
>> #else
>> #include <PCSC/musclecard.h>
>> #endif
>>
>> now, my question...
>> Are those includes without "PCSC/" on purpose? I can't think of a
>> suitable explanation for myself in my tiny little world.
>
> There is a global include directory called PCSC, part of libmusclecard,
> e.g. in UNIX system /usr/include/PCSC or /usr/local/include/PCSC (except
> if defined __APPLE__, maybe for Apple MacOS systems ..., does not matter
> for this) and this directory is included in the include path for the
> compiler, e.g. gcc ... -I/usr/include/PCSC (Well, this is done
> automatically by the configure script with the help of pkg-config). So
> wehre is the problem with this?

I am packaging such software for NetBSD's pkgsrc. pkgsrc is a portable
package infrastructure that runs on a few different operating systems:
NetBSD, Solaris, Linux, Darwin (Mac OS X), FreeBSD, OpenBSD, IRIX,
BSD/OS, AIX, Interix (Microsoft Windows Services for Unix),
DragonFlyBSD, OSF/1 and possibly others

On such infrastructure, all packages are installed in a special
directory, which normally is /usr/pkg, but can be instructed to be
anywhere, without any kind of damage to the system. This directory
contains all usual subdirectories like bin/ sbin/ lib/ share/ and so on.

I noticed there are some hardcoded options and directory names, and
there are some of which I need to patch for pkgsrc. This specific
#include problem occurred (I actually had several broken compiles), and
so I decided to patch the include files so that any other applications
that need these will not need additional CFLAGS just because of these
includes.

I also noticed this:
MusclePAM does not have a configure script
muscleTools does not have a configure script
XCardII does not have a configure script

my sources for them are (.tar.gz):
DISTNAME= muscleframework-1.1.5
MASTER_SITES= http://alioth.debian.org/download.php/463/

DISTNAME= muscleTools-0.9.2
MASTER_SITES= http://alioth.debian.org/download.php/395/

DISTNAME= XCardII-0.9.9
MASTER_SITES= http://alioth.debian.org/download.php/394/

Am I running outdated versions that don't have configure scripts instead
of your new ones?

Some of the packages and committed so far:
http://cvs.sourceforge.net/viewcvs.py/pkgsrc-wip/wip/pcsc-lite/
http://cvs.sourceforge.net/viewcvs.py/pkgsrc-wip/wip/libmusclecard/
http://cvs.sourceforge.net/viewcvs.py/pkgsrc-wip/wip/muscle-pkcs11/
http://cvs.sourceforge.net/viewcvs.py/pkgsrc-wip/wip/muscle-tools/
http://cvs.sourceforge.net/viewcvs.py/pkgsrc-wip/wip/openct/ (I need
this as an ifd for my reader)

> Do you want to make a new MuscleCard Plug-In? Because you checked out
> muscleframework?

I really apologize for any offense you might have taken, but I really
did not mean any.

> Karsten

Thanks, and sorry for any inconvenience
Evaldo Gardenali

_______________________________________________
Muscle mailing list
Musclelists.musclecard.com
http://lists.drizzle.com/mailman/listinfo/muscle

• application/x-pkcs7-signature attachment: S/MIME Cryptographic Signature

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]