List Info

Thread: OpenSC New Build System
OpenSC New Build System
user name
 2008-02-13 14:09:41 
Hello All,

I've been working on a new build system for OpenSC.

Win32 binaries are available at [1], source tarball is
available at [2], svn
trunk at [3].

Please provide feedback or review branch [4], so I can
request merge.

After this, I will do the same for other OpenSC packages.

Some highlights:
1. Complete rewrite and cleanup of OpenSC build system.
2. Build system now support MinGW (Windows) compilation
using msys and
cross compilation.
3. Ability to explicitly disable and enable dependencies of
the package.
4. openct, pcsc and nsplugins features are disabled by
default.
5. Modified pcsc driver to use pcsc dynamically, no compile
time
dependency is required.
6. --enable-pcsc-lite configuration option renamed to
--enable-pcsc.
7. Install opensc.conf file (as opensc.conf.new if
opensc.conf exists).
8. Add--enable-doc configuration option, allow installing
documentation into target.
9. Add export files to each library in order to export only
required
symbols. Windows native build may use these files instead of
scanning
objects' symbols.
10. Add opensc-tool --info to display some general
information about the build.
11. Create compatibility library to be linked against
library instread
of recompiling the same source files in different places.
12. Add different win32 version resource to each class of
outputs.
13. Make xsl-stylesheets location selectable.
14. Some win32 fixups.
15. Some warning fixups.
16. Many autoconf/automake cleanups.
17. xsl-stylesheets is required for svn checkout build.

Best Regards,
Alon Bar-Lev.

[1] http://alon.barlev.googlepages.com/opensc-tru
nk-mingw32-002.tar.bz2
[2] http://alon.barlev.googlepages.com/opensc-0.11.4-svn.
tar.gz
[3] http://www.opensc-project.org/opensc/browser/b
ranches/alonbl/mingw
[4] svn diff -r 3315:HEAD
http://www.opensc-project.org/svn/opensc/branches/
alonbl/mingw
_______________________________________________
opensc-devel mailing list
opensc-devellists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc
-devel
Re: OpenSC New Build System
country flaguser name
Netherlands		 2008-02-13 17:00:50 
hi Alon,

sorry for not responding any sooner (I saw your previous
plea for 
Windows testers) but I won't get around to testing your new
MingW builds 
until next week. It's definitely on my list, as we are still
making 
extensive use of (parts of) opensc with our Aladdin eTokens
(and with 
the Aladdin RTE software). Hang in there 

cheers,

JJK

Alon Bar-Lev wrote:
> Hello All,
>
> I've been working on a new build system for OpenSC.
>
> Win32 binaries are available at [1], source tarball is
available at [2], svn
> trunk at [3].
>
> Please provide feedback or review branch [4], so I can
request merge.
>
> After this, I will do the same for other OpenSC
packages.
>
> Some highlights:
> 1. Complete rewrite and cleanup of OpenSC build
system.
> 2. Build system now support MinGW (Windows) compilation
using msys and
> cross compilation.
> 3. Ability to explicitly disable and enable
dependencies of the package.
> 4. openct, pcsc and nsplugins features are disabled by
default.
> 5. Modified pcsc driver to use pcsc dynamically, no
compile time
> dependency is required.
> 6. --enable-pcsc-lite configuration option renamed to
--enable-pcsc.
> 7. Install opensc.conf file (as opensc.conf.new if
opensc.conf exists).
> 8. Add--enable-doc configuration option, allow
installing
> documentation into target.
> 9. Add export files to each library in order to export
only required
> symbols. Windows native build may use these files
instead of scanning
> objects' symbols.
> 10. Add opensc-tool --info to display some general
information about the build.
> 11. Create compatibility library to be linked against
library instread
> of recompiling the same source files in different
places.
> 12. Add different win32 version resource to each class
of outputs.
> 13. Make xsl-stylesheets location selectable.
> 14. Some win32 fixups.
> 15. Some warning fixups.
> 16. Many autoconf/automake cleanups.
> 17. xsl-stylesheets is required for svn checkout
build.
>
> Best Regards,
> Alon Bar-Lev.
>
> [1] http://alon.barlev.googlepages.com/opensc-tru
nk-mingw32-002.tar.bz2
> [2] http://alon.barlev.googlepages.com/opensc-0.11.4-svn.
tar.gz
> [3] http://www.opensc-project.org/opensc/browser/b
ranches/alonbl/mingw
> [4] svn diff -r 3315:HEAD
> http://www.opensc-project.org/svn/opensc/branches/
alonbl/mingw
> _______________________________________________
> opensc-devel mailing list
> opensc-devellists.opensc-project.org
> http://www.opensc-project.org/mailman/listinfo/opensc
-devel
>   

