<kintel>
sparsh-n We run all tests on GitHub CI using the msys2 build, so that should definitely work
<kintel>
Test failure can be a lot of things, so my usual workflow is to select the most innocent looking failing test and run that in isolation using ctest -R <testname>
<kintel>
..then look at the test report
<kintel>
..or cat Testing/Temporary/LastTest.log
<kintel>
It's usually some environment-related issue
<kintel>
If you look at the log and it's puzzling, you can just execute exactly what's in the log manually and troubleshoot from there
snaked has joined #openscad
bitbasher has quit [Ping timeout: 244 seconds]
mmu_man has quit [Ping timeout: 252 seconds]
foul_owl has quit [Ping timeout: 276 seconds]
sculptor has quit [Read error: Connection reset by peer]
sculptor has joined #openscad
sculptor has joined #openscad
sculptor has quit [Changing host]
foul_owl has joined #openscad
J25k65 has quit [Quit: Client closed]
J25k65 has joined #openscad
sparsh-n has joined #openscad
<sparsh-n>
https://bpa.st/CDKQ these are what the msys2 test errors look like. I remember a few errors popping up when running MSYS2 build, although I'll fetch for updates. Haven't updated this branch since around april. It's a combination of mostly Failed, and some not run/disabled. Looking at the error log, some of them note that openscad.com can't be
<sparsh-n>
found, and from what I can see it wasn't built at all when I built with MSYS2.
<kintel>
right, there some trick
J25k65 has quit [Quit: Client closed]
J25k65 has joined #openscad
<kintel>
I think openscad.com is built in a separate folder
<kintel>
..so you have to cmake --install
<kintel>
..or move openscad.com next to the .exe
<InPhase>
Shouldn't tbe build process alone result in a fully runnable end product?
<InPhase>
If openscad.com has to be there, the build should move it there I think.
sculptor has quit [Ping timeout: 248 seconds]
kintel has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
ccox has quit [Ping timeout: 252 seconds]
<sparsh-n>
Redid the whole build process, this time referencing the workflow on windows and all the tests pass now. I guess the wikibooks could be updated in the build> section to call cmake instead of make
teepee has quit [Remote host closed the connection]
teepee has joined #openscad
califax has quit [Remote host closed the connection]
JakeSays has joined #openscad
califax has joined #openscad
JakeSays_ has quit [Ping timeout: 260 seconds]
howiemnt4 has quit [Remote host closed the connection]
howiemnt4 has joined #openscad
mmu_man has joined #openscad
howiemnt has joined #openscad
howiemnt4 has quit [Ping timeout: 260 seconds]
rawgreaze_ has joined #openscad
rawgreaze has quit [Ping timeout: 265 seconds]
rawgreaze_ is now known as rawgreaze
howiemnt1 has joined #openscad
howiemnt has quit [Ping timeout: 248 seconds]
bitbasher has joined #openscad
bitbasher has quit [Changing host]
bitbasher has joined #openscad
greenbigfrog has quit [Ping timeout: 244 seconds]
J25k65 has quit [Quit: Client closed]
J25k65 has joined #openscad
teepee_ has joined #openscad
teepee has quit [Ping timeout: 244 seconds]
teepee_ is now known as teepee
greenbigfrog has joined #openscad
J25k65 has quit [Quit: Client closed]
J25k65 has joined #openscad
mmu_man has quit [Ping timeout: 268 seconds]
mmu_man has joined #openscad
bitbasher has quit [Ping timeout: 244 seconds]
J25k65 has quit [Quit: Client closed]
J25k65 has joined #openscad
bitbasher has joined #openscad
bitbasher has quit [Changing host]
bitbasher has joined #openscad
snaked has quit [Quit: Leaving]
kintel has joined #openscad
<kintel>
InPhase It does, as part of the install step. Not ideal of course, but that can be changed.
<kintel>
I believe a better way of running tests from a built-not-not-installed OpenSCAD would be great in general; that could unlock some wanted features on all platforms
<kintel>
sparsh-n: Thanks for the update!
mmu_man has quit [Ping timeout: 252 seconds]
teepee has quit [Remote host closed the connection]
kintel has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
teepee has joined #openscad
<InPhase>
kintel: Yeah, after you build you should be able to run from the build directory. Which I've always regarded as working just fine as it should be, but I've never tested this under Windows.
<InPhase>
kintel: Since it's been so long since a release, like 95% of my OpenSCAD runs happen from out of a copy of the repo. I don't think I ever once ran a make install or anything of the sort. Then again, I pretty much never run make install in any repo I didn't write myself from scratch, because you can never really trust what such a command will put where, and it can sometimes be very challenging to undo.
<InPhase>
In my head "make install" is an outdated idea from the 90s. :)
<InPhase>
With the onset of fully upgradeable systems, it stopped fitting well into it, due to the absence of proper compartmentalization.
J25k65 has quit [Quit: Client closed]
J25k65 has joined #openscad
<Scopeuk>
I think the limit is having two build executable targets under windows in the .exe and the .com and build chains being fussy. relocating under build would be nice I guess, it only really comes up with the console driven testing (well any expectation scripting I guess) where the com is needed to work around windows console weirdness
sculptor has joined #openscad
califax has quit [Remote host closed the connection]
califax has joined #openscad
califax has quit [Remote host closed the connection]
califax has joined #openscad
Guest1 has joined #openscad
<Guest1>
ust downloaded openScad, but aspect ratio is off, no viewport-control window? is there a hotkey or command line switch to force a aspect-ratio?
<teepee>
aspect ratio off means what exactly? I don't think there's any setting in openscad for that
<teepee>
the viewport aspect ratio is only the pixel number not the pixel geometry
<Guest1>
its not square, when I rotate a cube it looks skewed I think the screen Y axis is squished
<Guest1>
even when I look with ortho view on, when I turn off perspective
<teepee>
which OS?
<Guest1>
windows 11
<teepee>
any updates lately? try rebooting?
<teepee>
sometimes graphics drivers get confused when updating in the background
<Guest1>
lemme give it a reboot.
<Guest1>
that didn't help. a cube, rotated 45 degrees on the X-axis looks like a squished diamond.
<teepee>
what's the opengl driver? see help->library info there's a couple of lines showing what driver is used
<Guest1>
I sincerely apologize... I had a top level resize...
<teepee>
haha :)
<Guest1>
"first time using openscad huh?"
<teepee>
happens
<Guest1>
I just rotated it and was like, wait the diamonding, squishing isn't the same.
<Guest1>
Thank you for dusting my cobwebs
<teepee>
no worries, just waiting for my coffee to be ready :)
<kintel>
InPhase I still end up having to make install various software to get all the files into the right places. Especially Linux autotools-based stuff. I always install in a folder I control of course with no root access, as I too do not trust anyone :)
<kintel>
Anyway, the windows .com stuff is a bit of a kludge. Needs fixing, but this is why we want to make it easier for Windows-native folks to contribute :)
<buZz>
arent windows .com files fake?
<buZz>
compared to the msdos .com (which banned relocation or something)
<buZz>
iirc .com files on msdos are limited to 'fit inside a single segment of 64k'
<buZz>
and .com on windows are just PE32?
<teepee>
the openscad one probably is, yes
<buZz>
hmmmm, makes me dream about 'openscad for msdos'
<buZz>
:D
<buZz>
using one of those ancient 'digitizers'
<buZz>
hahaha
<kintel>
I believe on Windows, you have two ways of attaching stdio; GUI mode and console mode, and that's compiled into the binary
<kintel>
..and to avoid having two binaries with different names for GUI vs cmd-line, OpenSCAD adds openscad.com for cmd-line mode, as that will take precedence when just asking Windows to run 'openscad'
<buZz>
hmhm, yeah that used to be a nice 'hack' back on old msdos installs, just 'install a .com in path with same name as a .exe' , it would always take precedence :P
<kintel>
I have no idea how people deal with this in a non-hacky way though
sinned6915861 has joined #openscad
sinned691586 has quit [Ping timeout: 252 seconds]
<InPhase>
kintel: Well, my most recent encounter with autotools was after the xz compromise when I joined that channel for a few weeks with the goal of convincing the project lead of xz that he needs to switch from autotools to something like cmake, because the tarballs he was distributing were effectively trust-based binaries pretending to be source code (which directly led to the compromise). He listened. xz
<InPhase>
has cmake now.
<kintel>
heh, good thing you got to them before meson did ;)
sinned6915861 is now known as sinned691586
<InPhase>
kintel: Well I think in my discussion I mentioned meson as a viable choice as well. ;) I don't have a horse in the race of which tool is actually used, except for the fact that one cannot distribute gigantic unreadable undiffable .m4 files that are beyond human validation and then pretend this is any better than trying to disassemble a binary.
mmu_man has joined #openscad
<InPhase>
cmake is the easy choice right now just for being most widely used.
<InPhase>
Despite its periodic weirdnesses, it's far far less messed up than the standard autotools path.
<kintel>
Yup, every build system is suboptimal, but cmake may be the least suboptimal today
<InPhase>
The debian chain separately immunized itself from this compromise path by rolling out a build server process which will centralize package building straight from validated git tagged releases, rather than external trust tarballs.
<kintel>
meson is fine, but the dev teams is anti-Apple, which makes my life very hard when building for macOS : (
<InPhase>
So the ecosystem as a whole is better guarded by these broader realizations as well.
<InPhase>
Oh. Well I actually haven't used meson. I do get it recommended to me a bunch of times when I voice my complaints about cmake though. Just never got around to trying it.
<InPhase>
Some people find the fact that meson has a python dependency to be a non-starter. I actually think it's a virtue, and that python should be a widespread build-system baseline, because it would make handling dev issues in a standard manner much easier.
<InPhase>
But I'm not eager to be a build system trend-setter as a life goal. :)
<kintel>
Even Google invented two major build systems used for practically all Google SW; bazel and GN, and of course they don't interoperate. They also don't seem to get any traction elsewhere...
ToAruShiroiNeko has quit []
<Scopeuk>
I was about to say I came across something with bazel recently, but I think that was google test so that would follow
ToAruShiroiNeko has joined #openscad
<Scopeuk>
it appears everyone agrees there are issues with make, also apparently they don't agree what the issues are
kintel has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
J25k65 has quit [Quit: Client closed]
J25k65 has joined #openscad
kintel has joined #openscad
<kintel>
Heh, I guess there are 4 known issues with make: BSD Make, Posix Make, GNU Make, and Microsoft NMake :)
kintel has quit [Client Quit]
mmu_man has quit [Ping timeout: 272 seconds]
sparsh-n has joined #openscad
<sparsh-n>
I've come across Bazel before, although this is the first time I've heard of GN.\
<teepee>
google is probably just in the process to invent another new one ;-)
sparsh-n has quit [Quit: Client closed]
aiyion2 has quit [Remote host closed the connection]
J25k65 has quit [Quit: Client closed]
J25k65 has joined #openscad
aiyion2 has joined #openscad
sculptor has quit [Ping timeout: 252 seconds]
howiemnt1 has quit [Ping timeout: 252 seconds]
bitbasher has quit [Ping timeout: 260 seconds]
sculptor has joined #openscad
howiemnt has joined #openscad
sculptor has quit [Ping timeout: 244 seconds]
teepee_ has joined #openscad
califax has quit [Ping timeout: 244 seconds]
J25k65 has quit [Quit: Client closed]
J25k65 has joined #openscad
califax has joined #openscad
teepee has quit [Ping timeout: 244 seconds]
teepee_ is now known as teepee
mmu_man has joined #openscad
kintel has joined #openscad
zauberfisch has joined #openscad
kintel has quit [Quit: My Mac has gone to sleep. ZZZzzz…]