Wrap C++ logging using Java logging framework

System information

• TensorFlow version (you are using): 0.3.1
• Are you willing to contribute it (Yes/No): No

By default, TensorFlow's C++ libraries log messages like this:

2021-03-29 15:50:24.014316: W external/org_tensorflow/tensorflow/stream_executor/platform/default/dso_loader.cc:60] Could not load dynamic library 'cudart64_110.dll'; dlerror: cudart64_110.dll not found
2021-03-29 15:50:24.014340: I external/org_tensorflow/tensorflow/stream_executor/cuda/cudart_stub.cc:29] Ignore above cudart dlerror if you do not have a GPU set up on your machine.

Ignoring the contents of the logs for a minute (I know how to resolve this warning) I would like to redirect all logging output from the C++ library into a java logging framework (such as slf4j) so that I can control the logging level, redirect logs to a file, specify a rollover policy (e.g. truncate logs at the end of every day) and so on.

L’issue ne nomme aucun fichier, test ni point d’entrée. Commencez par suivre la frontière de logging Java-to-C++ et déterminer comment les messages natifs parviennent actuellement aux utilisateurs. Le travail est considéré comme terminé lorsque les logs de la bibliothèque C++ peuvent être acheminés via un framework de logging Java, avec des niveaux, une sortie fichier et un comportement de rollover contrôlables.