Skip to content
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

Missing documentation on getting C-in-docker running. #2

Open
cmorty opened this issue Apr 24, 2020 · 1 comment
Open

Missing documentation on getting C-in-docker running. #2

cmorty opened this issue Apr 24, 2020 · 1 comment

Comments

@cmorty
Copy link

cmorty commented Apr 24, 2020

I tried to get the C-in-docker example to run using Windows and a Linux-Docker-Image, but failed. The readme just says, that it does not run out of the box, but not what needs to be done. 15knots/cmake4eclipse#110 suggests that this should be working.
I'm experimenting using cpp-2020-03.
The closest I got was creating a Makefile project and using a Makefile that calls cmake. That way I was at least able to get the Builtins and System-includes into Eclipse. I however failed to get the Output Parser, as well as the Compilation Database Parser to work.
Thanks in advance!

@15knots
Copy link
Owner

15knots commented Feb 6, 2022

I once had the running in a docker container on Linux. Unfortunately I forgot how I configured the docker daemon and the Eclipse workbench.
For the Compilation Database parser, I doubt include-path detection will work when building in a (Linux-)docker container on Windows. In this case, the parser is expecting backslash-saparated directory names but cmake is running in a Linux container and writes forward slashes to the compile_commands.json file.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants