Hi Anton,

You know, after having a second thought, maybe it does not make much sense 
to have it compiled under Windows natively.
I was unable to find any Windows console function calls in the source code 
(such as SetConsoleTextAttribute). And, as far as I can see from report.cc, 
all colors are made by ANSI ESC sequences not wrapped into any platform 
#ifdefs, but ESC sequences do not work with pure Windows Console (unless 
something such as ANSICON 
<http://en.wikipedia.org/wiki/ANSI_escape_code#cite_note-Ansicon-7>
installed).
That means if Windows build succeeds, there will be no colorful output 
out-of-the-box.

Unless I find some time to contribute (or anybody else does) to the project 
and add some pieces #ifdef WIN32 ... SetConsoleTextAttribute ... #endif, I 
do not see spending time to compile it natively for Windows reasonable.

IMHO, it is better to bother installing Cygwin, than to (1) do a bunch of 
tricks during compilation (2a) still have black&white output or (2b) still 
install a "dependency" ANSICON.


And yes, Cygwin bash shell has functions to make the life easier. 
One make write something like this in some bash script:

function bal {
        ledger -sVc bal $@
}

function reg {
        ledger --tail 20 -S d -w reg $@
}

To have a similar effect, I had to create a separate *.cmd files for each 
function.

On Wednesday, July 9, 2014 10:22:59 AM UTC-4, Anton Vodonosov wrote:
>
> On Wednesday, July 9, 2014 5:14:43 PM UTC+3, Maksym Satula wrote:
>
>> This is still a plan B for me, and my next goal is to have a native 
>> Windows binary compiled with MSVC 12 (VS 2013), which is much trickier. But 
>> that is not a topic for this thread.
>>
>
> Please don't forget to share your results on this group 
>  
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Ledger" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to