LuxCoreRender Forums

How about setting up Azur for nightly builds for osx .... can someone point me to startingpoint ? Do i need an Azur account ??

The Azure pipeline is controlled by this script:
https://github.com/LuxCoreRender/LuxCor ... elines.yml
The first and last part carry out common tasks, in the middle there is a section for each OS.
The one for MacOS was set up time ago by robbrown and is currently disabled:
https://github.com/LuxCoreRender/LuxCor ... s.yml#L154
Each section uses scripts dedicated to each OS, they are located in LuxCore/scripts/azurepipeline:
https://github.com/LuxCoreRender/LuxCor ... repipeline

The pipeline structure has changed a bit after the MacOS part was disabled. You could have a look at the Linux section, probably it's very similar to what you need.

If anything is unclear, please just ask!

OK I#ll have a look ... already had i still wonder how to include other repos like we need the MacOSXCompileDeps ...

You need to recreate the directory structure to build LuxCore on the azure VM. This probably includes downloading MacOSXCompileDeps to a proper location.
I'll try to post more detailed info later this morning, I'm on my phone right now...

acasta69 wrote: ↑Mon Dec 16, 2019 6:34 am You need to recreate the directory structure to build LuxCore on the azure VM. This probably includes downloading MacOSXCompileDeps to a proper location.

Just pack the binaries in a archive that can be uploaded and downloaded from GitHub like we do with Linux: https://github.com/LuxCoreRender/LinuxC ... v2.3alpha0 (see the linux_deps.tgz ?)

Robbrawn did the same for compiling MacOS on Azure some time ago: https://github.com/LuxCoreRender/MacOSC ... beta3eases (see the MacDistFiles.tar.gz ?)

BTW, u3real, do you want to become the new "official" MacOS project maintainer ? Change pretty much nothing but you will have direct access to the GitHub MacOS repositories and developer private forum.

I think i'm almost there .. LuxCore compiles well even without tbb on brew installed .. it was ..

There just seems to be a prop with denoise now when compiled with tbb in Macdeps.

dylibbundler complains about not finding @rpath ... well maybe i should use OIDN 1.0.0 and not 1.1.0 like i do now.

I had a look at azure and it seems to be pretty straight forward. Should work now like intended.

I'll finish it for this evening ..

And yes i'd love to be official ... again

In theory the azurepipeline "should work" now with latest commits.

I'm curious...

Oh we'll have to make a release for MacOSCompileDeps first !!!

Can i merge now in MacOSCompileDeps ?? and release

still unsure with python include ... should work with pyenv ... but i had to export CPLUS_INCLUDE_PATH .

We'll see. Is there like a log i can look at ?

u3dreal wrote: ↑Mon Dec 16, 2019 6:56 pm Oh we'll have to make a release for MacOSCompileDeps first !!!

Can i merge now in MacOSCompileDeps ?? and release

Yes, you should.

u3dreal wrote: ↑Mon Dec 16, 2019 6:56 pm We'll see. Is there like a log i can look at ?

It is all here: https://dev.azure.com/LuxCoreRender/Lux ... der/_build

OK did a release and fixed link in build.sh ... now it should work if someone merges.

Cool ...