_______________________________________________
opensc-devel mailing list
opensc-devellists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc
-devel
Re: OpenSC New Build System
country flaguser name
Estonia		 2008-02-14 11:01:53 
Hi Alon!

On Feb 13, 2008, at 10:09 PM, Alon Bar-Lev wrote:
> I've been working on a new build system for OpenSC.
Cool! This has needed attention for a while now.
> Please provide feedback or review branch [4], so I can
request merge.
I've not yet had the time to test it on a Debian box but
I'll try to  
do that before next week. I remember some minor things but
I'd like to  
give precise suggestions.

> 4. openct, pcsc and nsplugins features are disabled by
default.
I don't think it's a good idea to by default disable most
used reader  
interfaces by default, as I'd expect most software to behave
nicely  
after a ./configure; make; make install cycle. Have not
tried it on  
Linux, but we might include some special handling code for
Mac as Mac  
is a pretty defined platform. a ./configure; make; make
install cycle  
could work on osx as well flawlessly.

> 9. Add export files to each library in order to export
only required
> symbols. Windows native build may use these files
instead of scanning
> objects' symbols.
I should investigate this. While at it, we could also
'break' the  
windows build, drop libltdl dependance and have a wrapper
that uses  
native win32 API calls on windows and libltdl on other
platforms.

Great work and I hope we can release the next version with a
new build  
system and other generic improvements 

m.
-- 
Martin Paljak
http://martin.paljak.pri.
ee
+3725156495


_______________________________________________
opensc-devel mailing list
opensc-devellists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc
-devel
Re: OpenSC New Build System
user name
 2008-02-14 13:06:06 
On Thu, Feb 14, 2008 at 7:01 PM, Martin Paljak
<martinpaljak.pri.ee> wrote:
>  > 4. openct, pcsc and nsplugins features are
disabled by default.
>  I don't think it's a good idea to by default disable
most used reader
>  interfaces by default, as I'd expect most software to
behave nicely
>  after a ./configure; make; make install cycle. Have
not tried it on
>  Linux, but we might include some special handling code
for Mac as Mac
>  is a pretty defined platform. a ./configure; make;
make install cycle
>  could work on osx as well flawlessly.

I don't like packages that enable optional features
automatically.
Users/packagers should choose what they wish and enable
dependency explicitly.
In this case, nsplugin seldom used anyway, and there is not
much sense in
enabling both pcsc and openct.
And if the user has for some strange reason openct
installed, does it mean
the result of OpenSC compilation should depend on it?

I truly think users are able to choose, and I am sure distro
packagers will
enable the features by the dependency of their packages.

>  > 9. Add export files to each library in order to
export only required
>  > symbols. Windows native build may use these files
instead of scanning
>  > objects' symbols.
>  I should investigate this. While at it, we could also
'break' the
>  windows build, drop libltdl dependance and have a
wrapper that uses
>  native win32 API calls on windows and libltdl on other
platforms.

I also think that Windows does not need libltdl... Is there
any reason to
use it at *NIX? I don't think .la files are used anyway...
But this change can be done later...

>  Great work and I hope we can release the next version
with a new build
>  system and other generic improvements 

Thanks!
Waiting for your test results.
Alon.
_______________________________________________
opensc-devel mailing list
opensc-devellists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc
-devel
Re: OpenSC New Build System
user name
 2008-02-23 08:16:44 
