Package Details: clion-lldb 1:2024.3-1

Git Clone URL: https://aur.archlinux.org/clion.git (read-only, click to copy)
Package Base: clion
Description: JetBrains packaged LLVM Debugger for CLion
Upstream URL: http://www.jetbrains.com/clion
Keywords: C C++ IDE JetBrains
Licenses: custom
Submitter: rdoursenaud
Maintainer: Zrax
Last Packager: Zrax
Votes: 230
Popularity: 0.85
First Submitted: 2015-04-14 21:23 (UTC)
Last Updated: 2024-11-20 16:39 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 Next › Last »

srki_82 commented on 2017-02-16 19:49 (UTC)

@postadelmaga yaourt don't support split packages, try pacaur instead.

postadelmaga commented on 2016-12-17 05:53 (UTC)

if I try to install using yaourt, I got another packages ... am I doing something wrong ? $ yaourt -S clion resolving dependencies... looking for conflicting packages... Packages (1) jetbrains-toolbox-2:1.0.2095-1.2

Pastafarianist commented on 2016-12-16 22:03 (UTC)

I'm getting this when I start the debugger: === CTRL+C/CTRL+V START === Error during pretty printers setup: Error while executing Python code. Some features and performance optimizations will not be available. python >>>>>>>Traceback (most recent call last): File "<string>", line 3, in <module> ImportError: No module named 'default' Error while executing Python code. === CTRL+C/CTRL+V END === I guess this is a packaging problem, since the same error is also reported for the clion-eap package.

<deleted-account> commented on 2016-12-15 16:34 (UTC)

I'm not sure if anyone of you has the same problem as I do... Clion shows "can't resolve namespace/variable" errors when including, say, <cstdlib>, that lines is grayed out and the errors appear. Maybe I should open a ticket in upstream :/

orbital_sfear commented on 2016-11-22 07:26 (UTC) (edited on 2016-11-27 23:06 (UTC) by orbital_sfear)

Is anyone else suddenly getting this error? Am I doing something stupid? ==> Finished making: clion 1:2016.2.3-2 (Mon Nov 21 23:24:05 PST 2016) loading packages... error: 'clion-jre-1:2016.2.3-2-x86_64.pkg.tar.xz': duplicate target error: 'clion-cmake-1:2016.2.3-2-x86_64.pkg.tar.xz': duplicate target error: 'clion-gdb-1:2016.2.3-2-x86_64.pkg.tar.xz': duplicate target error: 'clion-lldb-1:2016.2.3-2-x86_64.pkg.tar.xz': duplicate target -- UPDATE I investigated further, and found that installing clion with pacaur, instead of packer as I was using above, the installation works fine.

Zrax commented on 2016-11-20 07:05 (UTC)

Great idea, thanks! It should be implemented in the latest (2016.2.3-2)

srki_82 commented on 2016-11-19 21:42 (UTC)

One more thing... CLion works only on x64 systems [1]. You should remove i686 from arch and unconditionally remove 32bit files from package. No need for checking for arch. [1]: https://intellij-support.jetbrains.com/hc/en-us/community/posts/205823389/comments/207284425

srki_82 commented on 2016-11-19 21:38 (UTC) (edited on 2016-11-19 23:10 (UTC) by srki_82)

@Zrax Since some of us like to use system libraries, while other want vanilla CMake, you could make split package from CLion archive. You could split it to clion, clion-jre, clion-cmake, clion-gdb and clion-lldb. That way we can easily choose wither to use system or vanilla components without modifying PKGBUILD. Maybe something like this: https://gist.github.com/anonymous/6815d54584a9c228590a89fd93409837

rdoursenaud commented on 2016-10-05 19:25 (UTC)

As I don't use CLion that much anymore, I'll stop maintaining this package. If you're keen to take over, just adopt the package!