Hi Jay,

I took a quick look and I saw that your package is built on top of LAMMPS. 
Unfortunately LAMMPS is one of an ever-shortening list of applications not yet 
supported by EB. Specifically for LAMMPS there have been a few attempts but 
nothing in the main codebase yet:
https://github.com/hpcugent/easybuild-easyblocks/pull/833

I also saw that you probably have quite a few dependencies (when I tried to 
compile VTK jumped out). Your particular case might take a bit of effort to get 
working. You need to do a bit of Makefile editing too (what is contained in 
Makefile.cirrus for example?).

Alan



On 20 March 2017 at 17:44, Kenneth Hoste 
<[email protected]<mailto:[email protected]>> wrote:
Hello Jay,

On 20/03/2017 16:31, [email protected]<mailto:[email protected]> wrote:
Hello,

I'm an application engineer currently using Lmod on a RHEL 6.x cluster.  I am
very interested in using EB to migrate some of the codes that I manage that
have a current build process.

We have installed EB 3.1.0 and I am trying to migrate my first code.  I have
an existing makefile and a build script.  I have looked at the easyconfig list
but my code is not listed.

Can someone point me to an example that I might be able to reference to get my
code (LIGGGHTS) up and running?

I managed about 36 other codes that are mixture or COTS and Opensource.  I am
very interested on working on getting as many as I can into EB.

The first aspect to take into account is which build & install procedure the 
software uses, since that determines which (generic) easyblock you can use.
An overview of the available generic easyblocks is available at 
http://easybuild.readthedocs.io/en/latest/version-specific/generic_easyblocks.html.

A high-level overview of what needs to go in an easyconfig file is available at 
http://easybuild.readthedocs.io/en/latest/Writing_easyconfig_files.html .

If the software doesn't follow a standard procedure, you may need to implement 
an accompanying easyblock as well, see 
http://easybuild.readthedocs.io/en/latest/Implementing-easyblocks.html .

As Jack already mentioned, the easyconfigs we already have can serve as 
examples where relevant.
If you're looking for examples of a particular easyblock, the search function 
in the easyconfigs repository may come in handy, see 
https://github.com/hpcugent/easybuild-easyconfigs/search?utf8=%E2%9C%93&q=configuremake
 .

While composing an easyconfig file, the extended dry run feature is quite 
useful, since you can get a quick idea of the build & install procedure that 
EasyBuild will be running using the provided easyconfig file, see 
http://easybuild.readthedocs.io/en/latest/Extended_dry_run.html .

And of course, if the software is publicly available, consider contributing 
back the working easyconfig files, see 
http://easybuild.readthedocs.io/en/latest/Contributing.html#contributing-easyconfig-files
 .

I hope this gives you enough the get started, don't hesitate to let us know if 
you have any questions!


regards,

Kenneth




Thanks,

Jay Blair
Sr. Applications Engineer |  ASRC Federal Data Solutions
P&G HPC Account
o 513-698-7880 m 937-902-5719




--
Dr. Alan O'Cais
E-CAM Software Manager
Juelich Supercomputing Centre
Forschungszentrum Juelich GmbH
52425 Juelich, Germany

Phone: +49 2461 61 5213
Fax: +49 2461 61 6656
E-mail: [email protected]<mailto:[email protected]>
WWW:    http://www.fz-juelich.de/ias/jsc/EN


------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------
Forschungszentrum Juelich GmbH
52425 Juelich
Sitz der Gesellschaft: Juelich
Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498
Vorsitzender des Aufsichtsrats: MinDir Dr. Karl Eugen Huthmacher
Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender),
Karsten Beneke (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt,
Prof. Dr. Sebastian M. Schmidt
------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------

Reply via email to