[90985] trunk/dports/science

Ryan Schmidt ryandesign at macports.org
Wed Mar 21 09:08:57 PDT 2012


On Mar 21, 2012, at 11:00, Leo Singer wrote:

>> The build process currently hides the actual compile commands from us, making it not totally easy to see whether we've succeeded. If you can make the build output more verbosely that would be great.
> 
> By build process, do you mean the MacPorts build process, or healpix's Makefiles?  healpix has a homebrew build system with two quirks: an interactive configure script (takes keystrokes instead of command line arguments) and handwritten Makefiles that produce output resembling Automake's silent build setting.

I meant healpix's Makefiles. If they have a setting for turning off these silent rules, and using "normal" verbose rules, let's use it. And if they don't have a setting for that, could you suggest they add one?


> Any other suggestions for revision 1?

It's probably fine not to increase the revision just for this change. healpix has a dependency (cfitsio); if the user had chosen a non-standard build_arch, cfitsio would have been built for that other build_arch, but healpix would then fail to build. So increasing the revision (thereby forcing a rebuild) would not benefit anyone.

I'd also still check whether adding a universal variant (i.e. by adding the line "variant universal {}" on a line before you invoke [get_canonical_archs]) works.


> (As to the compiler on Tiger, I think that in the long run I ought to introduce an OpenMP variant so that it is possible to build healpix with compilers that don't support OpenMP.)

If you come up with something that works well, let me know; the ImageMagick port needs this as well.



More information about the macports-dev mailing list