How to add a custom compiler path at runtime? #4702
ClockworkV
started this conversation in
General
Replies: 1 comment 3 replies
-
We haven't ever considered this use case before -- to do this on our side we point "trunk" builds at a symlink, and then switch the symlink. Does that work for you as a start point? |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm working on a team developing a custom compiler.
We would love to have a way of comparing output of some baseline version and the currently developed version.
I could hardcode it into some properties file, but then we'd get a huge list of compilers.
Ideally I could select the compiler as "Custom version" and provide a path to the executable.
What would be the path of least resistance to adding such a feature?
I started trying to add a "compilerPath" field next to the "Option" field in the compiler view top bar, and trying to change the .exe path. This didn't immediately work, and I'm wondering whether to pursue this direction, or try something else.
Another option could be to define new compilers, via the web interface, per user.
Has anyone done something similar, or has a clear idea of how to do this? I'm somewhat familiar with Typescript, so I'm not looking for someone else to actually do the work, just directions.
Cheers!
Vladi
Beta Was this translation helpful? Give feedback.
All reactions