Shibboleth Developers

[Peter Williams <>]

I'm going to take back my cygwin build flaw comment: the Shib2 packagesuite is mostly building fine, on a second try. One can assume User error for previous flaws. ( I have not done this kind of Unix build for a decade or more. One the one hand the tools have all changed; on the other hand they have not. Its just more esoteric scripting than ever.)

 

Im punting on being specific about the versions of packages I linking. Im just hoping that the cygwin latest openssl, cygwin latest default threading library, my chosen curl package version etc. are all compatible.

 

On Cygwin, the biggest hurdle so far has been having the build scripts recognize log4shib-config, which doesnt seem to quite make install properly. Installing it manually, as binscripts, didnt seem to help the consuming ./configure scripts much. But, Ill heep trying, again and again; user error to be assumed from hereonin.

 

Having built what I can with MSVC9, im hoping cygwin tools can compile the fastcgi featureset of Shib. Legacy libraries like iostream.h tend to stay around for ever, in Unix land.

 

._________________________
Peter Williams

---

From: Peter Williams
Sent: Mon 4/14/2008 8:35 PM
To:
Subject: RE: OpenID2 to SAML2 to SAML1.1 ... to Shib, anyone?

I've managed to build about 60% of the Win32 code for Shib2.0.0 SP, using msvc9 tool chain. This includes log4shib, libcurl (pre-packaged), openssl (pre-packaged), xerces, xmlsec. Some of these packages but not all, also build cleanly using cygwin. Various manual fiddles were required to make