Page 1 of 1
What are the "Static" options for in CMake?
Posted: 17 Jul 2017, 22:01
by mattwla
Spent the evening building and compiling the win64 openmw.
Things are finally going well, I've learned a lot.
I notice cmake has options for each dependency to make them static, such as "BOOST_STATIC" or "SDL2_STATIC"
What do these options do? My cmake seemed to generate fine without them.
Thanks,
Re: What are the "Static" options for in CMake?
Posted: 17 Jul 2017, 22:26
by Frik
Re: What are the "Static" options for in CMake?
Posted: 17 Jul 2017, 22:39
by mattwla
Thanks for the link, it really clarified things! In the public releases of openmw is static or dynamic used? Or a mix?
Re: What are the "Static" options for in CMake?
Posted: 17 Jul 2017, 22:49
by Frik
Afaik, public releases are static, so as to avoid all the different versions of libs that might be encountered on a given OS.
Compiling your own is the way go. It allows you to stay current between releases when there major updates to the master, such as with Distant Terrain.
Looks like you're on the right track.
Re: What are the "Static" options for in CMake?
Posted: 18 Jul 2017, 00:00
by psi29a
All releases from the PPA are dynamically linked, not static.
Re: What are the "Static" options for in CMake?
Posted: 18 Jul 2017, 01:04
by Frik
Just checked the generic Linux .41 build and you're right. It appears the libs are dynamically linked there. I thought I had seen an example of openmw with static libs. Meh, must have been another package I was thinking of.
What is done in the case where the distro doesn't provide the proper version of the dependent lib
(i.e
Fedora 26 & bullet3-2.86.1)?
Re: What are the "Static" options for in CMake?
Posted: 18 Jul 2017, 06:54
by psi29a
We had static libs on the PPA for those interested, but it never got much use so I disabled it. You can still build OpenMW that way if you wish, it just hasn't been tested in years.