I don't
On 5/12/2014 8:57 AM, Andrew Davis wrote:
>
> In Geant4/dagsolid/src/CMakeLists.txt:
>
> > +  add_library(dagsolid DagSolid.cc)
> > +  if (BUILD_SHARED_LIBS)
> > +    set_target_properties(dagsolid PROPERTIES
> > +      SOVERSION ${VERSION_MAJOR}.${VERSION_MINOR}
> > +      VERSION ${VERSION_MAJOR}.${VERSION_MINOR}.${VERSION_PATCH}
> > +      COMPILE_DEFINITIONS dagsolid_EXPORTS
> > +    )
> > +    target_link_libraries(dagsolid
> > +      ${Moab_MOAB_LIBRARY}
> > +      ${Moab_dagmc_LIBRARY}
> > +      ${Geant4_G4geometry_LIBRARY}
> > +      ${Geant4_G4clhep_LIBRARY}
> > +      ${Geant4_G4global_LIBRARY}
> > +    )
> > +  endif ()
> > +  install(TARGETS dagsolid DESTINATION Geant4/lib)
>
> So you think the libdagsolid.so file is better placed in Geant4/lib?
>

I did not have an opinion except that this might evolve into a build of
the entire tree, and I did not know whether this library name was reused
in other parts of the tree (because there was no g4 namespacing or 
equivalent).

My personal preference is a flat hierarchy, such as

   dagsolidg4 dagsolidfl dagsolidmcnp

or some such, where under each directory one has the source and headers for
that library.  Then one can enforce strong layering, e.g., having a base 
directory
libdagbase, that the others depend on.    Then with all libraries and 
headers having
distinct names, they all get installed into lib and include respectively.

......J