I just took the Plunge and tried to compile darktable 2.3.0 from source on my Fedora 26 box. The build process apparently stopped when it encountered the following error:
/darktable/src/common/curve_tools.c:108:5: error: argument 1 range [18446744071562067968, 18446744073709551615] exceeds maximum object size 9223372036854775807 [-Werror=alloc-size-larger-than=]
x = (float *)calloc(n, sizeof(float));
Could somebody please provide me with a bit of guidance to get through this? Itās my first time trying to compile! Thanks in advance
Indeed, I want to push my luck to see if I can build 2.3.0 !
Iāve followed the directions as per the links provided but I think that Iām not doing something correctly when trying to install the jsonschema scriptā¦
pkg_resources.DistributionNotFound: The ājsonschema==2.5.1ā distribution was not found and is required by the application
make[2]: *** [data/CMakeFiles/validate_noiseprofiles_json.dir/build.make:59: data/CMakeFiles/validate_noiseprofiles_json] Error 1
The way that I had attempted this was by entering:
requires = ājsonschema==2.5.1ā
import sys
from pkg_resources import load_entry_point
if name == āmainā:
sys.exit(
load_entry_point(ājsonschema==2.5.1ā, āconsole_scriptsā, ājsonschemaā)()
)" | sudo tee /usr/local/bin/jsonschema
before entering:
sudo chmod +x /usr/local/bin/jsonschema
And, yes, I did manage to install all of the dependencies.
Solved the jsonschema issue: The script called for version 2.5.1 yet the current file is 2.6.0. After I had edited the script accordingly, the build finished
So now comes another question: How do I start this self-complied version rather than the one installed from the Fedora repositories? Can I have both on my system or must I get rid of the latter?
Iāve been googling but clearly, Iāve not been asking the right question. So, Iāll post it here (again):
Prior to compiling 2.3.0., I already had 2.2.5 installed from the Fedora repository. As I had expected (but not wanted), when I enter ādarktableā on the command line, the latter version fires up.
My question is: How can I run the self-compiled 2.3.0 version? Iām certain that this must be quite basic for many of you but, for me itās new and unfamiliar. Your help would be appreciated!
The git version, ie, v2.3, is in /opt/DarkTable/bin/DarkTable (if you followed the instruction)
So, in terminal, type
$ sudo /opt/DarkTable/bin/DarkTable
Thanks, everybody, for your help. After deleting the āsanctionedā version, I added /opt/darktable/bin/darktable to my path.
Since Iām curious but donāt wish to precariously remain only on the bleedinā edge, Iāll reinstall darktable from the repositories and then I plan to change the executable name in /opt/ā¦ to ādarktable23ā. Hopefully that will provide me with the best of both worlds!
Yes. Because I the current rpm is limited to version 2.2.5. I want to live precariously and see what I donāt know how to do with any new developments which are only available on the freshest git version!
Please be aware that you canāt share a darktable library between different versions. In theory it should gracefully fail (same with XMP files) and just not load the database, but be warned and make backups.
Thanks, Houz. At the back of my mind I had a feeling that perhaps I may be treading on thin ice. Your āIn theoryā qualifier concerns meā¦
Iāll only run the git versions on one machine. However, since my photo and xmp files reside on a server and thus are also accessed by my production machine, should I be worried about the sidecars being ācontaminatedā or at worst, ādamagedā if opened with the not-ready-for-prime-time version of darktable?
Yes, you should. If the production system uses 2.2.0 or newer then there shouldnāt be any loss of data or corruption, but once the development build touched the picture and wrote the XMP it might have included data that the old dt doesnāt understand and will therefore refuse to load.
That he linked to an alternative rpm repository which has up2date rpms for fedora and opensuse for darktable master branch. they are actually rebuild for every git push.