On 21/11/24 11:06, Chary Chary wrote:
Also, out of curiosity, how is the beancount windows .whl file build,
which goes to the PyPI? I assume it is done using github actions? If
yes, how doe github do it, if even we struggle?
I'm not sure I understand the question.
There is really no struggle in building Beancount once the dependencies
are in place. Installing build tools on Windows sucks, but that is
hardly anything that we can fix on the Beancount side.
The "recipe" that build the release wheels is here
https://github.com/beancount/beancount/blob/master/.github/workflows/wheels.yaml
It looks complicated but it build redistributable wheels for three
platforms on a number of architectures, dealing with installing the
dependencies on all of them.
The "recipe" that simply builds Beancount and runs the tests is simpler
https://github.com/beancount/beancount/blob/master/.github/workflows/tests.yaml
As I wrote in another message, the CI infrastructure uses MSYS2 and its
package manager to install flex and bison because it is the easiest
thing to do given that MSYS is already installed on the CI virtual
machine images. There is really nothing unusual.
Cheers,
Dan
--
You received this message because you are subscribed to the Google Groups
"Beancount" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/beancount/8b28c911-6df2-4415-8881-e26517b848f8%40grinta.net.
