There just hasn been time to test it and integrate it into Boomerang if suitable. Looking for a nice little project?
17. Why am I suddenly getting link errors after updating (Linux)? It’s probably because Makefile.in has changed. In order for changes to flow from Makefile.in to Makefile, you have to run ./configure, or the shortcut ./config.status . (The latter is safe as long as your environment hasn’t changed, like installing a new package). The Makefiles and other configured files (e.g. include/config.h) are not booked in, because they are generated from other files, and are tailored to your particular configuration. When a new module (.o file) is added to Boomerang, and the Makefile is not up to date, there will usually be a large number of link-time errors, since a whole bunch of functions will not be known by the linker. 18. Why am I suddenly getting link errors after updating (Windows)? It’s probably because boomerang.vcproj has changed. This file is kept in the win32make/ directory. You probably are loading the project file from elsewhere. So you could copy the file from win32make/ to whereev
