<html><head></head><body bgcolor="#ffffff" text="#2e3436" link="#2a76c6" vlink="#2e3436"><div>Hi Michalis,</div><div><br></div><div>On Thu, 2018-01-18 at 22:25 +0100, Michalis Kamburelis wrote:</div><blockquote type="cite"><pre>2018-01-18 20:56 GMT+01:00 Michalis Kamburelis <<a href="mailto:michalis.kambi@gmail.com">michalis.kambi@gmail.com</a>>:
<blockquote type="cite">
So, we should get to the point where CGE (or any other package
using fpmake) can be compiled by simple
~~~
unset FPCDIR
fpc fpmake.pp
./fpmake # without any additional options like --globalunitdir
~~~
</blockquote>
I created a "simplest possible example of using fpmake", so that you
can test it all without dealing with (unrelated) Castle Game Engine
code and Makefiles:
- Get <a href="https://github.com/michaliskambi/simplest-fpmake-test">https://github.com/michaliskambi/simplest-fpmake-test</a> .
- Run "./testme.sh", that just calls "./fpmake".
- I think that we should make it "just work" if user installed FPC
from a Debian package. Without the need to set $FPCDIR, without the
need to pass --globalunitdir .
Right now, it will not work. Right now, you need to use
--globalunitdir pointing to the proper location when invoking fpmake
(see testme.sh comments).
(In the previous FPC versions, setting environment variable FPCDIR was
also enough, without the need for --globalunitdir . It doesn't work
for me now, although I see that the code reading $FPCDIR is in
TFPCDefaults.CompilerDefaults. As far as I observed, this was broken
in FPC 3.x upstream, unrelated to Debian.)
</pre></blockquote><div>Thank you for this example. I'll use it to debug this WE and hope we get it fixed by beginning of next week.</div><div><br></div><div><div style="white-space: normal;"><span><pre><pre>-- <br></pre>Cheers,
Abou Al Montacir</pre></span></div></div></body></html>