So,
With the new build system what's the best way to develop a new example?
Previously I would do this:
cd libmesh/examples/introduction
cp introduction_ex3 introduction_ex17
# Change everything in introduction_ex17 to say ex17
make
./introduction_ex17
What's the best way of doing that now?
If
And actually... a follow on question.
What are the steps necessary for adding a new file (like new a new header
file and associated .C) to libMesh now?
Thanks,
Derek
On Sat, Jan 19, 2013 at 3:14 PM, Derek Gaston wrote:
> So,
>
> With the new build system what's the best way to develop a new
On Sat, 19 Jan 2013, Derek Gaston wrote:
> What are the steps necessary for adding a new file (like new a new header
> file and associated
> .C) to libMesh now?
Check out Ben's include/rebuild_include_HEADERS.sh and
src/rebuild_libmesh_SOURCES.sh; IIRC those do all the magic (other
than the git
On Sat, 19 Jan 2013, Roy Stogner wrote:
> the git commands
Actually, speaking of the git commands, there is one big hassle:
Make sure that you re-run bootstrap before committing any build system
commits, and be sure to re-run it with the versions of automake,
autoconf, and libtool from libmesh
So, here's my workflow for adding a new example (in a new examples
directory).
cd libmesh/examples
mkdir mesh_transfer
cp -r introduction/introduction_ex3 mesh_transfer/simple_dtk
cd mesh_transfer/simple_dtk
# Rename files to simple_dtk (or whatever)
# Edit Makefile.am to include the name of the n
On Jan 19, 2013, at 4:14 PM, Derek Gaston wrote:
> So,
>
> With the new build system what's the best way to develop a new example?
>
> Previously I would do this:
>
> cd libmesh/examples/introduction
> cp introduction_ex3 introduction_ex17
> # Change everything in introduction_ex17 to say ex17
On Jan 19, 2013, at 5:26 PM, Derek Gaston wrote:
> So, here's my workflow for adding a new example (in a new examples directory).
>
> cd libmesh/examples
> mkdir mesh_transfer
> cp -r introduction/introduction_ex3 mesh_transfer/simple_dtk
> cd mesh_transfer/simple_dtk
> # Rename files to simple_
Thanks for getting back to me...
On Sat, Jan 19, 2013 at 4:37 PM, Kirk, Benjamin (JSC-EG311) <
benjamin.kir...@nasa.gov> wrote:
> You do not to build in a separate directory unless you want to. I do this
> so I can use many different compilers on a number of machines that all
> share the same s
On Sat, Jan 19, 2013 at 4:57 PM, Derek Gaston wrote:
> Hmmm we did some testing with this this week and there are a couple of
> issues:
>
> 1. If you don't "make install" then Make.common does not get created
> (obviously not necessary for an example... but that is problematic for
> some us
On Jan 19, 2013, at 6:08 PM, Derek Gaston wrote:
> On Sat, Jan 19, 2013 at 4:57 PM, Derek Gaston wrote:
> Hmmm we did some testing with this this week and there are a couple of
> issues:
>
> 1. If you don't "make install" then Make.common does not get created
> (obviously not necessary
On Sat, Jan 19, 2013 at 5:17 PM, Kirk, Benjamin (JSC-EG311) <
benjamin.kir...@nasa.gov> wrote:
> In tree builds work fine, and you should be able to do any
> 'libmesh-centric' development without a 'make install' - including running
> the examples.
>
So, to build an example when doing an in-tree
On Jan 19, 2013, at 6:25 PM, Derek Gaston wrote:
> So, to build an example when doing an in-tree build I have to run "make
> check"? Why doesn't "make" work?
Mostly consistency and because 'make check' is the generic target for building
a self-test.
automake rules will always recurse into
--
John
On Jan 19, 2013, at 5:08 PM, Derek Gaston wrote:
> On Sat, Jan 19, 2013 at 4:57 PM, Derek Gaston wrote:
>> Hmmm we did some testing with this this week and there are a couple of
>> issues:
>>
>> 1. If you don't "make install" then Make.common does not get created
>> (obviousl
On Sat, Jan 19, 2013 at 6:16 PM, Kirk, Benjamin (JSC-EG311) <
benjamin.kir...@nasa.gov> wrote:
> Mostly consistency and because 'make check' is the generic target for
> building a self-test.
>
> automake rules will always recurse into subdirectories and $(MAKE)
> whatever target you have specified
14 matches
Mail list logo