Package Base Details: clion

Git Clone URL: (read-only)
Keywords: C C++ IDE JetBrains
Submitter: rdoursenaud
Maintainer: Zrax
Last Packager: Zrax
Votes: 106
Popularity: 7.443690
First Submitted: 2015-04-14 21:23
Last Updated: 2016-12-29 01:26

Latest Comments

1 2 3 4 Next › Last »

postadelmaga commented on 2016-12-17 05:53

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

I'm getting this when I start the debugger:

Error during pretty printers setup: Error while executing Python code.
Some features and performance optimizations will not be available.

>>>>>>>Traceback (most recent call last):
File "<string>", line 3, in <module>
ImportError: No module named 'default'
Error while executing Python code.

I guess this is a packaging problem, since the same error is also reported for the clion-eap package.

carmelo12341 commented on 2016-12-15 16:34

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

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


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

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

srki_82 commented on 2016-11-19 21:42

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.


srki_82 commented on 2016-11-19 21:38

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:

rdoursenaud commented on 2016-10-05 19:25

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!

rdoursenaud commented on 2015-12-31 06:59

@sh4wn Removing the provided GDB, cmake or JRE (Clang is not part of the package) would not change the download size any bit.
Also it may cause issues (It has in the past which is why JetBrains provides them). That's why I prefer to stick to the upstream.
But feel free to edit the PKGBUILD before install, it has all the required commands ready for you to be uncommented.

sh4wn commented on 2015-12-30 20:40

I would also vote for using the system wide GDB and Clang installations by default, now it downloads just a bunch of unnecessary stuff for most of the people.