[Pkg-pascal-devel] Bug#741792: Bug#741792: doublecmd: FTBFS: install: cannot stat '*.so*': No such file or directory

[Graham Inggs]

On 17 March 2014 21:45, Paul Gevers <elbrus at debian.org> wrote:
> If I am not much mistaken, you need to fix src/doublecmd.lpi for the new
> location of the units. I think line 43, but there are better experts on
> this mail-list.

Thanks Paul.  I did try changing src/doublecmd.lpi in various ways but
was not successful.
Alexander (doublcmd's upstream) suggested changing
components/build.sh, which I did as follows:

--- a/components/build.sh
+++ b/components/build.sh
@@ -9,7 +9,7 @@
   then
   $lazbuild /usr/lib/lazarus/default/compo
nents/lazcontrols/lazcontrols.lpk $DC_ARCH -B
   $lazbuild /usr/lib/lazarus/default/components/synedit/synedit.lpk $DC_ARCH -B
-  $lazbuild /usr/lib/lazarus/default/ideintf/ideintf.lpk $DC_ARCH -B
+  $lazbuild /usr/lib/lazarus/default/components/ideintf/ideintf.lpk $DC_ARCH -B
 fi

 # Build components

That solved the problem with zvdatetimepickerpropedit.pas but then I
got a different error:

objectinspector.pp(37,45) Fatal: Can't find unit TreeFilterEdit used
by ObjectInspector
TExternalToolList.Run Exception:
/usr/lib/lazarus/default/components/ideintf/objectinspector.pp(37,45)
Fatal: Can't find unit TreeFilterEdit used by ObjectInspector

and the problem with gifanim.pas remains.  Alexander then replied as follows:

> The real problem in lazarus package. Lazarus can not build any LCL-Qt
> application that uses controls from "lazarus/components" directory. It is
> because this components marked as "manually build" in lazarus debian package
> (lazarus debian rules file manually change it). In RPM distros (Fedora for
> example) they marked as "automatically build" (that is upstream default
> behavior) so there are no such problem. I make a workaround that worked in
> previous lazarus versions (forced build of some components from lazarus
> directory, that you can see in "components/build.sh"). But now it does not
> work because they depends on each other.

I have confirmed this by simply commenting out the section that builds
doublecmd-qt in debian/rules and the doublecmd-gtk package builds
without problem.

Regards
Graham