Anno domini 2022 Mon, 21 Mar 22:48:27 -0500 Hunter Ellett via tde-devels scripsit:
Hello devs,
In the past few months I had an issue on the TGW related to imlib while building the FreeBSD port. We had resolved it as if it was my error but it turns out I was not alone.
https://forums.freebsd.org/threads/make-error-code-1-when-compiling-trinity-...
Thankfully, they resolved the issue by using make -k (a flag I didnt know about) which allows you to continue building with errors. As I write this, Im in the process of doing the same.
Anyways, he also mentions that on the Gitea workspace imlib has not been updated in 2 years while other dependencies hosted on the TGW have. Is this something we're aware of? And better yet, I was told imlib2 is backwards compatible with imlib. Is there a reason we hold an older version of imlib than point to imlib2 which most distros and BSDs have? This may resolve more than just FreeBSD issues.
It's a pitty, but imlib2 is not 100% backwards compatible to imlib11. In fact they don't even have the same API calls nor the same functionality. E.g.: in the days when imlib2 "replaced" imlib1 I had issues with red/blue color channels swapped on RGBA images, which was architecture dependend so beeing a lot of fun to debug.
As the devuan/debian repository still has both versions I doubt that the surprise-moments of imlib2 are irioned out.
Nik
Thanks.
-- Please do not email me anything that you are not comfortable also sharing with the NSA, CIA ...