Clement, For your first question, you can search for inspiration in https://github.com/open-mpi/ompi/blob/master/opal/mca/btl/sm/Makefile.am btl/sm uses common/sm (and common/cuda too), so it looks pretty similar to what you are trying to achieve.
For your second question, and even if I do not fully get what you want to achieve, you can have a look at https://github.com/open-mpi/ompi/blob/master/ompi/tools/wrappers/Makefile.am and see how ompi_wrapper_script is installed via make install. During make check, it might be enough to invoke the script in $(top_srcdir)/... If your project is not confidential, you can publish it on github so we can have a look and provide better guidance. You can also create a private repository on bitbucket and grant access to only a few developers (both options are free) Cheers, Gilles On Wednesday, October 26, 2016, Clement FOYER <clement.fo...@gmail.com> wrote: > Hi everyone, > > I've got two Makefile configuration problems, and I thought maybe someone > here could give me hints to resolve them. > > I've been working on a component that is part in ompi/mca/pml/comp, and > part in mca/common/comp. And I don't really know which variables/target to > set in order to have a proper linking when generating both .la and .so > files. > > Also, on the test Makefile.am, I would like to distribute a script that > strat different benchmarks. How should I that up the makefile so the script > is copied to (or linked in) the build directory when just calling "make", > and to the installation directory when calling "make install" ? > > Thank you in advance, > > Clément FOYER > > _______________________________________________ > devel mailing list > devel@lists.open-mpi.org > https://rfd.newmexicoconsortium.org/mailman/listinfo/devel
_______________________________________________ devel mailing list devel@lists.open-mpi.org https://rfd.newmexicoconsortium.org/mailman/listinfo/devel
