Re: [lmi] building latest cvs with MSVC (PETE paths)

[Vaclav Slavik]

Hi,

On Fri, 2008-09-19 at 17:37 +0000, Greg Chicares wrote:
> The PETE directory structure in lmi cvs is intended to resemble
> the structure of the original PETE archive here:
>   http://www.codesourcery.com/public/pooma/pete-2.1.0.tgz
> in particular:
>   pete-2.1.0/src/PETE/PETE.h
>   pete-2.1.0/examples/Vector/Eval.h says '#include "PETE/PETE.h"'
> with these correspondences:
>   pete-2.1.0/src/PETE/        <--> lmi/tools/pete-2.1.1/PETE/
>   pete-2.1.0/examples/Vector/ <--> lmi/tools/pete-2.1.1/
> 
> The installation command above flattens that structure. ('*.*' is
> deliberate: it ignores 'CVS' subdirs and other irrelevant files.)
> 
> Why flatten it? Because it didn't work otherwise, at least not with
> MinGW gcc--or como either, IIRC.

This is causing problems with the Automake build system too -- it is
currently broken, you have to manually install PETE headers somewhere.
I'm not aware of any PETE packages for Linux (not even for Debian that
usually has everything), so we can't rely on PETE as a dependency and
have to build it as part of LMI build process. In other words, it would
be much preferable to be able to use PETE headers in-place. I'll see if
I can make it work at least on the Automake side. 

To complicate matters even more, the nonstandard, LMI-specific
et_vector.hpp header is stored in tools/pete-2.1.1, not
tools/pete-2.1.1/PETE, but is #included as <PETE/et_vector.hpp>. This
can never work without some installation step, of course. Would it be
acceptable to move it either into the PETE directory or change the
#include lines for it?

Thanks,
Vaclav