Conversation
|
btw something like // I tried for an hour and was not able to get anything working :(not sure if this is the best exposure of such a feature though |
|
And what about what I had mentioned earlier - write out a script/batch file and then run it in prebuild? |
|
|
|
I mean you can already do this at comptime: ( let startInfo = scope ProcessStartInfo();
startInfo.SetFileNameAndArguments("<command>");
startInfo.UseShellExecute = false;
startInfo.RedirectStandardOutput = true;
startInfo.CreateNoWindow = true;
let proc = scope SpawnedProcess();
if (proc.Start(startInfo) case .Err)
return;
let output = scope FileStream();
let sr = scope StreamReader(output);
proc.AttachStandardOutput(output);
while (!proc.HasExited)
{
let str = sr.ReadToEnd(.. scope .());
Console.Write(str);
}it's just a more convinenient way of doing that |
|
It's not the "executing things" that I object to, it's the "interacting with the build system via comptime" that I object to. |
|
but |
|
https://github.com/beefytech/Beef/pull/2417/changes#diff-b6a56ea0c901990ffc877cad40196069f530a9aa0c1418c94a40cce1e98b87f7R800
|
|
I thought it only starts a process and streams it's stdout to the output window, but I can change the implementation if you like |
|
I don't think you're hearing me, here. This feature is not happening. |
adds:
Console.Write[Line]to comptimeEnvironment.[G|S]etVariableto comptimeCompiler.Options.*eval to their enum type instead of toint32Console.RunShellCommand