[Pkg-pascal-devel] Bug#823706: lazarus opengl

Abou Al Montacir abou.almontacir at sfr.fr
Fri Nov 11 21:49:22 UTC 2016


Hi Paul,
On Mon, 2016-11-07 at 21:33 +0100, Paul Gevers wrote:
> Hi,
> 
> On 07-11-16 18:23, Abou Al Montacir wrote:
> > > The need for user to compile stuff inside Lazarus sources normally
> > > occurs only for packages (which may be needed by user's applications
> > > or other packages), not for applications (*.lpi).
> > 
> > When using IDE, the packages get compiled into ${HOME}/.lazarus. 
> > If you want to package them then just compile them after compiling the
> > IDE. Please see my previous mail.
> 
> The point is that I want to automatically test that what we ship is
> compilable by the user (to check e.g. that we didn't miss shipping
> stuff). Obviously, that (automatic testing) can't be done using the IDE,
> and I understood from Michalis that lazbuild was the right tool. Seems
> like he wasn't aware that it wasn't.
I agree with the goal (test delivered stuff), and agree with the tool
(lazbuild). I'm not sure I understand your statement about lazbuild is not the
right tool. If a package builds using lazbuild, then it will build using IDE.
The opposite is also true, if it does not build using lazbuild it will not build
using IDE. Of course the the issue is that you don't have any way to let
lazbuild chenge output dir except the sed on lpk or cp -Rfpl of
/usr/lib/lazarys. The latest one is my preferred.
> So, it looks like I can check most (but not all) *.lpk packages with
> lazbuild. As the IDE seems to be doing stuff differently, I can't test
> that properly.
I think I need more clarification of above statement.
> Interesting note: the lazarus source ships multiple *.lpk files that
> can't be build using only the lazarus source as the dependencies are NOT
> in the tar ball. What do you think, should we not ship these *.lpk files
> as they are useless without the proper source? E.g. lazarus doesn't have
> the source for something called bgrabitmappack:
That we can ask upstream to explain how do they expect to get sources of missing
packages. It may just be a bug in packaging.
> paul at testavoira ~ $ HOME=/tmp lazbuild -B
> /usr/lib/lazarus/1.6/components/tachart/tachartbgra.lpk
> ERROR: Broken dependency: TAChartBgra 1.0->bgrabitmappack
> 
> paul at testavoira ~/lazarus $ rgrep -i bgrabitmappack *
> components/tachart/tachartbgra.lpk:        <PackageName
> Value="bgrabitmappack"/>
> components/tachart/demo/bgra/bgrademo.lpi:        <PackageName
> Value="bgrabitmappack"/>
> components/tachart/demo/bgra/bgrademo.lpr:  bgrabitmappack, tachartbgra,
> tachartlazaruspkg,
Seems a third party project: https://github.com/bgrabitmap/lazpaint/tree/master/
bgrabitmap
there youc an find https://github.com/bgrabitmap/lazpaint/blob/master/bgrabitmap
/bgrabitmappack.lpk
and https://github.com/bgrabitmap/lazpaint/blob/master/bgrabitmap/bgrabitmappack
.pas

I hope this helps
-- 
Cheers,
Abou Al Montacir
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-pascal-devel/attachments/20161111/50bee557/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: This is a digitally signed message part
URL: <http://lists.alioth.debian.org/pipermail/pkg-pascal-devel/attachments/20161111/50bee557/attachment.sig>


More information about the Pkg-pascal-devel mailing list