Try copying the makefile from one of the examples then and using it for your
application. They are all the same.
$ find $LIBMESH_ROOT/examples -name Makefile
On May 27, 2014, at 10:53 AM, walter kou wrote:
> Thanks for your message, I did "make install", and I did find the Make.common
> in
Thanks for your message, I did "make install", and I did find the
Make.common in the default installed place: /usr/local
However, I tried to use this make file, get many linkage errors such as:
/usr/local/lib/libmesh_opt.a(libopt_la-ex_put_loadbal_param_cc.o): In
function `ex_put_loadbal_param_cc
Did you do a 'make install'?
Make.common should exist in the install directory.
-Ben
On May 27, 2014, at 10:27 AM, walter kou wrote:
> Hi Roy,
>
> Thanks for your message, what do you mean by "Make.common still exists"? I
> do see Make.common in several subfolders such as /examples, /contrib
Hi Roy,
Thanks for your message, what do you mean by "Make.common still exists"? I
do see Make.common in several subfolders such as /examples, /contrib. But
I do not see Make.common in the parent folder that version 0.8.0 called.
Walter
On Mon, May 26, 2014 at 10:57 PM, Roy Stogner wrote:
>
>
On Mon, 26 May 2014, walter kou wrote:
> Recently, I switched from libmesh-0.8.0 to libmesh 0.9.3, and found
> Make.common-based way in 0.8.0 did not work for 0.9.3.
>
> Is there example/instruction on writing a Makefile for libmesh 0.9.3, if
> one wants to include new codes?
Make.common still e
On Tue, 13 Aug 2013, John Peterson wrote:
> On Tue, Aug 13, 2013 at 9:24 AM, Lorenzo Zanon
> wrote:
>
>> Actually in the Makefile "old version" the path to Make.common is
>> LIBMESH_DIR/Make.common, so I set LIBMESH_DIR=LIBMESH_ROOT/installed then
>> typed "make" from my example's directory. The
On Tue, Aug 13, 2013 at 9:24 AM, Lorenzo Zanon
wrote:
> Actually in the Makefile "old version" the path to Make.common is
> LIBMESH_DIR/Make.common, so I set LIBMESH_DIR=LIBMESH_ROOT/installed then
> typed "make" from my example's directory. The Make.common file is found but
> there's still someth
Actually in the Makefile "old version" the path to Make.common is
LIBMESH_DIR/Make.common, so I set LIBMESH_DIR=LIBMESH_ROOT/installed then typed
"make" from my example's directory. The Make.common file is found but there's
still something wrong, since I'm getting a compile error:
ex23aa.C(29):
Yes, and then you can copy the Makefile from any of the installed examples and
use that. Everything then should just work.
-Ben
On Aug 13, 2013, at 6:30 AM, "David Knezevic"
wrote:
> If you do "make install", then that will put Make.common in the
> installed directory.
>
>
>
> On 08/13/
If you do "make install", then that will put Make.common in the
installed directory.
On 08/13/2013 01:28 PM, Lorenzo Zanon wrote:
> Hi,
>
> I re-installed libmesh as you indicated. I didn't use --with-methods="opt" in
> the configuration though, since I usually run my own code in dbg mode, so
Hi,
I re-installed libmesh as you indicated. I didn't use --with-methods="opt" in
the configuration though, since I usually run my own code in dbg mode, so I
configured with all three methods.
Now, for running my code, should I copy the Make.common file in
${LIBMESH_ROOT}/installed in my code
On Mon, Aug 12, 2013 at 9:57 AM, Lorenzo Zanon
wrote:
> Hello,
>
> To be more specific, my code now is based on libmesh version 0.7.3. I
> would like to run it with the newest version.
>
> What I tried to do is to copy the Make.common file from libmesh/contrib/
> to /libmesh (folder where the new
Hello,
To be more specific, my code now is based on libmesh version 0.7.3. I would
like to run it with the newest version.
What I tried to do is to copy the Make.common file from libmesh/contrib/ to
/libmesh (folder where the new version is), then type into the shell:
cd /my_example/directory
13 matches
Mail list logo
