Yeah that makes sense. The alpha is pretty stable anyway.
I wonder if it would be possible just to use libs installed with brew now that we figured out that static linking
or does Lux need exact lib versions to work ?
Oh and on the LuCore 2.1 test scene i get an error of jpg beeing too new. version 90 expected 80 . Could this be an old
jpg version in the macoscompile git ? v9b i guess ... that should not be too old ... well 2 years .. should i update to v9c ?
Does anyone know how to fix the permissions issue with the denoise executable ?
Compile on MacOS 10.13
Re: Compile on MacOS 10.13
check out my newest stuff http://q3de.com/research/
portfolio http://q3de.com/
MB Pro i7 2.3Ghz, IrisPro 1.5GB, GTX750m 2GB - BigSur
Xeon X5650@4Ghz, RX 5700 - BigSur , Windows 10, Ubuntu 20.04
portfolio http://q3de.com/
MB Pro i7 2.3Ghz, IrisPro 1.5GB, GTX750m 2GB - BigSur
Xeon X5650@4Ghz, RX 5700 - BigSur , Windows 10, Ubuntu 20.04
Re: Compile on MacOS 10.13
Most of the times, yes, you need the exact version otherwise you can experience a lot of subtle and unknown problems compared to the other 2 platforms (Linux+Windows).
If you use tar instead of zip, it will save file "read/write/execute bits.
Re: Compile on MacOS 10.13
good to know i'll tryIf you use tar instead of zip, it will save file "read/write/execute bits.
So all the dependnecies in MacOsCompile repo are up-to-date now ??
And yes should i commit the changes made ? Review someone
check out my newest stuff http://q3de.com/research/
portfolio http://q3de.com/
MB Pro i7 2.3Ghz, IrisPro 1.5GB, GTX750m 2GB - BigSur
Xeon X5650@4Ghz, RX 5700 - BigSur , Windows 10, Ubuntu 20.04
portfolio http://q3de.com/
MB Pro i7 2.3Ghz, IrisPro 1.5GB, GTX750m 2GB - BigSur
Xeon X5650@4Ghz, RX 5700 - BigSur , Windows 10, Ubuntu 20.04
Re: Compile on MacOS 10.13
I have no idea
You can use GitHub pull request process to submit any change to the repository
Re: Compile on MacOS 10.13
Sorry i don't get it. I have cloned the lux repo and now i would like to push not pull .. maybe got that wrong
guess not anyone can push to the repo
Never done that. I would like to commit these changes.
or will i have to make a new branch ??
guess not anyone can push to the repo
Never done that. I would like to commit these changes.
or will i have to make a new branch ??
check out my newest stuff http://q3de.com/research/
portfolio http://q3de.com/
MB Pro i7 2.3Ghz, IrisPro 1.5GB, GTX750m 2GB - BigSur
Xeon X5650@4Ghz, RX 5700 - BigSur , Windows 10, Ubuntu 20.04
portfolio http://q3de.com/
MB Pro i7 2.3Ghz, IrisPro 1.5GB, GTX750m 2GB - BigSur
Xeon X5650@4Ghz, RX 5700 - BigSur , Windows 10, Ubuntu 20.04
Re: Compile on MacOS 10.13
It is explained here: https://help.github.com/en/github/colla ... l-requests
You clone the repository on GitHub so you have your own copy, you create a branch with all your patches and submit a "pull request".
It is a method so anyone can submit patches to an "official" repository.
You clone the repository on GitHub so you have your own copy, you create a branch with all your patches and submit a "pull request".
It is a method so anyone can submit patches to an "official" repository.
Re: Compile on MacOS 10.13
OK lets see --... i'll check the build_deps script once more and then i'll push Macosdeps repo first
check out my newest stuff http://q3de.com/research/
portfolio http://q3de.com/
MB Pro i7 2.3Ghz, IrisPro 1.5GB, GTX750m 2GB - BigSur
Xeon X5650@4Ghz, RX 5700 - BigSur , Windows 10, Ubuntu 20.04
portfolio http://q3de.com/
MB Pro i7 2.3Ghz, IrisPro 1.5GB, GTX750m 2GB - BigSur
Xeon X5650@4Ghz, RX 5700 - BigSur , Windows 10, Ubuntu 20.04
Re: Compile on MacOS 10.13
OK now there should be a pull request for MacOSCompileDeps
check out my newest stuff http://q3de.com/research/
portfolio http://q3de.com/
MB Pro i7 2.3Ghz, IrisPro 1.5GB, GTX750m 2GB - BigSur
Xeon X5650@4Ghz, RX 5700 - BigSur , Windows 10, Ubuntu 20.04
portfolio http://q3de.com/
MB Pro i7 2.3Ghz, IrisPro 1.5GB, GTX750m 2GB - BigSur
Xeon X5650@4Ghz, RX 5700 - BigSur , Windows 10, Ubuntu 20.04
Re: Compile on MacOS 10.13
I'm still investigating the jpg error.
could it be the lib is tooo new ??? v9b was is the mac repo v3c bringst the same error and in the linux repo i can find version v6?
Strange....
Code: Select all
Error opening image file : /var/folders/zh/g9zxh0gs09v2j_tfw8by4v0r0000gn/T/tmp78a0ujo3.jpg (error = JPEG error: Wrong JPEG library version: library is 90, caller expects 80 ("/var/folders/zh/g9zxh0gs09v2j_tfw8by4v0r0000gn/T/tmp78a0ujo3.jpg"))
Strange....
check out my newest stuff http://q3de.com/research/
portfolio http://q3de.com/
MB Pro i7 2.3Ghz, IrisPro 1.5GB, GTX750m 2GB - BigSur
Xeon X5650@4Ghz, RX 5700 - BigSur , Windows 10, Ubuntu 20.04
portfolio http://q3de.com/
MB Pro i7 2.3Ghz, IrisPro 1.5GB, GTX750m 2GB - BigSur
Xeon X5650@4Ghz, RX 5700 - BigSur , Windows 10, Ubuntu 20.04