trying to build in Mac OS on my laptop
okay .. i have gotten further in Sonoma than i did in Windows
everything installed .. the dependencies script run .. it gets as far as building “graphite” and then in the output i see a lot of warnings:
clang++clang++: : warning: argument unused during compilation: '-msse2' [-Wunused-command-line-argument]
warning: unknown warning option '-Wno-class-memaccess'; did you mean '-Wno-class-varargs'? [-Wunknown-warning-option]
anyone know if that is significant?
and multiple errors:
error: unknown FP unit 'sse'
because at the end i see this
/usr/bin/ranlib libgraphite2-file.a
[ 42%] Built target grlisttest
[ 42%] Built target graphite2-file
make: *** [all] Error 2
===
scrolling back to the top of the log i see this early in the config build:
CMake Deprecation Warning at gr2fonttest/CMakeLists.txt:1 (CMAKE_MINIMUM_REQUIRED):
Compatibility with CMake < 3.10 will be removed from a future version of
CMake.
Update the VERSION argument <min> value. Or, use the <min>...<max> syntax
to tell CMake that the project requires at least <min> but has been updated
to work with policies introduced by <max> or earlier.
should i create an issue to do the updates we are being warned about?
more CMake warnings — should i create an issue for these too?
CMake Deprecation Warning at CMakeLists.txt:1 (CMAKE_MINIMUM_REQUIRED):
Compatibility with CMake < 3.10 will be removed from a future version of
CMake.
Update the VERSION argument <min> value. Or, use the <min>...<max> syntax
to tell CMake that the project requires at least <min> but has been updated
to work with policies introduced by <max> or earlier.
CMake Warning (dev) at CMakeLists.txt:4 (find_package):
Policy CMP0148 is not set: The FindPythonInterp and FindPythonLibs modules
are removed. Run "cmake --help-policy CMP0148" for policy details. Use
the cmake_policy command to set the policy and suppress this warning.
This warning is for project developers. Use -Wno-dev to suppress it.
-- Found PythonInterp: /usr/local/bin/python3 (found suitable version "3.13.7", minimum required is "3.6")
-- The C compiler identification is AppleClang 16.0.0.16000026
-- The CXX compiler identification is AppleClang 16.0.0.16000026
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Build: Release
-- Building library: shared
-- File Face support: enabled
-- Tracing support: disabled
CMake Warning at CMakeLists.txt:62 (message):
vm machine type direct can only be built using GCC
-- Using vm machine type: call
CMake Warning (dev) at CMakeLists.txt:69 (EXEC_PROGRAM):
Policy CMP0153 is not set: The exec_program command should not be called.
Run "cmake --help-policy CMP0153" for policy details. Use the cmake_policy
command to set the policy and suppress this warning.
Use execute_process() instead.
This warning is for project developers. Use -Wno-dev to suppress it.
CMake Deprecation Warning at src/CMakeLists.txt:22 (CMAKE_MINIMUM_REQUIRED):
Compatibility with CMake < 3.10 will be removed from a future version of
CMake.
Update the VERSION argument <min> value. Or, use the <min>...<max> syntax
to tell CMake that the project requires at least <min> but has been updated
to work with policies introduced by <max> or earlier.
On 21.09.25 13:14, vulcan_--- via Discuss wrote:
more CMake warnings — should i create an issue for these too?
All that looks like exactly one issue to me: "Update CMakeLists.txt
to minimum supported cmake" which I recently verified could be
version 3.22.1.
So in theory one issue would be fine, that said, my hopes anyone
who is not looking into this stuff anyway is going to pick it up
is zero. So it's probably just a waste of time to create it and
will create extra effort to find and close once the changes are
done.
ciao,
Torsten.
but unless testing the graphite build is the last thing in the configuration script my build is blocked by this
/usr/bin/ranlib libgraphite2-file.a
[ 35%] Built target graphite2-file
[ 35%] Built target grlisttest
make: *** [all] Error 2
with the tests failing my build is blocked
On 21.09.25 16:44, vulcan_--- via Discuss wrote:
but unless testing the graphite build is the last thing in the
configuration script my build is blocked by this
You could disable graphite for your local builds, it's an optional
dependency to Harfbuzz providing an additional font backend. Missing
this will only slightly reduce supported font features, e.g. like
the one shown in:
https://github.com/openscad/openscad/issues/6069
ciao,
Torsten.
Some comments:
-
In general, to be able to respond to build errors, a lot more info is needed about your system, which scripts you ran, which CMake options you enabled etc.
-
It’s generally a lot easier to use Homebrew rather than building your dependencies from source, i.e. scripts/macosx-build-homebrew.sh rather than scripts/macosx-build-dependencies.sh
For individual build issues, opening a ticket per issue might be the most productive as we can address isolated issues instead of discussing a handful of different topics in the same email thread.
-Marius
Marius Kintel wrote:
Some comments:
- In general, to be able to respond to build errors, a lot more info is needed about your system,
okay .. i will get more verbose
- It’s generally a lot easier to use Homebrew rather than building your dependencies from source, i.e. scripts/macosx-build-homebrew.sh rather than scripts/macosx-build-dependencies.sh
but i am following the instructions that say to first run m-b-dependencies.sh .. then run m-b-homebrew.sh
that is why i was saying i was blocked. .. now, how do i disable graphite … hummm.
On Sep 22, 2025, at 12:48, vulcan_--- via Discuss discuss@lists.openscad.org wrote:
but i am following the instructions that say to first run m-b-dependencies.sh .. then run m-b-homebrew.sh
The instructions say to use one of the two options.
That said, both the options should work, so you’re obviously running into some unknown issue. If you’re able to reproduce, feel free to open a ticket and I’ll look into it.
-Marius
Marius Kintel wrote:
On Sep 22, 2025, at 12:48, vulcan_--- via Discuss discuss@lists.openscad.org wrote:
but i am following the instructions that say to first run m-b-dependencies.sh .. then run m-b-homebrew.sh
The instructions say to use one of the two options.
That said, both the options should work, so you’re obviously running into some unknown issue. If you’re able to reproduce, feel free to open a ticket and I’ll look into it.
I am still collecting data on the m-b-dependencies.sh issues .. but i did get the m-b-homebrew.sh version to work .. had to learn some stuff about Qt to get past some mismatched type errors but the build is working
as i suspected the problem is due to Save As .. and Save a Copy both calling the Save() function .. i am seeing messages in the console:
saved newfile.scad
loaded newfile.scad
but newfile is the copy .. it should not be reloaded right ..
i see the code that is writing the file to Save it .. but that reload message ? where is that coming from. It does not appear in TabManager.cc as far as i can tell
Hints? Tips?
On Sep 23, 2025, at 10:34, vulcan_--- via Discuss discuss@lists.openscad.org wrote:
i see the code that is writing the file to Save it .. but that reload message ? where is that coming from. It does not appear in TabManager.cc as far as i can tell