`The issue is whether or not to build macros.py dynamically in the Android port, or just to commit the file. If it is committed, then where?
The Android platform does not support Dtrace so there is no real requirement for this to be programmatically generated.
The current workaround is to hard-code the contents of macros.py and this is committed at the top-level, although this is clearly not a general solution.
`The issue is whether or not to build macros.py dynamically in the Android port, or just to commit the file. If it is committed, then where?
The Android platform does not support Dtrace so there is no real requirement for this to be programmatically generated.
The current workaround is to hard-code the contents of macros.py and this is committed at the top-level, although this is clearly not a general solution.
https://github.com/paddybyers/node/commit/a58cae664d96c420d50a15fa2c36941b5c15c0c9