Pkg-config for Eclipse CDT macOS | None of my brew packages are showing - eclipse

I am new to Eclipse and am setting up a Gtk development environment. I am trying to use this Eclipse plugin here: https://marketplace.eclipse.org/content/pkg-config-support-eclipse-cdt
My issue is I have been unable to get Project > Properties > C/C++ Build > Pkg-config to populate with any of my packages installed through brew.
I was following this tutorial:
https://villavu.com/forum/showthread.php?t=85880
As the tutorial suggests, in Eclipse settings > C/C++ > Build > Environment, I have added PKG_CONFIG_PATH and the pkg-config folder path as the value.
I have tried in Project > Properties > C/C++ Build > Pkg-config > Advanced to adjust the default pkg-config search path to /opt/homebrew/lib/pkgconfig which is where my packages are.
I am not sure whether it is my system, the Eclipse plugin, or I am missing something easy. If someone has a proven IDE for Gtk on mac M1, then I am also open to trying it.
Thanks!
System: Mac M1 chip, Ventura 13.1.

Related

- AVR GCC plugin

eclipse could not execute Avr-GCC
I am new in eclipse.
I intend to use the eclipse Avr GCC plugin, but after offline installation of that I confront an error:
could not execute Avr-GCC, please check the avr paths in the preferences
what's your advice to solve the error?
eclipse could not execute Avr-GCC

How to enable CUDA in eclipse without nvidia docker container?

I have installed eclipse for C/C++ version on ubuntu 18.04, 64 bit
I have installed cuda 11.0.221.
nvcc and nvcc-smi works showing that cuda compiler and device driver are both installed
I have added cuda to eclipse using eclipse->help->install new software as suggested in Nsight Eclipse Plugins Edition Getting Started Guide and Nsight Eclipse Plugins Installation Guide
While installing it failed to install the "nvidia docker container launch" but installed the "cuda developer tools" and "cuda remote launch".
After installation, I don't see any CUDA related entry in Eclipse->Window > Preferences or Eclipse->file->new project. Images are below after the question:
My question is:
What to do so that eclipse is enabled with CUDA?
Other information:
OS: ubuntu 18.04 x86_64.
cuda 11.0.221.
Eclipse information:
Version: 2022-03 (4.23.0)
Build id: 20220310-1457
OS: Linux, v.5.4.0-74-generic, x86_64 / gtk 3.22.30
Java vendor: Ubuntu
Java runtime version: 11.0.13+8-Ubuntu-0ubuntu1.18.04
Java version: 11.0.13
If your version of Eclipse is compatible with the version of the NsightEE Eclipse plugins provided with the CUDA version you're trying to install for, then - after a successful installation - the File > New Project... dialog will have the entry C/C++ > CUDA C/C++ Project.
If it doesn't show up, then the installation has failed. I would guess that it might be a version incompatibility, and you might try using an older version of Eclipse (or a newer version of CUDA). Alternatively, perhaps the installation procedure got botched somehow.

How do you change the cmake generator in Eclipse?

For some reason it forces -G Ninja when I try to build within eclipse. I would prefer Eclipse just not specify the -G option to cmake, but I can't figure out how to configure Eclipse to do that.
For exampe, this in my console window:
Building in: /home/bgass/eclipse-workspace/scomlib/build/default
cmake -G Ninja -DCMAKE_BUILD_TYPE=Release -DCMAKE_EXPORT_COMPILE_COMMANDS=ON /home/bgass/eclipse-workspace/scomlib
CMake Error: Error: generator : Ninja
Does not match the generator used previously: Unix Makefiles
Either remove the CMakeCache.txt file or choose a different binary directory.
cmake --build . -- -v
GNU Make 4.2.1
Built for x86_64-redhat-linux-gnu
Copyright (C) 1988-2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Build complete (0 errors, 0 warnings): /home/bgass/eclipse-workspace/scomlib/build/default
In a terminal it works just fine without the generator specified.
cmake -DCMAKE_BUILD_TYPE=Release -DCMAKE_EXPORT_COMPILE_COMMANDS=ON /home/bgass/eclipse-workspace/scomlib
-- Configuring done
-- Generating done
-- Build files have been written to: /home/bgass/eclipse-workspace/scomlib/build/default
I always execute cmake outside eclipse and open the generated eclipse project in Eclipse.
use -G "Eclipse CDT4 - Unix Makefiles" to specify Eclipse as the generator.
Following are the full set of Eclipse generators.
Eclipse CDT4 - NMake Makefiles
= Generates Eclipse CDT 4.0 project files.
Eclipse CDT4 - MinGW Makefiles
= Generates Eclipse CDT 4.0 project files.
Eclipse CDT4 - Ninja = Generates Eclipse CDT 4.0 project files.
Eclipse CDT4 - Unix Makefiles= Generates Eclipse CDT 4.0 project files.
Type in cmake --help to see what generators are supported by your specific cmake version.

Eclipse maven unable to locate karma executable

I am able to run my Jasmin tests in Karma using the karma command line and maven command line, but when trying to run maven (eg. mvn install) from within STS 3.2.0.RELEASE (Eclipse Juno 4.2) I get the following error:
Failed to execute goal com.kelveden:maven-karma-plugin:1.2:start (default) on project store-webapp: There was an error executing Karma. Cannot run program "karma": error=2, No such file or directory -> [Help 1]
It's as if when Eclipse shells maven, it does not have /usr/local/bin in the path. Is there a way to configure the path eclipse uses when invoking maven?
My environment is:
Mac OSX 10.8.4
STS 3.2.0.RELEASE (Eclipse Juno 4.2)
maven-karma-plugin 1.2
karma 0.8.6 (installed globally via npm
install -g karma)
Node.js 0.10.12 (installed using the OSX package)
Jean
It appears in Mac OS X 10.8 (and possible earlier), GUI apps do not get the same path as the terminal. To add /usr/local/bin to the global path, you need to edit (and possibly create) /etc/launchd.conf to include setenv PATH /usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin You must edit/create this file with admin privs so use sudo with vi or nano sudo nano /etc/launchd.conf You will need to reboot your Mac before this change can take effect. This information was found on ServerFault https://serverfault.com/questions/16355/how-to-set-global-path-on-os-x/277034#277034

cygwin gcc 4.7+ in Eclipse CDT updating from 3.4

I've followed the steps on the Cygwin wiki for updating my version of gcc. Now I have two installations of gcc in Cygwin: 3.4 in /bin and 4.7 in /usr/local/bin. Now, in Eclipse the only way to use it seems to be changing the invocation command from g++ to C:/cygwin/usr/local/bin/g++, and this has to be done for all projects. Is there any way to make Eclipse CDT use this by default? I have changed the Path environment variable, and typing g++ --version in a command line gives 4.7, but building a project in Eclipse with --version still gives 3.4