NOTE: You also need to run vglcygsetup from a Cygwin Bash shell, as the
User's Guide instructs.

On 4/18/19 6:20 PM, marcus wrote:
> Thanks for the information! I see why this step is needed previously.
> Now I am able to continue and MIT-SHM does appear in the xdpyinfo output.
> 
> For the next part, connecting to the VirtualGL server, I tried to use
> the command:
> 
> /opt/VirtualGL/bin/vglconnect /user/@/server/
> 
> 
> but vglconnect does not exist in that location. There's no /opt
> directory to start with. I'm only able to find vglconnect in
> ./cygdrive/c/Users/username/AppData/Local/Packages/MirrorName/LocalState/rootfs/opt/VirtualGL/bin/.
> Also running it gives me 
> 
>     ./vglconnect: line 111: ./vglclient: cannot execute binary file:
>     Exec format error
>     [VGL] ERROR: vglclient failed to execute.
> 
> 
> Did I install it wrong or is it something else? Thanks in advance!
> 
> 
> 
> Here is the output when I ran vglcygsetup script:
> 
>     $ ./vglcygsetup 
>     Fetching setup.ini ...
>     Fetching x86_64/VirtualGL-2.3.3-20131014.tar.bz2 ...
>     Fetching x86_64/VirtualGL-2.3.90-20140717.tar.bz2 ...
>     Fetching x86_64/VirtualGL-2.4-20150126.tar.bz2 ...
>     Fetching x86_64/VirtualGL-2.4.1-20150612.tar.bz2 ...
>     Fetching x86_64/VirtualGL-2.4.90-20151027.tar.bz2 ...
>     Fetching x86_64/VirtualGL-2.5-20160215.tar.bz2 ...
>     Fetching x86_64/VirtualGL-2.5.1-20161001.tar.bz2 ...
>     Fetching x86_64/VirtualGL-2.5.2-20170302.tar.bz2 ...
>     Fetching x86_64/VirtualGL-2.5.90-20180425.tar.bz2 ...
>     Fetching x86_64/VirtualGL-2.6-20180824.tar.bz2 ...
>     Fetching x86_64/VirtualGL-2.6.1-20190101.tar.bz2 ...
>     Fetching Cygwin setup ...
>     Launching Cygwin setup ...
>     note: Hand installation over to elevated child process.
> 
> and I followed the setup window to install VirtualGL. 
> 
> 
> 
> On Thursday, April 18, 2019 at 8:08:07 AM UTC-7, DRC wrote:
> 
>     The CYGWIN environment variable is used to tweak the behavior of
>     Cygwin's Unix emulation layer.  It has nothing to do with the PATH.
>     However, according to the documentation
>     (https://cygwin.com/cygwin-ug-net/using-cygwinenv.html
>     <https://cygwin.com/cygwin-ug-net/using-cygwinenv.html>), setting
>     CYGWIN=server is apparently no longer necessary.  It was necessary at
>     one time in order to fully enable shared memory emulation.
> 
>     On 4/18/19 2:17 AM, marcus wrote:
>     > Hi,
>     >
>     > I'm new to VirtualGL and encounter a problem when configuring the
>     > windows client. In ver 2.6.1 doc, there is a step that I got stuck:
>     >
>     >     5. Add |server| to the |CYGWIN| system environment variable
>     (create
>     >     this environment variable if it doesn’t already exist)
>     >
>     >
>     >  I'm not very familiar with cygwin so I'm wondering what the 'server'
>     > path is in this scenario. (I believe 'CYGWIN' variable refers to PATH
>     > and i could add it through 'export PATH=$PATH:/path/to/server')
>     >
>     > Thank you!
> 
> -- 
> You received this message because you are subscribed to the Google
> Groups "VirtualGL User Discussion/Support" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to [email protected]
> <mailto:[email protected]>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/virtualgl-users/e4b6b002-c270-408a-b41b-3a96b346232c%40googlegroups.com
> <https://groups.google.com/d/msgid/virtualgl-users/e4b6b002-c270-408a-b41b-3a96b346232c%40googlegroups.com?utm_medium=email&utm_source=footer>.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"VirtualGL User Discussion/Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/virtualgl-users/6a0b09c4-c299-9a35-3575-300c6391c811%40virtualgl.org.
For more options, visit https://groups.google.com/d/optout.

Reply via email to