WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: VT needs gpm.  (Read 365 times)

Offline labeas

  • Full Member
  • ***
  • Posts: 126
VT needs gpm.
« on: February 12, 2017, 08:25:33 PM »
TC's X mouse:Copy/Paste is good; but VT also needs mouse-able.
The dependency-tree that I manually traced,
starting from:
http://tinycorelinux.net/7.x/x86_64/tcz/gpm.tcz.dep
== <URL cannot be found>

=> "gpm" is NOT in MY current file-listing of:
 http://tinycorelinux.net/7.x/x86_64/tcz/

Currently I must launch gpm from a non-TC partition.

Offline Misalf

  • Hero Member
  • *****
  • Posts: 1530
Re: VT needs gpm.
« Reply #1 on: February 12, 2017, 09:03:31 PM »
This simply means it doesn't exist as an extension for 64-bit.
You can request extensions at Extension requests
Download a copy and keep it handy: Core book ;)

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 9294
Re: VT needs gpm.
« Reply #2 on: February 12, 2017, 09:04:58 PM »
There has never been a gpm extension for corepure64.

If you've got wifi working, you can download the compiletc extension and compile gpm?

Offline labeas

  • Full Member
  • ***
  • Posts: 126
Re: VT needs gpm.
« Reply #3 on: February 13, 2017, 02:11:05 AM »
OK, If WiFi works: the BIG gcc can be fetched, to be able to run gpm.

But judging from net-posts re. <Linux setup WiFi> I expect big problems there.
Which surprised me since it's so automatic under M$.

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 9294
Re: VT needs gpm.
« Reply #4 on: February 13, 2017, 02:24:14 AM »
Part of the problem is that some suppliers (for example broadcom) don't supply open source drivers and/or firmware to linux, which means that the drivers need to be reverse engineered (for example b43).

gpm posted to corepure64 repo (read the info file)

Offline labeas

  • Full Member
  • ***
  • Posts: 126
Re: VT needs gpm.
« Reply #5 on: February 14, 2017, 01:54:55 AM »
> gpm posted to corepure64 repo (read the info file)

 OK I'll check that, but it's become less important now, since I've got LNO running.

The following is an extract of what I posted on the <need WiFi> thread:-
The ETHO/wily family allows the user to:
 have multiple text frames accessible together on the screen;
 mouse driven - at the extreme can be used without keybrd;
 no need to look-away from the screen to find the X-key;
 User created menus of Commands are just <moused>
   also to include parameter/s;
 ETHO change color & font to give extra dimension/association
   to complexly related text-pieces in several TextFrames,
   by merely wipe-text & <dab in sample> of required color/font;
and much more.