![]() Another idea was to create a centralized Windows PC for users to logon via remote loginĪnother alternative could be to use WSL, which is part of Windows, so it’s more acceptable to IT, it just needs to be activated (if your machine is not too old, I suppose, and can run VMs, although WSL is not a VM) with Ubuntu (also coming from MicroSoft, installed via the MS store or from a PowerShell terminal) it uses about 2 GB of drive space plus any packages you may add, of course, so it’s much less than VS and all the things that may or may not be needed but have to be installed because we don’t know. I’m not sure how much easier this is for the users. We also had that thought using containers. This is definitely the last solution… not again please Yes, that was my solution for the last 8 years or so… and then root was back on windows… Inside, you can have a Linux environment, with ROOT 5 or 6 and anything else you need (the problem now is that Docker started to ask money for their “desktop” tool on Windows, but maybe there exist ways to deal with it). SDK without vs)įrom Stay with the much smaller and easily “embeddable” ROOT 5, if you can. Isn’t there any possibility to provide a minimum Windows root release that only needs some basics? (e.g. I guess headers and dlls are coming with the SDK, is the compiler needed for running root? What else? Of course there is no runtime for C++, Maybe you can explain me more in detail what components of Visual Studio and SDK are really needed? I also mixed up some software packages here. And I could try to bring that in a team meeting, but not sure that re-engineering the core of ROOT for Windows users would be easily accepted I’m not the guy from the legal department, but as far as I do understand, we are not allowed to use the community version.įrom don’t know what you mean by “using the Runtime Environment”. Its just really disappointing to see that there is no user-friendly (user in the meaning of having really no clue of programming) solution to install root on windows.įrom said that Visual Studio professional is needed? I don’t use Visual Studio professional, we use the free version (Community) Make a minimal root runable without visual studio (why not using the Runtime Environment)). put the core-essentials like file-io, TTree, histograms and stuff like this into a core runtime environment. Try to find an “out-of-the-box” solution.Which mismatches between build-machine and executing machine are allowed? ![]() I will not need python in a lot of cases e.g. Not only vs 2019, but also version of the sdk, what components are really needed.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |