Thanks. The reason why I am asking this is that I am trying to build my libMesh application using CMake. Has anybody had experience with libMesh+CMake?
Miguel From: John Peterson <jwpeter...@gmail.com<mailto:jwpeter...@gmail.com>> Date: Friday, April 1, 2016 at 10:37 AM To: Miguel Salazar <salazardet...@llnl.gov<mailto:salazardet...@llnl.gov>> Cc: "libmesh-users@lists.sourceforge.net<mailto:libmesh-users@lists.sourceforge.net>" <libmesh-users@lists.sourceforge.net<mailto:libmesh-users@lists.sourceforge.net>> Subject: Re: [Libmesh-users] Linking application to libMesh On Fri, Apr 1, 2016 at 11:29 AM, Salazar De Troya, Miguel <salazardet...@llnl.gov<mailto:salazardet...@llnl.gov>> wrote: Hello I am trying to understand the compilation process here. Using the Make.common in my Makefile generates libmesh_LIBS that I will use in my application’s Makefile. However, as I have recently learned, since libmesh is a shared library, I might not need to link to all those libraries since libMesh already links to them. How should I deal with this? Does libtool come here to get rid of all the unnecessary libraries? I found this in one of the examples’ old Makefile. $(notdir $(target)): $(objects) @echo "Linking "$@"..." @$(libmesh_LIBTOOL) --tag=CXX $(LIBTOOLFLAGS) --mode=link \ $(libmesh_CXX) $(libmesh_CXXFLAGS) $(objects) -o $@ $(libmesh_LIBS) $(libmesh_LDFLAGS) $(EXTERNAL_FLAGS) Yes, this is the right way to do linking, i.e. using $(libmesh_LIBS) *and* libtool, because it handles differences in dynamic linking on different platforms. -- John ------------------------------------------------------------------------------ Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://pubads.g.doubleclick.net/gampad/clk?id=278785471&iu=/4140 _______________________________________________ Libmesh-users mailing list Libmesh-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-users
