Makefile, docs/manual, support, toolchain: remove Eclipse integration

Back many years ago, we developed an Eclipse plugin that simplified
the usage of Buildroot toolchains. Enabling the BR2_ECLIPSE_REGISTER=y
was registering the Buildroot toolchain into a special file in your
HOME folder that the Eclipse plugin would recognize to allow to
directly use the Buildroot cross-compiler.

This Eclipse plugin has not been maintained for years. The last commit
in the repository dates back from September 2017. Since then Eclipse
has moved on, and the plugin is no longer compatible with current
versions of Eclipse.

Also, Eclipse is probably no longer that widely used in the embedded
Linux space, as other more modern IDEs have become more popular.

All in all, it's time to say good bye to this Eclipse integration.

Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
This commit is contained in:
Thomas Petazzoni
2022-07-27 21:05:10 +02:00
committed by Yann E. MORIN
parent 32b341fa34
commit c857b8ff0e
6 changed files with 9 additions and 123 deletions

View File

@@ -1,76 +0,0 @@
#!/bin/sh
# This script registers the toolchain of a Buildroot project into the
# Eclipse plugin. To do so, it adds a new line for the Buildroot
# toolchain into the $HOME/.buildroot-eclipse.toolchains file, which
# the Eclipse Buildroot plugin reads to discover automatically the
# available Buildroot toolchains on the system.
#
# This script should typically not be called manually. Instead, one
# should enable the BR2_ECLIPSE_REGISTER configuration option, which
# will lead Buildroot to automatically call this script with the
# appropriate arguments.
#
# Usage:
# eclipse-register-toolchain project-directory toolchain-prefix architecture
#
# project-directory is the absolute path to the Buildroot project
# output directory (which contains the host/, target/, build/,
# images/, etc. subdirectories). It should be an absolute and
# canonical path.
#
# toolchain-prefix is the prefix of the cross-compilation tools, i.e
# 'arm-linux-' if the cross-compiler executable is 'arm-linux-gcc'.
#
# architecture is the lower-cased name of the architecture targetted
# by the Buildroot project.
if test $# -ne 3; then
echo "Invalid number of arguments."
echo "Usage: $0 project-directory toolchain-prefix architecture"
exit 1
fi
project_directory=$1
toolchain_prefix=$2
architecture=$3
if test ! -d ${project_directory} ; then
echo "Non-existing project directory ${project_directory}"
exit 1
fi
if test ! -d ${project_directory}/host ; then
echo "Your project directory does not look like a Buildroot output"
exit 1
fi
if test ! -e ${project_directory}/host/bin/${toolchain_prefix}gcc ; then
echo "Cannot find the cross-compiler in the project directory"
exit 1
fi
TOOLCHAIN_ECLIPSE_FILE=${HOME}/.buildroot-eclipse.toolchains
# First, we remove all lines from the ${TOOLCHAIN_ECLISPE_FILE} that
# correspond to toolchains that no longer exist.
if test -f ${TOOLCHAIN_ECLIPSE_FILE} ; then
mv ${TOOLCHAIN_ECLIPSE_FILE} ${TOOLCHAIN_ECLIPSE_FILE}.tmp
cat ${TOOLCHAIN_ECLIPSE_FILE}.tmp | while read toolchain ; do
path=$(echo ${toolchain} | cut -f1 -d ':')
# Filter lines corresponding to still existing projects
echo "Testing ${path} ..."
if ! test -d ${path} ; then
continue
fi
# .. and the current project
if test ${path} = ${project_directory} ; then
continue
fi
echo ${toolchain} >> ${TOOLCHAIN_ECLIPSE_FILE}
done
rm ${TOOLCHAIN_ECLIPSE_FILE}.tmp
fi
# Add the toolchain
echo "${project_directory}:${toolchain_prefix}:${architecture}" >> ${TOOLCHAIN_ECLIPSE_FILE}