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

Glass and SysId not installed via installAllTools #711

Open
person4268 opened this issue Jan 7, 2024 · 4 comments
Open

Glass and SysId not installed via installAllTools #711

person4268 opened this issue Jan 7, 2024 · 4 comments

Comments

@person4268
Copy link

person4268 commented Jan 7, 2024

This is because:
a)

project.getTasks().register("InstallAllTools", task -> {
task.setGroup("GradleRIO");
task.setDescription("Install All Tools");
for (WPITool tool : tools) {
task.dependsOn(tool.getToolInstallTask());
}
});
doesn't iterate over the cppTools array

b)

//toolInstallTask = project.tasks.register("${name}Install".toString(), CppToolInstallTask, name, config, dependency)
is commented out

and c) WPICppTool has no getToolInstallTask() method (not that it would be called without a being fixed.

Not sure whether it's intentional as the git history doesn't say much, but I believe I asked Peter (iirc) at Worlds and he said it wasn't intentional and was a bug (the specific question I asked was why installAllTools on Linux didn't install Glass or SysID, but it seems like it doesn't install it at all, just didn't notice as I use the installer on Windows).

@ThadHouse
Copy link
Member

ThadHouse commented Jan 8, 2024

Its not intentional, its more that I just haven't had time to do it. Its a little more complicated to grab the C++ tools on windows, as we also need to grab the MSVC runtime.

@person4268
Copy link
Author

Would bailing out/warning on Windows if the prerequisite runtime (not sure specifically which year MSVC runtime you need) is not installed be sufficient? Or are you looking more towards getting them installed (perhaps by invoking the installer or getting the MSVC dlls somehow and putting them next to the exes).

@ThadHouse
Copy link
Member

We install the runtime DLLs next to the exe when the installer runs. So that side works. So it's just gradle that we need to implement that part. The gradle tool download is not our recommendation however, we very much do recommend the installer.

@person4268
Copy link
Author

I do agree that it's generally the best option, but I generally prefer to use the gradle tool download on my personal machine, as I don't have much use for the offline artifacts and won't keep it up to date relative to my robot project anyway. I'll look towards me implementing it the coming couple of weeks if I find time to. Seems like I'd need to make gradle download edu.wpi.first.msvc:runtime from maven (if on windows) and create a CppToolInstallTask that includes all the necessary logic.

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