00:00 <InPhase> peepsalot: I have a CMakeLists for work that, if a submodule isn't there, uses execute_process to do a git submodule update. So you can get pretty flexible once you take the bold step of starting to run stuff. For example, you can run cmake externally, or run a script.

00:02 <InPhase> Sometimes I feel a little fenced in inside of cmake's logic process. It does one niche set of jobs well, and most other jobs really awkwardly.

01:06 <peepsalot> InPhase: it can be definitely get pretty frustrating. seems like its not very consistent or well documented regarding scope and value inheritance

01:06 <peepsalot> is there no "CMake Core Guidelines" type of doc?

01:12 <InPhase> peepsalot: The docs don't seem to do much of a high level principles thing.

01:13 <InPhase> Everything I find is examples and jargon-filled descriptions of individual commands.

01:15 <InPhase> peepsalot: Maybe you can poke someone here to point you toward a comprehensive description, or nudge someone into typing one up by a good cmake-nerd-snipe question? https://discourse.cmake.org/

01:16 <InPhase> Probably a general/specific dual question is best.

01:18 <teepee> I started looking at https://cliutils.gitlab.io/modern-cmake/ some time ago, but have not read through everything yet

01:55 <InPhase> I'm not sure where the "modern" part is.

01:55 <InPhase> Maybe I already gradually adjusted to "modern" cmake and didn't notice.

01:58 <InPhase> I guess they specify a few old commands that I should not be using, that I do in fact use interspersed with the new commands, but mostly because I'm blindly following examples and grabbing from old cmake files because it's a mess to wade through the docs all over again. ;)

02:06 <teepee> my interpretation so far is that "modern" mostly means working with targets as things that have setup/properties/...

02:06 <teepee> basically having none or only very limited global setup that is then just applied everywhere

02:06 <teepee> but it's really hard to do with just the reference docs

02:31 <InPhase> teepee: Yeah. Although I almost always just have one target.

15:13 <gbruno> [github] t-paul closed issue #3933 (Issue in latest macOS development snapshots (from 2010-10-04)). https://github.com/openscad/openscad/issues/3933

16:19 <gbruno> [github] bob-ewart opened issue #3945 (BOSL2 cyl with rounding fails in nightly build). https://github.com/openscad/openscad/issues/3945

17:28 <gbruno> [github] t-paul closed issue #3945 (BOSL2 cyl with rounding fails in nightly build). https://github.com/openscad/openscad/issues/3945

18:46 <InPhase> Solid success for the nightlies there. peepsalot's new undefined operation warnings highlighted a scad code error the 2019 release was glazing over.

18:47 <InPhase> Well, "new".

18:49 <teepee> no issue with the latest version of bosl2 though, no idea what the issue was

19:52 <InPhase> Oh, I thought that came from a BOSL2 dev. I guess that was just a BOSL2 user.

20:11 <teepee> yeah, I think so. I'm fine with the latest version looking good :)

20:18 <gbruno> [github] gounthar opened issue #3946 (Raspberry Pi 3 running Raspbian 10 buster armv7l Linux 5.10.63-v7+: /usr/include/GLES3/gl32.h:1821:187: error: void __glewTexStorage3DMultisample(GLenum, GLsizei, GLenum, GLsizei, GLsizei, GLsizei, GLboolean) redeclared as different kind of symbol). https://github.com/openscad/openscad/issues/3946

20:18 <gbruno> [github] gounthar edited issue #3946 (Raspberry Pi 3 running Raspbian 10 buster armv7l Linux 5.10.63-v7+: /usr/include/GLES3/gl32.h:1821:187: error: void __glewTexStorage3DMultisample(GLenum, GLsizei, GLenum, GLsizei, GLsizei, GLsizei, GLboolean) redeclared as different kind of symbol). https://github.com/openscad/openscad/issues/3946

23:50 <Guest70> m brand new to this and am trying to modify something. How do I wrap text or have 2 lines of text in an item?

23:51 <teepee> there's no text formatting, so it's basically just the script having 2 text objects

23:51 <Guest70> so how would I set that up in the script?

23:56 <teepee> simplest case is to really just move the text parts to the places they should appear:

23:56 <teepee> difference() { cube([60, 50, 2]); translate([10, 30]) linear_extrude(5, center = true) text("Hallo"); translate([10, 10]) linear_extrude(5, center = true) text("World!"); }

23:56 <teepee> the dev snapshots have some features to ask for sizes of text, so it would be possible to actually do line wrapping

23:57 <teepee> but this is fairly new, so I'm not sure if there's much code using it - also it's an experimental feature still, so needs to be enabled in preferences

23:58 <teepee> https://en.m.wikibooks.org/wiki/OpenSCAD_User_Manual/WIP#Text_Metrics_/_Font_Metrics