With this Windows GnuCash discussion, I see several categories of choices
that seem to be in play for Windows. I'll write here my thoughts and invite
you all to add yet more clarity.
*Library and ABI ecosystem:*
- This is gcc, g++ within msys2 ecosystem while using Linux-esque
libraries.
Op dinsdag 27 augustus 2019 19:00:59 CEST schreef John Ralls:
> > On Aug 27, 2019, at 1:29 AM, Geert Janssens
> > wrote:>
> > Op maandag 26 augustus 2019 18:32:40 CEST schreef John Ralls:
> >>> On Aug 26, 2019, at 1:49 AM, Geert Janssens
> >>> wrote:>
> >>>
> >>> Op zaterdag 24 augustus 2019
> On Aug 27, 2019, at 1:29 AM, Geert Janssens
> wrote:
>
> Op maandag 26 augustus 2019 18:32:40 CEST schreef John Ralls:
>>> On Aug 26, 2019, at 1:49 AM, Geert Janssens
>>> wrote:>
>>> Op zaterdag 24 augustus 2019 19:40:06 CEST schreef Matthew Forbis:
I was running gnucash directly
> On Aug 27, 2019 w35d239, at 11:01 AM, John Ralls wrote:
>
>
> VSCode can't build anything, it's just an editor. But it can call[1] out to
> the build system to do whatever build for whatever platform you like. Visual
> Studio is the full-featured IDE and there's a free (as in beer,
My understanding, and the link you posted does nothing to gainsay it, is that
VSCode is an editor like emacs. You need other tools to do the building,
packaging, and debugging. Like emacs, those tools can be integrated with the
editor via tasks (link in previous email).
What's your full setup
Interesting.
Also very interesting, is this graph form the survey showing how the
technologies relate to each other, and from that one *might* surmise the use
cases:
https://insights.stackoverflow.com/survey/2018#correlated-technologies
If I’m reading that correctly, it looks like VSCode is
> On Aug 26, 2019, at 10:15 PM, Adrien Monteleone
> wrote:
>
>
>> On Aug 26, 2019 w35d238, at 11:28 PM, Sumit Bhardwaj
>> wrote:
>>
>> WSL would provide a Linux binary, not a Windows binary. Is that what you are
>> thinking of building? I am also not sure how to get GUI running for WSL.
Op dinsdag 27 augustus 2019 14:37:21 CEST schreef Dale Phurrough:
> I noticed earlier the use of "VS" and was watching it for context. Now I
> see more clearly what was intended.
> You want to actually use the Visual Studio UI and the Visual Studio
> compiler. And consider VS Code a lesser option
If your goal is to use a Windows computer to run and/or develop GnuCash,
then an option is to...
Execute GnuCash in Linux
Display GnuCash in Windows
I do not recommend deep investment into the current WSL. The drastically
different WSL2 is already in preview and will be available within ~6-9
Op maandag 26 augustus 2019 18:32:40 CEST schreef John Ralls:
> > On Aug 26, 2019, at 1:49 AM, Geert Janssens
> > wrote:>
> > Op zaterdag 24 augustus 2019 19:40:06 CEST schreef Matthew Forbis:
> >> I was running gnucash directly from the inst directory and not creating
> >> an
> >> installer
> On Aug 26, 2019 w35d238, at 11:28 PM, Sumit Bhardwaj
> wrote:
>
> WSL would provide a Linux binary, not a Windows binary. Is that what you are
> thinking of building? I am also not sure how to get GUI running for WSL. (WSL
> is really good tool.)
That’s what I was thinking too, but maybe
. I haven't tried it after that, but I
can try and report back.
-Sumit
-Original Message-
From: gnucash-devel
On Behalf Of John Ralls
Sent: Monday, August 26, 2019 09:33
To: Geert Janssens
Cc: gnucash-devel@gnucash.org; Matthew Forbis
Subject: Re: [GNC-dev] Building on Windows
> On Aug 26, 2019, at 1:49 AM, Geert Janssens
> wrote:
>
> Op zaterdag 24 augustus 2019 19:40:06 CEST schreef Matthew Forbis:
>> I was running gnucash directly from the inst directory and not creating an
>> installer first. This explanation makes sense.
>>
>
> There you go.
>
> It would
Op zaterdag 24 augustus 2019 19:40:06 CEST schreef Matthew Forbis:
> I was running gnucash directly from the inst directory and not creating an
> installer first. This explanation makes sense.
>
There you go.
It would be nice though to be able to run directly from the inst directory
while
Op zaterdag 24 augustus 2019 18:22:42 CEST schreef John Ralls:
> > On Aug 23, 2019, at 11:28 PM, Geert Janssens
> > wrote:
> >
> > Op vrijdag 23 augustus 2019 22:49:12 CEST schreef Matthew Forbis via
> > gnucash->
> > devel:
> >> I have finally had time to sit down and try again. When libxml
>
I was running gnucash directly from the inst directory and not creating an
installer first. This explanation makes sense.
Thanks,Matt
On Saturday, August 24, 2019, 11:22:48 AM CDT, John Ralls
wrote:
> On Aug 23, 2019, at 11:28 PM, Geert Janssens
> wrote:
>
> Op vrijdag 23
> On Aug 23, 2019, at 11:28 PM, Geert Janssens
> wrote:
>
> Op vrijdag 23 augustus 2019 22:49:12 CEST schreef Matthew Forbis via gnucash-
> devel:
>> I have finally had time to sit down and try again. When libxml development
>> was installed via pacman, it installed icu64 in addition to the
Op vrijdag 23 augustus 2019 22:49:12 CEST schreef Matthew Forbis via gnucash-
devel:
> I have finally had time to sit down and try again. When libxml development
> was installed via pacman, it installed icu64 in addition to the icu61 that
> was already installed by the gnucash script. I was able
I have finally had time to sit down and try again. When libxml development was
installed via pacman, it installed icu64 in addition to the icu61 that was
already installed by the gnucash script. I was able to remove icu64 and clear
out the entire build and inst directories and try again. It
Yes I have that commit on my system and had a clean build directory for
gnucash prior to starting the compile.
Thanks,Matt
On Thursday, August 15, 2019, 10:21:50 PM CDT, John Ralls
wrote:
I had a similar build failure on MacOS a few hours ago and pushed
Hi responding to myself:
First, forgot plain text in the first email, so I fixed the formatting in the
original below to make it easier to read.
Second, my system has both icu 61 which is the one explicitly required for
webkit as well as has icu 64 which was installed as part of the libxml2
Hi All,
I have recently worked on building GNUCash on windows to try to debug a problem
I've been having with my reports. I found a few things that look like the
script might need to be updated for (or I had something wrong in my procedure).
1. I had to install some packages through pacman
22 matches
Mail list logo
