Uh oh!
There was an error while loading. Please reload this page.
sourcepkg: add a complete source package build - #8
Conversation
bradfitz
commented
Mar 3, 2023
Typo package |
crawshaw
commented
Mar 4, 2023
No strong opinions here, something like this makes sense. Is the top-level Makefile necessary or could those targets be in the sourcepkg/Makefile? |
raggi
commented
Mar 4, 2023
I could move the top level makefile, it just gets a bit harder to write (I could also use bash or something to do the work there). The makefile inside sourcepkg is the one that goes in the tar ball, so it could contain the targets but it'd be a bit odd for someone reading it when they just cracked open the tarball. |
crawshaw
commented
Mar 5, 2023
We're going to end up with a lot of bespoke build systems (the Java one is already oof) and so I'm wondering if we can keep ~everything in sub-levels for now. Maybe a |
raggi
commented
Mar 6, 2023
Yeah, makes sense, I'll move it to be contained. |
raggi
commented
Mar 9, 2023
note to self, from crawshaw:
there could be a target in Makefile.src to help users produce this |
80f163f to
8d5d0aaCompareraggi
commented
Aug 16, 2023
I'll have to defer addressing this, as there's something strange going on with the toolchain: |
1b4702a to
5344780CompareUh oh!
There was an error while loading. Please reload this page.
There is a makefile that will produce a libtailscale.tar.zst. This archive contains a vendored Go source tree for libtailscale, and a `configure` and `Makefile` that will produce a .so, a .a, and a .pc file for building & linking against. Updates tailscale/tailscale#8912
If you want to construct a package build for a distribution, you typically need a copy of all of the sources. This produces an archive that has a sufficiently common form that packagers can easily consume.
The final tarball
make installtarget installs .h, .so, .a and .pc into $prefix, e.g.and pkg-config is configured: