Hi,

I normally don't add FPC bin directory to my PATH environment variable, because I use multiple versions of FPC.

But around the time FPC 2.4.0 was released, Lazarus IDE cannot find fpcres when I rebuild the IDE. So I have to open a command prompt, set the PATH environment variable, and then run Lazarus IDE and rebuild it from inside the command prompt.

Why can't Lazarus IDE find the 'fpcres' program in the same directory location as the specified ppcXXX FPC compiler?

Here are the last few lines of build messages when I try and build Lazarus IDE from a desktop icon.

------------------------------------
[....snip.....]
"Compiling package SQLDBLaz 1.0.1" completed
make: Entering directory `/opt/git/lazarus_argon'
/usr/bin/make -C ide ide
make[1]: Entering directory `/opt/git/lazarus_argon/ide' ../tools/svn2revisioninc .. revision.inc
/usr/bin/make --assume-new=lazarus.pp lazarus
make[2]: Entering directory `/opt/git/lazarus_argon/ide' /opt/fpc_2.4.1/x86_64-linux/bin/ppcx64 -gl -dlclgtk2 -Fu../lcl/units/x86_64-linux -Fu../lcl/units/x86_64-linux/gtk2 -Fu../components/codetools/units/x86_64-linux
-Fu../components/synedit/units/x86_64-linux -Fu../components/custom -Fu../components/mpaslex -Fu../ideintf/units/x86_64-linux -Fu../designer -Fu../debugger -Fu../debugger/frames -Fu../converter -Fu../packager -Fu../packager/frames -Fu../packager/units/x86_64-linux -Fu../units/x86_64-linux -Fuframes -Fu. -Fiinclude -Fiinclude/linux -Fi../images -FE.. -FU../units/x86_64-linux -Cg
-Fl/usr/lib/gcc/x86_64-linux-gnu/4.2.4 -Flinclude
-Fl/etc/ld.so.conf.d/*.conf @/home/graemeg/.lazarus-stable/idemake.cfg -dx86_64 lazarus.pp
Free Pascal Compiler version 2.4.1 [2010/01/14] for x86_64 Copyright (c) 1993-2009 by Florian Klaempfl
Target OS: Linux for x86-64
Compiling lazarus.pp
/opt/git/lazarus_argon/ide/lazarus.pp(130,1) Error: resource compiler "fpcres" not found, switching to external mode
/opt/git/lazarus_argon/ide/lazarus.pp(130,1) Fatal: There were 1 errors compiling module, stopping

------------------------------------

The various locations of programs on my system.

Lazarus
/opt/lazarus/
^--- is a directory symlink from /opt/git/lazarus_argon

/opt/fpc_2.4.1/$(TargetCPU)-$(TargetOS)/bin/ppcXXX ^-- 32 & 64 bit directories, and Win32 cross-compiler eg:
/opt/fpc_2.4.1/x86_64-linux/bin/*
/opt/fpc_2.4.1/i386-linux/bin/*
/opt/fpc_2.4.1/i386-win32/bin/*
/opt/fpc_2.4.1/cross_i386-win32/bin/*

/opt/fpc_2.2.5/$(TargetCPU)-$(TargetOS)/bin/ppcXXX ^-- 32 & 64 bit directories, and Win32 cross-compiler same layout as FPC 2.4.1 directory.

Currently my Lazarus IDE is setup to use the following compiler: /opt/fpc_2.4.1/x86_64-linux/bin/ppcx64

So surely based on that compiler location, the IDE can find 'fpcres' inside /opt/fpc_2.4.1/x86_64-linux/bin/ without the need of the PATH environment variable set?

Regards,
- Graeme -

Anybody go a solution for this?

Maybe as an alternative to "auto guessing the location of fpcres", add a new option in Environment settings like the paths to Compiler and Compiler Source - adding an option for 'Path to fpcres'?

Do all Linux users (and maybe Windows users too) always specify FPC bin directory in the PATH environment variable? If so how do you handle working with multiple FPC versions and Lazarus IDE using the correct version fpcres tool?

Regards,
- Graeme -

1 2 3 4 5 6 7 123456789012345678901234567890123456789012345678901234567890123456789012345

Regards,
- Graeme -

Il 29/01/2010 07:47, Graeme Geldenhuys ha scritto:

Lazarus doesn't call fpcres - it's fpc that calls fpcres to compile resources. You might place fpcres in the same directory of ppcxxx executable. Or, you could add a -FD or -e option to the fpc.cfg file, playing with $fpcversion and $fpctarget macros.

Giulio

Giulio Bernardi wrote

Lazarus doesn't call fpcres - it's fpc that calls fpcres to compile resources.

Ah, I did not know that.

You might place fpcres in the same directory of ppcxxx executable. Or, you could add a -FD or -e option to the fpc.cfg file, playing with $fpcversion and $fpctarget macros.

Thanks, I did not know about the -FD option either. I already used the macros for other paths and modifying my ~/.fpc.cfg file with the -FD option solved the problem.

Thank you very much!

Regards,
- Graeme -