Custom build tag/target

Help
1

I currently find it useful to use #+build window to place platform-specific code into separate files. Now I’d like to target a certain category of devices that isn’t tied to a specific OS or architecture. For example, in my project it would be helpful to apply the same approach to distinguish between headless and non-headless devices.

I haven’t found a way to do this yet. I’m still pretty new to this area, so it’s possible I’m missing an existing design or convention that intentionally avoids this kind of setup.
Apologies in advance if that’s the case, thanks for your help!

1 Like
2

My best guess for this sort of thing would be to use a “when” statement, which is a compile time conditional. Then define things in that block.

maybe something like

when ODIN_ARCH == .Unknown { ... }

or do this, which could be set with -microarch command line switch

when ODIN_MICROARCH_STRING == "some arch" { ... }

You can also define your own build flags with something like

MY_ARCH :: #config(MY_ARCH, false)

when MY_ARCH { ... }

then build with
odin . -define:MY_ARCH=true

2 Likes
3

considering you can’t wrap import statements in when, even i’d like the ability to be able to define custom build tags

1 Like
4

My understanding is that only code that is actually used when compiled is pulled into the binary. Unused imports should be ignored. It seems that way at least for Odin libraries. Not sure about foreign ones.

I have a scratch project with just about everything in Odin imported so I can quickly throw something together. If I have an empty main, the resulting binary is the same size as it is if I remove all the unused imports.

Others with more experience in this area could probably correct me or explain it better.