Preprocessor directives

Since there is now the option of disabling all the modules you do not need in your project, there might still be assets that try to be as modular as they are. For that reason, preprocessor directives would be necessary to compile features out that are not even activated. Is there a list of these?

 

@okcompute_unity alright, nice to know

 

@okcompute_unity hi,
a year has passed. What's the status of this?

 

@okcompute_unity That's great to hear. How does that work against something like the ARFoundation package. It's optional. I'd like to create assets optional in regards to this package. If available, make mine available.

 

I try to rephrase and we'll see if your answer is still no
Let's say I create an asset that has optional AR features and therefore partially relies on the ARFoundation package. Now two customers download that package, one wants to use it, the other does not, hence, one has the ARFoundation package installed while the other has not. The AR features should be compiled or stripped respectively.
How do I depend an ASMDEF on the existence of a package?
The closest that I've seen is basing it on "define constraints" but for that, ARFoundation would need to set a directive I I need to know it (That's the list I was talking about in my initial comment).
Version Defines seems to expect active packages or modules to even be selectable from the dropdown and only checks against their version but not against there existence.

Was that more clear?