![]() ![]() However, the main issue from the start was that many development tools didn't support it. It is incomparably better on WSL2 and made me switch full-time to Windows. ![]() I've been a huge fan from the start, even with WSL1, but I still kept my dual-boot, mainly cause of performance. ![]() Note: This is not an intro nor a guide on how to set up and install WSL2! Windows Subsystem for Linux is out for quite some time right now & it's finally getting into perfect shape and becoming a perfect tool for most developers. It's a shame that something as simple as a project specific build space setting will likely be a deal breaker on being able to use it.TLDR: Now you can use IntelliJ IDEs installed on Windows & store projects on Linux filesystem without needing to configure anything else & with a full speed advantage □. I'm still evaluating CLion and i \*REALLY\* like it so far. I guess I could also just have a completely separate CLion install per project inside the truecrypt container with the idea./properties customized, but that seems kind of silly and wasteful (and a real pain since I'd have to re-do all of my settings/plugins/etc. Isn't there any way other than setting the entire system directory to re-point the build path? I suppose I could keep a separate idea.properties for each project's work and move them around as I start/close CLion to work on each project, but this seems hackish at best. Each project has a separate truecrypt volume with its data and so I need the source code to not "wander" when I build. I need to have the project build directories for different projects stored in project-specific locations because of compartmentalization needs. ![]() I have a similar (bus slightly different) scenario. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |