OpenSC Build System

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

OpenSC Build System

Michael Heydemann
Hello OpenSC Development Team,

I am not sure who has knowledge about the build system,
therefore I post at the list.
I am trying to build and package OpenSC for Windows 7 32bit and 64bit.
Therefore I followed the official instructions reachable in the internet.

First I tried to build in a Windows 7 Environment.
Somehow I could not get this done.
The ./bootstap freezes the command line when libtoolize starts working.
And downloading many Gigs for the necessary tooling felt not quite handy.

As I am more a Linux friend, I tried with Ubuntu 14.04.1 64bit.
I cross-compiled successfully for Win 32 and Win 64.
But I am not sure, if the binaries will run.
This is what I have done:

************************************************************************************************************************
sudo apt-get install wine gcc-mingw-w64-x86-64 docbook-xsl autoconf automake libtool libpcsclite-dev patch nsis git

git clone https://github.com/OpenSC/OpenSC.git

libopensc.exports -> remove iasecc_sdo_encode_update_field (otherwise does not link)

./bootstrap

32 Bit:
./configure --prefix=/usr/i686-w64-mingw32 --host=i686-w64-mingw32 --build=x86_64-linux --disable-doc

64 Bit:
./configure --prefix=/usr/x86_64-w64-mingw32 --host=x86_64-w64-mingw32 --build=x86_64-linux --disable-doc

make
************************************************************************************************************************

