-
Notifications
You must be signed in to change notification settings - Fork 107
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature request] a FreeBSD port #84
Comments
Hello. WIFEXITED is not in stdlib.h in FreeBSD, it is in sys/wait.h instead.
|
That's true, I've seen that being an issue with ocamllibs. I can send in a fix if you don't mind. But nonetheless, does anybody have any feedback on my request? |
Sorry I can't comment on it, I'm not familiar enough with ports |
A FreeBSD port would really be awesome. neko is working fine in my FreeBSD 10.2 box. I am not familiar with the working of git, so please send them a pull request with <sys/wait.h> path :P |
Updated the makefile at the beginning of the thread. @ncannasse would you mind if I submit it myself, pointing to HaxeFoundation/neko repository as it is (not to my own fork)? I'll take care of the blame mail if something goes wrong as well. @Vyal Pull request is in. The port works for on my machine, but I haven't done any poudriere runs on it yet (that helps to convince port commiters). You can try playing with it locally too. |
@ppenzin no problem for me |
I ran into libraries problem: need to define what neko libs would be installed. It seem that Debian What libraries do you want to see in the port? The easiest (but least practical) way is to include everything by default and may be let user exclude some of the libraries if they are building the port (binary package would come with everything). I can separate some of the libraries into additional ports (for example apache modules and GTK bindings can have their own ports). |
all of the libs here are usually installed as part of neko distrib |
Thanks for the explanation! I got them all to build (unfortunately required minor code change, pull request is coming) and enabled them in the port by default. If a user will build it they will be able to opt out of building some/all libraries, but when installing as a binary package everything will be in. Another problem is I ran into is that FreeBSD want all installed binaries to be stripped. And even though most of them are, libneko.so and the libraries are not. Should I add a strip step to the |
Thanks, with this I am almost done. I can build and install. I am sending one more pull request for strip changes, let me know if you want that. |
Can we close now ? :) |
Was just waiting for #69 to come to some resolution :) If you want me to just take current HEAD, I'll try that. |
One of the questions I got from a ports committer that I could not answer was about headers in libs/include. Contents of libs/include is only used on Windows (that's what LICENSE file in it says), right? |
Yes, those are only used on Windows. |
Thanks! On Mon, Jan 18, 2016 at 11:34 PM, Andy Li notifications@github.com wrote:
|
@ppenzin Any update on this? ;) |
Sorry, I got the most of the port working, but then stuck on licensing, FreeBSD wants to have a license stated for the project, but there are quite a few here: https://github.com/HaxeFoundation/neko/blob/master/LICENSE They have an API for declaring different licenses for different parts of the project, but I am not sure how that would work yet. I don't know if we should keep the issue open since the progress is very slow. |
For the license, you can specify multiple licenses as suggested. You may also split neko into several packages if needed, e.g. neko, neko-mysql, neko-zip, etc, and each of them may have different licenses according to our LICENSE file. Let's keep this issue open since there may be people who are interested in using neko in FreeBSD as well. |
Thanks, "split into multiple packages" approach looks interesting, I didn't think about that. |
FreeBSD committers puzzle me - after grilling me for months, they just went and accepted the code, even without waiting for me to update the version :) |
We are in: https://reviews.freebsd.org/rP426533 |
lol |
I can try |
Haxe already compiles on FreeBSD. Problem is getting hxcpp and lime work. I On Nov 23, 2016 10:43 AM, "Petr Penzin" notifications@github.com wrote:
|
I did try to build haxe on FreeBSD, but ran into trouble with OCaml, that I don't know how to resolve. Anyway, that should be probably a separate task, I can open issue on Haxe repo. Will there be a release with CMake changes (made since last release) soon? Those will help with enabling build options in the port. |
I want to have a new release too. The only thing I wish being resolved in the next release is #126, but I honestly lack the knowledge to work on it... |
I was going to look at it, but never got to the build to work, sorry. |
I've fixed #126 and released Neko 2.2.0. Please update the FreeBSD port ;) |
I have submitted the necessary changes to @ppenzin: [ snip ] Well, it doesn't seem to be that simple. I don't know why cmake is used in such a relatively complex way... I had to patch cmake files like this:
... this way we get rid of an ugly (and incorrect) FreeBSD workaround:
I just wonder why |
As discussed, I would like to add Neko to a FreeBSD's Ports Collection. I can find some traces of a Neko port and it also seems like it was
taken down.
I apologize in advance if that is too straightforward to someone, I want to explain what I am trying to do to those not very familiar with the process. Also, feedback is welcome and appreciated!
Information on how Ports Collection works can be found in Porter's
Handbook. There is a straight-forward walkthrough of a simple port at the
beginning.
A binary install package is created automatically for every port (not right away though).
Port files
To do get a port we need four files:
pkg-plist and distinfo can be (and should be) autogenerated, more on that below.
pkg-descr:
Makefile (with my comments):
I would really appreciate any feedback on this. Also, if you are curious or
want to test my work read below for instructions.
Port generation and testing
For the curious, to generate the rest of the port on a FreeBSD machine first
generate checksum (as root, connected to the internet):
This will download a tarball into distfile directory and create distinfo with a
checksum. Then get a list of files to add to pkg-plist (root not required):
Copy the list of paths at the end of the output to pkg-plist file in the same directory. After that you can proceed to test it as described in Porter's Handbook.
The text was updated successfully, but these errors were encountered: