-
-
Notifications
You must be signed in to change notification settings - Fork 144
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
Built-in C compiler #448
Comments
I'm not sure what the idea is :). Can you elaborate on what you're trying to achieve? |
Light-speed compiling without communication with an external compiler. 😄 |
You mean tup would compile files without doing a fork()/exec()? How much time would that save vs. invoking the compiler? And is most of the overhead of the fork/exec really just FUSE? What is the overhead of using the ldpreload server with fork/exec as compared to a built-in compiler? |
Yes. |
I guess give it a shot and see how it goes! I imagine it could be implemented similarly to !tup_ln (mostly in parser.c and updater.c I think). |
Just thought: Tiny C can be used as a very fast scripting engine. |
Honestly neither belong in tup, if you really want to use a programming language you can use that to generate a tupfile and then run it - perhaps from standard input instead? |
The best candidates in my humble opinion:
If you don't mind the idea, I can start working on it. ;)
The text was updated successfully, but these errors were encountered: