This is my first time posting on stack exchange so I apologize if this is too much or not enough info on the problem.
A few months ago I installed Ubuntu Mate 18.04 on a Raspberry Pi 3B+ and tried to compile the blink program found on the wiringPi website. I got the "No such file or directory error" but typing "gpio" in the command line confirmed that wiringPi was installed. Some time later dropped Ubuntu Mate and installed Raspian and there was no such problem - blink.c compiled without a hitch. Now I have switched back to Ubuntu Mate to use ROS and I am having the same old problem with wiringPi not working.
I copied and pasted the code and compilation commands exactly as they are from the wiringPi website so I won't include it here and I know that that should work because it did on Raspbian. I also tried more elaborate compilation commands found in similar problems on stack exchange and elsewhere and got the same error.
I searched through /usr/include and can't find wiringPi anywhere. When I tried to find it with other commands I got a list of files that was to big to read through.
What I would like help with:
I think I need to find the wiringPi.h and .c files and move them to /usr/include directory but I don't have the linux skills to refine my search to what I want.
Could ROS be interfering with gcc?
Shedding some light on why this is happening would be greatly appreciated. I've searched for this problem and tried everything that was suggested in other posts, nothing made a bit of difference.
Should I just try to get along with ROS? The point of taking this wriringPi baby step is not to skip over it when it doesn't work.