/home/pi/lazarus_1.8RC/bin/lazbuild -B project1.lpi
- fpcres works anywhere in shell command lineHow did you add /home/pi/fpc-3.1/bin to your PATH variable?
It could be you added it only for the interactive bash shell (in which case it isn't in PATH when Lazarus is run).
Adding a symbolic link in /usr/local/bin will work because /usr/local/bin is already in PATH for your standard profile.
PATH=/home/pi/fpc/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/games:/usr/games
# I also have below environment variable set.
PPC_CONFIG_PATH=/home/pi/fpc/bin
You STILL didn't specify HOW you added the fpc-directory to the PATH. That's very important.How did you add /home/pi/fpc-3.1/bin to your PATH variable?Below is my search path and if I do not make a symbolic link I cannot have Lazarus to build successfully.
It could be you added it only for the interactive bash shell (in which case it isn't in PATH when Lazarus is run).
Adding a symbolic link in /usr/local/bin will work because /usr/local/bin is already in PATH for your standard profile.
Path is added in ".bachrc" file.Yep, in that case it's only added for bash-shells. But when a program is not run through a bash-shell (i.e. the desktop environment), it doesn't have the correct PATH. So Lazarus can't compile itself without adding an extra symlink to a directory in the PATH.
.profile is for things that are not specifically related to Bash, like environment variables PATH and friends, and should be available anytime. For example, .profile should also be loaded when starting a graphical desktop session.
.bashrc is for the configuring the interactive Bash usage, like Bash aliases, setting your favorite editor, setting the Bash prompt, etc.