paul0noah

Results 13 comments of paul0noah

Thats very interesting. On my Machine (M1 Macbook) i have the following output for: ``` from vedo import * sphere = Sphere() sphere.cut_with_plane() scals = sphere.points()[:, 0] sphere.pointdata["scalars"] = scals...

Alright. Well at least it is do-able somehow 👍 You can close the issue already if you want to.

Update: I manage to build using `Eigen::all` as pointed out above when I include eigen "manually". With terminal inside example project folder i first `mkdir external && cd external &&...

I think its nothing newer. The `Eigen::all` is at least two years out. And judging from [https://github.com/libigl/libigl/blob/main/cmake/recipes/external/eigen.cmake](this) cmake file i suppose libigl uses eigen 3.4.0 which was released about one...

It is the most recent version from the gitlab repository (downloaded via git clone)

Thanks @jdumas this works! Apparently, this is also mentioned in release log of libigl v2.4.0 (see [here](https://github.com/libigl/libigl/releases)). Maybe it makes sense to mention it somwhere in the example project how...

### Compiling gptoolbox for M1 Mac with [Matlab R2022b beta](https://de.mathworks.com/support/apple-silicon-r2022b-beta.html) (native apple silicon support): I tried compiling gptoolbox/mex for Matlab beta (as it is faster than rosetta version). Unfortunately, this...

the main errors basically are that findMATLAB does not support the matlab silicon version, this includes: - matlab bin prefix can not be identified (fixed with step 1) - matlab...

Yes, sorry that my post did not make this clear enough.

Hi @scarfelab, I did some debugging in the the findMATLAB.cmake file shipped with gptoolbox and found that `CMAKE_OSX_ARCHITECTURES` was unset which caused that the findMATLAB script was searching inside `/Applications/MATLAB_R2023b.app/bin/maci64`...