[MOAB-dev] Building moab with cgm?

[JR Cary]

On 12/17/15 8:10 AM, Vijay S. Mahadevan wrote:
>
> Hmm I'm unsure what's missing in the CMake build with CGM. We are 
> currently not testing cmake as extensively (in terms of feature 
> combination) as autotools. Ben Boeckel submitted a PR with some Cmake 
> updates but this is still under review. So there is a possibility that 
> this is broken.
>

Okay.  I will try going back to autotools, but ho
>
> We can add a build to our nightly to test this configuration combo. 
> I'll also let you know if we are able to replicate your issues 
> locally. Are you using CGM with OCE or Cubit? Version?
>

oce-OCE-0.17 (the 0.17 release tag of OCE).

Thx...John

> Vijay
>
> On Dec 17, 2015 8:44 AM, "JR Cary" <cary at txcorp.com 
> <mailto:cary at txcorp.com>> wrote:
>
>     Hi Vijay, Before I do that, just briefly, since you ask for
>     config.log,
>     I'll mention that I am using CMake.  Should that work?
>
>     Thx...John
>
>     On 12/17/15 7:39 AM, Vijay S. Mahadevan wrote:
>
>         John,
>
>         All users should only be branching off from or directly using
>         master
>         branch and not develop branch. The "develop" branch is our
>         throwaway
>         integration branch which is under active development and so we
>         make no
>         guarantees of clean builds on all configuration combinations
>         due to
>         some untested features. The master branch should always be
>         stable and
>         shouldn't have any problems (hopefully). This philosophy is true
>         across the stack (CGM/MOAB/MeshKit).
>
>         I haven't seen those errors before. Perhaps the other devs can
>         chime
>         in. Can you also send along your MOAB config.log ?
>
>         Vijay
>
>         On Thu, Dec 17, 2015 at 4:05 AM, JR Cary <cary at txcorp.com
>         <mailto:cary at txcorp.com>> wrote:
>
>             I've just created a fresh branch of develop of CGM and
>             configured
>             it with cmake, then built and installed it.
>
>             I also have a fresh branch of develop of MOAB.  I configure it
>             with cmake, then try to build it.  It fails at
>
>             /home/research/cary/projects/composerall/moab/src/io/ReadCGM.cpp:
>             In member
>             function ‘moab::ErrorCode
>             moab::ReadCGM::store_surface_senses(std::map<RefEntity*,
>             long unsigned
>             int>&, std::map<RefEntity*, long unsigned int>&)’:
>             /home/research/cary/projects/composerall/moab/src/io/ReadCGM.cpp:256:11:
>             error: ‘cout’ is not a member of ‘std’
>                         std::cout << "Surface " << face->id() << " has
>             reverse sense " <<
>
>             I fixed those by including <iostream>, but then I get
>             errors like
>
>             /home/research/cary/projects/composerall/moab/src/io/ReadCGM.cpp:689:11:
>             error: ‘ModelEntity’ was not declared in this scope
>                 DLIList<ModelEntity*> me_list;
>
>             At this point I see that there exists ModelEntity.hpp in
>             the CGM source
>             but not in the installation.  I tried adding it to the
>             installation, but
>             then CGM fails to compile.
>
>             Is this something that should be fixed in cgm?
>
>             Or am I doing something different from how you get moab to
>             compile?
>
>             Thx.....John
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/moab-dev/attachments/20151217/d0d87e05/attachment.html>