Page 2 of 2

Re: Windows build deps

Posted: Sat Apr 27, 2019 10:24 pm
by Fox
If i build libs, do i have to build only static or dynamic or doesn't matter?

Re: Windows build deps

Posted: Sun Apr 28, 2019 7:48 am
by acasta69
Almost everything should be static.
OpenImageIO is dynamic.
Embree, tbb and OIDN are also dynamic, but we use distributed binaries for those. Same for Qt.

Re: Windows build deps

Posted: Tue Jul 16, 2019 5:34 pm
by Fox
Has anybody some inside how to use the vcpkg https://github.com/microsoft/vcpkg
to update deps?

The vcpkg prints out 2 lines of info:
find_package(xxxxx config required)
TARGET_LINK_LIBRARIES(xxxxxx xxxxxx)
And i have to point to vcpkg cmake toolchain file in cmakelist.txt

https://youtu.be/4z2jmDr36Fc?t=665

But the targets look to be written out a little different in cmakelist files, but not only in cmakelist, there are other files.
Sometimes there is full list of file names that some lib includes.
Another times, like with openexr 2.3, the vcpkg build doesn't even have some files where some luxcore files point.

Looks to be too much work :) I wonder if there is easy way with vcpkg to automate it little?

Re: Windows build deps

Posted: Tue Jul 16, 2019 7:49 pm
by acasta69
I've never used vcpkg, don't really know how to help with that.
Should it help keeping all deps updated to latest versions?

Re: Windows build deps

Posted: Tue Jul 16, 2019 8:28 pm
by Fox
acasta69 wrote:
Tue Jul 16, 2019 7:49 pm
Should it help keeping all deps updated to latest versions?
I actually don't know myself, if vcpkg is better or not for luxcore.
It sure built all the dependencies that build-deps-x64.bat failed to build.

Even so, if i had all the deps built, i got over 1900 errors by just manual copy paste new libs over the old libs in WindowsCompileDeps and running the cmake-build-x64.bat

Re: Windows build deps

Posted: Mon Jan 27, 2020 4:07 am
by Fox
I have no particular need to update libs, it's just exciting to learn.
Anyways, with the help of vcpkg ports i got openimageio 2.2.0.0-dev built with boost 1.72.

I started with vcpkg CMAKE_TOOLCHAIN_FILE in CMake gui,
but in the end i disabled it and hand edited the CMakeCache,
where i set everything -NOTFOUND,
every library entirely that had missing parts.
I think the vcpkg TOOLCHAIN keeps re enabling them broken libs.
Ptex for one is broken, with old PKG config version from year 2008, it asks zlib module.

For some reason the vcpkg boost can't build libboost files (also numpy),
hand built version has them.

Someone has updated the eos_portable_archive-v5.1 to Boost 1.69
but maybe it's broken in 1.72, or the error comes from somewhere else:
https://github.com/daldegam/eos-portabl ... ll/2/files