Hi Mattias,
To the project, or the package? The package would be the right place.
I have the same problem (thanks Felipe for mentioning it) on the same
code under Linux. As you told me before, I should never need to
manually add paths, as long as I add a unit from every directory to
the package. Which we did do.
A quick overview of the directory layout for both platforms. The
screenshot also shows the files included in the package and you can
see only two paths are used.
/trunk
/GFX
fpgfx.pas
/gdi
fpgfxpackage.lpk <- package used under Windows
gfxinterface.pas
/x11
fpgfxpackage.lpk <- package used under Linux
gfxinterface.pas
/examples
/gfx
/eventtest
eventtest.lpi <- depends on fpgfxpackage.lpk
Open gfx\fpgfx.pas. Popup Menu -> Unit Info -> Source Paths. Is gfx\gdi there with full filename?
/home/graemeg/programming/personal/fpGUI/gfx /opt/lazarus/packager/units/i386-linux /opt/lazarus/packager/registration This is my output. As you can see the 'x11' directory is missing.
There should be several Source Directories. One entry for gfx and one for gfx\gdi (with full filename).
I get the same as Felipe. As also, the compiling works fine, just navigating the code with Ctrl-click gives issues. What is strange, is that a couple months back when we spoke about a similar problem I had with the tiOPF code, you made some changes and everything worked fine. Until 2-4 weeks ago, when the fpGUI packages started giving problems. I haven't noticed this issue in other project packages yet. I event created a new .lpk file with a different name, thinking that something might be corrupted in the original one, but still the same problem. -- Graeme Geldenhuys Location: S 34° 03.168' E018° 49.342' http://tinyurl.com/y6lc26 There's no place like 127.0.0.1
fpgfxpackage.png
Description: PNG image
