having to use an older gcc to get VirtualT to build was beginning to annoy me so I spent a few minutes just now to workout why it wouldn't build and changing line 40 in src/Flu_DND.cpp from

objUnderMouse = false;

to

objUnderMouse = (void *)false;

fixes the error(the message only as who knows what side effects it might have :) )

and allows using gcc-6+ to build

bst rgrds

Russell

On 9/24/2019 9:39 AM, r cs wrote:
Thank you kindly!

On Tue, Sep 24, 2019 at 9:36 AM Russell Davis <[email protected] <mailto:[email protected]>> wrote:

    Just built it on raspbian (debian stretch) on a raspberry pi. had
    to use an older version of gcc (4.8) as it failed using gcc6. i'm
    using fltk-1.3.4. As i'm using an ARM board I had to make a few
    mods to the makefile and recall having to make a few mods to
    linking order and libraries linked that I scripted. it shouldn't
    take much to either remove the ARMisms or mod the standard makefile

    maybe the script will help

    https://gist.github.com/ukscone/577b2c8f186b4bffacc0222552dc852c


    bst rgrds

    Russell


    On 9/24/2019 3:40 AM, r cs wrote:
    If you've successfully rebuilt VirtualT under Linux lately I'd
    appreciate hearing what configuration you used to do it please.

    My Linux daily driver has issues building FLTK which I will
    continue working on, but I'm taken enough with VirtualT I'd like
    to set up a whole Linux laptop dedicated just to building and
    running VirtualT so I can keep it running literally forever (at
    least from my point of view), so I'm open to create a
    purpose-built, known-good Linux configuration.

    Information on if you're using /<whatever>/ Linux /x.x/, with
    FLTK x.x.x, and xft and freetype 2 release /x/, and gcc /x.x.x/
    etc. would be most appreciated.

    Thanks!
    rcs

-- /Níl aon tinteán mar do thinteán féin. /[Irish Gaelic]
    (There is no fireside like your own fireside.)




--
/Níl aon tinteán mar do thinteán féin. /[Irish Gaelic]
(There is no fireside like your own fireside.)


Reply via email to