August 2009 - SmartcardServices-Dev

Building using darwinbuild
by William Siegrist 23 Jan '10

23 Jan '10

I wanted to report on recent work done to make SmartCardServices buildable outside of Apple. You can now build the Tokend and SmartCardServices projects that shipped with 10.5.6 and 10.5.7 using darwinbuild. We had to add a patch that adds includes that were needed to build with CFLite, but otherwise the source is unmodified. Darwinbuild helps by automatically putting roots in a chroot that have the private headers you need. First, install darwinbuild ( http://darwinbuild.macosforge.org/ ), then: # create a build environment $ mkdir ~/9J61 && cd ~/9J61 $ sudo darwinbuild -init 9J61 # build stuff $ sudo darwinbuild SmartCardServices $ sudo darwinbuild Tokend That's it. In this example, everything is kept in a chroot under ~/ 9J61/BuildRoot/. You can use /usr/local/share/darwinbuild/ packageRoots to produce a tarball in ~/9J61/Packages/ of your build. You can use /usr/local/bin/darwinup to install it like so: $ sudo darwinup install ~/9J61/Packages/SmartCardServices.root.tar.gz ... and to uninstall $ sudo darwinup list $ sudo darwinup uninstall <uuid from the list output above> -Bill

3 5

Re: [SmartcardServices-Dev] Proposal for patching and maintaining the main source repository
by Garth Cummings 21 Oct '09

21 Oct '09

Hi, > And now darwinbuild can handle subversion working copies (as of rev > 544). I made the necessary modifications to the SmartcardCCID.plist > already, so now the entire workflow is down to: > > $ mkdir ~/ccid && cd ~/ccid > $ darwinbuild -init http://svn.macosforge.org/repository/smartcardservices/trunk/SmartcardCCID/… > $ darwinbuild SmartcardCCID This is great, but I get a build failure because there's apparently supposed to be a ccid/ccid directory: > Build log begins here: > > the proj is: ccid > (cd /SourceCache/SmartcardCCID/SmartcardCCID-1/ccid/ccid && ./MacOSX/ > configure --no-configure --disable-opensc ) > /bin/sh: line 0: cd: /SourceCache/SmartcardCCID/SmartcardCCID-1/ccid/ > ccid: No such file or directory > make: *** [install] Error 1 > +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > +++++++++++ > BUILD TIME: 0h 0m 0s > EXIT STATUS: 2 Maybe the install target should be dependent on the installsrc target in the Makefile? --gc ____________________________________________________________________ Garth Cummings gcummings(a)apple.com Sr. Software Engineer Apple Developer Technical Support <http://developer.apple.com/technicalsupport>

3 2

Proposal for patching and maintaining the main source repository
by William Siegrist 09 Aug '09

09 Aug '09

Getting the source in the subversion repo to build is a little trickier that just checking it out and using Xcode. It is basically identical to what was released with 9J61, which means it requires a lot of extra stuff that is not in your retail copy of Leopard. So what I am proposing is using darwinbuild to continue patching and building the source. I think it'll be the easiest way to take contributions back from the public and keep things building. If you have another suggestion, please let us know. The SmartCardServices project on Mac OS Forge would provide a plist, a set of patches, and (optionally) a tarball of source. A typical workflow that contributes back a patch for SmartCardServices would look like: # download the custom plist with curl or svn $ curl -LO http://svn.macosforge.org/repository/smartcardservices/trunk/plists/scs_leo… # make a new environment $ mkdir ~/scsleo && cd ~/scsleo $ sudo darwinbuild -init ~/scs_leopard.plist ... watch darwinbuild fetch the other plists you need ... $ sudo darwinbuild SmartCardServices ... watch it load all the roots you need ... ... watch it build ... # save the original source to diff later $ cd BuildRoot/SourceCache/SmartCardServices/ $ cp -R SmartCardServices-34733 SmartCardServices-34733.orig $ cd ../../.. # make your changes $ vi BuildRoot/SourceCache/SmartCardServices/SmartCardServices-34733/ path/to/file.c ... edit more files as needed ... # try to build your changes # using -nosource is important as it tells darwinbuild to not overwrite your changes to the source cache $ darwinbuild -nosource SmartCardServices ... watch it build your modified source ... ... edit more files, repeat as necessary ... # create your patchfile $ cd BuildRoot/SourceCache/SmartCardServices/SmartCardServices-34733/ $ diff -ru ../SmartCardServices-34733.orig ./ > ~/ SmartCardServices_MyFix.patch Then you submit the patch to the project. When accepted, the project committers would need to modify the plist to include that patch filename and commit the new plist plus patch to the subversion repository (perhaps under trunk/plists and trunk/patches). Then the next person to perform the above workflow gets the new plist which uses the new patch. Note that this method does not use the source in the subversion repo. What could happen periodically is all of the patches get applied to the subversion repo and a new tarball is generated. Then the plist is modified to point to the new tarball and no patches. If you have any suggestions or opinions about working on the source in this manner, let us know. Thanks -Bill

2 8