Editors for meson.build, meson_options.txt and *.ninja files. Just
highlighting for now based on textmate grammars.
Added tm4e to target to enable resolving tm4e bundles.
Change-Id: I22859b2d39a96dcd777ee96d2a5e7465e4884839
Signed-off-by: Alexander Kurtakov <akurtako@redhat.com>
- use sh -c to invoke meson and ninja commands so that
the default environment including PATH is set up
- don't bother trying to find the commands locally and
don't bother trying to find local environment (only
use env options from property page or run ninja command)
- add a check after running meson to ensure that
ninja.build file gets created, otherwise issue error
message and stop build
- fix comments for RunNinjaPage
- add future Container support by allowing a special
target OS when checking for isLocal build
Change-Id: Ie8d736c0909b44fe8db14265afbc8b05262b51f3
- fix visibleWhen attribute of menuContribution
- also fix some warnings due to command not being set up
properly
Change-Id: I8b5239b1edcd5da20201e71d23dce3bfb18c6d0c
Need to convert paths from MSYS style to proper Windows
native.
Change-Id: I8c459274a1eb33af026c1ae383db67c8cbcdc29f
(cherry picked from commit fea65eeb15)
- Fix issue with Meson and changing toolchains since
Meson is based on CMake plug-ins
- Cleaned up add and remove of toolchain files and handling of when
a toolchain changes for a config
Change-Id: I147a30454c69e3d8d86fc50c561a1667ddfb5df3
- change ToolChainManager so that when creating the types map for
the first time, make it a LinkedHashMap instead of HashMap so
order of input is preserved (first in = first out)
- fix GCCPathToolChainProvider so that it adds non-tupled gcc
to the ToolChainManger before adding any tupled version
Change-Id: I84602a98dd4949a2f9847d4e72c428cdedd60688
Consider the superclass value when setting pre & post build steps, error
parsers, tool commands & tool command line patterns to avoid changing
the .cproject file unnecessary
Change-Id: Ida323982fe5bce7b0dd9b70eb23a6ee778be5403
Signed-off-by: William Riley <william.riley@renesas.com>
Store a flag to indicate if an empty or null list. Existing projects
without flag will be considered as non-empty when loaded to maintain
existing behaviour for them.
Change-Id: I745c887eb2888910c6e76d5bc057d592a3d8fb3a
Signed-off-by: William Riley <william.riley@renesas.com>
Don't rely on hardcoded path to wikitext but instead use maven to
download it and call ant properly. Moved to latest 3.0.22 wikitext.
Regenerated the help with the latest wikitext too.
To auto regenerat one has to call maven with -PregenHelp.
Change-Id: Ie30779dfa4bd1c52dfa20411f810c96288daf509
Signed-off-by: Alexander Kurtakov <akurtako@redhat.com>
- add new RunNinjaCommandHandler, RunNinja,
AbstractMesonCommandHandler, and
RunNinjaPage classes to support running ninja manually
with env variables added and options specified
- add a new build method to MesonBuildConfiguration which
specifies ninja options and environment variables
- add SWTImagesFactory for supplying the meson logo image
- add WizardMessages class for specifying messages for
meson ui wizards
- add new MesonUtils class and move stripEnvVars from
MesonBuildConfiguration to here
- add new constants to IMesonConstants interface
Change-Id: I8d635b2bd96792800bb07f4b3f1730be6e41eb24
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
- 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 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 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)
- bump up org.eclipse.cdt.remote.core so that autotools.core
can refer to the latest version in its dependencies
Change-Id: I4ec198d7c5d367a4a479a1dd39839f3c2d8c4a96
In the new toolchain wizard, the select button wasn't hooked up.
So I turned it off. Also, we had no build settings tab on the serial
launch.
Change-Id: I811f579334889085f49d298878589109c5e4a228
Move Toolchains directly under C/C++ and rename to Core
Build Toolchains. Add a label describing what the toolchains
are for in hope of avoiding confusion with managed build.
Also move Qt into C/C++.
Change-Id: Ia1d76087c65b26562d1001243ea355c7ac32365e
We weren't passing in the base settings to the compiler for
discovery. Also had a bug in the defines regex that mishandled
values with spaces in them.
Change-Id: I48183bfc3f61056324da009e58327cdcfed8754a
We were missing the dialog to ask if you wanted to continue
after build errors in a project. We were missing the method
that provided the list of projects to do that check.
Also while testing that noticed the handling of the build
and clean command UI was broken with make projects.
Change-Id: I698e151672a114bb22c815f49d362b6413b9c315
If we're building for non-local targets we need a toolchain
file. Print out an error message when it's missing at build
time. Recover when one is added.
Also a rider that makes sure the Makefile projects are
marked experimental.
Change-Id: I0c295dc5b3d71a04c60c3385ce790553f172859d
Makefile projects depend on build output parsing to pick up
compiler options to use while indexing. Sometimes, that just
doesn't work. As a back up we've always allowed users to manually
add them to the project. Long ago when we had pure make projects
we had UI for this. This change hooks that old UI up. It was a
time before build configs so they get applied to them all but it
serves it's role as a backup when users run into problems.
Unmarked everything I use here from deprecated until we decide
how to replace these with Core build config aware settings.
Change-Id: I6fc4d48e5315df3c60c7591b026ae0a53a1f505e
Removed the empty debug.core.tests project. Also removed the
utils-feature and remote-feature projects since these shouldn't
be features.
Change-Id: Ib5d297c626de5328e3421a1fc9346330d9907750
Also set BUILD_MODE to the launch mode so the makefile can do
different things based on the mode. Change template to add -g
option for debug.
Also fix a deadlock I detected due to side affect build folder
creation.
Change-Id: Ic7b13ba3238e6ef201cccb1b2bfc8dcc6956ea3a
The CMake toolchain file editor was not recording the correct
toolchain. The same was also true for the toolchain selection in
the build settings tab.
Change-Id: I62e4c7ae0175da7c1b5ffb7f89e321a371a6e8e0
Using ESP-IDF (the ESP32 FreeRTOS SDK) on MSYS2 as a test bed.
Making sure the indexer picks up as much as it can. Removed -j
since that messes up build output parsing. Add UI so you can put
it back if you want.
Change-Id: I767c739dce1412c75fb56d0bb1efceb913883a5f
Often Makefile projects are intended to be built from the project
root directory, such as ESP32 IDF projects. This adds a setting to
control that.
Change-Id: I151ebf60a7609461d24e192a9d6418fccb737055
Reuses the old makeNature. Reuses the StandardBuildConfiguration.
Generates a pretty simple project for now. Also handles the case
where you don't want to generate anything, just create an empty or
on an existing source tree.
Change-Id: I2f3cddc85d55792a2c537e37d4bc236a3073d930
Starting for Ninja, check for build.ninja file on whether to run
CMake again. Need to do same for makefiles. Change default to run
cmake --build instead of hardcoding ninja or make. Added message
to the end of the build to know when it's done.
Change-Id: Ibbb352ef7c64f6e1fcbe122ef0b73f2c91bb1aa7
- modify runCommand and runScript methods in AutotoolsNewMakeGenerator
class to take an ICommandLauncher to use
- modify AutotoolsNewMakeGenerator regenerateMakefile method to
pass a local CommandLauncher when running autotool commands, but
using one from the CommandLauncherManager when running configure
or config.status to do the configuration
- modify RemoteCommandLauncher to add a constructor that includes
the ICommandLauncher to use if the project is not remote
- fix AbstractAutotoolsHandler to use local CommandLauncher
Change-Id: Ib3f0deff3cca4b7b40459b5dd691d73dcbf2a87c
Signed-off-by: Jeff Johnston <jjohnstn@redhat.com>
The new Autotools core build executes autoreconf which is a perl
script. We've been assuming up until now they were always
Windows exes or bats. If there's no proper extension, try
finding sh and passing the command to it.
Change-Id: I71ba66d7658db0bdc45608abc356b5efe80669af
