c:
"[email protected]<mailto:[email protected]>"
mailto:[email protected]>>
Subject: Re: [Libmesh-users] Linking application to libMesh
that is strange... find_package(Pkgconfig QUIET) calls exactly FindPkgConfig.
what
c/lib”)
>
> Miguel
>
> From: Antonio Cervone
> Date: Thursday, April 7, 2016 at 3:09 AM
> To: Miguel Salazar , Roy Stogner <
> [email protected]>
> Cc: "[email protected]" <
> [email protected]>
>
> Subjec
[email protected]<mailto:[email protected]>"
mailto:[email protected]>>
Subject: Re: [Libmesh-users] Linking application to libMesh
I have developed this in the past
https://github.com/capitalaslash/fsi/blob/master/cmake/FindLIBMESH.cmake
it us
I have developed this in the past
https://github.com/capitalaslash/fsi/blob/master/cmake/FindLIBMESH.cmake
it used to work for both opt and debug builds.
let me know if it is of help
antonio
On Wed, Apr 6, 2016 at 7:59 PM Salazar De Troya, Miguel <
[email protected]> wrote:
> The compiler
The compiler flags are provided by ${LIBMES_DIR}/bin/libmesh-config
‹cxxflags and ‹cflags right? In that case, I do pass them. This is the
object compilation output for the cmake and the Makefile
/usr/local/tools/openmpi-intel-1.8.4/bin/mpicxx -std=gnu++11 -std=gnu++11
-fopenmp -g -w1 -g -wd175 -w
On Wed, 6 Apr 2016, Salazar De Troya, Miguel wrote:
> I understand that this error is difficult to diagnose through email, but I
> would really appreciate help on how to debug it. The same application runs
> perfectly when I compile it with the usual Makefile.
Are you compiling with the libMesh
I was able to compile my libMesh application with CMake, but I am having
problems when running it, specifically, I get this segfault:
Program received signal SIGSEGV, Segmentation fault.
0x2aaab3f64eca in std::_Rb_tree_decrement(std::_Rb_tree_node_base*) ()
from /usr/lib64/libstdc++.so.6
Missi
Yup, that was it. Thanks
On 4/4/16, 12:28 PM, "Roy Stogner" wrote:
>
>On Mon, 4 Apr 2016, Roy Stogner wrote:
>
>> That definitely looks like the issue. _counts is declared if and only
>> if DEBUG is defined. If you define DEBUG when building your
>> application then you need to be linking a
On Mon, 4 Apr 2016, Roy Stogner wrote:
> That definitely looks like the issue. _counts is declared if and only
> if DEBUG is defined. If you define DEBUG when building your
> application then you need to be linking against a dbg-mode libMesh
> build too.
And as I should have said earlier: the
On Mon, 4 Apr 2016, Salazar De Troya, Miguel wrote:
CMakeFiles/vector_cmake.dir/vector_fe_ex1.C.o: In function
`libMesh::ReferenceCounter::increment_constructor_count(std::string const&)':
/g/g92/miguel/code/libmesh_2D/include/libmesh/reference_counter.h:166:
undefined reference to `libMesh:
o:[email protected]>>
Date: Friday, April 1, 2016 at 11:19 AM
To: Miguel Salazar mailto:[email protected]>>
Cc:
"[email protected]<mailto:[email protected]>"
mailto:[email protected]>>
Subject: Re: [Li
On Fri, Apr 1, 2016 at 12:16 PM, Salazar De Troya, Miguel <
[email protected]> wrote:
> That’s exactly what I have been doing, and I can compile the application
> with CMake, however, I was told that linking to all the libraries resulting
> from $LIBMESH_DIR/bin/libmesh-config —libs might be
mailto:[email protected]>"
mailto:[email protected]>>
Subject: Re: [Libmesh-users] Linking application to libMesh
On Fri, Apr 1, 2016 at 11:56 AM, Salazar De Troya, Miguel
mailto:[email protected]>> wrote:
Thanks. The reason why I am asking this
On Fri, Apr 1, 2016 at 11:56 AM, Salazar De Troya, Miguel <
[email protected]> wrote:
> 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?
>
I do not, but it should be pretty straightforw
[email protected]>>
Cc:
"[email protected]<mailto:[email protected]>"
mailto:[email protected]>>
Subject: Re: [Libmesh-users] Linking application to libMesh
On Fri, Apr 1, 2016 at 11:29 AM, Salazar De Troya, Miguel
mai
On Fri, Apr 1, 2016 at 11:29 AM, Salazar De Troya, Miguel <
[email protected]> 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 l
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 l
17 matches
Mail list logo
