-
Notifications
You must be signed in to change notification settings - Fork 207
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Project import using Make fails prematurely #2604
Comments
Can CLion be configured to use I looked into this a bit -- the problem here relates to using I think the option At any rate, I don't see this as a flaw with the CFE makefiles, I see it as a flaw with the assumptions of the The |
I found this link, it seems it does support the JSON file method: https://www.jetbrains.com/help/clion/compilation-database.html |
Please note that CFE/CFS is not just a simple CMake project. This is necessary to produce binaries and table files for multiple different architectures with a single "make" and build tree. However this layering means that it doesn't match what most IDEs expect when you indicate something as a "CMake project". For example with VS Code and Eclipse - I configure the IDE as a general C/C++ project with custom makefiles. I do not use whatever pre-canned logic it as for a CMake project, as CFE/CFS is more complicated than your average CMake project. |
Describe the bug
When cloning cFS and after configuring the Makefile/CMake files, CLion is unable to properly import the project.
Clion runs the command
make --just-print --print-directory --keep-going all
which typically errors out, but now does so before anything useful happens.To Reproduce
Steps to reproduce the behavior:
f378320af1d9a1b2399dabfde5f6b22af3b1416b
cfe/cmake/Makefile.sample
to the project root as well ascfe/cmake/sample_defs
make prep
thenmake --just-print --print-directory --keep-going all
f378320af1d9a1b2399dabfde5f6b22af3b1416b
make distclean && make prep
andmake --just-print --print-directory --keep-going all
Expected behavior
At the end of this import process, CLion should be able to provide code sense and other features.
System observed on:
f378320af1d9a1b2399dabfde5f6b22af3b1416b
(last known working hash:0befc9779e348b8af9d403a7f6d858a5474bc907
)dab2f42e9d54b187e6d18140d7c961cd88c2b6d1
(last known working hash:b524c691ecfde656b29b513c84be9aaafc96c453
)It would seem that the offending commit stems from #2587
Additional context
The logs provided by CLion are as follows:
It is interesting of note that
still works as intended.
You will also notice between offending and non offending commits a block in the output of the make containing:
which (including lines prior) gives CLion the information it needs to understand how
ci_lab
is built. Without it CLion is clueless.The text was updated successfully, but these errors were encountered: