On 30 Mar 2013, at 14:55, Fotis Georgatos wrote: >> PS: The CUDA support we hoped to include in EasyBuild v1.3.0 has been >> delayed to a future release, mainly due to time constraints. > > This is not so bad as it sounds: > > * CUDA toolchain *IS* now included, only the combo goolfc toolchain is > missing; > fyi. Adam's advice has helped us produce quite decent CUDA support, we just > need > to "packetize" it in toolchain now so that it is of generic use for composite > builds. > fi. the 1st file seen in PR #165, should do the right thing (TM) or, it used > to ;-)
There's more to it than just producing a decent CUDA module. See https://github.com/boegel/easybuild-framework/tree/goolfc_support for the work-in-progress on goolfc support in the framework. > ps1. shouldn't the version suffix of CUDA be reflected in the filename? Yes, and that renaming fix is part of https://github.com/hpcugent/easybuild-easyconfigs/pull/191. I opened a separate PR to fix that for v1.3.0, which is important imho, see https://github.com/hpcugent/easybuild-easyconfigs/pull/195 . > ps2. we have quite a few lib* packages that ended up in "devel" category... > let's fix it? Which ones? Can you open a PR to the v1.3.0.x branch to fix them? K.
