Eclipse export generates wrong formatted Include Paths inside the .cproject #3529
Comments
bittailor
added a commit
to bittailor/mbed-os
that referenced
this issue
Jan 5, 2017
Eclipse CDT expects the include paths to include the project name like '/<project>/<include-path>' for workspace include directories. See issue ARMmbed#3529.
1 task
|
See pull request #3531 |
|
@bittailor Which OS is this on? I don't have this issue on macOS 10.11.2 (as in: I see that the paths are wrong, but Eclipse doesn't give me any warnings)... |
|
OS is OS X El Capitan 10.11.6 so nearly the same as yours. |
|
@janjongboom do you also have no warning signs (orange triangle with exclamation mark) on the include directories when you open
|
|
@bittailor Ah there, yes, I see that. Good catch. 👍 |
|
@bittailor, your PR was merged. Can this issue be closed? |
|
Fixed with PR #3531 |
adbridge
pushed a commit
that referenced
this issue
Jan 13, 2017
Eclipse CDT expects the include paths to include the project name like '/<project>/<include-path>' for workspace include directories. See issue #3529.
simonqhughes
pushed a commit
to simonqhughes/mbed-os-1
that referenced
this issue
Jan 31, 2017
Eclipse CDT expects the include paths to include the project name like '/<project>/<include-path>' for workspace include directories. See issue ARMmbed#3529.
simonqhughes
pushed a commit
that referenced
this issue
Jan 31, 2017
Eclipse CDT expects the include paths to include the project name like '/<project>/<include-path>' for workspace include directories. See issue #3529.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
When exporting a application to eclipse
mbed export -i eclipse_gcc_armand importing it into an Eclipse workspace Eclipse shows lots ofInvalid project path:warnings:This is because the include paths are wrong formatted for eclipse. They are
/./<path>instead of/<project>/<path>:I locally fixed the generator to format it correctly (will do a pull request) and the warnings are gone:
and the paths look like this:
Bug
Target
NUCLEO_F401RE
Toolchain:
GCC_ARM
Toolchain version:
not relevant
mbed-cli version:
1.0.0
meed-os sha:
0789928
DAPLink version:
not relevant
Expected behavior
correct formatted Eclipse include paths
Actual behavior
wrong formatted Eclipse include paths
Steps to reproduce
mbed export -i eclipse_gcc_armThe text was updated successfully, but these errors were encountered: