-
Notifications
You must be signed in to change notification settings - Fork 63
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
Support FreeBSD with bespoke upstream build #71
Support FreeBSD with bespoke upstream build #71
Conversation
21b659e
to
6071aac
Compare
6071aac
to
197e6be
Compare
@josevalim done. It's great to see how #60 turned out, this is the way! |
💚 💙 💜 💛 ❤️ |
🚀 🤩 🏓 🌍 🌊
|
Hi!, it seems that my FreeBSD version (13.1) isn´t compatible:
|
Hi again, after spending many hours trying to compile tailwind without success I downloaded the Linux version: |
hey @leonardorame I think this will be one of 2 issues:
Using https://people.freebsd.org/~dch/pub/tailwind/v3.2.6/tailwindcss-freebsd-x64
For the latter, I need to ask a few people to figure out how this can be accommodated. |
Hi @dch, yes I'm using quarterly ports and yes, I have gcc9, gcc10, gcc11 and gcc12. When I run ldd on that file I get this:
|
Hi @dch, I created a Jail with latest ports and it worked!. Now, it should be great if we can find a way to build it with quarterly ports. I think most users use RELEASE, which by default have quarterly ports. |
@leonardorame try this one, https://builds.sr.ht/~dch/job/950069 via
which should bind to gcc12 (lang/gcc atm) you'll need to have it installed but it |
Hi @dch - I used not your tailwind artifact on FreeBSD 13.1 (amd) with
I have gcc an gcc11 both available... @leonardorame can totally understand. One can build Elixir apps in hours and then has to spend hours or days to try to get this javascript tailwind crossover thingy running... UPDATE:
That's now way way way better to handle. I now just have a special mix step in my mix.exs that installs the freebsd bin and done!. So good !!!! |
We can't use upstream tailwind FreeBSD packages, because the vercel/pkg tool that
tailwind relies on builds in github actions, which don't support FreeBSD. Thus
we build these externally, and need to make a few modifications to accommodate this.
This is in "Works on my machine" mode presently; we could make further changes from here
if interested:
I will generate the build artifacts separately with verifiable checksum shortly, which
should improve the trust factor a bit.
Using https://builds.sr.ht/ and this manifest:
This is now the artefact at https://people.freebsd.org/~dch/pub/tailwind/v3.2.4/tailwindcss-freebsd-x64 at least for the moment.
Alternative approaches welcomed.