orbea

> One difference, though, is that before makefile.shared used to produce both shared and static libraries. Now I have to use makefile.unix to produce the static lib. Is that intended?...

> Anyway, this is what used to happen with the old makefile.shared, so I wonder.. why don't we keep supporting it? I think this was a consequence of not having...

@uroni This fix should be correct?

So...firefox is dead? How about porting it to palemoon? There is a lot of theme stuff that needs to be fixed there even if they dont have australized...

Well, I kind of disagree. There is a lot wrong with palemoon that CTR has fixed in firefox. Sure there are some stand alone addons that may work, but they...

I think a better solution would be to add at least a pkgconfig file for colm and use `PKG_CHECK_MODULES` so that `configure` would know about the `colm_CFLAGS` and `colm_LIBS` environment...

pkgconfig files (`.pc`) are widely supported and work for many build cases such as non-standard install locations of dependencies and cross compiling. On the other hand installing libtool archive files...

@barracuda156 `hostLangAsm` is supposed to be an exported symbol in `libfsm`, but perhaps it was the wrong symbol to check for. What symbols are exported in your `libfsm`? A `pc`...

I suggest that `ninja` is not hardcoded. Users could also use `samu` from the samurai project which is fully viable. https://github.com/michaelforney/samurai

I don't know about Alpine, but it is not a symlink in Slackware. Slackware current by default uses ninja, but it allows setting `NINJA=samu` as an environment variable. Ideally they...