@codebrainz I simply wanted to have a single meson.build where the import stuff is in. data, icons, po etc is rarely touched and can be in a separate meson.build so they don't create too much noise. But for the main build system work I don't want to constantly jump between build files.

Not putting meson.build into imported code was only a minor aspect but it's another advantage.

Don't build all the things into helper static libs (Scintilla, Ctags, etc) which are not distributed and only used to build the shared libgeany. These could all be built into the single libgeany shared_library directly.

I do that because they (can) have different CFLAGS/CXXFLAGS. You cannot set those per source file. Stuffing everything into one shared_library declaration (even mixed C/C++) can possibly be done but has no real advantage.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.