ppumove(1)

✨ ppumove(1) β€” Free Pascal unit mover ✨

okay bestie, sit DOWN because this is the manual page for ppumove, aka the Free Pascal unit mover, and honestly? it's giving underrated icon πŸ’…


🌸 NAME 🌸

ppumove β€” the FPC Pascal unit mover. that's it, that's the whole vibe. she moves units. she archives. she slays. πŸŽ€


πŸ¦‹ SYNOPSIS πŸ¦‹

ppumove [-sqbhw] [-o File] [-d path] [-e extension] files...

πŸ’– Description πŸ’–

so like, ppumove collects one or several Free Pascal unit files and archives them into a static or shared library. that's the whole job. she's a collector, a curator, a little archivist fairy 🧚✨


πŸŽ€ Usage πŸŽ€

you can invoke ppumove with just one required argument: the name of the unit you want to make an archive from. that's the bare minimum, no cap.

but wait, there's more πŸ‘‘ β€” specifying multiple files is also totally possible, and they'll all get put into the same archive. bestie behaviour honestly, keeping the friend group together 🫢


✨ Options ✨

ppumove has several options, and heads up: they are case sensitive. so -b is not -B. do not test her. 😭

  • -b β€” tells ppumove to write a shell script (a batch file on DOS) that performs the needed calls to ar and ld. the script will be called pmove, with an extension of .sh on Linux, and .bat on DOS. you can then call this script manually afterwards. very DIY of her πŸ”₯
  • -d path β€” tells ppumove where to generate the new unit files. by default, this is the same directory as where the files are found. ⚠️ and listen: if you specify as the output extension the same extension as the units you want to move, not specifying the destination directory may cause problems. so like, be careful babes.
  • -e ext β€” sets the extension of the new unit files to ext. by default .ppl is used. however, you can specify .ppu as the extension. if you do, be sure to use also the -d switch, or you will overwrite the old units. 😱 note however, that the compiler will only look for extensions .ppu and .ppl when looking for units. so those are the only two that matter, iykyk.
  • -h β€” shows a short help screen. your little emergency exit πŸšͺ✨
  • -o file β€” lets you specify the name of the library to be generated. you must use this option if you specify more than one unit on the command-line. if you specified only one unit on the command-line, the generated library will have the unit name, with lib prepended (on Linux). you do not need to specify the lib part β€” this will be prepended automatically if needed. she handles it, don't worry 🫢
  • -q β€” tells ppumove to operate quietly. no commentary, no drama, just vibes 🀫
  • -s β€” tells ppumove to generate a static library. by default, a shared library is generated (except on DOS). choose your fighter πŸ’…
  • -w β€” tells ppumove it should use the windows linker and archiver. > 🚨 do not use this option on Linux. like seriously, don't. that's not the move.

🌈 SEE ALSO 🌈

ppc386(1) ppudep(1) ppudump(1)

go read those too, they're all part of the same little friend group πŸ¦‹


and that's the whole page bestie!! this one comes to you from the Free Pascal girlies, dated 9 June 1999, and it lives at section ppumove(1) in the manual. πŸ’– thank you for coming to my ted talk, now go archive something iconic πŸ‘‘βœ¨πŸŽ€

πŸ“¦ where this page comes from