On 10/26/2015 11:51 AM, Bo Berglund wrote:
1) Control relays via the GPIO connector on the RPi2. Done OK
Of course this is rather appropriately done on the target.
2) Create a TCPIP communications object..
This is an example of what should be done on a Linux PC. It does not
involve any hardware stuff, as the socket interface is common to all
Linuxes.
Not entirely accurate, what I have are a few VMWare virtual machines
with some flavours of Linux Mint installed in order to use for web
development testing. So then I need to fire up the VMWare environment
too and start the virtual machine in order to get a display that sits
inside the VM...
Any Linux Desktop software uses an X interface as a display. Hence an X
server is running. VM now forwards the X-API towards the host OSes
display. Nonetheless the X-API the client sees should be perfectly
standard and should be usable via TCP/IP.
Do you mean that the Linux Mint has an X server that can be used by my
Raspbian Jessie on the Pi as the display when they are on the same
network?
I did not try such a thing but this is the paradigm ox X11.
Or do you mean I should switch away from the Pi and work in the Linux
Mint instead?
IMHO: in any case when using hardware features of the target are not
necessary to do the work at hand.
Never was able to install and use Xming for example.
I once used XMING on WinXP. That did work fine.
Do you have a suggestion as to which X-server I could run on Windows7
instead of using VNC?
IMHO the developing environment for a Linux target should not involve
any Windows stuff.
I already provided lots of hints on how the porting might be done, so I
can't help with approaches I would not recommend, anyway.
-Michael
--
_______________________________________________
Lazarus mailing list
[email protected]
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
