scons support and some general questions

[Julius Ziegler]

Dear all,

I am trying to build my first flatpak and am struggling already with
the first steps and also with the general understanding of what is
going on.

Our build tree is based on scons. It does support a prefix and produces
a bin/, lib/ etc. binary installation there. For the moment, I would be
happy if I could deploy a single executable as it gets installed into
bin. It will link to some .so's which are built and installed in lib,
plus some third-party libraries, which are found in system pathes.

This file


https://github.com/flathub/org.flatpak.Builder/blob/master/org.flatpak.Builder.json

inspired me to try this approach (some omissions for brevity):

{
    "app-id": "org.atlatec.afry",
    "runtime": "org.freedesktop.Platform",
    "runtime-version": "19.08",
    "sdk": "org.freedesktop.Sdk",
    "command": "annotate",
    "modules": [
        {
            "name": "afry",
            "buildsystem": "simple",
            "build-commands": [
                        "tar -xf scons-local-2.3.0.tar.gz",
                        "python2 scons.py install --prefix=/app"
            ],
            "sources": [
                {
                     "type": "archive",
                     "url": "http://[omitted]/afry.tar",
                     "sha256": "[omitted]"

                },
                {
                    "type": "file",
                    "url": "http://[omitted]/scons-local-2.3.0.tar.gz",
                    "sha256": "[omitted]"
                }
            ]
        }
    ]
}

Here, the flatpak-builder fails with "python2: command not found.".

Is there a recipe for using scons with flatpak?

My more general question is this: I understand that to build a flatpak,
we are building a sandbox virtual machine which contains the software,
a base runtime and additional dependencies.

Now, looking at the above (failed) approach for scons, it looks to me
that we do not only have to build this "runtime" sandbox, but also a
"build-time" sandbox, which has also all requirements for _building_
the software (scons is not required for _running_ the software, and the
same will apply to many "-dev" packages, but I did not even get that
far).

Is that the case? How do I get something (like a debian style -dev
package, or the python interpreter, as in the above example) into the
build-sandbox?

Sorry for these maybe to basic questions, any pointer is appreciated!

Kind regards
Julius


-- 
Dr.-Ing. Julius Ziegler

Phone:  +49 151 722 026 63
E-Mail: ziegler at atlatec.de
Web:    www.atlatec.de

Atlatec GmbH
Haid- und Neu-Strasse 7
D-76131 Karlsruhe

Sitz der Gesellschaft: Karlsruhe | Registergericht Mannheim
Handelsregisternummer: HRB 718673 | USt-IdNr. DE293003755
Geschäftsführer: Dr. Henning Lategahn