On Tue, Jan 22, 2013 at 9:37 AM, Derek Gaston <fried...@gmail.com> wrote:
> Have you guys tried to do a static build of libMesh on Linux and "make
> install" it somewhere and then try to build a libMesh based application
> against that?
>
> It is not working for us... because of missing tecplot symbols (like
> "tecini"). It looks like the executables in libMesh (like meshplot, etc.)
> have this on their link line (I'm building in a build directory underneath
> the libMesh directory):
>
> ../contrib/tecplot/lib/x86_64-unknown-linux-gnu/tecio.a
>
> However, that tecio.a file doesn't get installed into the prefix directory
> when you do "make install"... so there is no way for a libMesh based
> application to do something similar.
>
> I was kind of thinking that that tecio.a would have been linked into the
> actual libMesh static library... then there would be no problems...
>
> What should we do about this?
Just to add a bit more detail to this: if you configure libmesh with
--enable-static --enable-shared, and make install then we get the
following when running 'nm' on the static library.
nm lib/libmesh_opt.a | grep tecini
nm: tecio.a: File format not recognized
nm: lt1-tecio.a: File format not recognized
U tecini
It seems to me that tecplot is unique in that it's a binary blob we
download from the Tecplot website?
--
John
------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. ON SALE this month only -- learn more at:
http://p.sf.net/sfu/learnnow-d2d
_______________________________________________
Libmesh-devel mailing list
Libmesh-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-devel
