On Thu, Sep 13, 2012 at 11:11 AM, Kirk, Benjamin (JSC-EG311) <
benjamin.kir...@nasa.gov> wrote:
> Well, if you guys have such a vested interest in insulating Moose users
> from
> our churn, why make them responsible for knowing our header names at all?
>
> You could create your own libmesh.h which includes all our headers - hell,
> and then even create a precompiled header out of it!
>
Heh - we are actually heading in this direction. Unfortunately not all
compilers handle precompiled headers similarly... so we've hit some snags
there. And if you create a precompiled header... and you _don't_
precompile it (because a particular compiler doesn't work with PCH) then
your compile time will be ridiculous for that platform.
Even now our users don't typically have to #include libmesh headers... but
it does happen in certain advanced circumstances... but you are right that
we can work to mitigate that.
At any rate... we've been talking this over here and I have an addendum to
my previous suggestion of using symlinks.
How about we leave our include / src tree exactly the way that it is... but
off to the side we grow an "include tree" that is
as ridiculously complicated as we want... and just symlinks in the header
file directories at the point we want. Then you have the -I include lines
use this "include tree".
So basically you have one structure that is good for development (which is
the current structure) and then we have another structure that is good for
includes that symlinks into the first structure...
Derek
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Libmesh-devel mailing list
Libmesh-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-devel
