GitHub user nwellnhof opened a pull request:

    https://github.com/apache/lucy-clownfish/pull/69

    Perl build with make

    Create a static library of the core C code using the Makefile generated by 
charmonizer and link the result with the compiled XS code. This makes it 
possible to speed up the build of the Perl runtime by running make jobs in 
parallel. It also centralizes the selection of C source files which becomes 
important when building multiple binaries.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/nwellnhof/lucy-clownfish perl_build_with_make

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/lucy-clownfish/pull/69.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #69
    
----
commit 962e2e59e87e2a9d73fb1f161b68baa88287fed9
Author: Nick Wellnhofer <[email protected]>
Date:   2016-05-18T14:25:20Z

    Write hierarchy log file for Perl build

commit 34672d74fac1e33ccf98a0ce7c17f807328dbdc9
Author: Nick Wellnhofer <[email protected]>
Date:   2016-05-18T14:25:27Z

    Compile core C files for Perl build using make
    
    Create a static library of the core C code using the generated Makefile
    and link the result with the compiled XS code. Make options can be
    passed by running
    
        perl Build.PL --clownfish_params make_options=<options>
    
    Module::Build options can also be specified in ~/.modulebuildrc, so an
    easy way to always launch parallel builds is to add a line like
    
        Build_PL --clownfish_params make_options=-j5

commit 0ac247da1fec522ab8adf2ba4b5bd189f53cb0ca
Author: Nick Wellnhofer <[email protected]>
Date:   2016-05-18T14:25:35Z

    Use autogen/source only when needed

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to