[MacPorts] #41804: cryptlib @3.4.1 add universal variant

[MacPorts]

#41804: cryptlib @3.4.1 add universal variant
--------------------------+--------------------------------
  Reporter:  david@…      |      Owner:  macports-tickets@…
      Type:  enhancement  |     Status:  new
  Priority:  Normal       |  Milestone:
 Component:  ports        |    Version:  2.2.1
Resolution:               |   Keywords:
      Port:  cryptlib     |
--------------------------+--------------------------------
Changes (by ryandesign@…):

 * cc: ryandesign@… (added)
 * keywords:  i386 =>


Comment:

 I did try to make a universal variant for cryptlib 2 years ago, but its
 makefile says:

 {{{
 #                       If you want to build a universal binary you can
 use the a command
 #                       a bit like the following (with the path to your
 SDK install
 #                       substituted for the one in the command-lines
 below):
 #
 # make LDFLAGS='-isysroot /Developer/SDKs/MacOSX10.5.sdk' CFLAGS='-c
 -isysroot \
 # /Developer/SDKs/MacOSX10.5.sdk -Os -mmacosx-version-min=10.5 -arch ppc
 -arch \
 # ppc64 -arch i386 -arch x86_64 -DOSX_UNIVERSAL_BINARY -D__UNIX__ -DNDEBUG
 -I.'
 #
 # make LDFLAGS='-arch i386 -arch x86_64' CFLAGS='-c -O2 -mmacosx-version-
 min=10.5 \
 # -arch i386 -arch x86_64 -D__UNIX__ -DNDEBUG -I.'
 #
 #                       This will also required adding $(LDFLAGS) to the
 dylib build rule,
 #                       and removing LDFLAGS="-object -s" from the overall
 OS X build rule.
 #
 #                       This build method is rather trouble-prone because
 the low-level
 #                       crypto code has to configure itself for CPU
 endianness and word
 #                       size for the algorithms that require low-level bit
 fiddling, and
 #                       uses different code strategies depending on the
 CPU architecture
 #                       and bit width.  This single-pass build for
 multiple architectures
 #                       often causes problems, and you're more or less on
 your own if you
 #                       decide to try it.
 }}}

 So to avoid these problems we have to use the muniversal portgroup, but
 that adds complications of its own.

-- 
Ticket URL: <https://trac.macports.org/ticket/41804#comment:1>
MacPorts <http://www.macports.org/>
Ports system for OS X