slice2objc(1)

πŸ“¦
version 3.7.10 Β· 2 versions
, in arch rolling, debian bookworm, debian trixie, ubuntu jammy, ubuntu noble, ubuntu questing, ubuntu resolute

πŸ’… slice2objc β€” the Slice-to-Objective-C compiler bestie

okay so you found the slice2objc(1) page in the General Commands Manual and you're like "what is this" β€” don't worry, I got you. This is the tool that takes your Slice files and turns them into Objective-C. That's the whole vibe. πŸ¦‹


✨ NAME ✨

slice2objc β€” literally the Slice to Objective-C compiler. that's her. that's the name. πŸ‘‘


🌸 SYNOPSIS 🌸

slice2objc [options] [files]

options first, files after, classic. no notes. πŸ’–


πŸŽ€ DESCRIPTION πŸŽ€

slice2objc compiles your Slice files into Objective-C. periodt. and while it's doing that compilation, the macro __SLICE2OBJC__ gets defined β€” so if you're doing conditional stuff, that's your sign. ⭐

the full documentation for slice2objc is living online at:

https://doc.zeroc.com/ice/latest/language-mappings/objective-c-mapping/client-side-slice-to-objective-c-mapping/slice2objc-command-line-options

go read it, it's giving thorough. πŸ“šβœ¨


πŸ’… OPTIONS πŸ’…

  • -h, --help β€” shows you the help message. the "hello, here's what I do" moment. 🫢
  • -v, --version β€” prints the compiler version. so you know exactly which one you're dealing with. 🌈
  • -DNAME β€” defines the preprocessor symbol NAME. πŸ’œ
  • -DNAME=DEF β€” defines the preprocessor symbol NAME, but this time you're giving it the value DEF. πŸ’œ
  • -UNAME β€” undefines the preprocessor symbol NAME. un-defining. the opposite slay. 😭
  • -IDIR β€” adds the directory DIR to the search path for #include directives. so it knows where to go lookin. πŸ”
  • -E β€” prints the preprocessor output on stdout. just the preprocessed goods, nothing else. ✨
  • --output-dir DIR β€” drops the generated files into directory DIR. very "put it in the folder" of it. πŸŽ€
  • -d, --debug β€” prints debug information showing what the Slice parser is doing. peak behind-the-scenes content. πŸ“
  • --depend β€” prints dependency information to standard output by default, or to the file you name with --depend-file. heads up bestie: no code is generated when you use this option. πŸ’€
  • --depend-xml β€” same deal but the dependency info comes out in XML format, to standard output by default or to the file from --depend-file. and again: no code is generated when this option is specified. 🫠
  • --depend-file FILE β€” sends dependency information to the specified FILE. the output format depends on whether --depend or --depend-xml is also specified. pick your fighter. πŸ”₯
  • --validate β€” checks the command-line options you gave it for correctness, and generates absolutely no code. just vibes and verification. βœ…
  • --include-dir DIR β€” modifies #include directives in source files so the path name of each header file gets the directory DIR prepended to it. glow-up for your include paths. 🌟

πŸ‘‘ SEE ALSO πŸ‘‘

your other slice besties, all in one place:

slice2cpp(1), slice2cs(1), slice2java(1), slice2js(1), slice2php(1), slice2py(1), slice2rb(1), slice2swift(1)


and that's the whole page, no cap. this came to you straight from the General Commands Manual, page slice2objc(1) β€” main character energy, iconic, and now you know her. go compile something gorgeous. πŸ’–βœ¨πŸŽ€πŸ¦‹πŸ’