[MOAB-dev] Question about moab.make

[Dmitry Karpeev]

Got it. Thanks.
Dmitry.

On Mon, Dec 14, 2009 at 3:29 PM, Tim Tautges <tautges at mcs.anl.gov> wrote:
> As Jed states, this gets superseded by later lines in that file.  It's this
> way in order to be usable before installing.
>
> - tim
>
> Jed Brown wrote:
>>
>> On Sun, 13 Dec 2009 19:53:19 -0600, Dmitry Karpeev <karpeev at mcs.anl.gov>
>> wrote:
>>>
>>> I'm writing some parallel benchmarking tests for moab as MOAB-based
>>> stand-alone applications
>>> (similar to tools like mbperf etc).
>>> My question is what the standard build process for these should be?
>>> It appears that a Makefile for MOAB-based apps could be constructed by
>>> simply including ${MOAB_PREFIX}/lib/moab.make,
>>> where ${MOAB_PREFIX} is the install prefix specified at configure time.
>>> However, the first two lines of moab.make seem a little puzzling to me:
>>> MOAB_LIBDIR = /home/karpeev/sharp/moab/trunk/.libs
>>> MOAB_INCLUDEDIR = /home/karpeev/sharp/moab/trunk
>>> -I/home/karpeev/sharp/moab/trunk
>>>
>>> In particular, they refer to the source tree under 'trunk' and, as I
>>> understand it, this is subject to change according to other
>>> configurations etc.
>>> Am I missing anything?
>>
>> That crap is just hanging around, it's not actually being used because
>> the last two lines of that file replace those variables with paths in
>> $PREFIX.
>>
>> Jed
>>
>
> --
> ================================================================
> "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
>
>