Straightforward conversion. Still usages left that need deeper
investigation how to be done proper.
Some long time commented code removed as java formatter breaks trailing
whitespaces on save.
Change-Id: If74259bed5735b0d4cc98fc2cfa609c9c53c80c9
Signed-off-by: Alexander Kurtakov <akurtako@redhat.com>
I have no idea why JAX-RS was needed to parse JSON, may be meson has
REST based web-services? Who knows.
I removed com.fasterxml.jackson.jaxrs.jackson-jaxrs-json-provider that
seems to cause wiring issue - but I'm not sure that it is really gone.
I still can see a UI from json, checked it with modifying field
descriptions in "intro-buildoptions.json"
Change-Id: I2252ae0901e4e408ba6a4752c91ad3a1fbecb096
Signed-off-by: Alexander Fedorov <alexander.fedorov@arsysop.ru>
As the pages are served in an https:// frame, modern browsers will
only successfully link content if link is also to https.
This commit includes the regenerated from Wiki output
Change-Id: If4c3bc083ddbb5dc63a9edfb2b3cd9aaf47b54de
As the pages are served in an https:// frame, modern browsers will
only successfully link content if link is also to https.
This commit includes the regenerated from Wiki output
Change-Id: Ie09f411baa02cda76d33a294c8feaa9d35d0ffbe
- add meson 0.50.support
- fix MesonPropertyPage to look for meson-info directory if the
project is already configured and use the intro-buildoptions.json
file to parse the various options and default values etc...
- fix description of MesonPropertyCheckbox to only show the first
sentence of any description
- fix tooltip to show on option name, not just the widget
- bump up version of meson ui
Change-Id: Id0a528d4ffb000bc63a007037c5e216c956a199c
Choice is one of:
Kichwa Coders Ltd
Kichwa Coders Canada Inc.
depending if contributed by UK or Canadian company
Change-Id: I5c9fb96ea6abf97858a6896911a71fa68b8400b1
The source bundles are not published to the p2 repo and having
them built causes tycho's p2 compare and replace to error like this:
[ERROR] Failed to execute goal org.eclipse.tycho:tycho-p2-plugin:1.5.1:p2-metadata (baselinereplace-p2-metadata) on project org.eclipse.cdt.autotools.docs: baseline and build artifacts have same version but different contents
[ERROR] classifier-sources: not present in baseline
Change-Id: I409f96c7a7ed054da37159b9b87564dd271c31b5
Add common warning options usually not included in -Wall. (GCC/Clang)
Added hardening options and address randomization under misc
section (GCC)
Added sanitize options under debug section. (GCC/Clang)
Change-Id: I885d8f49192018e50fcc5d28ee5e60d8785aa947
Signed-off-by: Marco Stornelli <marco.stornelli@gmail.com>
Renamed c++0x to c++11, c++1y to c++14. Added c++17 and c++20
aka c++2a.
Change-Id: I3939cb56bf887e193bffe7484c6568cf45bd315d
Signed-off-by: Marco Stornelli <marco.stornelli@gmail.com>
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>
- add new checkIfQuotedOption() method to GnuMakefileGenerator
- have ensurePathIsGNUMakeTargetRuleCompatibleSyntax() look to
see if the path is actually an option with path in which case
if it is quoted, do not try to escape white space
Change-Id: I67a286962ba67acb75d1f8c29cac47069ab07353
These docs plug-ins were having baselinereplace-p2-metadata. This is due
to still having problems with the compare&replace logic. The root pom.xml
lits <pattern>index/*</pattern> to exclude from compare, which means if
the only thing that changes is the generate files, and not the source
files, then the jar is a candidate for replace. In commit 3bab315fd2,
the version of help-docs-eclipserun-repo was changed, which means that
the generated output changes too.
Change-Id: I7f73159776d209aadaa70587988652e125b60851
This allows us to consider more than just the os and arch in the build
config names as required by the selected toolchain.
Change-Id: I3e1a52c756aca13fbe6c83a95f9a86bb2f286f1d
Use the toolchain type and id as the key to the Map holding the
toolchain files instead of the Path to the file. Also simplifies the
build config since we can always figure out the toolchain file from
the toolchain. Deprecate getting toolchain by path since that shouldn't
be needed any more.
Also took the opportunity to add javadoc to the interfaces.
Change-Id: I11ae2ad8177a3f60399742c8c19576f85ea4b8c0
Problem:
========
Common builder invokes the build on all the referenced projects. For the
markers creation, the project on which build is invoked by user is used,
that is incorrect. Once all the referenced projects are built, the
actual project starts building and removes all the markers associated
with it, hence the markers created previously for referenced projects
are removed and now clicking on error/warning in build console of
referenced projects will not open source file because of missing
markers.
Fix:
====
Always set the correct project being built for markers creation using
setCurrentProject(..) API.
Change-Id: Ief051ac664ea964816fdcbe7f2f54bcf43caa212
Signed-off-by: Umair Sair <umair_sair@hotmail.com>
Problem:
========
filterConfigsToBuild(..) always filters the configs that are once added
to set irrespective if it has been built or not. Consider scenario where
there are three project a, b, c and a depends on b & c and b depends on
c. When a is built, filterConfigsToBuild(..) returns configs of b and c.
Then b starts building and filterConfigsToBuild(..) doesn't return
config of c because its already in set. This is wrong and it should
return config of c because it is not yet built and b depends on it.
Fix:
====
If a referenced config by any project/config is not yet built,
filterConfigsToBuild(..) shouldn't filter it.
Change-Id: I5fbe77789f14ce3114200998070a7461069c98ab
Signed-off-by: Umair Sair <umair_sair@hotmail.com>
Also fix version numbers in all bundles who's binary contents have
changed despite no change in the source of the bundle.
Change-Id: Ic67b79aafa801c7ce96c5e52843ad5c881827d84
The constructor's body and the rest of the class was already using
IToolChain.
Change-Id: I905e15dcedb6c3280c271bf3c47ef6f1e898d3b9
Signed-off-by: Clément Hurlin <clement.hurlin@provenrun.com>
