This file does not belong to the project clion что делать
Запуск проекта в clion
Clion и SFML
Добрый день, уважаемые программисты. Недавно, у меня появилась довольно отличная идея, создать.
CMake, CLion, PDCurses
Возникли проблемы с подключением файлов библиотеки PDCurses. CMake находит ее, подключает, но потом.
Запуск проекта без среды разработки
Здравствуйте! у меня готовый проект, но создавался он обычным способом,и файлов там много. Чтоб.
Mesteriis, Спасибо)Сейчас попробую
Добавлено через 2 минуты
DiffEreD, Спасибо) Щас попробую) Еще один вопрос от полного нуба: когда я нажимаю run у меня всплывает окно «edit configuration» я нажимаю на него и открывает как я понял настройка проекта, так что туда писать?Я в душе не понимаю!(
Kastaneda, О а я думал тебя заблочили почему то, ник был перечеркнут!
Подниму тему почти аналогичным вопросом: как подключать сторонние библиотеки в Cmake (именно его использует Clion)?
Мне нужен SFML и мои шаги для его получения слудущие:
1. Скачал с оффсайта прекомпилированную версию для minGW, распаковал,
2. Прописал в переменных среды SFML_ROOT до корневой папки распакованной библиотеки.
3. Закинул файл FindSFML.cmake в папку с такими же find файлами в директорию к cmake.
4. В cmakelist.txt прописал :
Ошибок на самом деле много и в процессе изменения cmakelist.txt они были разные. На данный момент «SFML found but some of its dependencies are missing ( FreeType libjpeg)».
Описание вроде бы очевидное, но где взять эти библиотеки и как их подключить и нужны ли они вообще?
Так же в специальном инфоокошке можно увидеть что Cmake нашел только динамические библиотеки (указан путь к ним), а вот статические увы нет, хотя они лежат в той же папке.
Здравствуйте! Также подниму тему. У меня MinGW подтянулась, но при компиляции простейшей программы (там при создании нового проекта всегда написан стартовый хеллоуворлд) выдает следующую простыню:
It fails with the following output:
Change Dir: C:/Users/Алёша/CLionProjects/start/cmake-build-debug/CMakeFiles/CMakeTmp
Run Build Command:»F:/PROGRA
mingw32-make.exe[1]: Entering directory
‘C:/Users/└ы╕°р/CLionProjects/start/cmake-build-debug/CMakeFiles/CMakeTmp’
Building C object CMakeFiles/cmTC_b9c5c.dir/testCCompiler.c.obj
gcc.exe: error:
C:\Users\в•ЁР*╨╗╤С╤Р�в•Ёв–‘\CLionProjects\start\cma ke-build-debug\CMakeFiles\CMakeTmp\testCCompiler.c:
No such file or directory
gcc.exe: fatal error: no input files
CMakeFiles\cmTC_b9c5c.dir\build.make:64: recipe for target
‘CMakeFiles/cmTC_b9c5c.dir/testCCompiler.c.obj’ failed
mingw32-make.exe[1]: *** [CMakeFiles/cmTC_b9c5c.dir/testCCompiler.c.obj]
Error 1
mingw32-make.exe[1]: Leaving directory
‘C:/Users/└ы╕°р/CLionProjects/start/cmake-build-debug/CMakeFiles/CMakeTmp’
Makefile:125: recipe for target ‘cmTC_b9c5c/fast’ failed
mingw32-make.exe: *** [cmTC_b9c5c/fast] Error 2
CMake will not be able to correctly generate this project.
Call Stack (most recent call first):
CMakeLists.txt:2 (project)
— Configuring incomplete, errors occurred!
See also «C:/Users/Алёша/CLionProjects/start/cmake-build-debug/CMakeFiles/CMakeOutput.log».
See also «C:/Users/Алёша/CLionProjects/start/cmake-build-debug/CMakeFiles/CMakeError.log».
Пожалуйста помогите разобраться, что нужно для работы ещё или почему ругается Clion. Спасибо за внимание!
CLion 2017.2 Release Candidate 2
We are approaching the final steps towards the CLion 2017.2 release and today we are glad to announce CLion 2017.2 Release Candidate 2 (build 172.3317.49). Give it a try, and if you find any bug at all, please file an issue in our tracker.
Non-project files
The users of CLion 2017.2 Release Candidate 1 noticed a new file-wide notifications appeared in non-project files. 
Files that do not belong to any CMake target are considered as not included into the project. For CLion it means that code insight features should be limited in such files, for example refactorings should not be performed. To identify these files with ease CLion marks them as greyed out in the project view. Now you can also easily identify such files in the editor, thanks to the file-wide notifications.
By the way, when you create new C++ class or C/C++ source or header file CLion suggests to add a new file to CMake target and suggests most probable options to select from. Use this feature to get all your new files included into CMake targets.
Besides, several performance improvements (in indexing) were implemented in this build. Release notes are available by the link.
Please note that to use CLion 2017.2 RC2 you need to have an active subscription (or start a 30-day evaluation period).
JetBrains
The Drive to Develop
27 Responses to CLion 2017.2 Release Candidate 2
beimingkun says:
Do I still have to add header files manually now? You have said this in the FAQ. Is this fixed now?
https://blog.jetbrains.com/clion/2014/09/clion-answers-frequently-asked-questions/
Anastasia Kazakova says:
beimingkun says:
Can I ask you how to configure CLion for cross-compile?
I have
1. Added “-D CMAKE_C_COMPILER=
-D CMAKE_CXX_COMPILER=” to Preferences/Settings | Build, Execution, Deployment | CMake | CMake options,
2. Added boost directory to cmake include_directories.
I don’t know if this is enough. It does find the correct header files now. However, in 2017.2 RC2, it complains for C++/ boost header files about “This file does not belong to any project target, code insight features might not work properly.”
BTW, I only use CLion for code reading, but not for actual compilation.
Anastasia Kazakova says:
Could you compile your project successfully? Check form the command line that the CMake call on this project with these settings run successfully.
The warning is about a different situation. It warns that you won’t be able to refactoring, etc. boost headers as they are not in the project (and most likely you indeed don’t want to).
beimingkun says:
I don’t use CLion for compilation, just for code reading. The compilation uses another mechanism.
I didn’t see this warning for boost headers in my Windows environment (MinGW+CLion). I only found this warning in my Ubuntu environment (cross compiling platform for ARM device). So I doubt whether I have configured the CLion project correctly.
Anastasia Kazakova says:
To configure CLion project correctly you need the CMake command to finish successfully on your project. Otherwise, CLion won’t be able to resolve the code in a proper way.
beimingkun says:
Yes. I have written a series of CMakeLists to configure the CLion project. And except for some CLion bugs, the code parsing is unbelievably good. My colleagues use Code Insight, VS or QT creator. I have to say, in the case of code parsing, CLion is undoubtedly the best. However, the IDE is too slow. (Although I can bear it now.) I do hope it can have a big performance improvement in the future.
Anastasia Kazakova says:
Do you mean typing performance or some intellisense like code analysis, code navigation, etc.?
Go to Settings | Appearance & Behavior | Appearance, Show memory indicator; switch it on; check the memory usage. If it’s close to the limit, then increase.
IAROSLAV KIKHTAN says:
CLion still does not able to recognize functions/symbols used inside macro definitions.
All “mature IDE features” like GotoDefinitions, FindReferences, ParametersHint, QuickInfo, QuickDefinitions, etc.. just do not work for stuffs inside macros.
Tickets are just being closed with “Won’t Fix”.
I am not believe that JatBrains cannot do that. VS can, Eclipse can, even VS Code(sic!) can.
Or do you think that C++ developer do not need macros at all?
Anastasia Kazakova says:
If you mean this (https://youtrack.jetbrains.com/issue/CPP-6544) we had some discussion about it with the team. The problem is that in general there is no way to get it parsed correctly as macro depends on its usages greatly, as it’s just a text substitution.
However, we might consider taking VS and other’s direction and solve the task in some basic cases.
Yaroslav Kihtan says:
I think that 99% cases are easy to parse correctly without any ambiguous (aliases, disable-able features, checks, etc). In ambiguous cases it is OK to just show popup with variants like others do.
Anastasia Kazakova says:
Thanks, we’ll consider that way.
Vincent says:
my 2017.1 has nice antialiased DejaVu Sans Mono (12) while starting the 2017.2.RC2 gives me an un-elegant font rendering for the same font.
Vincent says:
I’ll reply to myself…
As pointed here : http://soar.name/en/pro/ugly-fonts-in-jetbrains-ide-under-linux/
I just had to add the line
-Djava2d.font.loadFontConf=false
to my “
/.CLion2017.2/config/clion64.vmoptions” file
and restart CLion RC2.
Anastasia Kazakova says:
Thanks) We’ll check the problem and the settings.
Anastasia Kazakova says:
FB says:
How to disable the warning “This file does not belong to any prokect target, code insight features might not work properly.”? I do not want to change my project the way CLion thinks it should be, just make the warning go away.
Anastasia Kazakova says:
You can’t turn it off for now, as it shows that you’ve opened the file not included into the project in CLion. We’ll consider the possible changes to the behaviour.
FB says:
Thanks, moving back to 2017.1 then.
Mohd Faisal says:
“This file does not belong to any project target, code insight features might not work properly.”
Getting this message ever since I have updated my mac to High Sierra. Is it because of OS or something else?
Anastasia Kazakova says:
We’ve just added a notification in this case, so it was that way before, you just didn’t notice. That means file is not included into CMake project, thus CLion doesn’t treat it as a project file and turns off intellisense features, like refactorings for example.
Mark says:
The basic problem, unless I don’t understand the CLion flow, is that CLion requires the project to be built using CMake (to some degree now with Make) thus using the output from the build process for all the Intellisense features (i.e., or CTAGS).
Many people want a nice code editor (e.g., SlickEdit and Visual Code Studio come to mind) then use another mean to build the project. The team behind CLion don’t grasp this concept (at least from what I can tell). They demand the user to use CMake so their tool can use the output of the build for CLion features, which isn’t unreasonable I suppose.
The problem comes in when with the last two projects I have worked on. They use scripting tools (e.g., Perl and Python) to create auto-generated files (mainly header files). I edit on Windows, but build on a Linux box. Thus, the build process it a little more involved, but nothing outside the scope of what I have seen at other companies for their build process. Now, perhaps CLion can be coerced to work within this system, but if it does it requires a lot more hand holding. With either SlickEdit or Visual Studio Code, I can basically point it to a directly and most of my editing features are satisfied. I can’t understand why Clion can’t accomplish this same feat.
One of the most requested features is “Remote projects/toolchains support” (https://youtrack.jetbrains.com/issue/CPP-744). This feature request first create back in 2014 and one of the most requested features, but the CLion team hasn’t even assigned it to anyone and appear to have no desire to ever support this.
In my opinion, CLion is too dependent upon the output of other toolchains for its features support.
If my understanding if wrong, please correct me and point me to a support page that helps me set up the environment.
Lastly, not having the ability to turn of this banner is wasting precious screen real-estate. What idiot didn’t think people wouldn’t want to turn this off. Place the notification in the status bar.
Anastasia Kazakova says:
Thanks for your feedback.
Let me explain, how the CLion works. We use all the information from the CMake output to provide smart features in CLion. This includes not only the list of project files, compiler flags, but also linker information and more. CLion reads CMake files, as well as run CMake command to get all this information.
Still We understand that CMake is not the only build system used in the C++ eco-system. However, it’s one of the mostly used for the cross-platform projects, that’s why we started with it in CLion. But for sure, we plan to add support for the others. Also, we are currently working in the direction to implement remote projects support in CLion. Please check the roadmap for our next version and in general for the year 2018: https://blog.jetbrains.com/clion/2017/12/whats-next-clion-2018-1-roadmap/#roadmap
As for the banner, do you mean the message that the file is not in the project? You can resolve it by adding the file into CMake project. W/o it users are always confused that refactorings and other smart features are not working, as they can’t understand easily that the file is not in the project from CLion’s point of view, so CLion doesn’t have enough knowledge about it.
Adi Caspi says:
When I start a new project and write a simple main function with hello world it doesn’t let me compile and run it and says the file does not belong to any project target.
Anastasia Kazakova says:
Is the file with main function added to any CMake target?
Carlos says:
I am getting that same error. And in the CMakeLists.txt, the file which has the “Hello world” is included.
Anastasia Kazakova says:
Could you please send us a sample project which reproduces the problem? You can share it with clion-support at jetbrains.com
Discover more
CLion 2021.3 Release Candidate 2
Another Release Candidate for CLion 2021.3 is now available! To install CLion 2021.3 RC2 (build 213.5744.190), download it from the website, update from our Toolbox App, or use this snap package (for Ubuntu). The patch update from CLion 2021.3 RC is also available. You need to have an active subscription or a trial license to use CLion 2021.3 RC2. DOWNLOAD CLION 2021.3 RC2 In this EAP cycle, w
CLion 2021.3 Release Candidate
We are approaching the release, and the CLion 2021.3 Release Candidate is now available for download! To install CLion 2021.3 RC (build 213.5744.123), download it from the website, update from our Toolbox App, or use this snap package (for Ubuntu). You need to have an active subscription or a trial license to use CLion 2021.3 RC. No patches will be provided for this release candidate from the
CLion 2021.3 Goes Beta!
We are fast approaching the release – CLion 2021.3 has now reached Beta! Build 213.5744.5 is available from our website, via the Toolbox App, or as a snap package (for Ubuntu). No license is required, as this build is still free to use. DOWNLOAD CLION 2021.3 Beta CMake generator UI A new UI for setting the CMake generator was added to the CMake Profile settings page (Preferences/Settings | Build,
CLion 2021.3 EAP: VCS Enhancements and Other Fixes
The new CLion 2021.3 Early Access Preview build, 213.5605.4, is available from our website, via the Toolbox App, or as a snap package (if you are using Ubuntu). If you are on macOS, there is a separate build for Apple silicon (M1 chip). A patch update will also be made available shortly. DOWNLOAD CLION 2021.3 EAP Find the highlights below. New Push All up to Here action Sometimes, you may have sev
In CLion, header only library: file “does not belong to any project target, code insight features might not work properly”
November 2018
22.7k time
I have a header-only library project set up with the cmake command:
but when I open a source file, I get the warning:
This file does not belong to any project target, code insight features might not work properly
and I lose a lot of the functionality on things like code completion.
What is the proper way to set this up so CLion provides its usual functionality on a header-only library?
3 answers
Вы можете добавлять файлы заголовков в ваш проект, как это:
Вы также можете установить его в нескольких шагах, как так:
Хотя, как упоминалось в комментариях, вы, вероятно, не следует добавлять файлы заголовков для вашего проекта на всех.
Clion принимает информацию об исходных файлах из системы сборки CMake. При добавлении любого файла CPP источников список CMake автоматически сказать о заголовке с таким же именем. Так что, если имена каст / ч отличается (или у вас нет файла CPP на всех), вы должны включать в себя заголовок вручную.
Если вы не имеете любой исполняемый файл вы можете опустить последнюю строку, CLion будет еще знать о файлах
Маленький фон
Поскольку это совершенно правильный файл CMake и добавления включают файлы в исходные файлы, не идиоматическое, я не хочу, чтобы внести изменения в файл CMake.
Решение
Таким образом, этот заголовок не включает в исполняемых файлах и CLion уведомляет о том, что некоторые особенности коды проницательности могут не работать должным образом. Как временное решение вы можете использовать «каталог Отметить как» Библиотека файлов / Source и заголовки проекта для папки.
Как скомпилировать нормально в Clion?
На C++ возможно всё, просто это такой язык, в котором за вас никто ничего не будет делать, вы несёте ответственность за каждую мелочь, за каждую опцию, и должны это всё понимать, в отличие от других языков.
Погуглите, что такое статическая и динамическая линковки, что такое единица компиляции, объектный файл, почитайте про процесс линковки, как разрешаются имена во время линковки, почему могут быть коллизии, и т. п.
В любом языке программирования существуют runtime-библиотеки. В них хранится вся встроенная логика и стандартные библиотеки языка. В нормальных условиях принято линковать динамически. Это когда есть динамическая библиотека (DLL, SO, dynlib), она загружается в память единожды и её могут использовать все, кто к ней прилинкован.
Вы же используете Clion, который, в свою очередь, использует CMake для управления проектом. У CMake, как и, собственно, у многих других систем сборки, есть такая штука, Deploy называется. Вы же, как PHP-разработчик, ведь тоже выполняете деплой, верно? Точно так же делается и здесь, особенно на винде. Вам нужно написать CMake-target для деплоя, который сам посмотрит, что нужно вашему «сраному hello world’у», и соберёт в одном каталоге эти все дела для запуска. Дальше вы выбираете в CLion в поле Build/Run Configuration свою цель деплоя, жмёте Build. И все оказывается в одной папке и беспроблемно запускается везде.
Вот здесь есть пример использования модуля BundleUtilities для деплоя (fixup_bundle).
Спасибо за совет. у меня сейчас 2 файла есть
CMakeLists.txt
Может подскажите? не понимаю что делаю не так.
Вообще я конечно хочу писать чтобы на линукс сервере запускалось все, чисто под винду не хочу писать
Ну я же уже написал, что нужно делать. Пройдите по ссылке с примером, и напишите под себя макрос.
А на линуксе будет все само работать, ибо там уже все есть для запуска.
Manage CMake project files
Add new files
In the Project tree, right-click the folder you want to add a file into and select New from the context menu. Choose the desired file type:
Specify the name, type, and additional options for the new file.
If you clear the Add to targets checkbox, you can always add a new file to a target manually (for example, when creating another target for that file). See Quick CMake Tutorial: Adding targets for more details.
If you have selected the target on the previous step, the new entry will be automatically added to CMakeLists.txt : 
Manage included files
Add existing files
To add a file which is not included in any of the project files or CMake targets, you need to specify it as a project file manually. Use one of the following ways depending on the file location:
If the file is located under the project root, add it to a target using add_executable() or add_library() command. For example: 
When the directory that contains non-project sources is located under the project root, you can also mark it as library: right-click in the Project view and select Mark Directory As | Library Files from the context menu.
To use library files located outside the project root, you need to specify header search paths so that CLion can index the directories and provide completion and navigation for the #include statements:
Where MY_EXTERNAL_SOURCE__DIR is the required external path.
Upon any of these actions, CLion will prompt you to reload the project (when automatic reload is disabled).