I guess about an hour per release, but most of that time would be the computer
working, not me. The main effort would be in figuring out how to set things up
so that the two builds wouldn't get mixed up.
Regards,
John Ralls
> On Apr 22, 2023, at 1:44 AM, Geert Janssens
> wrote:
>
> Out of
Thanks John. Then I'm thinking to pack a no-gui gnucash (a.k.a. python
bindings and libgnucash) on conda-forge. This could drop massive
dependencies and work on multi platforms. I have successfully build one,
but it fails to import due to macOS's rpath mechanism and I'm not quit
familiar with it.
Out of curiosity, would it be much more work to create two release bundles ?
One with and
one without python bindings ?
I recall Libreoffice has done that for quite a while to optionally bundle a
java runtime.
Though they seem to have stopped doing that.
Regards,
Geert
Op vrijdag 21 april
Hi there,
The pure python client `piecash` seems obsoleted and no longer worked with
latest sqlalchemy and gnucash, so I'm trying to switch to original python
bindings. Since they aren't shipped in the pre-built bundle, I tried to
build those bindings but it seems have to build the whole gnucash
> On Apr 21, 2023, at 3:17 AM, monson wrote:
>
> Hi there,
>
> The pure python client `piecash` seems obsoleted and no longer worked with
> latest sqlalchemy and gnucash, so I'm trying to switch to original python
> bindings. Since they aren't shipped in the pre-built bundle, I tried to