Now, I have several DLL and EXE files distributed  in the /src/* directories.
The /win32 directory seems to be outdated, because the scrips try to checkout from an non-existing svn server.

I wonder how to get all the stuff in an EXE or MSI?
How is this working on the continues integration server?

Kind Regards,
Michael
------------------------------------------------------------------------------
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
http://p.sf.net/sfu/gigenet
_______________________________________________
Opensc-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/opensc-devel

smime.p7s (4K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: OpenSC Build System

Viktor Tarasov-3
Hi,

On Thu, Jan 22, 2015 at 7:35 PM, Michael Heydemann <[hidden email]> wrote:
Hello OpenSC Development Team,

I am not sure who has knowledge about the build system,
therefore I post at the list.
I am trying to build and package OpenSC for Windows 7 32bit and 64bit.
Therefore I followed the official instructions reachable in the internet.

First I tried to build in a Windows 7 Environment.
Somehow I could not get this done.
The ./bootstap freezes the command line when libtoolize starts working.
And downloading many Gigs for the necessary tooling felt not quite handy.

As I am more a Linux friend, I tried with Ubuntu 14.04.1 64bit.
I cross-compiled successfully for Win 32 and Win 64.
But I am not sure, if the binaries will run.
This is what I have done:

************************************************************************************************************************
sudo apt-get install wine gcc-mingw-w64-x86-64 docbook-xsl autoconf automake libtool libpcsclite-dev patch nsis git

git clone https://github.com/OpenSC/OpenSC.git

libopensc.exports -> remove iasecc_sdo_encode_update_field (otherwise does not link)

./bootstrap

32 Bit:
./configure --prefix=/usr/i686-w64-mingw32 --host=i686-w64-mingw32 --build=x86_64-linux --disable-doc

64 Bit:
./configure --prefix=/usr/x86_64-w64-mingw32 --host=x86_64-w64-mingw32 --build=x86_64-linux --disable-doc

make
************************************************************************************************************************

Now, I have several DLL and EXE files distributed  in the /src/* directories.
The /win32 directory seems to be outdated, because the scrips try to checkout from an non-existing svn server.

I wonder how to get all the stuff in an EXE or MSI?
How is this working on the continues integration server?

It's built on Windows platforms using the MSDN. The source package is taken from the builld on Linux platform, created with "make dist".
MSI is created with "WiX Toolset". 



Kind Regards,
Michael
------------------------------------------------------------------------------
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
http://p.sf.net/sfu/gigenet
_______________________________________________
Opensc-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/opensc-devel



------------------------------------------------------------------------------
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
http://p.sf.net/sfu/gigenet
_______________________________________________
Opensc-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/opensc-devel
Reply | Threaded
Open this post in threaded view
|

Re: OpenSC Build System

Douglas E Engert


On 1/23/2015 4:36 AM, Viktor Tarasov wrote:

> Hi,
>
> On Thu, Jan 22, 2015 at 7:35 PM, Michael Heydemann <[hidden email] <mailto:[hidden email]>> wrote:
>
>     Hello OpenSC Development Team,
>
>     I am not sure who has knowledge about the build system,
>     therefore I post at the list.
>     I am trying to build and package OpenSC for Windows 7 32bit and 64bit.
>     Therefore I followed the official instructions reachable in the internet.

Which instructions?

   https://github.com/OpenSC/OpenSC/wiki/OpenSC-Windows-installer

   https://github.com/OpenSC/OpenSC/wiki/OpenSC-Components-Build
(The above looks out of date...)

If you really want to see what is going on, look at Jenkins builds for a pull request.

    https://github.com/OpenSC/OpenSC/pulls

Find one with a green check For example:

    https://github.com/OpenSC/OpenSC/pull/363

Find the "All is well — Merged build finished.   details" line near the bottom,
click on details.

Look for Sub project builds: OpenSC-pr-win32 and OpenSC-pr-win64
Click on number after one of the above, for example:
   https://opensc.fr/jenkins/job/OpenSC-pr-win64/25/console
Then click on "Full Log":
   https://opensc.fr/jenkins/job/OpenSC-pr-win64/25/consoleFull

What you can't see (or I have not figured out how to see it) are the .bat files that makes all the calls:
  cmd /c call C:\Users\admin\AppData\Local\Temp\hudson7078456097108383939.bat
  C:\Users\admin\AppData\Local\Temp\hudson7719038757221935485.bat
But I thing all the commands are shown.


Note up front, two artifacts are copied from "OpenSC-pr-ubuntu"
Is this the tar file created on Ubuntu from  ./bootstrap; make dist

The combined with what Viktor said in his response might help.

So one way to get a test version is to get Jenkins to build with your changes.
submit a pull request to OpenSC, that causes Jenkins to compile it, then download the MSI files.


>
>     First I tried to build in a Windows 7 Environment.
>     Somehow I could not get this done.
>     The ./bootstap freezes the command line when libtoolize starts working.
>     And downloading many Gigs for the necessary tooling felt not quite handy.
>
>     As I am more a Linux friend, I tried with Ubuntu 14.04.1 64bit.
>     I cross-compiled successfully for Win 32 and Win 64.
>     But I am not sure, if the binaries will run.
>     This is what I have done:
>
>     ************************************************************************************************************************
>     sudo apt-get install wine gcc-mingw-w64-x86-64 docbook-xsl autoconf automake libtool libpcsclite-dev patch nsis git
>
>     git clone https://github.com/OpenSC/OpenSC.git
>
>     libopensc.exports -> remove iasecc_sdo_encode_update_field (otherwise does not link)
>
>     ./bootstrap
>
>     32 Bit:
>     ./configure --prefix=/usr/i686-w64-mingw32 --host=i686-w64-mingw32 --build=x86_64-linux --disable-doc
>
>     64 Bit:
>     ./configure --prefix=/usr/x86_64-w64-mingw32 --host=x86_64-w64-mingw32 --build=x86_64-linux --disable-doc
>
>     make
>     ************************************************************************************************************************
>
>     Now, I have several DLL and EXE files distributed  in the /src/* directories.
>     The /win32 directory seems to be outdated, because the scrips try to checkout from an non-existing svn server.
>
>     I wonder how to get all the stuff in an EXE or MSI?
>     How is this working on the continues integration server?
>
>
> It's built on Windows platforms using the MSDN. The source package is taken from the builld on Linux platform, created with "make dist".
> MSI is created with "WiX Toolset".
>
>
>
>     Kind Regards,
>     Michael
>     ------------------------------------------------------------------------------
>     New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
>     GigeNET is offering a free month of service with a new server in Ashburn.
>     Choose from 2 high performing configs, both with 100TB of bandwidth.
>     Higher redundancy.Lower latency.Increased capacity.Completely compliant.
>     http://p.sf.net/sfu/gigenet
>     _______________________________________________
>     Opensc-devel mailing list
>     [hidden email] <mailto:[hidden email]>
>     https://lists.sourceforge.net/lists/listinfo/opensc-devel
>
>
>
>
> ------------------------------------------------------------------------------
> New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
> GigeNET is offering a free month of service with a new server in Ashburn.
> Choose from 2 high performing configs, both with 100TB of bandwidth.
> Higher redundancy.Lower latency.Increased capacity.Completely compliant.
> http://p.sf.net/sfu/gigenet
>
>
>
> _______________________________________________
> Opensc-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/opensc-devel
>

--

  Douglas E. Engert  <[hidden email]>


------------------------------------------------------------------------------
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
http://p.sf.net/sfu/gigenet
_______________________________________________
Opensc-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/opensc-devel