Open pbauman opened 8 years ago
In hindsight we should have had an antioch_config from the start; it would also have saved a lot of work when going through the "now we're header-only! whoops, now we're not again!" changes. We'd still need to change antioch.m4 to use antioch_config, but at least it would be one change, and then the application side of configuration would be stable and forwards-compatible.
In hindsight we should have had an antioch_config from the start
Sorry, I'm not following about antioch_config
. Is there an example you could point to?
$ $LIBMESH_DIR/bin/libmesh-config
usage: /h2/roystgnr/LIBRARIES/libmesh-normal/bin/libmesh-config --cppflags --cxxflags --include --libs
/h2/roystgnr/LIBRARIES/libmesh-normal/bin/libmesh-config --cxx
/h2/roystgnr/LIBRARIES/libmesh-normal/bin/libmesh-config --cc
/h2/roystgnr/LIBRARIES/libmesh-normal/bin/libmesh-config --fc
/h2/roystgnr/LIBRARIES/libmesh-normal/bin/libmesh-config --fflags
/h2/roystgnr/LIBRARIES/libmesh-normal/bin/libmesh-config --version
/h2/roystgnr/LIBRARIES/libmesh-normal/bin/libmesh-config --host
/h2/roystgnr/LIBRARIES/libmesh-normal/bin/libmesh-config --ldflags
See also cppunit-config, cups-config, freetype-config, krb5-config, ...
Oh, right, of course! Thanks for the reminder.
@roystgnr wrote in grinsfem/grins#410
@pbauman responded with
Further discussions can take place here.