[Pkg-pascal-devel] Castle Model Viewer 5.2.0

[Michalis Kamburelis]

Hm, the important thing for now is: what errors occur afterwards? How
does the building fail? Or do you get correct "castle-model-viewer"
binary?

Can you submit a full instructions you execute and full output that results?

To explain:

- You cite 4 warnings, which mean that CASTLE_ENGINE_PATH environment
path does not point to the correct Castle Game Engine directory.

    But they are just warnings -- build tool should continue. As our
warnings tell, " We try to continue, assuming that engine unit paths
are already specified within fpc.cfg file, otherwise compilation will
fail." -> so we indeed try to continue using that assumption :), which
should be true if CGE is installed from Debian packages.

- To be clear, it's not "Castle Model Viewer" appending the "src",
it's the Castle Game Engine build tool (
https://castle-engine.io/build_tool, binary "castle-engine" ) which
gets executed when you do "compile.sh" (it pretty much just calls
"castle-engine compile"). And the build tool appends "src", because
that's how the Castle Game Engine directory should look like, when you
download the engine from our upstream downloads (
https://castle-engine.io/download ).

- Now, when Debian is packaging Castle Game Engine, it all should not
matter, at least for simple building of programs. The paths to
precompiled engine units should be specified inside your /etc/fpc.cfg
and the CASTLE_ENGINE_PATH should not be necessary.

- It's still a mystery what defines the (incorrect) CASTLE_ENGINE_PATH
in this case.

Note that I'm writing it all as upstream, I'm not testing on a Debian
system CGE from Debian packages. So, forgive me some guessing above :)

I'm using Debian myself too, but as upstream I generally test more how
things work with our downloads ( https://castle-engine.io/download ).
But if you can tell me what Debian version you're testing (stable,
testing, unstable?) and how do you reproduce this, I'll be happy to
take a look. Or maybe one of the Debian devs watching this issue can
help here too :)

Regards,
Michalis

pt., 22 lis 2024 o 18:54 Peter B <peter at pblackman.plus.com> napisał(a):
>
> On 21/10/2024 13:42, Michalis Kamburelis wrote:
> > So, suggested way forward: once everything is good with CGE
> > 7.0~alpha.3, just upgrade Debian packaging to Castle Model Viewer
> > 5.2.0, and this will be solved.
> >
> > Regards,
> > Michalis
>
> Hi Michalis,
>
> I'm afraid that after "just upgrade Debian packaging", Castle Model
> Viewer doesn't build
>
> ./compile.sh
> castle-engine: Warning: $CASTLE_ENGINE_PATH environment variable
> defined, but we cannot find Castle Game Engine sources inside:
> "/usr/src/castle-game-engine-7.0/". We try to continue, assuming that
> engine unit paths are already specified within fpc.cfg file, otherwise
> compilation will fail.
> castle-engine: Warning: $CASTLE_ENGINE_PATH environment variable
> defined, but we cannot find build tool data inside:
> "/usr/src/castle-game-engine-7.0/". We try to continue, but some
> packaging operations will fail.
> castle-engine: Warning: Path: Path
> "/usr/src/castle-game-engine-7.0/src/base" does not exist. Make sure
> that $CASTLE_ENGINE_PATH points to the directory containing Castle Game
> Engine sources.
> castle-engine: Warning: Path: Path
> "/usr/src/castle-game-engine-7.0/src/common_includes" does not exist.
> Make sure that $CASTLE_ENGINE_PATH points to the directory containing
> Castle Game Engine sources.
>
>
> It looks to me that Castle Model Viewer is appending "/src" to the value
> given in CASTLE_ENGINE_PATH
> which caused the fail. From the above log,
> "/usr/src/castle-game-engine-7.0/src/base" does indeed not exist because
> the sources are in
> "/usr/src/castle-game-engine-7.0/base"  without the "/src" appendage.
>
> Maybe the units should be in usr/share/... instead of /usr/src/.... but
> I don't know
> how Castle Game Engine can append "/src" to the install path using debputy.
>
> Can you fix Castle Model Viewer to stop appending "/src"?
>
>
> Regards,
> Peter B
>
>
>