From: Zack V. <jan...@gm...> - 2017-11-22 18:47:59
|
Thanks Ben and Roy, I will try configuring with these options and take note of the potential licensing trouble for later. I have a related question (using a mesh created through gmsh through pygmsh), but I'll ask that in another email. On Tue, Nov 21, 2017 at 9:55 AM, Roy Stogner <roy...@ic...> wrote: > > On Mon, 20 Nov 2017, Zack Vitoh wrote: > > This does not work for me, as it does not produce anything >> >> there is a flag >> >> #ifdef LIBMESH_HAVE_TRIANGLE >> >> which is apparently false >> > > Right - if you don't have Triangle enabled, we can't run programs > which require Triangle. > > I looked at 'configure' and it says >> >> # Triangle -- enabled unless --enable-strict-lgpl is specified >> >> I did not specify this 'enable-strict-lgpl', does anyone know why this >> happened? >> > > I'm afraid this is a misleading comment: "--enable-strict-lgpl" is the > *default*, because we don't want to make it easy for users to get into > licensing trouble by accident. You need to specify > "--disable-strict-lgpl" if you want non-LGPL-licensing-compatible > third party libraries incorporated into your libMesh build. > --- > Roy > |