Hi!
Waiting for your input 
Alon

On 2/14/08, Alon Bar-Lev <alon.barlevgmail.com> wrote:
> On Thu, Feb 14, 2008 at 7:01 PM, Martin Paljak
<martinpaljak.pri.ee> wrote:
>  >  > 4. openct, pcsc and nsplugins features are
disabled by default.
>  >  I don't think it's a good idea to by default
disable most used reader
>  >  interfaces by default, as I'd expect most
software to behave nicely
>  >  after a ./configure; make; make install cycle.
Have not tried it on
>  >  Linux, but we might include some special
handling code for Mac as Mac
>  >  is a pretty defined platform. a ./configure;
make; make install cycle
>  >  could work on osx as well flawlessly.
>
>
> I don't like packages that enable optional features
automatically.
>  Users/packagers should choose what they wish and
enable dependency explicitly.
>  In this case, nsplugin seldom used anyway, and there
is not much sense in
>  enabling both pcsc and openct.
>  And if the user has for some strange reason openct
installed, does it mean
>  the result of OpenSC compilation should depend on it?
>
>  I truly think users are able to choose, and I am sure
distro packagers will
>  enable the features by the dependency of their
packages.
>
>
>  >  > 9. Add export files to each library in
order to export only required
>  >  > symbols. Windows native build may use these
files instead of scanning
>  >  > objects' symbols.
>  >  I should investigate this. While at it, we could
also 'break' the
>  >  windows build, drop libltdl dependance and have
a wrapper that uses
>  >  native win32 API calls on windows and libltdl on
other platforms.
>
>
> I also think that Windows does not need libltdl... Is
there any reason to
>  use it at *NIX? I don't think .la files are used
anyway...
>  But this change can be done later...
>
>
>  >  Great work and I hope we can release the next
version with a new build
>  >  system and other generic improvements 
>
>
> Thanks!
>  Waiting for your test results.
>
> Alon.
>
_______________________________________________
opensc-devel mailing list
opensc-devellists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc
-devel
Re: OpenSC New Build System
user name
 2008-02-23 10:13:03 
On Thu, Feb 14, 2008 at 8:06 PM, Alon Bar-Lev
<alon.barlevgmail.com> wrote:
>  I don't like packages that enable optional features
automatically.
>  Users/packagers should choose what they wish and
enable dependency explicitly.

Exact. Automatic feature enabling can lead to
"problems".

For example someone rebuild all the Debian packages within
two
environments. One with as much as possible packages
installed and one
with as possible packages installed.

"938 packages produced different binary packages
according to debdiff. Of
those, 477 produced different Depends line (caused by some
features not
being explicitely enabled, but not being explicitely
disabled, usually)."

>  In this case, nsplugin seldom used anyway, and there
is not much sense in
>  enabling both pcsc and openct.
>  And if the user has for some strange reason openct
installed, does it mean
>  the result of OpenSC compilation should depend on it?
>
>  I truly think users are able to choose, and I am sure
distro packagers will
>  enable the features by the dependency of their
packages.

I have no doubts for "distro packagers". I am not
so sure for "users".
But if you (re)compile from source you may not be a
"simple" user any
more 

Bye

[1] http://lists.debian.org/debian-devel/2008/01/msg00869.
html

-- 
 Dr. Ludovic Rousseau
_______________________________________________
opensc-devel mailing list
opensc-devellists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc
-devel
Re: OpenSC New Build System
country flaguser name
Netherlands		 2008-02-25 08:07:41 
Hi Alon,

finally had some time to test your new build system on my
Windows XP box 
with both Cygwin and MingW installed.

./configure + make ran fine on cygwin; the resulting
pkcs11-tool (which 
is all I really use) was working fine
./configure ran on MingW after I added libtool to my MingW
installation.
make did *not* run on MingW because openssl was missing:

