whitequark changed the topic of #solvespace to: SolveSpace--parametric 2d/3d CAD · latest version 2.2 · http://solvespace.com · code at https://github.com/solvespace/solvespace · logs at https://irclog.whitequark.org/solvespace
_whitelogger has joined #solvespace
DocScrutinizer05 has quit [Disconnected by services]
DocScrutinizer05 has joined #solvespace
mumptai has joined #solvespace
mumptai has quit [Remote host closed the connection]
* cr1901_modern thinks he might know a decent solvespace project, looking at these tweets: https://twitter.com/Thaolia/status/782221504708808706
<cr1901_modern> The switch enclosure on my PC AT is completely shattered. I could prob 3d print a new one.
<whitequark> sure
<cr1901_modern> Just need to figure out how to get the power supply (of a similar supply I have) open, since the enclosure is screwed onto the inside.
<cr1901_modern> whitequark: How do you handle threaded holes in solvespace?
<d42> i don't think you do :^)
<d42> at best you can leave a comment around :^)
* cr1901_modern figured, but just wanted to make sure
<whitequark> you don't, ideed
<whitequark> note that you are also unlikely to 3d print threads successfully
<whitequark> at least not if you have some of the metric or UNC screws of small diameter
<whitequark> I advise using screws with self-cutting threads designed for plastic
<d42> i've always used threaded inserts ,_,,,
<whitequark> if you can get those, they are rather superior
<cr1901_modern> whitequark: Is linking solvespace against my system-provided libpng and zlib unsupported? The final solvespace link tries to do -lpng16_static, which as far as I can tell, is specific to CMake
<whitequark> on windows?
<cr1901_modern> yes
<whitequark> not really since I don't see any point; the windows build is designed to produce a self-contained executable
<whitequark> dependency management on windows for c++ is an utter disaster
<cr1901_modern> That's fine, but how do I force CMake to not use them
<whitequark> I haven't a faintest clue
<whitequark> (how to make it use the system libs on Windows, that is)
<cr1901_modern> lol... I'll look it up later. Been a while since I compiled solvespace
<whitequark> I don't even know what "system libs" are supposed to be on Windows, developer files wise
<whitequark> you can just grab a build from gh
<cr1901_modern> Oh... yea, that'll work too :P
<whitequark> or appveyor
<cr1901_modern> In my context, it's "the libs MSYS2/Mingw64 provides in it's virtual filesystem"
<whitequark> oh you are building on windows WITH MINGW
<cr1901_modern> yes
<whitequark> I have literally never built it on windows with mingw
<whitequark> I've built it on windows with msvc and on linux with mingw
<whitequark> windows+mingw isn't even an officially supported configuration, I don't know offhand what are the warts you have to work around
<whitequark> well
<cr1901_modern> Ahhh, well I can build it with msvc. I just defaulted to "what I'm used to" :P
<cr1901_modern> Compared to 90% of the software I compile for Windoze, solvespace is pretty well-behaved.
<whitequark> well duh
<whitequark> I make an effort to keep it easy to build...
<cr1901_modern> That was a compliment, not an observation :P
rqou has quit [Ping timeout: 250 seconds]
rqou has joined #solvespace
mumptai has joined #solvespace
mumptai has quit [Quit: Verlassend]