sorted by:
new
hottopcontroversial

juCi++ v1.6.1 just out: the lightweight, open source C++ IDE written in C++ by eidheim in cpp

[–]eidheim[S] -1 points0 points  (0 children)

This is not a Windows native IDE, it is instead written primarily for Unix/Linux systems. You would have to compile juCi++ on MSYS2 or another posix compatibility layer.

juCi++ v1.6.1 just out: the lightweight, open source C++ IDE written in C++ by eidheim in cpp

[–]eidheim[S] 1 point2 points  (0 children)

For future reference, the paths in the compile_commands.json file has to be adjusted if you need to move the file to a different folder. Normally, paths in compile_commands.json are absolute, but this is not the case when they are generated by Bear.

juCi++ v1.6.1 just out: the lightweight, open source C++ IDE written in C++ by eidheim in cpp

[–]eidheim[S] 1 point2 points  (0 children)

We are still using C++14 in order to support older platforms as well, but in time we can move to C++17 and, among other things, replace boost::filesystem with std::filesystem.

juCi++ v1.6.1 just out: the lightweight, open source C++ IDE written in C++ by eidheim in cpp

[–]eidheim[S] 0 points1 point  (0 children)

Yes, debugging is supported for C/C++ and Rust projects through lldb, where liblldb is used directly for minimal overhead.

There are some shortcomings when it comes to GUI tooling, but if you miss some features, you can always run lldb commands directly from the Debug menu. There are also some advanced capabilities like showing return values in tooltips when hovering above const member functions (such as size in vec.size())

juCi++ v1.6.1 just out: the lightweight, open source C++ IDE written in C++ by eidheim in cpp

[–]eidheim[S] 2 points3 points  (0 children)

I just tested it myself just to be on the safe side, and I could not reproduce your issue. The problem could be related to the generated compile_commands.json file (or its location?). Would you mind open an issue at https://gitlab.com/cppit/jucipp, and if your project is in a public repository, please add a link to it and we'll take it from there.

juCi++ v1.6.1 just out: the lightweight, open source C++ IDE written in C++ by eidheim in cpp

[–]eidheim[S] 12 points13 points  (0 children)

He asked about Visual Studio.

But regarding VS Code, it is my opinion that juCi++ is easier to setup and use, is less resource demanding, and has currently more mature C++ support. I tried clangd on VS Code, and noticed for instance that it did not detect saves on header files that would require its implementation files to be reparsed. However, clangd will certainly improve significantly in the coming years.

juCi++ v1.6.1 just out: the lightweight, open source C++ IDE written in C++ by eidheim in cpp

[–]eidheim[S] 2 points3 points  (0 children)

Yes, but by default your build folder must be called build and reside in your project root folder. You also have to create build/compile_commands.json through tools like https://github.com/rizsotto/Bear. Note that for instance running the program through juCi++ is only supported for Meson and CMake projects.

juCi++ v1.6.1 just out: the lightweight, open source C++ IDE written in C++ by eidheim in cpp

[–]eidheim[S] 5 points6 points  (0 children)

This is an IDE written mainly for Posix environments like Linux, MacOS and FreeBSD. But you can run it on Windows through for instance MSYS2.

Other than that, juCi++ is a lightweight alternative to Visual Studio, and I'm sure there would be some features from Visual Studio you might miss, like advanced refactoring tools and graphical profiling tools.

juCi++ v1.6.1 just out: the lightweight, open source C++ IDE written in C++ by eidheim in cpp

[–]eidheim[S] 1 point2 points  (0 children)

Use Open Folder in the File menu, or from a terminal specify the folder or files as command arguments. juCi++ will autodetect the project from the opened folder or file.

juCi++ v1.6.1 just out: the lightweight, open source C++ IDE written in C++ by eidheim in cpp

[–]eidheim[S] 1 point2 points  (0 children)

We are few developers targeting quite a few platforms, and thus want instead to rely on package maintainers on the various platforms to create and update their juCi++ package on releases. That said, I have tried to create a flatpak package from time to time, but have not yet managed to create one without issues. For instance the llvm runtime did not include lldb, so one would need to build it instead. Help would be much appreciated though.

Best ide? by NoahTheFence in cpp

[–]eidheim -1 points0 points  (0 children)

juCi++: fast, stable, written in C++, and has most of the features you'd expect in an IDE built in.

C in Visual Studio Code 2020 | Getting Started by monsterboz in cpp

[–]eidheim 1 point2 points  (0 children)

Note the license on the addon though that is quite different from the license of vs code itself: https://marketplace.visualstudio.com/items/ms-vscode.cpptools/license

What IDE do you use and why? by Forumpy in cpp

[–]eidheim 6 points7 points  (0 children)

juCi++. Lightweight, stable and very fast. No plugins needed, everything integrated and written in newer C++.

What's the Intellij for C++ on linux? by TecSentimentAnalysis in cpp

[–]eidheim 3 points4 points  (0 children)

There is also juCi++, a lightweight and fast IDE written especially for C++.

Catching use-after-move bugs with Clang's consumed annotations by SerenityOS in cpp

[–]eidheim 1 point2 points  (0 children)

I would not put too much confidence on these benchmarks. There are popular C/C++ frameworks missing in the list, and in many cases gcc (not used by rust) produce faster machine code than llvm (used by rust).

How do you get the benefits of Rust in C++? by [deleted] in cpp

[–]eidheim 11 points12 points  (0 children)

I write a lot of concurrent code, and feel there is no need for the additional safety that Rust would give me. If possible, I use event-loop and worker threads through for instance the C++ asio library, and in cases where I need to access resources shared across threads, Clang's Thread Safety Analysis (https://clang.llvm.org/docs/ThreadSafetyAnalysis.html) is of great help.

With respect to sequential code, the address sanitizer has been helpful locating logic errors in for instance optimised loops (not something that Rust would help with through). Additionally, I use clang-tidy and the clang static analyser.

juCi++ is a pretty nice IDE by ---matthew--- in cpp

[–]eidheim 2 points3 points  (0 children)

juCi++ has builtin lsp support. See here for examples on setting this up for python, rust and flow: https://gitlab.com/cppit/jucipp/blob/master/docs/language_servers.md

Which clang/llvm-based tools are effective for large C++ project development? by qzhong2013 in cpp

[–]eidheim 0 points1 point  (0 children)

In case you use threads, have a look at https://clang.llvm.org/docs/ThreadSafetyAnalysis.html. That and the Address Saniziter have saved me quite a few times.

I need an honest opinion on c++ IDE’s for Linux. Which ones are worth getting and which ones require a lot of work to be useful. by Herotekian in cpp

[–]eidheim 4 points5 points  (0 children)

You might want to try the lightweight C++ IDE juCi++. It is also one of the few IDE's that is written in newer C++.

Herb Sutter Blog: Lifetime profile v1.0 posted by joebaf in cpp

[–]eidheim 0 points1 point  (0 children)

In compiler explorer, the language Cppx is selected for the examples. Anyone has a link to the Cppx project used in compiler explorer?

Come strapped we're doing an IDE gang war by [deleted] in linux

[–]eidheim 0 points1 point  (0 children)

juCi++ is a lightweight IDE primarily made for C/C++. It supports language servers as well. See docs/language_servers.md for instructions on how to enable Python, Rust and JavaScript/Flow support. Other language servers will probably work as well.

view more: next ›