/bin/sh ../../libtool --tag=CC   --mode=compile gcc
-DHAVE_CONFIG_H -I. 
-I../.. -I../../src/include -I../../src/common 
-DWIN32_LEAN_AND_MEAN    
-L/usr/local/include  -fno-strict-aliasing -g -O2 -MT
pkcs15-piv.lo -MD 
-MP -MF .deps/pkcs15-piv.Tpo -c -o pkcs15-piv.lo
pkcs15-piv.c
 gcc -DHAVE_CONFIG_H -I. -I../.. -I../../src/include
-I../../src/common 
-DWIN32_LEAN_AND_MEAN -L/usr/local/include
-fno-strict-aliasing -g -O2 
-MT pkcs15-piv.lo -MD -MP -MF .deps/pkcs15-piv.Tpo -c
pkcs15-piv.c  
-DDLL_EXPORT -DPIC -o .libs/pkcs15-piv.o
pkcs15-piv.c:34:25: openssl/bio.h: No such file or
directory
pkcs15-piv.c:35:25: openssl/rsa.h: No such file or
directory
pkcs15-piv.c:36:25: openssl/pem.h: No such file or
directory

So building without openssl support does NOT seem to be
supported (which 
is fine, I guess, it's just that my very minimalistic MingW
install has 
no support for it, nor for readline or zlib).

cheers,

JJK



Alon Bar-Lev wrote:
> Hi!
> Waiting for your input 
> Alon
>
> On 2/14/08, Alon Bar-Lev <alon.barlevgmail.com> wrote:
>   
>> On Thu, Feb 14, 2008 at 7:01 PM, Martin Paljak
<martinpaljak.pri.ee> wrote:
>>  >  > 4. openct, pcsc and nsplugins features
are disabled by default.
>>  >  I don't think it's a good idea to by default
disable most used reader
>>  >  interfaces by default, as I'd expect most
software to behave nicely
>>  >  after a ./configure; make; make install
cycle. Have not tried it on
>>  >  Linux, but we might include some special
handling code for Mac as Mac
>>  >  is a pretty defined platform. a ./configure;
make; make install cycle
>>  >  could work on osx as well flawlessly.
>>
>>
>> I don't like packages that enable optional features
automatically.
>>  Users/packagers should choose what they wish and
enable dependency explicitly.
>>  In this case, nsplugin seldom used anyway, and
there is not much sense in
>>  enabling both pcsc and openct.
>>  And if the user has for some strange reason openct
installed, does it mean
>>  the result of OpenSC compilation should depend on
it?
>>
>>  I truly think users are able to choose, and I am
sure distro packagers will
>>  enable the features by the dependency of their
packages.
>>
>>
>>  >  > 9. Add export files to each library in
order to export only required
>>  >  > symbols. Windows native build may use
these files instead of scanning
>>  >  > objects' symbols.
>>  >  I should investigate this. While at it, we
could also 'break' the
>>  >  windows build, drop libltdl dependance and
have a wrapper that uses
>>  >  native win32 API calls on windows and
libltdl on other platforms.
>>
>>
>> I also think that Windows does not need libltdl...
Is there any reason to
>>  use it at *NIX? I don't think .la files are used
anyway...
>>  But this change can be done later...
>>
>>
>>  >  Great work and I hope we can release the
next version with a new build
>>  >  system and other generic improvements 
>>
>>
>> Thanks!
>>  Waiting for your test results.
>>
>> Alon.
>>
>>     

_______________________________________________
opensc-devel mailing list
opensc-devellists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc
-devel
Re: OpenSC New Build System
user name
 2008-02-25 09:56:15 
Hello,

Thank you for testing!

The pkcs15-piv.c should not have included openssl... I guess
this is
leftover from some other work.
Can you please try to remove these includes and continue
building?

Alon.

