On Tue, Jul 19, 2011 at 04:09:59PM +0200, Romain Geissler wrote: > Hi, > > Melt is creating annoying *.c files next to the .so module file, and i > just can no > longer handle temporary files polluting my final binary directory. > Here is a simple patch > that allow the user to give an explicit coutput file path in all > translateto* modes. > > By the way, trying to reach the C sources files and checking their > checksum with the loaded > .so module just don't make sens to me. This task should be done by a > proper Makefile by > the plugin developer, not by Melt. Gcc won't tell you that your file.o > is outdated because > file.c has changed, there is no reason for melt to act otherwise. At > least, disable this behavior > by default and allow it through a custom parameter.
The reason to do so is that is mode modes (eg runfile) MELT is generating a C file and (under the hoods) building a .so from it, then dlopen-ing it. I really want to avoid dlopen-ing the wrong (e.g. an outdated) MELT module. And MELT does run a make ... so we don't want to delegate that to the user's building system. Cheers. > > Romain Geissler > > -- > Message from the http://groups.google.com/group/gcc-melt group. > About GCC MELT http://gcc-melt.org/ a high level domain specific language to > code extensions to the Gnu Compiler Collection -- Basile STARYNKEVITCH http://starynkevitch.net/Basile/ email: basile<at>starynkevitch<dot>net mobile: +33 6 8501 2359 8, rue de la Faiencerie, 92340 Bourg La Reine, France *** opinions {are only mines, sont seulement les miennes} ***
