This time is was much better and created a package with executable files and not only. Its size however is 7.66 MB, less than yours of 8.24 MB (maybe you have different optimization options).
(commented out are not found). These are per unix/INSTALL file. I see you use different libraries. Where they come from?
Next, I did not modify BUILD_PREREQUIRES, which I anyway copied from you except cmd:msgfmt is not found in my case. Again, what is the source of information for all them?
Next:
BUILD()
{
export FORCE_UNSAFE_CONFIGURE=1 # Haiku user has root privileges
#cd clisp-clisp-$portVersion
./configure \
--with-included-regex \
--prefix=$prefix
# TODO To patch src/config.lisp
make
}
and probably --prefix=$prefix does the trick (it is the only change from previous recipe).
Finally:
TEST()
{
make check
}
again per unix/INSTALL. What exactly means (and where it comes from): make bench -Csrc
Is it equivalent of: cd src && make bench
Again where this bench target is defined?
I am sorry for so many questions. I just want to understand all this stuff
Running âmake check -Csrcâ invokdes them all in one row, but check-tests fails on 3 items (already mentioned at the begining), so it stops after that and doesnât run the 2 last tests then.
Warning: POLICY WARNING: Invalid top-level package entry "share"
Warning: POLICY WARNING: no matching provides "cmd:clisp_link" for "bin/clisp-link"
I tried several more scenaries, all resulting in 7.66 MB package. I believe it is because I really did not clone the haikuports repository and did not use it as described in document about haikuporter, just downloaded master tarball and used it locally.
Anyway, your and my recipes are converging. The only issue is haikuporter did not find libgettext, so I used libunistring instead (maybe this also afects the size). I will upload my latest recipe on google drive, but I will probably not create a merge request for it. I believe you, @Begasus can deal with recipe cleanup and submit much better than me. Of course, when a change will be necessary, I will take a look at it as soon as possible.
The idea behind all this was to prepare you so you could add this to haikuports
Starting out is always the hardest part in understanding how it all works, once you get the basics itâs rather simple (even me as a non developer can do it - granted, been busy with these kind of things for years)
Understand. Then I will prepare a merge request for the recipe and will maintain it (at least when it will fail to compile). This will take some more time, but as you said, this time is not lost.
Anyway, I will share my latest recipe on google drive and ask you to review it before that.
One thing, I still think we should go for master branch, as that is more evolved then the 2.50 branch, even if the name suggest otherwise.
In this case you could use:
You can do an âexport âŚâ in the recipe (Iâve mentioned this in the beginning somewhere), thatâs the easy way.
Or you can check for instance on inet_ntop/socket/gethostbyname checks with configure and see if a Haiku section could be added to check for those functions in libnetwork.
Taken a peek into configure/configure.in in the src/ directory, those checks are in there, but that configure script is kinda ⌠errr, not going to patch anything in there myself.
BUILD()
{
export FORCE_UNSAFE_CONFIGURE=1 # Haiku user has root privileges
./configure LDFLAGS="-lbsd -lnetwork" \ # new stuff
--with-included-regex \
--prefix=$prefix \
--datarootdir=$dataDir
# TODO Waiting for Haiku specific src/config.lisp
make
}
I see the only human readable entry libroot. It is necessary to add some more section?
) export -lbsd and -lnetwork for socket/gethostbyname etc ⌠(or patch upstream a check in configure for that)