Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

design reason for the header install method? #247

Open
M1cha opened this issue Oct 8, 2016 · 1 comment
Open

design reason for the header install method? #247

M1cha opened this issue Oct 8, 2016 · 1 comment

Comments

@M1cha
Copy link

M1cha commented Oct 8, 2016

Is there a reason that we only install the headers needed by syscalls.h and host_ops.h?
When using syscalls(in my case ioctl's) it's important to have access to all the uapi stuff.

Wouldn't it make more sense to use the default kernel header install method and then just move everything into the lkl subdirectory and recursively apply the patches?

@tavip
Copy link
Member

tavip commented Oct 8, 2016

The main reason is that the "parser" we are using the avoid name collisions with the native environment in case of Linux (e.g. struct iocb, struct ethaddr, etc) is kind of a joke. So until we use something more robust, we use this incremental approach were we improve and add support for more complex parsing as we add new headers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants