[Pkg-pascal-devel] Castle Model Viewer 5.2.0

[Abou Al Montacir]

Hi All,

On Sun, 2024-11-24 at 10:42 +0000, Peter Blackman wrote:
> On 24/11/2024 07:03, Michalis Kamburelis wrote:
> > Can you submit a full instructions you execute and full output that results?
> Attaching the debian tarball (the source package build works).
> Just unpack the debian directory into the source tree at top level.
> Easiest way to try a build, is to run debuild (no options or switches 
> needed)
> (debuild is in the Debian package devscripts)
I'll have a look at this, I think this is more on our side, rather than on
upstream side.
I'm just lacking a bit of time, but would for sure dig into this before next WE.
> 
> > - To be clear, it's not "Castle Model Viewer" appending the "src",
> > it's the Castle Game Engine build tool (
> Whatever. My point is that "Castle Game Engine" and "Castle Model Viewer",
> need to use the same directories. This does not seem to be happening.
Normally, CGE provides FP units path and all units should be found.
On Debian, we don't compile against sources, we enforce using pre-compiled units
to conform to Debian policy.
The issue, is that most FPC packages love using sources and this creates trouble
for us, but we need to tack all related issues and then ask upstream to fix
them.

The fact that CGE sources are not found, is normal, as we should not even build
depend on CGE sources.
> > - 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.
> NO, please!!  /etc/fpc.cfg is owned by fpc, and under root privilege.
> I can't be changed by another package's build.
Yes, but CGE adds a file in /etc/fpc.cfg.d/ which support was added by me to
handle similar issues on FPC libraries.
> 
> You can use a local fpc.cfg, or an environment variable.
> > - It's still a mystery what defines the (incorrect) CASTLE_ENGINE_PATH
> > in this case.
> It not a mystery, I thought I defined it correctly
> (using the directory that the units are actually in),
> but its gets mangled by "/src" being appended.
> If I remove the definition, build fails immediately with
> Fatal: Can't find unit CastleUtils used by castle_model_converter
> 
> I suspect the solution is to get working definitions of
> FPCDIR, CGE_UNITS_DIR & CASTLE_ENGINE_PATH into debian/rules
> Nothing I have tried so far will work.
Let me check all this and I'll also write some doc about how FPC based libraries
should work.
> 
> > 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.
> FWIW, I'm using Trixie (testing),
> but if you can demonstrate a working build on any distribution
> (without changing /etc/fpc.cfg !) that would be useful.
> (Even Arch AUR, or Ubuntu ppa would help)
Generally, one should build using sid which is easy if you have gbp and pbuilder
correctly configured.
I can help on that if needed.
-- 
Cheers,
Abou Al Montacir

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-pascal-devel/attachments/20241124/3e9c32fd/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: This is a digitally signed message part
URL: <http://alioth-lists.debian.net/pipermail/pkg-pascal-devel/attachments/20241124/3e9c32fd/attachment.sig>