Hello Kenneth, the keypoint is that I need to access the current working directory in this build_step procedure. I thought it was stored in the path variable but now figured out that I can access it with 'os.getcwd()'. The software I currently install is a bit tricky since it is a tarball that contains three tarballs in which each of them a 'make all' needs to be executed. I now extract and build those tarballs all in the build_step. Not the most elegant solution but it works :-)
Oliver -- Oliver Stolpe Bioinformatics Core Unit Berlin Institute of Health ________________________________ From: [email protected] [[email protected]] on behalf of Kenneth Hoste [[email protected]] Sent: Tuesday, September 29, 2015 1:11 PM To: [email protected] Subject: Re: [easybuild] EasyBlock MakeCp build_step path parameter Hi Oliver, On 29/09/15 12:12, Stolpe, Oliver wrote: Hello list, currently I am writing my own EasyBlock inherting from MakeCp (which itself inherits from ConfigureMake). ConfigureMake has the method 'build_step' which I am overriding. It accepts three parameters, build_step(self, verbose=False, path=None). I wonder where the path is set. I assumed it would be the path to the folder of the extracted tarball. But it is still set to None if I execute my script. In all the easyconfigs using this generic, no such variable is set, so I wonder heavily where it comes from. The optional parameter path=None in ConfigureMake.build_step is only there so that easyblocks that derive from ConfigureMake *can* specify an alternate value for 'path' if required, when calling out to ConfigureMake's build_step. At first sight, only the NAMD easyblock is currently doing that, see https://github.com/hpcugent/easybuild-easyblocks/blob/master/easybuild/easyblocks/n/namd.py#L118 . So, I don't think you need to worry about this too much in your own easyblock, unless you're writing another generic easyblock on top of MakeCp/ConfigureMake that may be used as a base for yet another easyblock where you may have to specify a custom value for the 'path' parameter (although I don't know what you're doing in build_step specifically). regards, Kenneth
