[MOAB-dev] MOAB examples

[Tim Tautges]

I know this seems really goofy, but I'd like to make it dead simple to see exactly how to build MOAB into applications 
using a completely trivial Makefile.  I'm ok with it being just for one example; the others can go into a combined 
Makefile.  Eventually, it may make sense to also have an example showing how to incorporate MOAB into an app's 
autoconf-libtool-based build and, it pains me to say this, cmake-based build.

- tim

James Porter wrote:
> Why not have Makefile.GetEntities et al and then a general Makefile that
> calls those? That way people can see the simple Makefiles (and call them
> directly with make -f) or they could say "make GetEntities".
> 
> - Jim
> 
> On Wed, 2010-03-17 at 14:54 -0500, Timothy J. Tautges wrote:
>> I'd like the 3 simple examples (GetEntities, SetsNTags, GetGeomHierarchy, or something like those names) to keep their own Makefile's and subdirs, since they're meant to be the simple read-this-first sort of examples.  The others can go into the same makefile if they're small.  I wonder if we should have a subdirectory there for 1-file examples, so those aren't all put up in the main examples directory?
>>
>> - tim
>>
>> ----- Original Message -----
>> From: "Robert Smith" <smithrm at mcs.anl.gov>
>> To: "Jason Kraftcheck" <kraftche at cae.wisc.edu>
>> Cc: moab-dev at mcs.anl.gov
>> Sent: Wednesday, March 17, 2010 6:27:35 PM GMT +00:00 Monrovia
>> Subject: Re: [MOAB-dev] MOAB examples
>>
>> Your proposal does seem cleaner.  Especially since they are each 1  
>> file and the makefiles are almost all alike.
>>
>> Also we need to put in some example mesh files to the directory.  I  
>> was going to write a README file for the examples once they were done  
>> to indicate what each one does and how to invoke it.
>>
>> Does anyone have some good input mesh files to use for the examples?
>>
>> --Bob
>>
>>
>> On Mar 17, 2010, at 1:05 PM, Jason Kraftcheck wrote:
>>
>>> Why do we have subdirectories under examples/ when all of our  
>>> examples (by
>>> design) are a single file?  Is it just so that each can have its own
>>> Makefile?  Would anyone mind if I were to move all the example  
>>> source files
>>> to the top examples/ directory and remove the individual subdirs?   
>>> Would it
>>> be a problem if all of them were to share a single Makefile?  This  
>>> would
>>> result in a simpler build system with fewer files to maintain.
>>>
>>> - jason
>>>
> 
> 
> 

-- 
================================================================
"You will keep in perfect peace him whose mind is
   steadfast, because he trusts in you."               Isaiah 26:3

              Tim Tautges            Argonne National Laboratory
          (tautges at mcs.anl.gov)      (telecommuting from UW-Madison)
          phone: (608) 263-8485      1500 Engineering Dr.
            fax: (608) 263-4499      Madison, WI 53706