Re: [geomview-users] Geomview under 32-bit Cygwin - opengl

[<llo...@ya...>]

Stuart,

the EXT functions are a problem with compiling only on 64-bit Cygwin, and yes, they can be renamed for that. It's a bit odd that 32-bit and 64-bit opengl code seems to be different here.

32-bit Cygwin's OpenGL is working again, thanks to an upstream llvm
fix and some Cygwin maintenance, but it's clear that the OpenGL maintainers are 64-bit focused at this point. I'd expect 32-bit opengl to break again eventually, so 64-bit is the way to go.

But Geomview doesn't run with SaVi on 64-bit Cygwin, due to failure in piping communications.

Cygwin maintainers want a simple test case - Geomview+SaVi is too complex a test case for them. I can't figure out a test case, and the Cygwin guys aren't going to compile and debug Geomview.

They do point to Cygwin/Linux differences in how longs are handled as a possibility:

https://cygwin.com/faq/ 
section 6.4 

http://cygwin.com/faq/faq.html#faq.programming.64bitporting
has some notes.some related comments:


"64-bit Windows is LLP64, while 64-bit Linux is LP64 on the same hardware."
"Varargs functions are fun.  A type mismatch int/long in the 5th and 6th arg would be invisible on Linux but potentially crash on Cygwin due to the ABI difference (MS vs. SysV).  We found a bug in OpenLDAP this way.."


"maybe is a piping problem, but there is no evidence; it could be a lot of different issues due to 64bit porting. I will not be surprise if there is wrong assumption on data size."
so their take is that Geomview probably isn't really 64-bit clean as far as Cygwin is concerned, and a possible cause of the piping communication problem on 64-bit Cygwin, never mind the other 64-bit Geomview scaling problems discussed earlier on this list.

(I have a few new minor features in SaVi development and would like to release SaVi 1.5 given time.) 

Lloyd Wood
http://savi.sf.net/


________________________________
From: Stuart Levy <sa...@il...>
To: llo...@ya...; "geo...@li..." <geo...@li...> 
Cc: Stuart Levy <sa...@il...>
Sent: Monday, 30 May 2016, 15:05
Subject: Re: [geomview-users] Geomview under 32-bit Cygwin - opengl



If the gl...EXT functions (which in the 1990s were the only way to access a bunch of texture functionality, and are now obsolete) are the only problem with 32-bit Cygwin OpenGL, it should be easy enough to get rid of them from the source code, right?   No reasonable implementation these days will require calling the ...EXT forms, so you could just batch-edit the mgopengl *.c files to strip the EXT suffixes from all function names.

I'm not sure from your note whether it looks as though there are
   more problems than that with the 32-bit version.


On 5/29/16 8:21 PM, llo...@ya... wrote:

Okay, to summarize the current Geomview on Cygwin situation: - 32-bit OpenGL is not well maintained, and now lags OpenGL for 64-bit Cygwin, as shown by the compiler substitution to drop EXT from functions - they're actually different codebases. (problem may be how LLVM changes interact with dri-driver upstream from Cygwin, but who knows?) - So 64-bit Cygwin would likely be the way to go for Geomview, if it wasn't for that piping problem between Geomview and modules that is a showstopper. So, sort out the piping problem, then recommend move to 64-bit Cygwin, and ignore 32-bit? (In other news, I've just tried SaVi 1.4.6+Geomview 1.9.4 on the latest Raspbian on a Raspberry Pi B; they're Debian packages there. Doesn't crash, but lots of errors OpenGL now can't even render a complete sphere; thank goodness for the -noopengl flag. Texturemapping used to work fine... but then, that's 32-bit, just like Cygwin. If I had a Death Star texturemap, I'd see something from Return of the Jedi, not A New Hope, on the Pi.) Guess Geomview now has to really embrace the 64-bit world, memory structures and all, as support for and maintenance of 32-bit dependencies fade away.  cheers Lloyd Wood http://savi.sf.net ----- Original Message -----
From: "llo...@ya..." <llo...@ya...> To: "geo...@li..." <geo...@li...> Sent: Sunday, 22 May 2016, 23:42
Subject: Geomview under 32-bit Cygwin - opengl Is anyone else running Geomview under Cygwin?
Would like to compare notes. I just did a recent compile on freshly cleanly
installed 32-bit cygwin and found that
running Geomview under opengl now crashes. With
geomview -noopengl -run ../savi/savi I get the usual expected behaviour, sans texturemapping. (Geomview under 64-bit Cygwin has different problems,
discussed previously.) thanks Lloyd Wood http://savi.sf.net/ ------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity 
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e _______________________________________________
geomview-users mailing list geo...@li... https://lists.sourceforge.net/lists/listinfo/geomview-users