The check-code-cleanliness CI jobs have not been running recently,
so this commit is to the code up to those minor changes
Change-Id: I9fb4b0213dec558f58c5ca718b3d2685564ef456
This language settings provider lets you specify the path to the
compile_commands.json and reuses existing build output parsers to figure out all
the language entries for each file to be used while indexing. With this, there
is no need to do a full build and in fact no need to have a working build
configured in CDT for indexing to work and be fully configured. This is
especially useful for non-CMake build systems that have no existing integration
in CDT but indexing would still works with little effort. The build output
parser (GCC, MSVC, etc) is selectable as part of the configuration of the CDB
provider. There is also an option to exclude any file that is not present in
the CDB. This option is useful for large projects in order to speed up indexing
but also to increase index accuracy (conflicting symbol names, etc).
Change-Id: If21455ec529f9e162cdf3e5aff7a1bca83e362f6
Signed-off-by: Marc-Andre Laperle <malaperle@gmail.com>
Note that many 2019-12 repos are not available yet or for other reasons
we aren't updating our dependencies yet, for these repos we are pointing
at the release versions of 2019-09 instead.
Change-Id: I824444d8a53cb95c5706e3ae4e26d6b2f45c5bc7
README:
Create a C/C++ Application launch as normal, and in the Launch
Configuration dialog click "Select other..." at the bottom/center
and selecting GDB (DAP) Debug Process Launcher
(you can't do this in the LaunchBar's dialog as it does not support
changing the launcher).
Then debug as you normally do (with less features so far :-)
Change-Id: Ia36acedf064b3774c6ac2a863880eaf7efe9c399
I haven't been able to get the automatic publishing working in time
and as Doug has been doing active work in that area I have temporarily
made this change.
Change-Id: I1d4b6776b77a116063b93f5f280dbf45719b7a6e
When installing CDT offline, I noticed javax.activation was missing and
needed to be pulled from Orbit. Normally Orbit dependencies should be included
in the update sites that use them.
Change-Id: I833debebadb60ac0ade9123f8e989d31f0861448
Signed-off-by: Marc-Andre Laperle <malaperle@gmail.com>
This was created for an experiment that has so far not worked other
than to cause confusion. As CDT is now building against the platform's
I-builds it is also unnecessary.
Change-Id: I6dfa720682a8f8404158acbe08d02c47f459ebd3
CDT nows defaults to targetting Eclipse 4.11 along with dependencies in the
Eclipse 2019-03 simultaenous release.
Once consequence is that 32-bit and ppc64 fragments are removed.
Change-Id: I032fedb27a4e5086f10051b3b2ca9c9c59c3b965
Signed-off-by: Marc-Andre Laperle <malaperle@gmail.com>
This target file is not for building releases, but rather to help
early identify whether we have problems coming down the pipe from
CDT dependencies.
Change-Id: I481cffb7076ba20d8293540852435975dbbd7ea8
The DSF Examples contains some commented out source that is enabled
via a script so this commit cleans that up for new formatting rules.
Change-Id: I82c5e195cc3746415c659b2c0fc72b8118cdc56c
The previous alignment of all the warnings/ignores
led to too many warnings that weren't there before. This
commit relaxes them a bit.
The core/org.eclipse.cdt.core/.settings/org.eclipse.jdt.core.prefs
is still the "master" copy, with
releng/scripts/check_code_cleanliness.sh containing the
exceptions that apply to test plug-ins.
Change-Id: Ibd4e31ade0b42b31e7cbe5a94f06c6fc15183a56
