trax: new recipe

[jmairboeck]

Fixes #10407

[pulkomandy]

Is installing the libraries to $libDir correct? Upstream installs them in a lib subdirectory, but I think having them in $libDir is nicer than in a subdirectory of $appsDir. Or should everything be put in a subdirectory of $appsDir, given there are two versions of the app?

Are these libraries used by multiple binaries in TraX? If so, it may make sense that this is shared code just for these binaries and not for anyone else. Otherwise, if it's private code for just one app it makes no sense to have it as a library, include it directly in the binary. And if it's meant to be used more generally, put it in $libDir and $developLibDir, and provide a _devel package, so everyone can use it in their own apps.

[jmairboeck]

Are these libraries used by multiple binaries in TraX?

They are both used by both versions of the app, according to haikuporter's policy checks.

And if it's meant to be used more generally, put it in $libDir and $developLibDir, and provide a _devel package, so everyone can use it in their own apps.

For libfind.so, that may make sense indeed, that has a kind-of "public" header in the repository (but it would need to be installed manually in the recipe). libTraX.so seems to be just for sharing code between the two app binaries.

[jmairboeck]

I created a Pull request to fix the existing standalone makefile for libfind.so. Then it could be packaged separately as e.g. "trax_findlib" (also with a secondaryArch package) and TraX made dependendant on that without complicating this recipe too much.