In the same vein as commit dff6b3bae3, this commit adds profiles
to trigger the build of the serial port component for the current
architecture, only when the profile is activated.
The serial port makefile is also improved to support building for
ppc64 and ppc64le architectures and to honour CFLAGS and LDFLAGS
that might be set in the environment, such as during RPM build.
I also hooked in the makefile "clean" targets so that invoking
"mvn clean verify" will do the right thing.
This simplifies the build for downstreams building from source
significantly.
Change-Id: Ie8cea95d953b256a1f62b77c76370ed7b3d81cee
Signed-off-by: Mat Booth <mat.booth@redhat.com>
This is a prereq for building against Photon. While at it update CBI
maven plugins to 1.1.4.
Change-Id: Ia4a5f8246978d6d6e915e1e7e022020b06889ebd
Signed-off-by: Alexander Kurtakov <akurtako@redhat.com>
Cleaned up add and remove of toolchain files, handling of when
a toolchain changes for a config, and the launch bar tracker to
be more accurate with toolchains.
Change-Id: I1a1efdf08a5f47058552c85404fe8d602d158e73
- default environment using EnvironmentReader in
CommandLauncherWrapper class in CommandLauncherManager
if no environment set for wrapper to match behaviour
of CommandLauncher
Change-Id: I71ff37b3d8f2049dc705e97bf28f939ac78bd390
- remove new exposed field from CommandLauncherManager and
add correct @since tags
- create new ICommandLauncherFactory2 interface so that no
additions are made to ICommandLauncherFactory
- add @since tag for ICBuildCommandLauncher interface
- make ContainerCommandLauncherFactory implement the new
ICommandLauncherFactory2 as well as ICommandLauncherFactory
Change-Id: I7bbacb59e284b43e6d142accf59b6ab9df274438
- fix RemoteCommandLauncher default constructor to set up
the fLocalLauncher field to point to a CommandLauncher
Change-Id: Ic01a5b1d80d4b31021c7eb7080b0986e8fb61eea
- rewrite unconfigure Meson Property page logic to parse the
output of meson --help and form the controls accordingly
- do not add an entry for help option
- add environment variable text entry to unconfigured property
page to allow the user to add things such as CFLAGS=xxxxx
- fix MesonBuildConfiguration to only use the MESON_ENV property
when running meson for the first time and to prepend the
current environment first to ensure local path, etc.. is
still set, otherwise it won't be able to find commands it
needs such as execvp
- parse the environment text string to look for entries that
use single or double quotes so that entries may use the = sign
or spaces
- when building, have ninja use the -v option so that the compile
and link commands are output to the console
Change-Id: I40d04234a7de74417c43f4c39bb2e21c86deb8a2
When a subsequent regular (non-friend) declaration of such a class
is indexed, the index binding needs to be marked as being fully
visible to name lookup.
Change-Id: I1a625f93eda1af257a9af50b5c4f115fc9bf6526
When AutoconfEditor is set to 2.67 or newer, relax the validation of
AC_INIT version string.
Change-Id: I65221857905e867e3eea2de219ddf68c60f6d39b
Signed-off-by: Chin Huat Ang <chin.huat.ang@intel.com>
- add new ICBuildCommandLauncher interface
- add new defaulted method to ICommandLauncherFactory interface
- add code to look at Build Configuration properties in
ContainerCommandLauncherFactory
- add new methods to CommandLauncherManager and
ContainerCommandLauncher
- add an update dialog call in ContainerTab
- add calls to set and get CBuildConfiguration to
ContainerCommandLauncher
Change-Id: If95fafe592c7ea4580bae1a15d168d1163e132fd
The first patch for bug 527697 made us not instantiate such an
argument, because determinePackSize() would return PACK_SIZE_DEFER.
The motivation for that fix was to avoid sizeof...(T) prematurely
instantiating to a concrete value in cases where T was mapped to
a pack expansion.
This patch reverts the change to determinePackSize() and applies a
different fix for the sizeof...(T), specific to EvalUnaryTypeId.
Change-Id: Idc231aeecb5d50e93dda364c6d2deb08057cc8b6
- fix LaunchShortcut find launch config method so that if the
active configuration is not enabled for Container build, then
it will look for config with default connection and image
Change-Id: If11865dd43cd2a08a0565b3483523002b0a00613
- fix CApplicationLaunchShortcut find config method test for
Container build so we don't ignore valid local launch configs
Change-Id: I4453ce2b26e15c9ec8ad53252e9e539c1268ddd8
- fix other way round, launching locally, then in Container
- add null check for connectionURI in Docker LaunchShort
when searching launch configs in case there is a local
configuration in the list
Change-Id: I08f89a9d1dccff3ace54667e86e9d3e8840f8694
- add logic in CApplicationLaunchShortcut find launch configs to
discard any launch config that has a Docker Connection URI
attribute
Change-Id: Ieb53f4c89b24cd3fac01bec35eafc8c62748d0b3
This avoids expontential complexity when type template arguments inside
an ambiguous name specifier themselves contain ambiguous name specifiers.
The patch also enhances TemplateIdStrategy to allow marking and backing
up to a branch point, and uses this ability in templateArgument().
Change-Id: Ia03e9cd0bc026b02b85edc05ed327cce883d6a59
- fix provided by Christian Walther
- fix createTreeForEntries() method to use addTreeListener() instead
of addPaintListener() to handle resizing
- in TreeListener, define treeExpanded method which uses pack method
for entries column
Change-Id: I28db2059d3e0561ce9e5e52f569409de9aff9a6d
- add new optional build property to run all Autotool
commands in Container
- for Autotool nature projects only, add a checkbox to the
ContainerPropertyTab to turn this new option on/off
- change the AbstractAutotoolsHandler class to look at the
optional build properties for the project to determine if
the fallback CommandLauncher used to run commands should come from
the CommandLauncherManager to run in Container or to a
local CommandLauncher
- change AutotoolsNewMakeGenerator the same way
- add new messages as needed (add a tooltip to warn user that
choosing new option may cause inconsistencies for files shared
among configurations)
Change-Id: Id828ec3015f32f320d2247bd0577944164c71df8
Not sure what changed but the launcher for these projects is now
returning null for an environment. Added a null check.
Change-Id: I05c94bb77f951f417577d0c2a3e3b4b6b996214b
(cherry picked from commit be9c1b8338)
The setting build.proj.ref.configs.enabled=true ensures CDT projects are
not rebuilt if non-related projects are changed. This setting cannot be
changed with product or command line customization, hindering products
which require this behavior.
The reason for this is that ACBuilder, which is asked for the value of
the preference, communicates with the instance scope of preferences.
Product and command line customization, however, are on default scope
level.
With this change, ACBuilder will also ask the default scope when
retrieving the value of the preference.
Change-Id: I09e895ea2a05b677e36fac9eb28f24f1f3bc2877
Signed-off-by: Simeon Andreev <simeon.danailov.andreev@gmail.com>
- modify ContainerTab to reset the error message when Docker
Connections/Image changes cause a listener notification and
then look to see if no connections or no images errors exist
- modify ContainerTab to reset the error message if the Docker
Connection selected gets changed
- bump org.eclipse.cdt.docker.launcher version to 1.1.1
Change-Id: Iad5051750a5dd53a0eb458d73570fffd9e3867c4
- bump up org.eclipse.cdt.remote.core so that autotools.core
can refer to the latest version in its dependencies
Change-Id: I4ec198d7c5d367a4a479a1dd39839f3c2d8c4a96
The special binding type CPPLambdaExpressionParameter is removed.
Instead, a lambda expression parameters's are represented as
regular CPPParameters owned by the closure type's generated
function call operator.
Change-Id: I4afeac90c2595a1f84dfa59f057d0494b64d079c
The pseudo-destructor is represented as a CPPImplicitFunction, computed
lazily and stored by CPPBasicType.
This commit also adds support for alias templates to
CPPTemplates.getTemplateName().
Change-Id: I6774556b2493cb68d32c3007d6ce48c7805595f4
The implementation strategy is as follows:
- Implement an option to find potential matches during an AST
definition search.
- Store names that resolve to ProblemBindings in the index,
as references for the candidate bindings, annotated as being
potential matches.
- Add an option to Index.findNames() to include potential matches.
- Use the added options for the index and AST searches in
OpenDeclarationsJob, prioritizing them accordingly (e.g. exact index
matches take precedence over potential AST matches, but if there
are no exact matches, potential matches from the AST and the index
are combined).
Change-Id: I19f5c58820eb3ec79a31652d69fd5b86acaba115
