New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not able to compile under Arch Linux #13
Comments
The issue seems to be related to the pyvips8 bindings, which are not enabled by the configure script on my system... could you try to refresh your repository and run the script again, and report wether it works for you? I've added --enable-pyvips8=no to the configure parameters, since Python bindings are anyhow not needed to compile photoflow. I've also included your suggestion of simply pulling the updated sources if the libvips directory already exists. |
Ok I think the Python bindings are not a problem anymore, but the build now fails with
But thanks for the quick response and fix! |
Oooops! It seems that your system is stricter than mine when linking the static vips library... I've explicitly added the GLib libraries to the linker command, which should fix the "undefined reference" issues. You'll need to pull the repository again. |
I did a git pull but there are still more compiling issues :( but thanks a lot for helping. If I can manage to compile it, I can create an package in the Arch Linux User Repository.
|
Uhmmm... then I would propose to take a different approach. This build_all.sh script was actually a "dirty" hack to help compiling both photoflow and VIPS from their git repositories, since generally the official VIPS development packages are too old in most of the distros. In order to do things properly, you need to:
This will create a photoflow executable: You might need to add "/usr/local/lib" to your LD_LIBRARY_PATH in order to find the custom VIPS libraries (that's why I've opted for static linking in the build_all.sh script...). If you could volunteer to create Arch packages I would be extremely glad! And I'll give you all the support I can to get the procedure running (we went through it for Ubuntu already, and now the packaging seems to run quite smoothly). |
This is "normal" (or at least "expected"): the module that opens raw files does not perform any post-processing, and the pixel data is still in bayer pattern format... this cannot (yet) be displayed correctly. You need to add a "RAW developer" layer above the "RAW loader" to process the RAW data (white balance, demosaicing, exposure compensation, color conversion, etc...). For that, you need to:
At this point, a new layer should be added and the RAW development configuration dialog should be opened automatically, and the preview should finally show your image. You will find a detailed tutorial about RAW image processing here: http://photoflowblog.blogspot.com/2014/09/tutorial-how-to-process-raw-image-in.html and another one here: http://photoflowblog.blogspot.com/2014/12/color-spot-raw-white-balance-mode-in.html The visualization of non-processed RAW files has definitely to be fixed, I agree... The advantage of having a separate tool for RAW development is that you can save your preferred settings as a preset, independently of the RAW file being actually processed. For that, you have to select the "RAW developer" layer and click on the "Save" button below the layers list. Then choose a meaningful file name with extension ".pfp": the current parameters of the "RAW develper" layer will be saved. Next time you will open a RAW file, instead of adding a "RAW developer" layer you could click on "Load" and choose the previously saved ".pfp" preset: this will create a "RAW developer" layer and set the parameters according to the values stored in the preset. |
Ok now I can see the image and it is looking great. I think this issue can be closed now. Just a last question: Btw. I like having the Raw Developer as a separate modul, maybe someday someone can build a preset which maked the images look like exported with the Nikon Software. Like with the colors as you described here. |
About your question: for an official package, I assume one has to install VIPS and PhotoFlow under /usr (and not /usr/local), so that there is no problem with paths. However, I do not really have experience with arch linux... Concerning the colors, I can try to "guide" you through the process I've followed to match the Nikon colors for my D300 camera. However, for that you'll need a windows machine for running ViewNX, as described here: http://50.87.144.65/~rt/w/index.php?title=How_to_get_Nikon_ICM_profiles_from_NX2. No IRC channel yet, I don't even know if I would have the time to follow that... |
I played arround with the color profiles and I really like it. The colors are exactly the same which is pretty nice. Now I can stop shooting Raw+Jpg because I get the same results just by adding a preset.
|
I personally still shoot RAW+Jpeg, simply because Jpegs are very handful for quick browsing... Concerning the crash, I'll modify the code so that wrong file names are properly handled and trigger a message dialog. |
I get this error: In file included from /home/user/build/photoflow/PhotoFlow/src/operations/raw_output.cc:47:0: I am on linux manjaro xfce. Can someone help me with this? |
The easiest solution is to make this warning not fatal... I'll make a patch for that as soon as possible. This part of code is directly inherited from darktable, and I prefer not to make modifications there that I would need to repeat every time I update the file from the darktable sources... |
This should be fixed in the next update of the master branch. I'll put a message here as soon as it will be available (probably in a couple of days). |
I've committed a fix to the master branch. Could you checkout the latest version and try to compile again? Let me know if the fix was enough. Thanks! |
After some tweaks, I got it working: |
Was this after the fix I've committed? Did you use the build_all.sh script in the "build" subdirectory? This script should in principle take care of building and installing VIPS locally, if a recent enough version is not available from your distribution... |
Yes, this was after you committed the fix. I used instructions you provided in a post on jan. 29.. |
Then I would say that the issue can be closed. Only one minor suggestion: since you are compiling and installing VIPS from sources, I would suggest you to give /usr/local ans the installation prefix, nit to mix it with the official packages. Then you need to set the PKG_CONFIG_PATH accordingly before compiling photoflow:
Hope this clarifies all your questions. |
The build script ./build_all.sh stopps with the error:
Is it right that the compile process wants to create a folder at /gi not at .../LIBVIPS_DIRECTORY/gi?
Also it would be good, to add a check to the build script, that checks if there is already the libvips repo, and if so just doing a git pull. When I tried to figure out what is wrong with the build script it always did the git clone again which took some time.
The text was updated successfully, but these errors were encountered: