Hi Andreas, If this is the case, wouldn't it make sense to copy the config.h to the system include folder during the installation?
Best Paolo On Fri, Jun 27, 2014 at 12:14 AM, Andreas Lauser <[email protected]> wrote: > Hi, > > Sorry for this being slightly off-topic, but I had to say something here: > > On Thursday, June 26, 2014 14:55:09 Arne Morten Kvarving wrote: > > if an application uses config.h unconditionally, that is a bug. > > This is not a bug for the following reason: all source files of the > libraries > are compiled with taking the macros of config.h in consideration. If you > now > try to compile with another set of values for these macros, you will get > unexpected behavior, in particular if the headers also have some of these > #ifs > (e.g. a few attributes of the EclipseWriter class are conditional on the > HAVE_ERT macro). In the best case this leads to a segfault and in the > worst to > very subtle runtime bugs which are also very hard to debug. This means that > config.h is always required and that it needs to be compatible with the one > used to compile the libraries... > > cheers > Andreas > > -- > Notice: "String" and "Thread" are the same thing to non-computing > people. > — Programming.com > > _______________________________________________ > Opm mailing list > [email protected] > http://www.opm-project.org/mailman/listinfo/opm > >
_______________________________________________ Opm mailing list [email protected] http://www.opm-project.org/mailman/listinfo/opm
