----------------------------------------
> Date: Thu, 4 Aug 2016 19:11:03 -0500
> From: royst...@ices.utexas.edu
> To: marchy...@hotmail.com
> CC: libmesh-users@lists.sourceforge.net
> Subject: Re: [Libmesh-users] FW: libmesh problem: libmesh_nullptr was not
> declared in scope
>
>
>
> On Thu, 4 Aug 2016, Mike Marchywka wrote:
>
>>> I have not followed the exchange but sometimes I end up including headers
>>> within a namespace or
>>> something. Is libmesh being included within something? Not sure what that
>>> does with some
>>> macros and others not lol.
>
> That was my first guess, too! That's actually why I was asking about
> the config macros - if he was in the nullptr-workaround case, then
> accidentally including a libMesh header within a namespace would have
> exactly the effect seen: the class we define wouldn't exist in the
> global namespace and the compiler wouldn't recognize it.
I skimmed most of the messages and it did sound like it would be something
easy to find by looking at the exact code so I was a bit surprised with that
last post :)
For problems in unfamiliar code grep can be amazingly
useful even if you expect 1000's of hits they usually end up being easy to sort
out.
The linking is a bit unorthodox, indeed I think you had some specific
recommendations for linking to libmesh that hid most of the details, but
actually building it and compiling with it were pretty easy. I turned on some
debug info
from the example make script, just copied its invokation of g++ and libtool
and that seems to work for some simple case.
> ---
> Roy
------------------------------------------------------------------------------
_______________________________________________
Libmesh-users mailing list
Libmesh-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-users
