[CIG-SHORT] Adding to the libraries

[Matthew Knepley]

On Fri, Aug 4, 2017 at 2:38 PM, Ehsan Haghighat <ehsanh at mit.edu> wrote:

> Hi Brad,
>
> What I do is similar to what is briefed in the document. However, the
> compilation process is still not very clear to me.
>
> When I call ‘make’ or ‘make install’ it does not find the changes in
> subfolder; that’s why I call “make pylith” and then it rebuilds the pylith.
> However, it will not call automake or swig. Any suggestions here?
>

I cannot know exactly what you are doing from this description. First, show
exactly what you typed. Second, show the output.

   Matt


> Ehsan
>
>
>
> > On Aug 4, 2017, at 1:38 PM, Brad Aagaard <baagaard at usgs.gov> wrote:
> >
> > Ehsan,
> >
> > Please see the example for adding a material in the templates/materials
> directory discussed in Section 9.2 in the PyLith v2.2.0 manual.
> >
> > automake should run automatically when you run "make" in the build
> directory; you should not need to do it separately. Note that we have not
> been successful getting PyLith to run properly with SWIG versions 3.0.3 and
> later. See https://github.com/geodynamics/pylith/issues/28.
> >
> > I highly recommend initially following the templates/materials example.
> If you would like to contribute the material back to PyLith, please fork
> from the PyLith Git repository and make a pull request.
> >
> > Regards,
> > Brad
> >
> > On 8/4/17 8:19 AM, Ehsan Haghighat wrote:
> >> I built once from the source. After that, I added a new material to
> >> libsrc/modulesrc/pylith, similar to other materials. Then I just call
> >> “make pylith” form “build/pylith” folder. Where should I call ‘make’ and
> >> ‘make install”?
> >>
> >>
> >>
> >>> On Aug 4, 2017, at 11:15 AM, Matthew Knepley <knepley at rice.edu
> >>> <mailto:knepley at rice.edu>> wrote:
> >>>
> >>> On Fri, Aug 4, 2017 at 8:39 AM, Ehsan Haghighat <ehsanh at mit.edu
> >>> <mailto:ehsanh at mit.edu>> wrote:
> >>>
> >>>    Hi,
> >>>
> >>>    I would like to extended/add some libraries to the PyLith, for
> >>>    instance a new material. Searching to find out how another
> >>>    material is implemented, I realized I need to run automake again
> >>>    to correctly reflect changes in Makefile.am. What about the
> >>>    materials_wrap.cxx? How this can be recreated? I am using the
> >>>    “swig -python materials.i”, however the generated wrapper looks
> >>>    very different from the original one. Can you please confirm the
> >>>    steps I am taking? Is there any documents to describe the steps to
> >>>    add libraries to the pylith.
> >>>
> >>>
> >>> If you want to do new development, you should be building from source.
> >>> Are you? If so, you just need to do 'make' and 'make install'.
> >>>
> >>>   Matt
> >>>
> >>>
> >>>    Thanks,
> >>>    Ehsan
> >>>
> >>>
> >>>    _______________________________________________
> >>>    CIG-SHORT mailing list
> >>>    CIG-SHORT at geodynamics.org <mailto:CIG-SHORT at geodynamics.org>
> >>>    http://lists.geodynamics.org/cgi-bin/mailman/listinfo/cig-short
> >>>    <http://lists.geodynamics.org/cgi-bin/mailman/listinfo/cig-short>
> >>>
> >>>
> >>> _______________________________________________
> >>> CIG-SHORT mailing list
> >>> CIG-SHORT at geodynamics.org <mailto:CIG-SHORT at geodynamics.org>
> >>> http://lists.geodynamics.org/cgi-bin/mailman/listinfo/cig-short
> >>
> >
> > _______________________________________________
> > CIG-SHORT mailing list
> > CIG-SHORT at geodynamics.org
> > http://lists.geodynamics.org/cgi-bin/mailman/listinfo/cig-short
>
>
> _______________________________________________
> CIG-SHORT mailing list
> CIG-SHORT at geodynamics.org
> http://lists.geodynamics.org/cgi-bin/mailman/listinfo/cig-short
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.geodynamics.org/pipermail/cig-short/attachments/20170804/426d4352/attachment.html>