I need a "simple" buildsystem.

[Michael Gratton]

Hi,

Using Meson <http://mesonbuild.com/> is probably the best way forward: 
it's designed to get out of your way as a developer, is already well 
supported and integrated into flatpak, is widely available in all 
mainstream Linux distros, and will prevent you from having to re-invent 
several wheels if you do roll your own.

//Mike

-- 
⊨ Michael Gratton, Percept Wrangler.
⚙ <http://mjog.vee.net/>

On Sun, May 13, 2018 at 2:23 PM, Lothar Scholz 
<"scholz.lothar"@gmail.com> wrote:
> Hello,
> 
> I don't like autotools (and i would give up Linux before using them in
> my project). Can i use the simple buildsystem to generate the unix
> typical filesystem of "include/bin/lib/shared" directories and
> populate them myself with my files using my very own ruby script?
> 
> But your documentation mentions in the description of "build-commands"
> that some make and install invocation is still done.  So what must my
> build script produce? This MUST get better documented.
> 
> And is there any documentation what is in the SDK? How do i inject
> build tools like my latest version of the ruby interpreter into the
> SDK as tool and not as part of the build result?
> 
> I don't think SDK tool bundling is a good idea because there is just
> too much. This could soon make the SDK become some kind of  'Linux
> Developer Distribution' on it's own . Please only focus on the most
> common include headers and shared libraries in the runtime and the
> security restrictions.
> _______________________________________________
> Flatpak mailing list
> Flatpak at lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/flatpak