I have set up my Ubuntu machine as described in
http://www.opensc-project.org/opensc/wiki/WindowsInstaller
Unfortunately I am getting the following error:
/bin/bash ../../libtool --tag=CC --mode=link i586-mingw32msvc-gcc
-DSIMCLIST_NO_DUMPRESTORE -fno-strict-aliasing --include=cardmod-mingw-com
Martin Paljak wrote:
> On Mar 25, 2010, at 21:32 , Douglas E. Engert wrote:
>> I realize that OpenSC does not a lot of Windows experts, what it does have
>> is a lot of Unix experts that try and do everything from Unix. But we do
>> have some windows expertise, as shown by the development of a CS
On Mar 25, 2010, at 21:32 , Douglas E. Engert wrote:
> I realize that OpenSC does not a lot of Windows experts, what it does have
> is a lot of Unix experts that try and do everything from Unix. But we do
> have some windows expertise, as shown by the development of a CSP.
I don't know what is the
Alon Bar-Lev wrote:
> On Thu, Mar 25, 2010 at 4:54 PM, Douglas E. Engert wrote:
>>
>> Alon Bar-Lev wrote:
>>> 1. I did not find any way to sign binaries outside windows.
>>>
>>> 2. OpenVPN compilation is required as the OpenSSL is dynamically
>>> loaded by both projects causing one to segfault i
On Thu, Mar 25, 2010 at 4:54 PM, Douglas E. Engert wrote:
>
>
> Alon Bar-Lev wrote:
>>
>> 1. I did not find any way to sign binaries outside windows.
>>
>> 2. OpenVPN compilation is required as the OpenSSL is dynamically
>> loaded by both projects causing one to segfault if not compiled the
>> sam
Alon Bar-Lev wrote:
> 1. I did not find any way to sign binaries outside windows.
>
> 2. OpenVPN compilation is required as the OpenSSL is dynamically
> loaded by both projects causing one to segfault if not compiled the
> same. Hence, you cannot use OpenSC PKCS#11 with OpenVPN without this.
> T
On Mar 25, 2010, at 11:51 , Kalev Lember wrote:
> On 03/25/2010 09:26 AM, Martin Paljak wrote:
>> On Mar 24, 2010, at 21:55 , Alon Bar-Lev wrote:
>>> I just provide them because after I rewrote the opensc build
>>> system, there was no reason to maintain parallel build system for
>>> windows only,
On 03/25/2010 09:26 AM, Martin Paljak wrote:
> On Mar 24, 2010, at 21:55 , Alon Bar-Lev wrote:
>> I just provide them because after I rewrote the opensc build
>> system, there was no reason to maintain parallel build system for
>> windows only, and the windows build was unmaintained anyway.
> Right
On Thu, Mar 25, 2010 at 10:14 AM, Martin Paljak wrote:
>> 2. OpenVPN compilation is required as the OpenSSL is dynamically
>> loaded by both projects causing one to segfault if not compiled the
>> same. Hence, you cannot use OpenSC PKCS#11 with OpenVPN without this.
>> This is optional anyway, use
On Mar 25, 2010, at 10:08 , Alon Bar-Lev wrote:
> 1. I did not find any way to sign binaries outside windows.
OK.
> 2. OpenVPN compilation is required as the OpenSSL is dynamically
> loaded by both projects causing one to segfault if not compiled the
> same. Hence, you cannot use OpenSC PKCS#11 w
Why not just host MingGW on the site and create installs on-line?
I have recently used a "Cloud" Compiler and it is nice to not
have to mess with setups and stuff.
Just an idea.
Anders
Martin Paljak wrote:
> Hi,
>
> On Mar 24, 2010, at 21:55 , Alon Bar-Lev wrote:
>> I try to avoid wine as much
1. I did not find any way to sign binaries outside windows.
2. OpenVPN compilation is required as the OpenSSL is dynamically
loaded by both projects causing one to segfault if not compiled the
same. Hence, you cannot use OpenSC PKCS#11 with OpenVPN without this.
This is optional anyway, user can i
Hi,
On Mar 24, 2010, at 21:55 , Alon Bar-Lev wrote:
> I try to avoid wine as much as I can.
I'm not very fond of it either but it is something that makes Windows hating
Linux users tolerate the beast :)
> Anyway, I have no feeling for the windows binaries... I do not use the
> output anyway :)
I
I try to avoid wine as much as I can.
Anyway, I have no feeling for the windows binaries... I do not use the
output anyway :)
I just provide them because after I rewrote the opensc build system,
there was no reason to maintain parallel build system for windows
only, and the windows build was unma
On Mar 24, 2010, at 16:04 , François Leblanc wrote:
>> The download link for i386 installer is included in the wiki page together
>> with some comments and questions. Unlike NSIS >InnoSetup is a win32
>> application but I have successfully used it from wine.
> It's the main reason why we choice
>The download link for i386 installer is included in the wiki page together
>with some comments and questions. Unlike NSIS >InnoSetup is a win32
>application but I have successfully used it from wine.
It's the main reason why we choice NSIS, I think using wine to build installer
a bit complic
Hello,
build svn recently grew a NSIS installer script.
As an alternative, here's a try with the InnoSetup utility, slightly customized
from an installer version for OpenSC that has been used for several years in
Estonia. It provides IMHO (at least now) a smoother and more familiar
experience
17 matches
Mail list logo
