Wow. I'm really impressed! Freenas?

[simoncn]

(14-02-2015 01:21)airflow Wrote:  After setting JAVA_HOME, the error went away - but other files were missed (for example jni_md.h or libjvm.so). I solved these problems by creating symlinks to the desired places.

I believe there are other environment variables that you can set to make the Java build work without adding symlinks.

Quote:After that, compilation failed with the error "<malloc.h> has been replaced by <stdlib.h>". I could resolve this by simply removing the inclusion of malloc.h in each source-file of ohNet where it was used.

See my comment about this on the ohNet forum.

Quote:Compilation succeeded then, and I could package the zip-file with both needed .so-files of ohNet. MinimServer started successfully without an error, after which it updated itself, after which the same error occured again. I replaced the now renamed zip-file with the external libs again with my self-made version of it, after which MinimServer starts without any problems in version 0.8.3 update 57. Great! Finally! :-)

After initial configuration the server is available for my renderers in my network. I'm actually listening to music with it right now. There are several facts about MinimServer which I really like: It's faster than any other UPnP-server I tested yet. It provides a great, functional and fast search. And it takes tagging seriously. :-)

For the future I guess, updates will result in continual manual work/adaption for me. That's fine with me. But in case you want to provide an official way of providing a FreeBSD-version, I'm happy to help you if I can.

Thanks for doing this work. I am very pleased to hear that the result is successful.

Before I could make FreeBSD an officially supported platform for MinimServer, I would need to set up a FreeBSD environment so that I could build and test MinimServer running in this environment. I would also need to consider the implications for MinimServer of the missing functionality that has been discussed on the ohNet forum. I don't think it is likely that I would have the time to do this in the foreseeable future.

You won't need to rebuild the ohNet zip file for every update, only those updates that include a new version of ohNet. This would typically happen about once every couple of months.