mpir/yasm/plugins
2009-07-31 11:57:37 +00:00
..
dbg replace with yasm svn 2227 , delete yasm .svn stuff , run yasm's autogen , replace symbolic links in config directory with real files , run yasm's ./configure && make && make check && make distclean (this does add a few files we need ) , rm autom4te.cache , add to svn 2009-07-31 11:57:37 +00:00
x86 replace with yasm svn 2227 , delete yasm .svn stuff , run yasm's autogen , replace symbolic links in config directory with real files , run yasm's ./configure && make && make check && make distclean (this does add a few files we need ) , rm autom4te.cache , add to svn 2009-07-31 11:57:37 +00:00
README replace with yasm svn 2227 , delete yasm .svn stuff , run yasm's autogen , replace symbolic links in config directory with real files , run yasm's ./configure && make && make check && make distclean (this does add a few files we need ) , rm autom4te.cache , add to svn 2009-07-31 11:57:37 +00:00

These directories contain example yasm plugins.
Yasm is only capable of loading plugins when it was built using cmake.
To build yasm with cmake on Unix, from the yasm source tree, do:
  mkdir objdir
  cd objdir
  cmake ..
  make

The plugins are written to be compiled against an *installed* yasm.
Plugins may be loaded on the yasm command line using the -N command line
option, e.g.:
  yasm -N ./libdbgmod.so
  yasm -N Release/dbgmod.dll
  yasm -N /usr/local/lib/libx86mod
(the .so will be automatically appended)
If no directory path is specified, yasm will search in standard library
locations (e.g. LD_LIBRARY_PATH, the rpath of the yasm executable, etc) to
try to load the plugin.  Thus the last example (after installing the plugin)
could likely be written:
  yasm -N x86mod

Plugins may override builtin modules like x86.