5 ms·
I think there was no C++ (ahem native) debugger in IDEA... but I'll check again, could be wrong really...
by malkia 2y ago
I think there was no C++ (ahem native) debugger in IDEA... but I'll check again, could be wrong really...
- teh64 2y agoSadly not, as Clion is not available as a plugin like almost all other IDEs: https://www.jetbrains.com/products/compare/?product=idea&product=clion https://www.jetbrains.com/products/compare/?product=idea&pro...
- malkia 2y agoThanks!!! I also saw your other post about C# - maybe one day JetBrains would change their mind! I'm trying latest IDEA (2025.1 EAP) and for the first time a bazel project that I have got parsed successfully (had to enable some old legacy flag though), so there is hope!
- LeFrosch 2y agoDid you use the google plugin or the new BSP based one by JetBrains?
- malkia 2y agoOver the years I've tried both the google plugin, and now the BSP one. Mixed results. Almost always works on Linux/OSX, but my dominant platform is Windows. Yesterday tried it again (BSP one) with IDEA 21.5 EAP with nightly on the plugins, and things got synced, but was not able to find any targets (they are C++ targets), funny it found and listed a "filegroup" But I have my hopes up, the BSP looks like it's doing the right thing discovering much faster the targets, and probably needs more work just to finish all edge cases (like mine - Windows).
- pjmlp 2y agoMeanwhile Eclipse and Netbeans have been supporting mixed language development, and JNI debugging, for the last two decades.
- Macha 2y agoIntelliJ has supported this for over a decade also, and having used Eclipse for PHP a decade ago, I think it's very generous to say that that was actually supporting non-Java languages as an IDE, rather than just a very slow and heavyweight text editor. I'd say Eclipse's weakness for Python, PHP, etc. at that time led to how long IDE-skepticism has been a thing.
- pjmlp 2y agoNo it wasn't, you have to have IntelliJ and Clion to debug JNI, and there are no plans on the roadmap to ever do otherwise. In fact, the JNI tooling support on Android Studio is a custom implementation done by Android team themselves.
- memsom 2y agoIsn't that mostly because Android uses its own VM, not a standard Java one?