On 2/25/08, Jan Just Keijser <janjustnikhef.nl> wrote:
> Hi Alon,
>
>  finally had some time to test your new build system on
my Windows XP box
>  with both Cygwin and MingW installed.
>
>  ./configure + make ran fine on cygwin; the resulting
pkcs11-tool (which
>  is all I really use) was working fine
>  ./configure ran on MingW after I added libtool to my
MingW installation.
>  make did *not* run on MingW because openssl was
missing:
>
>  /bin/sh ../../libtool --tag=CC   --mode=compile gcc
-DHAVE_CONFIG_H -I.
>  -I../.. -I../../src/include -I../../src/common 
-DWIN32_LEAN_AND_MEAN
>  -L/usr/local/include  -fno-strict-aliasing -g -O2 -MT
pkcs15-piv.lo -MD
>  -MP -MF .deps/pkcs15-piv.Tpo -c -o pkcs15-piv.lo
pkcs15-piv.c
>   gcc -DHAVE_CONFIG_H -I. -I../.. -I../../src/include
-I../../src/common
>  -DWIN32_LEAN_AND_MEAN -L/usr/local/include
-fno-strict-aliasing -g -O2
>  -MT pkcs15-piv.lo -MD -MP -MF .deps/pkcs15-piv.Tpo -c
pkcs15-piv.c
>  -DDLL_EXPORT -DPIC -o .libs/pkcs15-piv.o
>  pkcs15-piv.c:34:25: openssl/bio.h: No such file or
directory
>  pkcs15-piv.c:35:25: openssl/rsa.h: No such file or
directory
>  pkcs15-piv.c:36:25: openssl/pem.h: No such file or
directory
>
>  So building without openssl support does NOT seem to
be supported (which
>  is fine, I guess, it's just that my very minimalistic
MingW install has
>  no support for it, nor for readline or zlib).
>
>
>  cheers,
>
>  JJK
>
>
>
>  Alon Bar-Lev wrote:
>
> > Hi!
>  > Waiting for your input 
>  > Alon
>  >
>  > On 2/14/08, Alon Bar-Lev <alon.barlevgmail.com> wrote:
>  >
>  >> On Thu, Feb 14, 2008 at 7:01 PM, Martin
Paljak <martinpaljak.pri.ee> wrote:
>  >>  >  > 4. openct, pcsc and nsplugins
features are disabled by default.
>  >>  >  I don't think it's a good idea to by
default disable most used reader
>  >>  >  interfaces by default, as I'd expect
most software to behave nicely
>  >>  >  after a ./configure; make; make
install cycle. Have not tried it on
>  >>  >  Linux, but we might include some
special handling code for Mac as Mac
>  >>  >  is a pretty defined platform. a
./configure; make; make install cycle
>  >>  >  could work on osx as well flawlessly.
>  >>
>  >>
>  >> I don't like packages that enable optional
features automatically.
>  >>  Users/packagers should choose what they wish
and enable dependency explicitly.
>  >>  In this case, nsplugin seldom used anyway,
and there is not much sense in
>  >>  enabling both pcsc and openct.
>  >>  And if the user has for some strange reason
openct installed, does it mean
>  >>  the result of OpenSC compilation should
depend on it?
>  >>
>  >>  I truly think users are able to choose, and
I am sure distro packagers will
>  >>  enable the features by the dependency of
their packages.
>  >>
>  >>
>  >>  >  > 9. Add export files to each
library in order to export only required
>  >>  >  > symbols. Windows native build may
use these files instead of scanning
>  >>  >  > objects' symbols.
>  >>  >  I should investigate this. While at
it, we could also 'break' the
>  >>  >  windows build, drop libltdl dependance
and have a wrapper that uses
>  >>  >  native win32 API calls on windows and
libltdl on other platforms.
>  >>
>  >>
>  >> I also think that Windows does not need
libltdl... Is there any reason to
>  >>  use it at *NIX? I don't think .la files are
used anyway...
>  >>  But this change can be done later...
>  >>
>  >>
>  >>  >  Great work and I hope we can release
the next version with a new build
>  >>  >  system and other generic improvements

>  >>
>  >>
>  >> Thanks!
>  >>  Waiting for your test results.
>  >>
>  >> Alon.
>  >>
>  >>
>
>
_______________________________________________
opensc-devel mailing list
opensc-devellists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc
-devel
Re: OpenSC New Build System
country flaguser name
Netherlands		 2008-02-25 09:59:40 
Hi Alon,

I already did and continued; turns out that my LIBTOOL setup
was/is 
still not OK (lots of missing -lltdl lines in the
makefiles). After 
correcting that one the build continued until
pkcs11-global.c, where it 
ran into problems with the gettimeofday function that MingW
does not 
seem to support. The compile error was something about an
unknown struct 
size:
  struct _timeb time_buf;

At that point I decided to scratch my entire Mingw/Msys
setup. I will 
re-install MingW+msys tools tomorrow and continue.

cheers,

JJK

Alon Bar-Lev wrote:
> Hello,
>
> Thank you for testing!
>
> The pkcs15-piv.c should not have included openssl... I
guess this is
> leftover from some other work.
> Can you please try to remove these includes and
continue building?
>
> Alon.
>
> On 2/25/08, Jan Just Keijser <janjustnikhef.nl> wrote:
>   
>> Hi Alon,
>>
>>  finally had some time to test your new build
system on my Windows XP box
>>  with both Cygwin and MingW installed.
>>
>>  ./configure + make ran fine on cygwin; the
resulting pkcs11-tool (which
>>  is all I really use) was working fine
>>  ./configure ran on MingW after I added libtool to
my MingW installation.
>>  make did *not* run on MingW because openssl was
missing:
>>
>>  /bin/sh ../../libtool --tag=CC   --mode=compile
gcc -DHAVE_CONFIG_H -I.
>>  -I../.. -I../../src/include -I../../src/common 
-DWIN32_LEAN_AND_MEAN
>>  -L/usr/local/include  -fno-strict-aliasing -g -O2
-MT pkcs15-piv.lo -MD
>>  -MP -MF .deps/pkcs15-piv.Tpo -c -o pkcs15-piv.lo
pkcs15-piv.c
>>   gcc -DHAVE_CONFIG_H -I. -I../..
-I../../src/include -I../../src/common
>>  -DWIN32_LEAN_AND_MEAN -L/usr/local/include
-fno-strict-aliasing -g -O2
>>  -MT pkcs15-piv.lo -MD -MP -MF .deps/pkcs15-piv.Tpo
-c pkcs15-piv.c
>>  -DDLL_EXPORT -DPIC -o .libs/pkcs15-piv.o
>>  pkcs15-piv.c:34:25: openssl/bio.h: No such file or
directory
>>  pkcs15-piv.c:35:25: openssl/rsa.h: No such file or
directory
>>  pkcs15-piv.c:36:25: openssl/pem.h: No such file or
directory
>>
>>  So building without openssl support does NOT seem
to be supported (which
>>  is fine, I guess, it's just that my very
minimalistic MingW install has
>>  no support for it, nor for readline or zlib).
>>
>>
>>  cheers,
>>
>>  JJK
>>
>>
>>
>>  Alon Bar-Lev wrote:
>>
>>     
>>> Hi!
>>>       
>>  > Waiting for your input 
>>  > Alon
>>  >
>>  > On 2/14/08, Alon Bar-Lev <alon.barlevgmail.com> wrote:
>>  >
>>  >> On Thu, Feb 14, 2008 at 7:01 PM, Martin
Paljak <martinpaljak.pri.ee> wrote:
>>  >>  >  > 4. openct, pcsc and nsplugins
features are disabled by default.
>>  >>  >  I don't think it's a good idea to
by default disable most used reader
>>  >>  >  interfaces by default, as I'd
expect most software to behave nicely
>>  >>  >  after a ./configure; make; make
install cycle. Have not tried it on
>>  >>  >  Linux, but we might include some
special handling code for Mac as Mac
>>  >>  >  is a pretty defined platform. a
./configure; make; make install cycle
>>  >>  >  could work on osx as well
flawlessly.
>>  >>
>>  >>
>>  >> I don't like packages that enable
optional features automatically.
>>  >>  Users/packagers should choose what they
wish and enable dependency explicitly.
>>  >>  In this case, nsplugin seldom used
anyway, and there is not much sense in
>>  >>  enabling both pcsc and openct.
>>  >>  And if the user has for some strange
reason openct installed, does it mean
>>  >>  the result of OpenSC compilation should
depend on it?
>>  >>
>>  >>  I truly think users are able to choose,
and I am sure distro packagers will
>>  >>  enable the features by the dependency of
their packages.
>>  >>
>>  >>
>>  >>  >  > 9. Add export files to each
library in order to export only required
>>  >>  >  > symbols. Windows native build
may use these files instead of scanning
>>  >>  >  > objects' symbols.
>>  >>  >  I should investigate this. While
at it, we could also 'break' the
>>  >>  >  windows build, drop libltdl
dependance and have a wrapper that uses
>>  >>  >  native win32 API calls on windows
and libltdl on other platforms.
>>  >>
>>  >>
>>  >> I also think that Windows does not need
libltdl... Is there any reason to
>>  >>  use it at *NIX? I don't think .la files
are used anyway...
>>  >>  But this change can be done later...
>>  >>
>>  >>
>>  >>  >  Great work and I hope we can
release the next version with a new build
>>  >>  >  system and other generic
improvements 
>>  >>
>>  >>
>>  >> Thanks!
>>  >>  Waiting for your test results.
>>  >>
>>  >> Alon.
>>  >>
>>  >>
>>
>>
>>     

_______________________________________________
opensc-devel mailing list
opensc-devellists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc
-devel
Re: OpenSC New Build System
user name
 2008-02-25 10:05:49 
1.libtool

How did you build libtool?
Have you added LTLIB_CFLAGS="-I<>"
LTLIB_LIBS="-L<> -lltdl" to configure?

2. mingw runtime should have gettimeofday... Please tell me
if it does
not work after your update.

Thanks!

On 2/25/08, Jan Just Keijser <janjustnikhef.nl> wrote:
> Hi Alon,
>
>  I already did and continued; turns out that my LIBTOOL
setup was/is
>  still not OK (lots of missing -lltdl lines in the
makefiles). After
>  correcting that one the build continued until
pkcs11-global.c, where it
>  ran into problems with the gettimeofday function that
MingW does not
>  seem to support. The compile error was something about
an unknown struct
>  size:
>   struct _timeb time_buf;
>
>  At that point I decided to scratch my entire
Mingw/Msys setup. I will
>  re-install MingW+msys tools tomorrow and continue.
>
>
>  cheers,
>
>  JJK
>
>  Alon Bar-Lev wrote:
>  > Hello,
>  >
>  > Thank you for testing!
>  >
>  > The pkcs15-piv.c should not have included
openssl... I guess this is
>  > leftover from some other work.
>  > Can you please try to remove these includes and
continue building?
>  >
>  > Alon.
>  >
>  > On 2/25/08, Jan Just Keijser <janjustnikhef.nl> wrote:
>  >
>  >> Hi Alon,
>  >>
>  >>  finally had some time to test your new build
system on my Windows XP box
>  >>  with both Cygwin and MingW installed.
>  >>
>  >>  ./configure + make ran fine on cygwin; the
resulting pkcs11-tool (which
>  >>  is all I really use) was working fine
>  >>  ./configure ran on MingW after I added
libtool to my MingW installation.
>  >>  make did *not* run on MingW because openssl
was missing:
>  >>
>  >>  /bin/sh ../../libtool --tag=CC  
--mode=compile gcc -DHAVE_CONFIG_H -I.
>  >>  -I../.. -I../../src/include
-I../../src/common  -DWIN32_LEAN_AND_MEAN
>  >>  -L/usr/local/include  -fno-strict-aliasing
-g -O2 -MT pkcs15-piv.lo -MD
>  >>  -MP -MF .deps/pkcs15-piv.Tpo -c -o
pkcs15-piv.lo pkcs15-piv.c
>  >>   gcc -DHAVE_CONFIG_H -I. -I../..
-I../../src/include -I../../src/common
>  >>  -DWIN32_LEAN_AND_MEAN -L/usr/local/include
-fno-strict-aliasing -g -O2
>  >>  -MT pkcs15-piv.lo -MD -MP -MF
.deps/pkcs15-piv.Tpo -c pkcs15-piv.c
>  >>  -DDLL_EXPORT -DPIC -o .libs/pkcs15-piv.o
>  >>  pkcs15-piv.c:34:25: openssl/bio.h: No such
file or directory
>  >>  pkcs15-piv.c:35:25: openssl/rsa.h: No such
file or directory
>  >>  pkcs15-piv.c:36:25: openssl/pem.h: No such
file or directory
>  >>
>  >>  So building without openssl support does NOT
seem to be supported (which
>  >>  is fine, I guess, it's just that my very
minimalistic MingW install has
>  >>  no support for it, nor for readline or
zlib).
>  >>
>  >>
>  >>  cheers,
>  >>
>  >>  JJK
>  >>
>  >>
>  >>
>  >>  Alon Bar-Lev wrote:
>  >>
>  >>
>  >>> Hi!
>  >>>
>  >>  > Waiting for your input 
>  >>  > Alon
>  >>  >
>  >>  > On 2/14/08, Alon Bar-Lev
<alon.barlevgmail.com> wrote:
>  >>  >
>  >>  >> On Thu, Feb 14, 2008 at 7:01 PM,
Martin Paljak <martinpaljak.pri.ee> wrote:
>  >>  >>  >  > 4. openct, pcsc and
nsplugins features are disabled by default.
>  >>  >>  >  I don't think it's a good
idea to by default disable most used reader
>  >>  >>  >  interfaces by default, as
I'd expect most software to behave nicely
>  >>  >>  >  after a ./configure; make;
make install cycle. Have not tried it on
>  >>  >>  >  Linux, but we might include
some special handling code for Mac as Mac
>  >>  >>  >  is a pretty defined
platform. a ./configure; make; make install cycle
>  >>  >>  >  could work on osx as well
flawlessly.
>  >>  >>
>  >>  >>
>  >>  >> I don't like packages that enable
optional features automatically.
>  >>  >>  Users/packagers should choose what
they wish and enable dependency explicitly.
>  >>  >>  In this case, nsplugin seldom used
anyway, and there is not much sense in
>  >>  >>  enabling both pcsc and openct.
>  >>  >>  And if the user has for some
strange reason openct installed, does it mean
>  >>  >>  the result of OpenSC compilation
should depend on it?
>  >>  >>
>  >>  >>  I truly think users are able to
choose, and I am sure distro packagers will
>  >>  >>  enable the features by the
dependency of their packages.
>  >>  >>
>  >>  >>
>  >>  >>  >  > 9. Add export files to
each library in order to export only required
>  >>  >>  >  > symbols. Windows native
build may use these files instead of scanning
>  >>  >>  >  > objects' symbols.
>  >>  >>  >  I should investigate this.
While at it, we could also 'break' the
>  >>  >>  >  windows build, drop libltdl
dependance and have a wrapper that uses
>  >>  >>  >  native win32 API calls on
windows and libltdl on other platforms.
>  >>  >>
>  >>  >>
>  >>  >> I also think that Windows does not
need libltdl... Is there any reason to
>  >>  >>  use it at *NIX? I don't think .la
files are used anyway...
>  >>  >>  But this change can be done
later...
>  >>  >>
>  >>  >>
>  >>  >>  >  Great work and I hope we can
release the next version with a new build
>  >>  >>  >  system and other generic
improvements 
>  >>  >>
>  >>  >>
>  >>  >> Thanks!
>  >>  >>  Waiting for your test results.
>  >>  >>
>  >>  >> Alon.
>  >>  >>
>  >>  >>
>  >>
>  >>
>  >>
>
>
_______________________________________________
opensc-devel mailing list
opensc-devellists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc
-devel
[1-10] [11-18]

about | contact  Other archives ( Real Estate discussion Medical topics )