.TH MUSE 1.SH NAMEmuse.SH SYNOPSIS.B muse.B -o.I out.B -p.I pkg[.B -h] [.B -d.I dbg] [.B -l.I libs] [.I file ...].SH DESCRIPTION.PPThe.I musetool acts as a linker for.I .usefiles. It reads all of the usefiles provided to it on thecommand line, filters them by package, and outputs a newusefile with the merged set of symbols. Both the.B -o.I out.useand the.B -p.I pkgoptions are mandatory..PPThe output of.I museis architecture-independent. However, the format of thegenerated file is not stable, and is not guaranteed to work acrossdifferent compiler versions..PPThe.I museoptions are:.TP.B -hPrint a summary of the available options..TP.B -d [flTri]Print debugging dumps. Additional options may be given to give moredebugging information for specific intermediate states of the compilation..TP.BI -p\  packageTake the symbols that match.I packageand their dependencies, and merge them into a single package. Only symbolsmatching the package name will be reexported..TP.BI -o\  output-fileSpecify that the generated usefile should be named .I output-file.By convention,.I output-fileshould match up with the package name given to the.B -poption..SH EXAMPLE.IP.EX    muse -o library.use -p library foo.use bar.use.EE.LP.SH FILESThe source for.I museis available from.B git://git.eigenstate.org/git/ori/mc.gitand lives in the.I muse directory within the source tree..SH SEE ALSO.IR 6m (1),.IR 2l (1),.IR 2a (1).SH BUGS.PPThere is insufficient checking and validation done on usefiles..PPThe file format is in flux, and in current iterations, it is not at all compact..PPThere is no versioning on the usefiles as it stands. If you use the wrongversion with the wrong compiler, a mysterious error or even segfault islikely..PPThis utility should not exist. Instead, the compiler should put theexported symbol information into the object file or library directly.